public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fang at csl dot cornell dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/36709] Compiler allows namespace and class to have same name and doesn't generate ambiguous reference error when it should result from this. Date: Thu, 31 Jul 2008 07:21:00 -0000 [thread overview] Message-ID: <20080731071939.18547.qmail@sourceware.org> (raw) In-Reply-To: <bug-36709-16409@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from fang at csl dot cornell dot edu 2008-07-31 07:19 ------- Dupe of PR 30734 (first reported as PR 2708). -- fang at csl dot cornell dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fang at csl dot cornell dot | |edu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36709
next prev parent reply other threads:[~2008-07-31 7:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-07-03 2:03 [Bug c++/36709] New: " rquabili at princeton dot edu 2008-07-31 7:21 ` fang at csl dot cornell dot edu [this message] 2008-07-31 8:40 ` [Bug c++/36709] " 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=20080731071939.18547.qmail@sourceware.org \ --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).