Related articles |
---|
Anyone got an LALR(2) parser-generator ? lindsay-j@rmc.ca (1995-08-25) |
Re: Anyone got an LALR(2) parser-generator ? Martin.Jourdan@inria.fr (1995-09-04) |
Re: Anyone got an LALR(2) parser-generator ? BARRETO%VELAHF@ECCSA.Tr.Unisys.com (1995-09-04) |
Re: Anyone got an LALR(2) parser-generator ? Thomas.Herter@mch.sni.de (1995-09-04) |
Re: Anyone got an LALR(2) parser-generator ? Martin.Jourdan@inria.fr (1995-09-11) |
Re: Anyone got an LALR(2) parser-generator ? farzu@uvg.edu.gt (1995-09-18) |
Re: Anyone got an LALR(2) parser-generator ? grosch@cocolab.sub.com (1995-10-30) |
Newsgroups: | comp.compilers |
From: | BARRETO%VELAHF@ECCSA.Tr.Unisys.com |
Keywords: | parse, tools, question |
Organization: | Compilers Central |
References: | 95-09-009 |
Date: | Mon, 4 Sep 1995 13:44:00 GMT |
"John H. Lindsay" <lindsay-j%rmc.ca@trsvr> wrote:
> I'm working with a language definition that needs an LALR(2)
> parser-generator for a couple of good reasons;
Although it is quite common to find non-LALR(1) constructs in
programming language grammars, in most cases they are easily (?)
removed by rewriting the grammar. I'm curious about the reasons
to need LALR(2) power. What kind of language structure makes
such an unusual requirement? Wouldn't perhaps a full LR(1) parser
generator be enough for the task?
Paulo S. L. M. Barreto -- Software Analyst -- Unisys Brazil
Standard disclaimer applies ("I do not speak for Unisys", etc.)
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.