public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Branko Cibej <branko.cibej@hermes.si>
Cc: Carlo Wood <carlo@runaway.xs4all.nl>,
	"egcs@cygnus.com" <egcs@cygnus.com>
Subject: Re: Desire gcc option to skip warnings in standard headers
Date: Tue, 30 Jun 1998 00:42:00 -0000	[thread overview]
Message-ID: <15746.899189654@hurl.cygnus.com> (raw)
In-Reply-To: <3597B270.EC811EB4@hermes.si>

  In message < 3597B270.EC811EB4@hermes.si >you write:
  > Carlo Wood wrote:
  > 
  > > | Comments, anybody? Is this the right way to do it?
  > >
  > > I don't like this, I think the new option should turn
  > > warning off if used, but by default give warnings for
  > > system headers too.
  > 
  > That's trivial to do, of course -- most probably I should just invert the
  > meaning of the option. What about the name of the option, though? I don't like
  > -W(no-)system-headers, even though I thought it up myself...
Warnings should be enabled by -W<foo> and disabled by -Wno-<foo>.  I'm
not aware of any that do not follow that convention and I don't think we
should start making any now :-)

The default behavior can either be on or off, that's separate from 
making -W<foo> and -Wno-<foo> do the right thing.

jeff

  parent reply	other threads:[~1998-06-30  0:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
1998-06-30  9:03         ` Branko Cibej
1998-06-29  9:38   ` Branko Cibej
     [not found] <9806261352.AA18188.cygnus.egcs@ipl.rpi.edu>
1998-07-01 20:15 ` Nathan Myers
1998-07-04 12:40   ` Joseph H. Buehler

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=15746.899189654@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=branko.cibej@hermes.si \
    --cc=carlo@runaway.xs4all.nl \
    --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).