This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: iso646 and 'and'
- To: Benjamin Kosnik <bkoz at cygnus dot com>
- Subject: Re: iso646 and 'and'
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Date: 22 Jul 2000 10:02:02 +0200
- Cc: gcc-bugs at gcc dot gnu dot org, zack at wolery dot cumb dot org
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <200007220114.SAA18562@purist.soma.redhat.com>
Benjamin Kosnik <bkoz@cygnus.com> writes:
| libstdc++-v3 has a testfile that looks at ciso646 conformance.
|
| This code:
|
| #ifdef and
| test = false;
| #endif
|
| previously did not cause any problems. Now:
|
| warning: #ifdef with invalid argument
|
| What's the deal? How come things like 'and' give warnings but stuff
| like 'int' (also a keyword) don't give me a problem?
|
| -benjamin
|
| here's the testfile:
|
|
|
| // 2.11 Keywords
| // alternative representations
| // and, and_eq, bitand, bitor, compl, not, not_eq, or, or_eq, xor, xor_eq
There are not keyword but digraphs, thus invalid operands of #ifdef or
#define.
-- Gaby