public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "emreturkay at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39681] New: Compile error is not descriptive Date: Tue, 07 Apr 2009 15:34:00 -0000 [thread overview] Message-ID: <bug-39681-17544@http.gcc.gnu.org/bugzilla/> (raw) Note: This enhancement request (in my opinion) is related with the compiler frontend (of C++ and probably also C) and can be applied to all platforms. Given a .cpp file (3 lines below only, nothing else); int main() { int* p = new foo; } When tried to compile gives the following error: error: expected type-specifier before ‘foo’ error: expected ‘,’ or ‘;’ before ‘foo’ Which is not descriptive. Something like; error: ‘foo’ was not declared in this scope would be better, and consistent with the error report of the compilation of; int main() { foo i; } -- Summary: Compile error is not descriptive Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: emreturkay at gmail dot com GCC build triplet: i486-linux-gnu GCC host triplet: i486-linux-gnu GCC target triplet: i486-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39681
next reply other threads:[~2009-04-07 15:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-07 15:34 emreturkay at gmail dot com [this message] 2009-04-07 15:38 ` [Bug c++/39681] " 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-39681-17544@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).