Re: parsing errors

David Corbin wrote:
> Is there any work being done to improve the error messages when you 
> write bad code.  Getting "parse error" for nearly every mistake I make 
> is beginning to get old.

If I got "parse error" near the place where the error is it would be 
sufficient for me. In some cases it is detected on correct place, in 
some cases I get an error a few screenfuls later or on the EOF.
I'd like to send some reports of these 'leaks' but I do not know what 
exactly would be useful for debugging the parser.

But if the parser told what went wrong it would give better idea where 
to search.

Reporting improper begin..end and {..} nesting would also help both find 
the error earlier in the code by the parser and locating it once reported.

But I understand writing a parser from which you get good error reports 
is quite hard.