public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/17314] Error message wrongly shows declared rather than inherited access Date: Thu, 16 May 2013 12:49:00 -0000 [thread overview] Message-ID: <bug-17314-4-9czufgPGKf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-17314-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17314 Paolo Carlini <paolo.carlini at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|gcc-bugs at gcc dot gnu.org | --- Comment #13 from Paolo Carlini <paolo.carlini at oracle dot com> --- I may be missing details, but I'm not sure we have a serious problem here. Note that: class A { public: A(){} }; class B : virtual A { }; class C : public B {}; int main () { C c; } is fine. Thus, to be clear, isn't that the "declared access" doesn't matter. The real issue seems that the complete rules of protected access are complex and hard to, so to speak, summarize in the error message. Gaby?
next parent reply other threads:[~2013-05-16 12:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17314-4@http.gcc.gnu.org/bugzilla/> 2013-05-16 12:49 ` paolo.carlini at oracle dot com [this message] 2013-05-16 13:00 ` paolo.carlini at oracle dot com 2013-05-16 14:07 ` jason at gcc dot gnu.org 2013-05-16 14:52 ` paolo.carlini at oracle dot com 2013-05-16 20:09 ` jason at gcc dot gnu.org 2013-05-16 23:49 ` paolo.carlini at oracle dot com 2013-11-07 10:36 ` paolo.carlini at oracle dot com 2020-04-10 15:22 ` ich.freak at gmx dot net 2020-12-29 0:14 ` anthonysharp15 at gmail dot com 2021-01-06 13:11 ` anthonysharp15 at gmail dot com 2021-01-06 23:26 ` igodard at pacbell dot net 2021-01-07 0:57 ` anthonysharp15 at gmail dot com 2021-01-29 12:34 ` anthonysharp15 at gmail dot com 2021-01-29 13:03 ` redi at gcc dot gnu.org [not found] <bug-17314-6594@http.gcc.gnu.org/bugzilla/> 2006-03-21 2:48 ` jason at gcc dot gnu dot 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-17314-4-9czufgPGKf@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).