Re: Is there an error correcting parser generator out there?

rockwell@nova.umd.edu (Raul Deluth Miller)
Wed, 5 Oct 1994 02:17:05 GMT

          From comp.compilers

Related articles
[5 earlier articles]
Re: Is there an error correcting parser generator out there? jon@mauney.com (1994-09-29)
Re: Is there an error correcting parser generator out there? dtarditi@cs.cmu.edu (David Tarditi) (1994-09-29)
Re: Is there an error correcting parser generator out there? parrt@everest.ee.umn.edu (Terence Parr) (1994-09-30)
Re: Is there an error correcting parser generator out there? johnm@po.EECS.Berkeley.EDU (1994-10-01)
Re: Is there an error correcting parser generator out there? adrian@platon.cs.rhbnc.ac.uk (1994-10-04)
Re: Is there an error correcting parser generator out there? andrew@bugalugs (1994-10-05)
Re: Is there an error correcting parser generator out there? rockwell@nova.umd.edu (1994-10-05)
Re: Is there an error correcting parser generator out there? rfg@netcom.com (1994-10-05)
Re: Is there an error correcting parser generator out there? thoni@softlab.se (1994-10-05)
Re: Is there an error correcting parser generator out there? clark@quarry.zk3.dec.com (1994-10-05)
Re: Is there an error correcting parser generator out there? johnm@po.EECS.Berkeley.EDU (1994-10-06)
| List of all articles for this month |

Newsgroups: comp.compilers
From: rockwell@nova.umd.edu (Raul Deluth Miller)
Keywords: parse, errors
Organization: University of Maryland University College
References: 94-09-142 94-10-023
Date: Wed, 5 Oct 1994 02:17:05 GMT

A Johnstone:
: Personally I have always been an RD convert for the very simple
: reason that debugging output from LALR generators is a
: nightmare. When you are developing a new language, as opposed to
: hacking in someone else's C grammar this is a real issue.


Hmm... back when I was mucking around with yacc, I found it essential
to have a tool to correlate the dynamic and static debugging output
from yacc. With such a tool (I used emacs, configured to move show me
the rule that corresponded to the debugging text), it was pretty easy
to see where problems were occuring, etc. [I've long since thrown out
the code, and it wasn't that elegant, but it wasn't very long either
and shouldn't take much to reproduce.]


Raul D. Miller
<rockwell@nova.umd.edu>
--


Post a followup to this message

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