Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.compilers > #1216

Re: Error message with bison and flex

Show all headers | View raw

Hans-Peter Diettrich <DrDiettrich1@aol.com> wrote:

(snip)

> 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.

When I first started programming, with OS/360 compilers, it was usual
for the compiler to print an annotated listing file with some type of
numbering. Ones I remember printed ISN (internal statement number)
instead of input file line numbers, which you could match up on the
listing.

Fortran G prints a $ in the suspected error column on the next line,
where Fortran H gives the column number.

I suppose the printed listing file has some similarity to the full
screen display in an IDE.

The listing file also could contain a list of variables with their
address and line number in which they were used.

With cards, you had to print the file and look at it. With WYLBUR, you
could fetch the file back to an editing session, search through it
using editor command, such as search for the word ERROR, then purge
the file without printing it.

I don't know if any compilers still generate listing files with line
numbers and cross references.

-- glen

Back to comp.compilers | Previous | Next — Previous in thread | Find similar | Unroll thread

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