public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60994] gcc does not recognize hidden/shadowed enumeration as valid nested-name-specifier
Date: Tue, 29 Apr 2014 07:56:00 -0000 [thread overview]
Message-ID: <bug-60994-4-dKP9fo860L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60994-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60994
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|RESOLVED |NEW
Last reconfirmed| |2014-04-29
Resolution|INVALID |---
Ever confirmed|0 |1
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Momchil Velikov from comment #0)
> According to the C++11 Standard, [basic.lookup.qual] #1
>
> "If a :: scope resolution operator in a nested-name-specifier is not
> preceded by a decltype-specifier, lookup of the name preceding that ::
> considers only namespaces, types, and templates whose specializations are
> types."
Confirmed. C++03 said "During the lookup for a name preceding the :: scope
resolution operator, object, function, and enumerator names are ignored."
next prev parent reply other threads:[~2014-04-29 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 7:00 [Bug c++/60994] New: " momchil.velikov at gmail dot com
2014-04-29 7:07 ` [Bug c++/60994] " trippels at gcc dot gnu.org
2014-04-29 7:56 ` redi at gcc dot gnu.org [this message]
2014-04-29 9:59 ` momchil.velikov at gmail dot com
2014-08-28 19:02 ` aaw at gcc dot gnu.org
2015-02-12 13:49 ` redi at gcc dot gnu.org
2015-02-12 13:53 ` jakub at gcc dot gnu.org
2015-02-12 14:28 ` momchil.velikov at gmail dot com
2015-04-14 15:30 ` jason at gcc dot gnu.org
2021-08-04 21:03 ` pinskia at gcc dot gnu.org
2021-08-04 21:04 ` pinskia at gcc dot gnu.org
2023-12-02 11:16 ` cvs-commit at gcc dot gnu.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=bug-60994-4-dKP9fo860L@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).