public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fonseca@mip.sdu.dk
To: gcc-gnats@gcc.gnu.org
Subject: c++/3816: namespace and anonymous struct identifier conflict
Date: Wed, 25 Jul 2001 09:46:00 -0000	[thread overview]
Message-ID: <20010725164519.10560.qmail@sourceware.cygnus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

>Number:         3816
>Category:       c++
>Synopsis:       namespace and anonymous struct identifier conflict
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 25 09:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     René Fonseca
>Release:        gcc-3.0 and gcc-2.95-3 and more
>Organization:
>Environment:
GNU/Linux (RedHat 7.1), Windows 2000 (Cygwin), and Solaris 8.
>Description:
GCC fails to compile a valid typedef of an anonymous struct when the name of the typedef is identical to a namespace in an outer scope.

See the code below to reproduce the problem. The line resulting in the error has been marked with "// conflict with A namespace!!!".
>How-To-Repeat:
Here is some code that illustrates the problem:

namespace A {};

namespace OtherNamespace {

  typedef struct {
    int member;
  } A; // conflict with A namespace!!!

}; // end of namespace

int main() {
  return 0;
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-25  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  9:46 fonseca [this message]
2001-08-13  6:49 gdr
2003-01-03 12:50 neroden

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=20010725164519.10560.qmail@sourceware.cygnus.com \
    --to=fonseca@mip.sdu.dk \
    --cc=gcc-gnats@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: link
Be 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).