From: kaih@khms.westfalen.de (Kai Henningsen)
To: gcc@gcc.gnu.org
Subject: Re: new parser: error recovery needs work
Date: Sun, 19 Jan 2003 14:48:00 -0000 [thread overview]
Message-ID: <8e5PX$CXw-B@khms.westfalen.de> (raw)
In-Reply-To: <m3el7a7v5u.fsf@uniton.integrable-solutions.net>
gdr@integrable-solutions.net (Gabriel Dos Reis) wrote on 18.01.03 in <m3el7a7v5u.fsf@uniton.integrable-solutions.net>:
> Phil Edwards <phil@jaj.com> writes:
>
> | You really don't want to rely on the text of an error message not changing
> | over time. For this kind of thing to work, we need error messages to have
> | numbers (like every other compiler does, and with reason).
>
> Well, I must confess that I don't believe in numbers. Computers are
> very good at that, humans are not I'm afarid. Certainly we could do
> improvments by categoryzing diagnostics, but I'm -not- convinced that
> numbers are the way to go.
So long as we get *any* kind of short identifier ...
Personally, I would like to see a scheme that makes it possible to isolate
the exact place in the gcc source that decided to throw out this
particular message, but I gather some other people here object to that
much precision.
Just one of many possible schemes:
file.cc:123: warning: pedantic-17: blah blah ...
MfG Kai
next prev parent reply other threads:[~2003-01-19 5:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 13:40 Robert Dewar
2003-01-16 17:20 ` Joe Buck
2003-01-16 18:15 ` Mark Mitchell
2003-01-16 17:34 ` Joe Buck
2003-01-16 18:05 ` Gareth Pearce
2003-01-16 20:00 ` Phil Edwards
2003-01-16 20:15 ` Neil Booth
2003-01-16 21:43 ` Janis Johnson
2003-01-16 23:33 ` Mark Mitchell
2003-01-17 8:12 ` Phil Edwards
2003-01-18 16:48 ` Gabriel Dos Reis
2003-01-17 8:12 ` Fergus Henderson
2003-01-17 10:06 ` Stan Shebs
2003-01-17 11:36 ` Ben Elliston
2003-01-17 19:15 ` DJ Delorie
2003-01-17 12:27 ` Neil Booth
2003-01-17 23:26 ` Stan Shebs
2003-01-19 14:38 ` Kai Henningsen
2003-01-19 5:18 ` Fergus Henderson
2003-01-19 7:02 ` Neil Booth
2003-01-19 9:45 ` Fergus Henderson
2003-01-19 11:38 ` Zack Weinberg
2003-01-18 16:46 ` Gabriel Dos Reis
2003-01-17 5:26 ` Gareth Pearce
2003-01-17 8:36 ` Phil Edwards
2003-01-17 9:10 ` Gareth Pearce
2003-01-18 16:32 ` Gabriel Dos Reis
2003-01-19 14:48 ` Kai Henningsen [this message]
2003-01-19 19:45 ` Phil Edwards
2003-01-16 23:04 ` Mark Mitchell
2003-01-18 16:52 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 17:31 Robert Dewar
2003-01-18 21:53 Robert Dewar
2003-01-14 14:31 Jeff Donner
2003-01-14 1:24 Joe Buck
2003-01-14 7:35 ` Mark Mitchell
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='8e5PX$CXw-B@khms.westfalen.de' \
--to=kaih@khms.westfalen.de \
--cc=gcc@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).