Related articles |
---|
[7 earlier articles] |
Re: Backtracking yacc sasghm@unx.sas.com (1992-09-17) |
Re: Backtracking yacc diamond@jit081.enet.dec.com (18-Sep-1992 1420) (1992-09-18) |
Re: Backtracking yacc harwood@progress.com (Tom Harwood) (1992-09-18) |
Re: Backtracking yacc ipser@solomon.technet.sg (1992-09-19) |
Re: Backtracking yacc andrewd@cs.adelaide.edu.au (1992-09-21) |
Re: Backtracking yacc sasghm@unx.sas.com (1992-09-21) |
Re: Backtracking yacc sasghm@unx.sas.com (1992-09-23) |
Re: Backtracking yacc schrod@iti.informatik.th-darmstadt.de (1992-09-23) |
Re: Backtracking yacc andrewd@cs.adelaide.edu.au (1992-09-25) |
Re: Backtracking yacc sasghm@unx.sas.com (1992-09-25) |
Re: Backtracking yacc neitzel@ips.cs.tu-bs.de (1992-09-25) |
Newsgroups: | comp.compilers |
From: | sasghm@unx.sas.com (Gary Merrill) |
Organization: | SAS Institute Inc. |
Date: | Wed, 23 Sep 1992 13:29:17 GMT |
Originator: | sasghm@theseus.unx.sas.com |
Keywords: | yacc, parse, LALR, LL(1) |
References: | 92-09-059 92-09-126 |
andrewd@cs.adelaide.edu.au (Andrew Dunstan) writes:
|> Why not use all this to write grammars any old LR(k)-how, and then
|> transform them? Basically, because it's not worth the bother, at least
|> most of the time. LALR(1) is powerful enough for most purposes. (In fact I
|> am more taken with LL(1), for reasons I won't go into here.)
Wait a minute! Please *do* go into these reasons here. I think they
might very well be of general interest. I to am more "taken" will LL(1)
grammars. They seem more "natural" to me. I think I could make this
more precise, but I am quite interested in hearing the feelings of others.
--
Gary H. Merrill [Principal Systems Developer, C Compiler Development]
SAS Institute Inc. / SAS Campus Dr. / Cary, NC 27513 / (919) 677-8000
sasghm@theseus.unx.sas.com ... !mcnc!sas!sasghm
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.