public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "filip.roseen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60927] New: Ambiguity not caught when name introduced through using-directive conflicts with previously declared entity Date: Tue, 22 Apr 2014 21:31:00 -0000 [thread overview] Message-ID: <bug-60927-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60927 Bug ID: 60927 Summary: Ambiguity not caught when name introduced through using-directive conflicts with previously declared entity Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: filip.roseen at gmail dot com Created attachment 32656 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32656&action=edit testcase.cpp namespace N { namespace A { int x = 1; } } struct A { static int x; }; int main () { using namespace N; A::x = 123; } ---------------------------------------------------- `gcc` accepts the above even though there's an ambiguity between `N::A::x` and `A::x` when referenced as `A::x` in `main`. ------------------------------------------------------ [ note: `gcc` treats the `A::x` as referring to `N::A::x`. ] [ note: `clang` shows the correct behaviour and issues a diagnostic saying that `A::x` is ambiguous. ]
next reply other threads:[~2014-04-22 21:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-22 21:31 filip.roseen at gmail dot com [this message] 2014-04-22 22:27 ` [Bug c++/60927] " mbos at google dot com 2014-12-14 14:54 ` ville.voutilainen at gmail dot com
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-60927-4@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: 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).