public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16168] -Weffc++ item 14 improvements
Date: Mon, 28 Jun 2004 19:33:00 -0000 [thread overview]
Message-ID: <20040628192952.15272.qmail@sourceware.org> (raw)
In-Reply-To: <20040624021703.16168.bkoz@gcc.gnu.org>
------- Additional Comments From bangerth at dealii dot org 2004-06-28 19:29 -------
Here's a testcase:
------------
struct A {
~A ();
};
struct B : public A {};
------------
g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -Weffc++ -c x.cc
x.cc:5: warning: base class `struct A' has a non-virtual destructor
I'm not really sure whether we want to avoid the error message here,
but I guess it makes sense if there are no virtual functions.
W.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2004-06-28 19:29:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16168
next prev parent reply other threads:[~2004-06-28 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 2:21 [Bug c++/16168] New: " bkoz at gcc dot gnu dot org
2004-06-28 19:33 ` bangerth at dealii dot org [this message]
2004-06-28 20:16 ` [Bug c++/16168] " Gabriel Dos Reis
2004-06-28 20:14 ` gdr at acm dot org
2004-06-28 20:51 ` bangerth at dealii dot org
2005-03-29 1:49 ` pinskia at gcc dot gnu dot org
[not found] <bug-16168-4@http.gcc.gnu.org/bugzilla/>
2012-01-05 15:56 ` f-roth at megaera dot de
2012-01-05 17:04 ` redi at gcc dot gnu.org
2014-01-10 15:34 ` gcc-oren@ben-kiki.org
2014-01-10 15:59 ` redi at gcc dot gnu.org
2014-01-10 16:11 ` oren@ben-kiki.org
2014-01-10 16:34 ` redi at gcc dot gnu.org
2014-01-10 16:55 ` gcc-oren@ben-kiki.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=20040628192952.15272.qmail@sourceware.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).