This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Still a lot of C++ files getting "fixed"
- To: pedwards at jaj dot com
- Subject: Re: Still a lot of C++ files getting "fixed"
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Tue, 25 Jan 2000 12:53:31 -0800
- Cc: gcc-bugs at gcc dot gnu dot org, austern at sgi dot com, autogen at linuxbox dot com
- Organization: CodeSourcery, LLC
- References: <200001252027.PAA21194@jaj.com>
>>>>> "Phil" == Phil Edwards <pedwards@jaj.com> writes:
>> True. But, -ansi is specifically documented to be
>> pedantically ANSI; that's its whole purpose in life.
Phil> Very true.
Phil> Since the C99 standard now specifies the same results as
Phil> C++98, wouldn't "pedantically ANSI" now /require/ the new
Phil> behavior?
Well, that's a question about what ANSI means. I think we're going to
have modes for "GNU C", pedantically ANSI/ISO C89, pedantically
ANSI/ISO C99, etc. Probably, we'll have way more modes than we
should. :-) (One risk with open source software is that people tend to
add whatever features are convenient for them at the moment -- and
that can lead to a maintenance nightmare, an overly complex user
interface, etc.)
Kaveh's point that we can perhaps treat system headers differently
from user source is well-taken; I suppose it might make sense to
accept `//' comments only in system headers, under the assumption that
nowhere does there a lie a system header where this will change the
semantics of the of the program.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com