public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tkmt@sm.sony.co.jp To: gcc-gnats@gcc.gnu.org Subject: c++/5202: Elaborated type specifier doesn't work for a name in a namespace Date: Wed, 26 Dec 2001 22:26:00 -0000 [thread overview] Message-ID: <20011227061744.10406.qmail@sources.redhat.com> (raw) >Number: 5202 >Category: c++ >Synopsis: Elaborated type specifier doesn't work for a name in a namespace >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Dec 26 22:26:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: tkmt@sm.sony.co.jp >Release: gcc version 3.0.3 >Organization: >Environment: Linux 2.2.13-33 running on i686-pc >Description: Name look up problem. I believe `struct CLASS_NAME' can find a class name hidden by a function name. However, it doesn't work if CLASS_NAME is qualified with a namespace name. >How-To-Repeat: -- source ---------------------------------------------------------- namespace NS { struct stat { }; void stat() { } } struct NS::stat *x; -- result ---------------------------------------------------------- $ gcc -v -c structerr.cc Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/specs Configured with: ../gcc-3.0.3/configure Thread model: single gcc version 3.0.3 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=3 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__ -D__tune_pentiumpro__ structerr.cc -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase structerr.cc -version -o /tmp/ccQpoKyI.s GNU CPP version 3.0.3 (cpplib) (i386 Linux/ELF) GNU C++ version 3.0.3 (i686-pc-linux-gnu) compiled by GNU C version 3.0. ignoring nonexistent directory "/usr/local/i686-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include/g++-v3 /usr/local/include/g++-v3/i686-pc-linux-gnu /usr/local/include/g++-v3/backward /usr/local/include /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/include /usr/include End of search list. structerr.cc:9: `NS' does not have a nested type named `stat' >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-12-27 6:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-26 22:26 tkmt [this message] 2001-12-29 3:33 nathan 2003-01-11 23:13 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=20011227061744.10406.qmail@sources.redhat.com \ --to=tkmt@sm.sony.co.jp \ --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: 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).