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

"ng2010" <ng2010@att.invalid>
Fri, 5 Feb 2010 22:32:31 -0600

          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: "ng2010" <ng2010@att.invalid>
Newsgroups: comp.compilers
Date: Fri, 5 Feb 2010 22:32:31 -0600
Organization: A noiseless patient Spider
Keywords: parse, question
Posted-Date: 06 Feb 2010 09:59:58 EST

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)?
[Seems to me that it makes a newline syntactically equivalent to a semicolon, unless you
have some plan for multi-line statements you haven't mentioned. -John]


Post a followup to this message

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