|More intellegent error reporting than 'parse error' with Bison email@example.com (2003-10-13)|
|Re: More intellegent error reporting than 'parse error' with Bison firstname.lastname@example.org (Carl Cerecke) (2003-10-13)|
|Re: More intellegent error reporting than 'parse error' with Bison email@example.com (2003-10-31)|
|From:||firstname.lastname@example.org (Norman Ramsey)|
|Date:||31 Oct 2003 23:07:03 -0500|
|Organization:||Debian GNU/Linux site|
|Posted-Date:||31 Oct 2003 23:07:03 EST|
[Look through the archives. This question has come up a lot, without many
useful answers. LALR parsers do a fine job on correct input, but on
incorrect input they tend to throw up their hands unless you put in lots
and lots of error rules along with adhoc stuff to track the context.
If you are willing to add better error messages by hand, Clinton
Jeffery recently had a very nice TOPLAS paper that explains how to do
it with tool support. See http://unicon.sourceforge.net/merr/
Return to the
Search the comp.compilers archives again.