Re: LL(1) vs LALR(1) parsers

maatwerk@euronet.nl (M.M._van_der_Laan)
9 Dec 1995 19:51:06 -0500

          From comp.compilers

Related articles
[15 earlier articles]
Re: LL(1) vs LALR(1) parsers jmccarty@spdmail.spd.dsccc.com (1995-11-29)
Re: LL(1) vs LALR(1) parsers pardo@cs.washington.edu (1995-11-29)
Re: LL(1) vs LALR(1) parsers CSPT@giraffe.ru.ac.za (Pat Terry) (1995-11-30)
Re: LL(1) vs LALR(1) parsers gvcormac@plg.uwaterloo.ca (Gord Cormack) (1995-12-01)
Re: LL(1) vs LALR(1) parsers bridges@cs.arizona.edu (1995-12-01)
Re: LL(1) vs LALR(1) parsers mparks@oz.net (1995-12-09)
Re: LL(1) vs LALR(1) parsers maatwerk@euronet.nl (1995-12-09)
Re: LL(1) vs LALR(1) parsers sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) (1995-12-09)
Re: LL(1) vs LALR(1) parsers mparks@oz.net (1995-12-12)
Re: LL(1) vs LALR(1) parsers solution@gate.net (1995-12-16)
Better tools than lex & yacc(was Re: LL(1) vs LALR(1) parsers) dkulkarn@aristotle.helios.nd.edu (1995-12-17)
Re: LL(1) vs LALR(1) parsers sb@metis.no (1995-12-17)
Re: LL(1) vs LALR(1) parsers scooter@mccabe.com (Scott Stanchfield) (1995-12-18)
[1 later articles]
| List of all articles for this month |

From: maatwerk@euronet.nl (M.M._van_der_Laan)
Newsgroups: comp.compilers
Date: 9 Dec 1995 19:51:06 -0500
Organization: Euronet Internet
References: 95-11-051 95-11-138 95-11-195 95-11-234
Keywords: parse, LALR, LL(1)

I want to add two ideas to this discussion:


About quality of error recovery:
Most errors are NOT detected in the parser, but afterwards. Errors
detected by the parser are of the kind 'missing something" and in
those cases there is no need for clever recovery - the program is
simply wrong, so just skip the statement. Therefore, in my
opinion error recovery is no argument for selection of the
right type of grammar.


For those in favor of handwritten parsers: I also like them
because they are so easy to understand and fast. But first
checking a grammer with yacc and then retyping it as code is
double work. Wouldn't everyone be happy with a simple generator
that checks the unattributed grammar and then generates a
recursive-descent parser that you can fill in by hand? Does
this exist?


Mauk van der Laan
--


Post a followup to this message

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