public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16166] -Weffc++ finer granularity
Date: Tue, 29 May 2012 10:03:00 -0000	[thread overview]
Message-ID: <bug-16166-4-LCUAsi0KPE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-16166-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16166

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-05-29 09:58:08 UTC ---
(In reply to comment #4)
> I would recommend against naming each warning -Weffc++[n], but rather, give a
> more descriptive name. My suggestion is to create a few warnings, so that
> -Weffc++ would map to the following set of warnings (with their current
> description for reference and my suggested name):
> 

David, if you wish to implement such a patch (or, even better, series of
patches, one for each new option), the only changes needed are:

* In the particular warning () calls, replace OPT_Weffc__ with the appropriate
OPT_W option.

* In c-family/c.opt, add a new entry for the new Wfoo option and use
EnabledBy(Weffc++)

* In doc/invoke.texi, document the new options.

* Bootstrap+regression test and submit to gcc-patches.

Profit!


  parent reply	other threads:[~2012-05-29  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16166-4@http.gcc.gnu.org/bugzilla/>
2011-11-07 16:14 ` redi at gcc dot gnu.org
2012-05-29  2:39 ` david at doublewise dot net
2012-05-29  9:07 ` redi at gcc dot gnu.org
2012-05-29 10:03 ` manu at gcc dot gnu.org [this message]
2012-05-29 21:01 ` david at doublewise dot net
2012-05-29 23:34 ` redi at gcc dot gnu.org
2014-04-27 12:19 ` redi at gcc dot gnu.org
2004-06-23 22:45 [Bug c++/16166] New: " bkoz at gcc dot gnu dot org
2004-06-24  2:09 ` [Bug c++/16166] " bkoz at gcc dot gnu dot org
2004-06-28 19:52 ` bkoz at gcc dot gnu dot org
2004-07-31 12:16 ` lerdsuwa at gcc dot gnu dot org
2005-01-29  3:19 ` pinskia at gcc dot gnu dot org

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=bug-16166-4-LCUAsi0KPE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).