public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12288] unintelligible error message for constructor declaration with misspelled type
Date: Tue, 16 Sep 2003 11:04:00 -0000	[thread overview]
Message-ID: <20030916084331.18953.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030915173035.12288.redi@gcc.gnu.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12288



------- Additional Comments From redi at gcc dot gnu dot org  2003-09-16 08:43 -------
Ah yes, I was a bit hasty filing this, should have checked a better reference. I
blame the unintelligible diagnostic for the fact I didn't spot that ;-)

When not in a constructor the same construct causes a different, but almost as
unintelligible message:

-----------------
class X {};

typedef X::T xt;
------------------

$ g++3 -c 12288-2.cc
map2.cc:3: error: expected init-declarator
map2.cc:3: error: expected `,' or `;'

This is a bit closer to the message in previous versions (which I don't think is
as bad as the current one) but still not much help for the average user trying
to work out what's wrong.


  parent reply	other threads:[~2003-09-16  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 17:41 [Bug c++/12288] New: "expected function-definition" error compiling constructor redi at gcc dot gnu dot org
2003-09-15 19:45 ` [Bug c++/12288] unintelligible error message for constructor declaration with misspelled type bangerth at dealii dot org
2003-09-16 11:04 ` redi at gcc dot gnu dot org [this message]
2003-12-29  0:31 ` pinskia at gcc dot gnu dot org
2004-10-28  2:08 ` pinskia at gcc dot gnu dot org
     [not found] <bug-12288-4@http.gcc.gnu.org/bugzilla/>
2013-05-20 14:38 ` paolo.carlini at oracle dot com
2013-05-20 17:15 ` paolo.carlini at oracle dot com
2013-05-20 17:17 ` redi at gcc dot gnu.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=20030916084331.18953.qmail@sources.redhat.com \
    --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: link
Be 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).