I’ve landed the change to JSC to silently ignore the assignment in the non-strict “var ident =“ case, everything else is still an error so deconstruction and |of| enumeration will trigger a syntax error.

—Oliver

On Mar 15, 2014, at 2:01 PM, Brendan Eich <brendan at mozilla.com> wrote:

> Brendan Eich wrote:
>> Peter van der Zee wrote:
>>> 
>>> Which browsers currently don't accept this construct? I wasn't even aware that JSC didn't support it at some point.
>>> 
>> 
>> Did anyone say JSC lacked support? I think KJS followed ES3, and this was in the ES1 grammar, so I doubt it was never supported.
> 
> Of course I was excluding the recent removal per draft ES6 that Oliver mentions in the root of this thread, "JSC has been trying to kill off the initialiser expression in the for(in) statement" -- sorry for confusion. Just to be clear, this is recent and per ES6, intentional.
> 
> Hoping my site evang pals can get somewhere with battlefield.com.
> 
> /be
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss

I’ve landed the change to JSC to silently ignore the assignment in the non-strict `var ident =` case, everything else is still an error so deconstruction and `of` enumeration will trigger a syntax error.