Error reporting/recovery

Jean-Marc Bourguet <bourguet@my-deja.com>
5 Apr 2000 22:19:30 -0400

          From comp.compilers
Related articles
Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-05)
Re: Error reporting/recovery iank@bearcave.com (2000-04-11)
Re: Error reporting/recovery grosch@cocolab.de (2000-04-11)
Re: Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-14)
Re: Error reporting/recovery bourguet@my-deja.com (Jean-Marc Bourguet) (2000-04-14)
Re: Error reporting/recovery rod.bates@wichita.boeing.com (Rodney M. Bates) (2000-04-14)
Re: Error reporting/recovery nr@labrador.eecs.harvard.edu (2000-04-16)
[2 later articles]
| List of all articles for this month |
From: Jean-Marc Bourguet <bourguet@my-deja.com>
Newsgroups: comp.compilers
Date: 5 Apr 2000 22:19:30 -0400
Organization: Deja.com - Before you buy.
Keywords: errors, comment

The parser generators I know of (I've looked at yacc variants and
pccts) are bad at error reporting/recovery at least when not helped
by suitable addition in the grammar description. I know that the
field has been studied and I'm quite sure that yacc is not at the
state of the art in this matter, so I wondered:
- if there was other parser generators freely available
who did a better jobs,
- if there was an available benchmark (grammars and
input) to test the error reporting/recovery of parser
generators.


Thanks,


-- Jean-Marc Bourguet
[You can get reasonable error recovery using yacc error rules, but it
is about as far from automatic as you can imagine. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.