> On Tue, 2007-10-23 at 14:58 +0200, liorean wrote:
> > It's there to prevent the grammar from being ambiguous. "function",
> > "let" and "{" have different meaning in statement context from
> > expression context. If the ExpressionStatement construct allowed them,
> > then they would be ambigous i
On Tue, 2007-10-23 at 14:58 +0200, liorean wrote:
> It's there to prevent the grammar from being ambiguous. "function",
> "let" and "{" have different meaning in statement context from
> expression context. If the ExpressionStatement construct allowed them,
> then they would be ambigous in statemen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:es4-discuss-
> [EMAIL PROTECTED] On Behalf Of David Teller
> Sent: Tuesday, October 23, 2007 4:11 AM
> To: JS2
> Subject: Rule 317
>
> Hello list,
>
> I'm still fighting the syntax of JS2. Attempting to feed it into a
> parser g
On 23/10/2007, David Teller <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> I'm still fighting the syntax of JS2. Attempting to feed it into a
> parser generator (menhir, for the moment), has already allowed me to
> find a few typoes in the spec and a few useless variables in the
> reference impl
Hello list,
I'm still fighting the syntax of JS2. Attempting to feed it into a
parser generator (menhir, for the moment), has already allowed me to
find a few typoes in the spec and a few useless variables in the
reference implementation, which is all I have to show for the moment.
That and t
