Still a lot of C++ files getting "fixed"
Zack Weinberg
zack@wolery.cumb.org
Tue Jan 25 17:17:00 GMT 2000
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
More information about the Gcc-bugs
mailing list