public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifixinc.com>
To: Omer Shenker <mail@omershenker.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Proposal: fine-grained control over -Werror
Date: Wed, 10 Mar 2004 01:52:00 -0000	[thread overview]
Message-ID: <404E74C8.1010604@specifixinc.com> (raw)
In-Reply-To: <404C8460.2050802@omershenker.net>

Omer Shenker wrote:
> I propose that for each warning -Wfoo, GCC should also accept 
> -Wfoo=error and -Wfoo=warn.

Some of the warnings already use the = form, e.g. -Wformat=2.  So there 
is a conflict here.

It is unlikely that anything will happen unless you volunteer a patch.

It is probably a lot of work to go through and identify everyplace where 
a warning is used and then add an optional error check.  Probably not 
feasible unless the warning flags are redesigned a bit, which would be 
even more work.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

      reply	other threads:[~2004-03-10  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 14:34 Omer Shenker
2004-03-10  1:52 ` Jim Wilson [this message]

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=404E74C8.1010604@specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mail@omershenker.net \
    /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).