From: Linus Torvalds <torvalds@osdl.org>
To: Richard Henderson <rth@twiddle.net>
Cc: Thomas Schlichter <thomas.schlichter@web.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] fix warning about duplicate 'const'
Date: Wed, 10 Mar 2004 07:43:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0403100740120.1092@ppc970.osdl.org> (raw)
In-Reply-To: <20040310054918.GB4068@twiddle.net>
On Tue, 9 Mar 2004, Richard Henderson wrote:
>
> seems dicey at best. I'm not sure what to do about this, actually.
> We might could do something with a new __nonqual_typeof(a) that
> strips outermost type qualifications, but I havn't given that much
> thought.
Ok, let's try just stripping the "const" out of the min/max macros, and
see what complains. What the code _really_ wants to do is to just compare
two types for being basically equal, and in real life what Linux really
would prefer is to have "types" as first-class citizens and being able to
compare them directly instead of playing games. And we may end up having
that as a preprocessor phase (ie I might add it to the semantic parse
thing).
Linus
next prev parent reply other threads:[~2004-03-10 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 23:43 Thomas Schlichter
2004-03-09 0:14 ` Andrew Morton
2004-03-09 0:32 ` Linus Torvalds
2004-03-09 1:17 ` Thomas Schlichter
2004-03-09 1:32 ` Linus Torvalds
2004-03-09 1:35 ` Linus Torvalds
2004-03-10 4:08 ` Keith Duthie
[not found] ` <20040310054918.GB4068@twiddle.net>
2004-03-10 8:10 ` Gabriel Dos Reis
[not found] ` <20040310064001.GA7584@daikokuya.co.uk>
2004-03-10 10:15 ` Joseph S. Myers
2004-03-10 15:43 ` Linus Torvalds [this message]
2004-03-10 18:22 ` Richard Henderson
2004-03-10 18:29 ` Andrew Haley
2004-03-10 18:35 ` Paul Koning
2004-03-10 18:37 ` Richard Henderson
2004-03-16 1:46 ` Mike Stump
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=Pine.LNX.4.58.0403100740120.1092@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=thomas.schlichter@web.de \
/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
all inboxes | Powered by JetHome®