This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: C++ vs. AIX -ansi
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: C++ vs. AIX -ansi
- From: Nathan Sidwell <nathan at codesourcery dot com>
- Date: Wed, 07 Feb 2001 09:51:26 +0000
- CC: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Organization: Codesourcery LLC
- References: <200102061923.OAA35594@mal-ach.watson.ibm.com>
David Edelsohn wrote:
> Actually, my suggestions were either:
>
> 1) separate CPP_SPEC for C and C++
Yes, I meant 'via the spec' - i'd forgotten that that would mean separate
cpp specs for c & c++.
> I specifically *do not* want to add more defines to the
> preprocessor command line. That is the incorrect assumption which is
> causing these problems.
I 100% agree.
Mark wrote:
> Another approach would simply be not to use -ansi in the testsuite
> when running `make check-g++'. That might be simplest, in the short
> term. Then, everyone could run tests, and it actually makes sense to
> test the default options most heavily. Then, if users want to use
> -ansi, they may find it doesn't work some places -- but they can
> always fall back to *not* using -ansi.
No no no no no :-)
if g++ 3.0 has the behaviour that `g++ -ansi -pedantic' is incompatible
with something like
#include <stdlib.h>
#include <vector> // whatever
it's *broken*.
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org