On 25 August 2011 18:57, Brendan Eich wrote:
> On Aug 25, 2011, at 6:17 AM, Andreas Rossberg wrote:
>
>>> There is no "before and after" or "both" here. Hoisting first, with rule 1
>>> enforced; then rule 2 checking. Relative source order of declarations is
>>> irrelevant.
>>
>> Well, only when
On Aug 25, 2011, at 6:17 AM, Andreas Rossberg wrote:
>> There is no "before and after" or "both" here. Hoisting first, with rule 1
>> enforced; then rule 2 checking. Relative source order of declarations is
>> irrelevant.
>
> Well, only when you're implicitly assuming a somewhat
> non-standard
On Aug 25, 2011, at 7:56 AM, Mark S. Miller wrote:
> [+es-discuss]
>
> On Thu, Aug 25, 2011 at 2:40 AM, Cameron McCormack wrote:
> +cc public-script-coord
> -cc,+bcc public-device-apis
>
> On 25/08/11 7:38 PM, Andreas Gal wrote:
> We should take this to the WebIDL list then. The order definite
[+es-discuss]
On Thu, Aug 25, 2011 at 2:40 AM, Cameron McCormack wrote:
> +cc public-script-coord
> -cc,+bcc public-device-apis
>
> On 25/08/11 7:38 PM, Andreas Gal wrote:
>
>> We should take this to the WebIDL list then. The order definitely
>> matters in practice for interoperability if people
On 24 August 2011 18:03, Brendan Eich wrote:
> On Aug 24, 2011, at 2:03 AM, Andreas Rossberg wrote:
>> On 23 August 2011 21:18, Brendan Eich wrote:
>>> I think the rules we have discussed are:
>>>
>>> 1. Any hoisting of var across let binding the same name (whether explicit,
>>> or as in catch b
5 matches
Mail list logo