public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16166] New: -Weffc++ finer granularity
Date: Wed, 23 Jun 2004 22:45:00 -0000	[thread overview]
Message-ID: <20040623222604.16166.bkoz@gcc.gnu.org> (raw)

It would be nice to be able to warn for just a particular EFC++ warning, not all
at once.

For instance, to warn for item 11:

-Weffc++11 

or 

-Weffc++=11

or whatever.

See:
http://gcc.gnu.org/ml/libstdc++/2004-04/msg00067.html
-benjamin

-- 
           Summary: -Weffc++ finer granularity
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bkoz at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2004-06-23 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 22:45 bkoz at gcc dot gnu dot org [this message]
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=20040623222604.16166.bkoz@gcc.gnu.org \
    --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).