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


> > > 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 either that or expect people who change error messages to update
the
> > documentation :P
> > not like that would happen...
>
> It's not the documentation that would need updating (well, it would, but
> that's not the killer).  It's the lookup tool you're proposing that would
> need to know about the new error text that it's using as a "lookup key".
>
> If, OTOH, you're assuming that the text of the error message itself is
> in the documentation verbatim, and you want a tool to find it when giving
> the error message, I refer you to "grep".  :-)

yes I considered it likely that once the documentation existed - such a tool
would be a simple script.
with alphanumeric identifier codes, it certainly would.

Gareth


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