From: Tim Hollebeek <tim@hollebeek.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
Gabriel Dos Reis <gdr@codesourcery.com>,
dewar@gnat.com, fw@deneb.enyo.de, bosch@gnat.com,
dnovillo@redhat.com, gcc@gcc.gnu.org, kenner@vlsi1.ultra.nyu.edu
Subject: Re: Really crummy error messages, was Re: Ada files now checked in
Date: Mon, 08 Oct 2001 16:49:00 -0000 [thread overview]
Message-ID: <20011008200202.A4815@cj44686-b.reston1.va.home.com> (raw)
In-Reply-To: <20011008163225.A18409@disaster.jaj.com>
On Mon, Oct 08, 2001 at 04:32:25PM -0400, Phil Edwards wrote:
>
> > While we're bitching, I am sick of seeing
> >
> > test.c:1: (Each undeclared identifier is reported only once
> > test.c:1: for each function it appears in.)
> >
> > I think the error message is perfectly clear without that.
>
> I'd agree with this too. Maybe GCC should have a beginner's mode? :-)
how about --verbose-errors, and have both a one-line and paragraph
explanation of each error?
test.c:1: Message always goes here
test.c:1: (iff --verbose errors, extended explanation
test.c:1: more...
test.c:1: etc)
This way you can normally use the normal options, and stick in
--verbose-errors when you see a new message or one you don't
understand.
-Tim
next prev parent reply other threads:[~2001-10-08 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 14:34 Phil Edwards
2001-10-07 23:01 ` Really crummy error messages Florian Weimer
2001-10-08 11:09 ` Really crummy error messages, was Re: Ada files now checked in Zack Weinberg
2001-10-08 13:31 ` Phil Edwards
2001-10-08 16:49 ` Tim Hollebeek [this message]
2001-10-09 23:32 ` Fergus Henderson
2001-10-10 2:25 ` Florian Weimer
2001-10-10 11:00 ` Phil Edwards
2001-10-11 14:04 ` Zack Weinberg
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=20011008200202.A4815@cj44686-b.reston1.va.home.com \
--to=tim@hollebeek.com \
--cc=bosch@gnat.com \
--cc=dewar@gnat.com \
--cc=dnovillo@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=gdr@codesourcery.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=pedwards@disaster.jaj.com \
--cc=zack@codesourcery.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).