From: Robert Dewar <dewar@gnat.com>
To: Nicolas Pavlidis <pavnic@sbox.tugraz.at>
Cc: James E Wilson <wilson@specifixinc.com>, gcc@gcc.gnu.org
Subject: Re: Confusing errormessage with implicit typename
Date: Sat, 04 Sep 2004 15:48:00 -0000 [thread overview]
Message-ID: <4139E3DE.4080202@gnat.com> (raw)
In-Reply-To: <m3zn46nisp.fsf@malloc.pavnic>
Nicolas Pavlidis wrote:
> Mayby it is possible to improve the warning/error messages. It is quite
> hard to understand some messages that gcc tells.
Why not take this on as a project? (fixing this particular warning). It's
not that difficult to get into the code, and I think you would find the
effort instructive. Ultimately the most efficient way of getting upgrades
to gcc is to do them yourself (assuming you are not in a mood to pay
someone to do it for you :-)
next prev parent reply other threads:[~2004-09-04 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1C2new-0007o7-00@deer.gmane.org>
2004-09-04 0:28 ` James E Wilson
2004-09-04 0:38 ` Joe Buck
2004-09-04 15:41 ` Nicolas Pavlidis
2004-09-04 15:48 ` Robert Dewar [this message]
2004-09-02 9:13 Nicolas Pavlidis
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=4139E3DE.4080202@gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=pavnic@sbox.tugraz.at \
--cc=wilson@specifixinc.com \
/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).