Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.lightlink.com!news.iecc.com!.POSTED!nerds-end From: glen herrmannsfeldt Newsgroups: comp.compilers Subject: Re: Error message with bison and flex Date: Sat, 12 Apr 2014 03:31:35 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 32 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-04-009@comp.compilers> References: <14-04-005@comp.compilers> <14-04-007@comp.compilers> <14-04-008@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: miucha.iecc.com 1397331432 58789 2001:470:1f07:1126:0:676f:7373:6970 (12 Apr 2014 19:37:12 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 12 Apr 2014 19:37:12 +0000 (UTC) Keywords: debug, history Posted-Date: 12 Apr 2014 15:37:12 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1216 Hans-Peter Diettrich 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