public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55813] New: Poorly named/documented option Wctor-dtor-privacy
Date: Wed, 26 Dec 2012 15:05:00 -0000	[thread overview]
Message-ID: <bug-55813-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55813
           Summary: Poorly named/documented option Wctor-dtor-privacy
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: harald@gigawatt.nl


The -Wctor-dtor-privacy option is documented as

`-Wctor-dtor-privacy (C++ only)'
     Warn when a class seems unusable, because all the constructors or
     destructors in a class are private and the class has no friends or
     public static member functions.

However, the option warns for more than just that:

class A { // warning: all member functions in class 'A' are private
    void f();
};

class B { // no warning
    void f() {}
public:
    B() {}
};

The documentation does not explain why a warning for A is issued, nor does it
explain why A is treated differently from B. The option's name suggests that no
warning should be generated for either of them, but I cannot tell what the
actual intended behaviour is, only that gcc has behaved this way since before
3.x.


             reply	other threads:[~2012-12-26 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 15:05 harald at gigawatt dot nl [this message]
2013-02-27 18:44 ` [Bug c++/55813] " paolo.carlini at oracle dot com
2013-02-28 10:01 ` paolo at gcc dot gnu.org
2013-02-28 10:03 ` paolo.carlini at oracle dot com

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-55813-4@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).