]
Sent: Friday, November 8, 2013 4:16 PM
To: Ian Halliday
Cc: es-discuss@mozilla.org
Subject: Re: Specification of use before declaration errors
On Nov 8, 2013, at 3:35 PM, Ian Halliday wrote:
Hello es-discuss,
I'm having difficulty figuring out where the ES6 draft spec specifies that a
use
that shadowing of bound names is not allowed at all.
Is this correct?
Ian
From: Allen Wirfs-Brock [mailto:al...@wirfs-brock.com]
Sent: Friday, November 8, 2013 4:16 PM
To: Ian Halliday
Cc: es-discuss@mozilla.org
Subject: Re: Specification of use before declaration errors
@mozilla.org
Subject: RE: Specification of use before declaration errors
Then for 13.1.8 shouldn't there be something like this
StatementListItem : Statement
1. If Statement is a Block then return a new empty List.
2. Else return VarDeclaredNames of Statement
defined in order to prevent
;
}
}
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of Ian
Halliday
Sent: Wednesday, November 13, 2013 4:14 PM
To: Allen Wirfs-Brock
Cc: es-discuss@mozilla.org
Subject: RE: Specification of use before declaration errors
Then for 13.1.8 shouldn’t
Hello es-discuss,
I'm having difficulty figuring out where the ES6 draft spec specifies that a
use before declaration error should be thrown. My last understanding of the
temporal dead zone was that ECMAScript would always issue a use before
declaration error at runtime, regardless whether it
On Nov 8, 2013, at 3:35 PM, Ian Halliday wrote:
Hello es-discuss,
I’m having difficulty figuring out where the ES6 draft spec specifies that a
“use before declaration” error should be thrown. My last understanding of
the temporal dead zone was that ECMAScript would always issue a “use
6 matches
Mail list logo
