From: Nathan Myers <ncm@cygnus.com>
To: egcs@cygnus.com
Subject: Re: Desire gcc option to skip warnings in standard headers
Date: Wed, 01 Jul 1998 20:15:00 -0000 [thread overview]
Message-ID: <359AB0B8.3590109D@cygnus.com> (raw)
In-Reply-To: <9806261352.AA18188.cygnus.egcs@ipl.rpi.edu>
Frederick W. Wheeler wrote:
>
> 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.
Note that not all warnings are undesirable even from very bad headers.
In particular, a warning that a macro is being redefined helps protect
you when non-system-header code defines a macro that is (re)defined in
a system header. System headers don't tend to do this to themselves,
so emitting the warning anyway would usually be a Good Thing.
Nathan Myers
ncm@cantrip.org
next parent reply other threads:[~1998-07-01 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9806261352.AA18188.cygnus.egcs@ipl.rpi.edu>
1998-07-01 20:15 ` Nathan Myers [this message]
1998-07-04 12:40 ` Joseph H. Buehler
1998-06-26 13:03 Frederick W. Wheeler
1998-06-29 8:41 ` Branko Cibej
1998-06-29 8:41 ` Carlo Wood
1998-06-29 8:41 ` Branko Cibej
1998-06-29 20:41 ` Carlo Wood
1998-06-30 0:00 ` Jeffrey A Law
1998-06-30 9:03 ` Andi Kleen
1998-07-01 0:54 ` Carlo Wood
1998-06-30 23:15 ` Mumit Khan
1998-07-01 20:15 ` Raja R Harinath
1998-06-30 0:42 ` Branko Cibej
1998-06-30 0:42 ` Jeffrey A Law
1998-06-30 9:03 ` Branko Cibej
1998-06-29 9:38 ` Branko Cibej
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=359AB0B8.3590109D@cygnus.com \
--to=ncm@cygnus.com \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).