This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: new parser: error recovery needs work


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]