public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/17851] New: [3.4/4.0 regression] Misleading diagnostic for invalid function decalrations Date: Tue, 05 Oct 2004 20:05:00 -0000 [thread overview] Message-ID: <20041005200518.17851.reichelt@gcc.gnu.org> (raw) Since gcc 3.4.0 I get an error message which is not very helpful for the following invalid code snippet: ================================ struct A { int operator[] (size_t); }; struct B { int foo(size_t); }; ================================ err.cc:3: error: declaration of `operator[]' as non-function err.cc:3: error: expected `;' before '(' token err.cc:8: error: expected `;' before '(' token With gcc 3.3.5 and before I get: err.cc:3: error: `size_t' was not declared in this scope err.cc:3: error: invalid data member initialization err.cc:3: error: (use `=' to initialize static data members) err.cc:3: error: declaration of `operator[]' as non-function err.cc:8: error: `size_t' was not declared in this scope err.cc:8: error: invalid data member initialization which says what's wrong: `size_t' was not declared in this scope. -- Summary: [3.4/4.0 regression] Misleading diagnostic for invalid function decalrations Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17851
next reply other threads:[~2004-10-05 20:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-05 20:05 reichelt at gcc dot gnu dot org [this message] 2004-10-05 20:16 ` [Bug c++/17851] " pinskia at gcc dot gnu dot org 2004-10-12 23:07 ` [Bug c++/17851] [3.4/4.0 regression] Misleading diagnostic for invalid function declarations with undeclared types reichelt 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=20041005200518.17851.reichelt@gcc.gnu.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).