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: "pinskia at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Jan 2007 23:37:53 -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 #4 from pinskia at gmail dot com 2007-01-01 23:37 -------
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.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30348