|Error reporting (for syntactic errors) firstname.lastname@example.org (Roar) (2007-01-08)|
|Re: Error reporting (for syntactic errors) email@example.com (Roar) (2007-01-09)|
|Re: Error reporting (for syntactic errors) firstname.lastname@example.org (Russ Cox) (2007-01-09)|
|Date:||9 Jan 2007 13:30:03 -0500|
|Posted-Date:||09 Jan 2007 13:30:03 EST|
> [There isn't any "official" way, just ways that are more or less bad.
Apart from adding productions for common errors, to recognize and
handle them spesifically, the approach of identifying a
point-of-no-return state inside a grammar production seems to work for
the tests I've done so far.
The idea is that deciding that a production has reached a
point-of-no-return, changes the meaning of failure to match required
elements from that of simply aborting the attempt and letting the
calling production decide what to do, to instead reporting an error,
based on what required element (production or token) failed.
Return to the
Search the comp.compilers archives again.