public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gpderetta at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/68161] New: Inconsistent behaviour of unnamed field with inheritance. Date: Fri, 30 Oct 2015 15:19:00 -0000 [thread overview] Message-ID: <bug-68161-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68161 Bug ID: 68161 Summary: Inconsistent behaviour of unnamed field with inheritance. Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gpderetta at gmail dot com Target Milestone: --- As an extension to C++, g++ allows the following: struct B { struct { int bar; }; }; int main() { B foo; (void)foo.bar; // ok } The following does not work though: struct A { int bar; }; struct B { struct : A {}; }; int main() { B foo; (void)foo.bar; // error: 'struct B' has no member named 'bar' } As unnamed struct fields are an extension, this is not really a bug as g++ can do whatever it wants, but it does seems inconsistent. The expected behaviour is useful to inject arbitrary names as members.
next reply other threads:[~2015-10-30 15:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-30 15:19 gpderetta at gmail dot com [this message] 2021-12-09 4:38 ` [Bug c++/68161] " 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-68161-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).