public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/68161] New: Inconsistent behaviour of unnamed field with inheritance.
@ 2015-10-30 15:19 gpderetta at gmail dot com
2021-12-09 4:38 ` [Bug c++/68161] " pinskia at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: gpderetta at gmail dot com @ 2015-10-30 15:19 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-09 4:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-30 15:19 [Bug c++/68161] New: Inconsistent behaviour of unnamed field with inheritance gpderetta at gmail dot com
2021-12-09 4:38 ` [Bug c++/68161] " pinskia at gcc dot gnu.org
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).