public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: georgeh@aya.yale.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/9791: -Woverloaded-virtual reports hiding of destructor
Date: Fri, 21 Feb 2003 18:06:00 -0000	[thread overview]
Message-ID: <20030221180549.30803.qmail@sources.redhat.com> (raw)


>Number:         9791
>Category:       c++
>Synopsis:       -Woverloaded-virtual reports hiding of destructor
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 21 18:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     George Heintzelman
>Release:        gcc-3.2.2
>Organization:
>Environment:
Solaris 8
>Description:
class Base {
public:
  virtual ~Base() { 
  }
};

class Derived: public Base {
public:
  int Base() { 
    return 5;
  }
};

int main() {
}

When compiled with -Woverloaded-virtual, this file produces:
../gcc-3.2.2/bin/g++ test-hiding.C -save-temps -Wall -Woverloaded-virtual
test-hiding.C:3: warning: `virtual Base::~Base()' was hidden
test-hiding.C:9: warning:   by `int Derived::Base()'

which is certainly not accurate. It is true that int Derived::Base() is hiding the name of the base class inside the class, but this is not the kind of name-hiding that (I think) the warning was intended to guard against; nor is it name-hiding that is likely to lead to an error. I think -Woverloaded-virtual should not give a warning in this case.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-02-21 18:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030221180549.30803.qmail@sources.redhat.com \
    --to=georgeh@aya.yale.edu \
    --cc=gcc-gnats@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).