public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65520] New: elaborated-type-specifiers and inaccessible injected-class-names Date: Mon, 23 Mar 2015 05:23:00 -0000 [thread overview] Message-ID: <bug-65520-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65520 Bug ID: 65520 Summary: elaborated-type-specifiers and inaccessible injected-class-names Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: rs2740 at gmail dot com Repro: struct A {}; struct B : private A {}; struct C : public B { struct A m_a; // error: A is the inaccessible injected-class-name }; Per [basic.lookup.elab]/p2, the elaborated-type-specifier `struct A` should cause an unqualified name lookup for `A`, and per [basic.lookup.unqual]/p7 the name is first searched in C and its base classes, which should find the inaccessible injected-class-name, rendering the code ill-formed. Instead, GCC accepts this code. It is rejected by all versions of Clang I tested (3.0 and later).
next reply other threads:[~2015-03-23 3:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-23 5:23 rs2740 at gmail dot com [this message] 2015-03-23 10:07 ` [Bug c++/65520] " redi at gcc dot gnu.org 2022-08-09 2:12 ` pinskia at gcc dot gnu.org 2022-08-09 2:13 ` pinskia 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-65520-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).