Re: Making semicolons optional moves LALR(1) language to LALR(2)?

Kaz Kylheku <kkylheku@gmail.com>
Mon, 8 Feb 2010 21:05:23 +0000 (UTC)

          From comp.compilers
Related articles
Making semicolons optional moves LALR(1) language to LALR(2)? ng2010@att.invalid (ng2010) (2010-02-05)
Re: Making semicolons optional moves LALR(1) language to LALR(2)? cr88192@hotmail.com (BGB / cr88192) (2010-02-06)
Re: Making semicolons optional moves LALR(1) language to LALR(2)? ng2010@att.invalid (ng2010) (2010-02-06)
Re: Making semicolons optional moves LALR(1) language to LALR(2)? kkylheku@gmail.com (Kaz Kylheku) (2010-02-08)
| List of all articles for this month |
From: Kaz Kylheku <kkylheku@gmail.com>
Newsgroups: comp.compilers
Date: Mon, 8 Feb 2010 21:05:23 +0000 (UTC)
Organization: A noiseless patient Spider
References: 10-02-025
Keywords: parse, LALR
Posted-Date: 10 Feb 2010 11:03:10 EST

On 2010-02-06, ng2010 <ng2010@att.invalid> wrote:
> For a hypothetical programming language that is LALR(1) and uses
> semicolons as statement terminators, would a change that makes semicolons
> only required on multi-statement lines and using the newline as an
> implicit statement terminator make the language LALR(2)?


The 2 in LALR(2) means ``look ahead two positions in the token stream'', not
``look ahead for two possible kinds of tokens''.


:)


Post a followup to this message

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