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: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Still a lot of C++ files getting "fixed"
- From: Zack Weinberg <zack at wolery dot cumb dot org>
- Date: Tue, 25 Jan 2000 17:16:32 -0800
- Cc: austern at isolde dot engr dot sgi dot com, austern at sgi dot com, mark at codesourcery dot com, autogen at linuxbox dot com, gcc-bugs at gcc dot gnu dot org
- References: <200001252028.PAA15401@caip.rutgers.edu>
On Tue, Jan 25, 2000 at 03:28:36PM -0500, Kaveh R. Ghazi wrote:
> > From: Mark Mitchell <mark@codesourcery.com>
> >
> > Matt> I tend to think that anyone who puts this kind of garbage in
> > Matt> a header deserves what they get, of course.
> >
> > True. But, -ansi is specifically documented to be pedantically ANSI;
> > that's its whole purpose in life. So, either we should can it, or
> > make sure it does what it's there fore.
>
> I think there is a middle ground. We certainly kill lots of
> diagnostics in system headers already because there is nothing a
> *user* can do when they get a message about a header file.
>
> So it is not a great leap to do the same for -ansi. It can be
> pedantically ANSI for user code, and more relaxed about system
> headers, IMHO.
If we're going to go down this road, we might consider also disabling
pedantic complaints about a token after #else/#endif in the system headers.
On SunOS, at least half the files modified have only that change.
zw