public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: benoit.sibaud@rd.francetelecom.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/8891: Unexplicit error message about naming conflict Date: Tue, 10 Dec 2002 06:55:00 -0000 [thread overview] Message-ID: <20021210145510.28312.qmail@sources.redhat.com> (raw) Synopsis: Unexplicit error message about naming conflict State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Tue Dec 10 06:55:08 2002 State-Changed-Why: I don't know what to do with this report, since the message is probably the best you can get. In any case, there is no _naming conflict_: declaring an enum member and a class with the same name is just fine, it's only when you access that you have to make clear what you want: by default, lookup happens _within_ the class, so you get the enum name, which of course does not go well with the "operator new". If you want the class name, you have to specify that: Foo* fct() { return new ::BadName; } This compiles just fine. So what you request is that upon seeing the bogus new enum-value; line, the compiler looks up whether somewhere, outside of its usual search area, there is class name with the same name as that enum value. I think this is asking for too much. Maybe someone of the C++ front end guys can comment on what we should do with this request. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8891
next reply other threads:[~2002-12-10 14:55 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 6:55 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-10 6:36 benoit.sibaud
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=20021210145510.28312.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=benoit.sibaud@rd.francetelecom.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).