Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #1215
| From | Hans-Peter Diettrich <DrDiettrich1@aol.com> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: Error message with bison and flex |
| Date | 2014-04-11 03:30 +0200 |
| Organization | Compilers Central |
| Message-ID | <14-04-008@comp.compilers> (permalink) |
| References | <14-04-005@comp.compilers> <14-04-007@comp.compilers> |
Kaz Kylheku schrieb: > On 2014-04-08, laplante.p@gmail.com <laplante.p@gmail.com> 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. Me2 > 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. DoDi [People do use the -C5 flag to grep. -John]
Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Error message with bison and flex laplante.p@gmail.com - 2014-04-07 22:36 -0700
Re: Error message with bison and flex Kaz Kylheku <kaz@kylheku.com> - 2014-04-10 15:06 +0000
Re: Error message with bison and flex Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2014-04-11 03:30 +0200
Re: Error message with bison and flex glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2014-04-12 03:31 +0000
csiph-web