This is the mail archive of the
mailing list for the GCC project.
Re: Warnings in the C++ Front-End and GCC in General
- To: amylaar at cygnus dot co dot uk (Joern Rennecke)
- Subject: Re: Warnings in the C++ Front-End and GCC in General
- From: Joe Buck <jbuck at Synopsys dot COM>
- Date: Wed, 9 Sep 98 9:21:55 PDT
- Cc: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de, mark at markmitchell dot com, egcs-patches at cygnus dot com, egcs at cygnus dot com, jason at cygnus dot com
> > First of all, thank you very much, Mark! I really like the idea of
> > turning warnings on and off from inside the source files; and I agree,
> > using #pragma is the way to go!
> When this principle is applied to system include files, this could well
> lead to a fixunclude orgy. We should keep in mind that there is a point
> where it is better to simply supress some warnings in system header files,
> rather than trying to add gcc-specific #pragmas to every header file.
My concern is that once we have a mechanism to suppress warnings in system
header files, the quality of glibc and libstdc++ will start to degrade ...
it will be too easy to just turn off warnings rather than to code things
correctly (and if avoiding a warning makes your code worse, the warning
is poorly designed or implemented).