|Error message with bison and flex firstname.lastname@example.org (2014-04-07)|
|Re: Error message with bison and flex email@example.com (Kaz Kylheku) (2014-04-10)|
|Re: Error message with bison and flex DrDiettrich1@aol.com (Hans-Peter Diettrich) (2014-04-11)|
|Re: Error message with bison and flex firstname.lastname@example.org (glen herrmannsfeldt) (2014-04-12)|
|From:||Hans-Peter Diettrich <DrDiettrich1@aol.com>|
|Date:||Fri, 11 Apr 2014 03:30:39 +0200|
|Posted-Date:||11 Apr 2014 21:42:31 EDT|
Kaz Kylheku schrieb:
> On 2014-04-08, email@example.com <firstname.lastname@example.org> wrote:
>> Sometime the text return from a syntax error is very short.
> Usually, there is little or no program text at all in a syntax error message.
>> I would like to output 5 lines before the error and
>> 5 lines after the error.
> I don't see the point of this.
> Just output errors in a way that an IDE can understand, so you can navigate
> through errors visually. Then you have all the lines you want before and after
> the error.
> [People do use lex, yacc, et al for other things than compilers that run under IDEs. -John]
In these cases the "source code" display may be even less helpful. IMO
every application using parsers needs its kind of an IDE, that
translates the syntactical errors into something meaningful to the user.
[People do use the -C5 flag to grep. -John]
Return to the
Search the comp.compilers archives again.