mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: davem@redhat.com, linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: [PATCH] warnkill trivia 2/2
Date: Sun, 1 Sep 2002 16:56:59 +0200	[thread overview]
Message-ID: <20020901145658.GD7325@louise.pinerecords.com> (raw)
In-Reply-To: <200209011452.QAA17260@harpo.it.uu.se>

> >i.e. it's impossible to have a constant
> >pointer to a non-constant value w/o using a qualified
> >typedef.
> 
> void g(int * const t) { *t = 0; }
>
>
> >W/o a typedef, gcc seems unable to tell the difference
> >between 'const int *' and 'int const *' altogether.
> 
> There is no difference. Read the C spec, or Harbison&Steele
> which has had an explanation of 'const' since their '87 2nd Ed.


Ok, that explains it, obviously I (and DaveM :D) didn't know the syntax.
Thanks for the reference!

I'm going to redo the patches.

T.

  reply	other threads:[~2002-09-01 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01 14:52 Mikael Pettersson
2002-09-01 14:56 ` Tomas Szepe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-01 10:56 Tomas Szepe
2002-09-01 10:57 ` David S. Miller
2002-09-01 11:28   ` Tomas Szepe
2002-09-01 11:25     ` David S. Miller
2002-09-01 11:37       ` Tomas Szepe
2002-09-01 11:35         ` David S. Miller
2002-09-01 12:10           ` Tomas Szepe
2002-09-01 12:16             ` David S. Miller
2002-09-01 12:39               ` Tomas Szepe
2002-09-01 21:57                 ` Bruce Guenter
2002-09-02 22:24     ` Jan Hudec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020901145658.GD7325@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mikpe@csd.uu.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome