public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: benoit.sibaud@rd.francetelecom.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/8891: Unexplicit error message about naming conflict
Date: Tue, 10 Dec 2002 06:36:00 -0000	[thread overview]
Message-ID: <20021210143313.12912.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]


>Number:         8891
>Category:       c++
>Synopsis:       Unexplicit error message about naming conflict
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 10 06:36:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Benoît Sibaud
>Release:        gcc-3.2.1
>Organization:
>Environment:
Debian Sarge i686-pc-linux-gnu
>Description:
class Foo
{
protected:
    enum {BadName, A, B, C};
};
class BadName : public Foo
{
};
class Toto : public Foo
{
 public:
    Foo* fct() { return new BadName; }
};

$ g++ -Wall foo.cpp
foo.cpp: In member function `Foo* Toto::fct()':
foo.cpp:18: parse error before `;' token
foo.cpp:18: warning: no return statement in function returning non-void

Conflict between ::BadName and BadName in Foo enum. The error message is not really helpful (the enum was deeply hidden in a class hierarchy in my case).
Tested with several 2.95.2, 3.0.x, 3.1.x and 3.2.x versions.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2002-12-10 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  6:36 benoit.sibaud [this message]
2002-12-10  6:55 bangerth

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=20021210143313.12912.qmail@sources.redhat.com \
    --to=benoit.sibaud@rd.francetelecom.com \
    --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).