This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Desire gcc option to skip warnings in standard headers
- To: egcs at cygnus dot com
- Subject: Re: Desire gcc option to skip warnings in standard headers
- From: jhpb at sarto dot gaithersburg dot md dot us (Joseph H. Buehler)
- Date: 04 Jul 1998 12:37:21 -0400
- Newsgroups: local.egcs
- Organization: /usr/lib/news/organization
- References: <9806261352.AA18188.cygnus.egcs@ipl.rpi.edu> <359AB0B8.3590109D@cygnus.com>
> It would be very convenient for me to have a gcc command-line option
> or #pragma to prevent the printing of warnings in the standard
> headers. Warnings could begin to be issued at the first line that is
> not #include <something.h>. It seems to me that this would be
> relatively easy to implement.
If this gets implemented in gcc, I suggest a better way to define
"system header" than "presence of #include<> syntax".
Where I work, we *never* use
#include "whatever.h"
because developers compile their files against a shared nightly build
area. Consider having a .c file in the shared area and a .h file
being edited in your private work area. Some vendors' compilers, when
compiling the .c file, will *always* look for the .h in the directory
containing the .c file: there is no way to override this.
So we always use the <> syntax so we have complete control over the
include file path.
Joe Buehler