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:08:32 -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 #8 from gdr at integrable-solutions dot net 2007-01-02 12:08 -------
Subject: Re: '#define false FALSE' undefines '#define FALSE false'
"pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| Subject: Re: '#define false FALSE' undefines '#define FALSE
| false'
|
| On Mon, 2007-01-01 at 22:43 +0000, h8_spam at sonic dot net wrote:
| > Right, but since true and false are keywords, I would expect the
| > #define true
| > TRUE and false FALSE to be no-ops.
|
|
| How? Preprocessing happens before tokenazation happens.
Right; however `true' and `false' are also pp-tokens with special meanings
during pre-processing.
Therefore I think the PR is invalid, but you have to double-check that
with a CPP expert.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30348