public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/17628] New: Error message gives inadequate info (quality of implementation) Date: Thu, 23 Sep 2004 07:13:00 -0000 [thread overview] Message-ID: <20040923071303.17628.igodard@pacbell.net> (raw) This is a quality of oomplementation issue, not a correctness issue: class i; namespace n{int i;}; using n::i; int main() {return i;} gets you: ~/ootbc/members/src$ c++ foo.cc foo.cc:3: error: `i' is already declared in this scope Which is somewhat annoying when the conflicting declaration is buried in an include stack. The message should (as most such messages do) give the location of the conflicting declaration. -- Summary: Error message gives inadequate info (quality of implementation) Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: igodard at pacbell dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17628
next reply other threads:[~2004-09-23 7:13 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-23 7:13 igodard at pacbell dot net [this message] 2004-09-23 11:59 ` [Bug c++/17628] " 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=20040923071303.17628.igodard@pacbell.net \ --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).