public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andrew dot stubbs at st dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32053] New: Anonymous union members' names should be distinct within enclosing scope Date: Wed, 23 May 2007 09:05:00 -0000 [thread overview] Message-ID: <bug-32053-10252@http.gcc.gnu.org/bugzilla/> (raw) The following program should not compile: extern int foo; static union { int foo; // clash }; C++ standard clause 9.5/2 states that members of anonymous unions must have names distinct from other names in the same scope. If the `extern' keyword is removed from the example above, the error is diagnosed correctly (followed by an ICE). -- Summary: Anonymous union members' names should be distinct within enclosing scope Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: andrew dot stubbs at st dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32053
next reply other threads:[~2007-05-23 9:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-23 9:05 andrew dot stubbs at st dot com [this message] 2007-10-31 16:15 ` [Bug c++/32053] " andrew dot stubbs at st dot com 2009-12-26 14:32 ` paolo dot carlini at oracle dot com
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-32053-10252@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).