public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25751] New: Poor error when templating on undefined types Date: Wed, 11 Jan 2006 15:22:00 -0000 [thread overview] Message-ID: <bug-25751-9525@http.gcc.gnu.org/bugzilla/> (raw) #include <vector> int main(void) { std::vector<foo> v; v.begin(); } Produces: temp.cc: In function 'int main()': temp.cc:5: error: 'foo' was not declared in this scope temp.cc:5: error: template argument 1 is invalid temp.cc:5: error: template argument 2 is invalid temp.cc:5: error: invalid type in declaration before ';' token temp.cc:6: error: request for member 'begin' in 'v', which is of non-class type 'int' That last warning doesn't seem to make any sense. Perhaps g++ should abandon parsing / producing errors earlier? -- Summary: Poor error when templating on undefined types Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: chris at bubblescope dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25751
next reply other threads:[~2006-01-11 15:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-11 15:22 chris at bubblescope dot net [this message] 2006-02-02 19:47 ` [Bug c++/25751] " 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=bug-25751-9525@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).