public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbeulich at novell dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/12620] New: compatibility issue with anonymous struct/union support Date: Wed, 15 Oct 2003 12:03:00 -0000 [thread overview] Message-ID: <20031015120301.12620.jbeulich@novell.com> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12620 Summary: compatibility issue with anonymous struct/union support Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jbeulich at novell dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu In class ccc { public: union { int i; }; }; all other compilers I can check with (Intel, Microsoft, Borland, MetroWerks) treat i as a member of ccc. Since the feature is documented to exist for compatibility reasons, the behavior should be compatible, too. This can easily be tested with above declaration and the code template<typename T> void test(T p); void test() { test(&ccc::i); } by observing what template instantiation is selected by the compiler.
next reply other threads:[~2003-10-15 12:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-15 12:03 jbeulich at novell dot com [this message] 2003-10-15 12:23 ` [Bug c++/12620] " jbeulich at novell dot com 2003-10-15 12:25 ` jbeulich at novell dot com 2003-10-15 17:52 ` pinskia at gcc dot gnu dot org 2003-10-16 7:46 ` jbeulich at novell dot com 2003-11-28 21:39 ` pinskia 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=20031015120301.12620.jbeulich@novell.com \ --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).