Related articles |
---|
Re: error recovery hankd@ee.ecn.purdue.edu (1989-04-30) |
Error recovery cayot@essi.fr (Cayot Robert-Olivier) (1997-03-21) |
Re: Error recovery gvcormac@plg.uwaterloo.ca (Gord Cormack) (1997-03-22) |
Re: Error recovery P.Whillance@ncl.ac.uk (Peter Whillance) (1997-03-27) |
Error Recovery markagr@aol.com (1997-05-12) |
Re: Error Recovery nandu@longs.dr.lucent.com (1997-05-25) |
Re: Error Recovery tc@charlie.cns.iit.edu (Thomas W. Christopher) (1997-05-25) |
Re: Error Recovery mag01@jvcam.northern.co.uk (Mark Gregory) (1997-05-27) |
Re: Error Recovery mcr@visi.com (Michael Roach) (1997-05-31) |
From: | markagr@aol.com (MarkAGr) |
Newsgroups: | comp.compilers |
Date: | 12 May 1997 00:34:01 -0400 |
Organization: | AOL, http://www.aol.co.uk |
Keywords: | parse, errors |
Hello John & Others,
The one thing we rarely get around here are questions concerning
error recovery while parsing. What systems exist already for error
recovery, and what form do they take? What would be the ideal and how
can we implement them? I have very few ideas in this area and would be
happy for any suggestions.
Mark
[Boy, there's a can of worms. We've discussed this in the past, and
the biggest problem seems to be that it's impossible to tell what the
programmer's intention was. You can guess, but can you guess correctly
often enough to do more good than harm? -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.