This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: ISO standards macro are rejected by g++
- To: gdr at codesourcery dot com
- Subject: Re: ISO standards macro are rejected by g++
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Mon, 1 May 2000 15:08:30 +0200
- Cc: egcs-bugs at egcs dot cygnus dot com
- Organization: Ecole Normale Superieure (quatramaran)
- References: <3905F82E.21525C6A@mandrakesoft.com> <20000425121856.N21810@wolery.cumb.org>
In article <flbt2yyn6i.fsf@sel.cmla.ens-cachan.fr> you write:
>Zack Weinberg <zack@wolery.cumb.org> writes:
>More generally, g++ does not (currently) reject some of GNU extenion
>identifiers beginning with __. I'm not sure what should be the right
>approach. For example I don't want g++ to complain about __complex__
>in the standard header <complex>. I guess one could complain
>conditionally according to some flags (for example testing
>in_system_header_p).
Normally, gnu extensions necessary for standard headers are flagged
with __extension__, which is explicitly designed to get pedantic to shut
up in that case.