This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/16192] Bug in expression evaluation when operand is missing
- From: "gnu at behdad dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Jun 2004 06:35:29 -0000
- Subject: [Bug preprocessor/16192] Bug in expression evaluation when operand is missing
- References: <20040625060108.16192.gnu@behdad.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gnu at behdad dot org 2004-06-25 06:35 -------
Would you please enlighten me why it's defined as one?
By the way, I still think there's a bug in gcc somewhere, either in
preprocessor, or in documentation. Because in the texinfo documentation I read:
* Identifiers that are not macros, which are all considered to be the
number zero.
Which immediately results that "(x < 2> && (y == 2)" should fail.
Moreover, I also read:
If EXPRESSION is not correctly formed, GCC issues an error and
treats the conditional as having failed.
Which again means that "(1 < 2) && ( == 2)" should fail.
To my not so humble opinion, these don't all make sense at the same time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16192