This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/30348] '#define false FALSE' undefines '#define FALSE false'
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Jan 2007 12:02:19 -0000
- Subject: [Bug c++/30348] '#define false FALSE' undefines '#define FALSE false'
- References: <bug-30348-11590@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from gdr at integrable-solutions dot net 2007-01-02 12:02 -------
Subject: Re: New: '#define false FALSE' undefines '#define FALSE false'
"h8_spam at sonic dot net" <gcc-bugzilla@gcc.gnu.org> writes:
| I ran into an issue where doing #define FALSE false followed by #define false
| FALSE undefined the first FALSE which is not what I would expect.
|
| Perhaps this is part of the standard, but in case not, I'm reporting it.
During the translation phases 3-6, `true' and `false' are pp-tokens
with special meanings. See 16.1/4.
I don't know how common this PR is, to warrant a warning.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30348