Re: Can `let`, `static` and `yield` still be used as Identifier?
Gary is right: `let` is disabled for web content in Firefox because our version isn't spec-compatible enough yet. In the shell or chrome code, where it is enabled, our behavior matches traceur's in that we treat the given examples as errors, too. On Fri, Jan 2, 2015 at 4:40 PM, Gary Guo nbdd0...@hotmail.com wrote: Thanks for your note, I'm not testing it under Nightly. Did you test that the 'let' declaration is working properly in JSFiddle? It may not be enabled in web pages by default if the script doesn't declare to be javascript 1.7. -- From: waldron.r...@gmail.com Date: Fri, 2 Jan 2015 14:23:31 + Subject: Re: Can `let`, `static` and `yield` still be used as Identifier? To: nbdd0...@hotmail.com CC: es-discuss@mozilla.org On Thu Jan 01 2015 at 9:47:47 PM Gary Guo nbdd0...@hotmail.com wrote: It seems that in JSFiddle running on Firefox, let declaration is disabled. So this cannot explain. I don't know why you'd say that, considering the fiddle works just fine. Open your developer console and you'll see the output. Note that I'm referring to Nightly. Rick ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
RE: Can `let`, `static` and `yield` still be used as Identifier?
Thanks for your note, I'm not testing it under Nightly. Did you test that the 'let' declaration is working properly in JSFiddle? It may not be enabled in web pages by default if the script doesn't declare to be javascript 1.7. From: waldron.r...@gmail.com Date: Fri, 2 Jan 2015 14:23:31 + Subject: Re: Can `let`, `static` and `yield` still be used as Identifier? To: nbdd0...@hotmail.com CC: es-discuss@mozilla.org On Thu Jan 01 2015 at 9:47:47 PM Gary Guo nbdd0...@hotmail.com wrote: It seems that in JSFiddle running on Firefox, let declaration is disabled. So this cannot explain. I don't know why you'd say that, considering the fiddle works just fine. Open your developer console and you'll see the output. Note that I'm referring to Nightly. Rick ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Can `let`, `static` and `yield` still be used as Identifier?
On Thu Jan 01 2015 at 9:47:47 PM Gary Guo nbdd0...@hotmail.com wrote: It seems that in JSFiddle running on Firefox, let declaration is disabled. So this cannot explain. I don't know why you'd say that, considering the fiddle works just fine. Open your developer console and you'll see the output. Note that I'm referring to Nightly. Rick -- From: waldron.r...@gmail.com Date: Wed, 31 Dec 2014 21:36:46 + Subject: Re: Can `let`, `static` and `yield` still be used as Identifier? To: a...@kocharin.ru; erik.arvids...@gmail.com; nbdd0...@hotmail.com; es-discuss@mozilla.org let = 1; console.log(let); // 1 var let = 1; console.log(let); // 1 let let = 1; // SyntaxError ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Can `let`, `static` and `yield` still be used as Identifier?
I just tested in the JS console of my FireFox 34, where "let=1" seems to be a "SyntaxError: missing variable name". But your jsfiddle works fine, so you're right, everything is good here. 01.01.2015, 00:36, "Rick Waldron" waldron.r...@gmail.com:On Wed Dec 31 2014 at 2:45:57 PM Alex Kocharin a...@kocharin.ru wrote: Firefox does parse `let=1` as illegal, Under what circumstance? All of these function according to the spec: let = 1; console.log(let); // 1 var let = 1; console.log(let); // 1 let let = 1; // SyntaxError (http://jsfiddle.net/rwaldron/L5kbtup6/) Rick 29.12.2014, 17:39, "Erik Arvidsson" erik.arvids...@gmail.com:This is a bug in Traceur.On Mon, Dec 29, 2014, 11:35 Gary Guo nbdd0...@hotmail.com wrote:From the specification I saw `yield` is being explicitly declared as an possible Identifier in non-strict mode, and there `let`, `static` are parsed as identifier first. However, I did not see anyway to distinguish `let` identifier and `let` keyword. `let=1` is parsed as illegal in traceur, and so does `static=1`. Is this a bug of traceur or it is intended? It would be incompatible in non-strict mode if this is intended. (And if this is intended, there will be no reason for keep `let` and `static` non-reserved-word during lex stage)___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss,___es-discuss mailing listes-discuss@mozilla.orghttps://mail.mozilla.org/listinfo/es-discuss___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
RE: Can `let`, `static` and `yield` still be used as Identifier?
It seems that in JSFiddle running on Firefox, let declaration is disabled. So this cannot explain. From: waldron.r...@gmail.com Date: Wed, 31 Dec 2014 21:36:46 + Subject: Re: Can `let`, `static` and `yield` still be used as Identifier? To: a...@kocharin.ru; erik.arvids...@gmail.com; nbdd0...@hotmail.com; es-discuss@mozilla.org let = 1; console.log(let); // 1 var let = 1; console.log(let); // 1 let let = 1; // SyntaxError ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Can `let`, `static` and `yield` still be used as Identifier?
Firefox does parse `let=1` as illegal, and I think this is a desired behavior. Otherwise you can't use `let` in non-strict mode, which is bad. 29.12.2014, 17:39, "Erik Arvidsson" erik.arvids...@gmail.com:This is a bug in Traceur.On Mon, Dec 29, 2014, 11:35 Gary Guo nbdd0...@hotmail.com wrote:From the specification I saw `yield` is being explicitly declared as an possible Identifier in non-strict mode, and there `let`, `static` are parsed as identifier first. However, I did not see anyway to distinguish `let` identifier and `let` keyword. `let=1` is parsed as illegal in traceur, and so does `static=1`. Is this a bug of traceur or it is intended? It would be incompatible in non-strict mode if this is intended. (And if this is intended, there will be no reason for keep `let` and `static` non-reserved-word during lex stage)___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss,___es-discuss mailing listes-discuss@mozilla.orghttps://mail.mozilla.org/listinfo/es-discuss___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Can `let`, `static` and `yield` still be used as Identifier?
On Wed Dec 31 2014 at 2:45:57 PM Alex Kocharin a...@kocharin.ru wrote: Firefox does parse `let=1` as illegal, Under what circumstance? All of these function according to the spec: let = 1; console.log(let); // 1 var let = 1; console.log(let); // 1 let let = 1; // SyntaxError (http://jsfiddle.net/rwaldron/L5kbtup6/) Rick 29.12.2014, 17:39, Erik Arvidsson erik.arvids...@gmail.com: This is a bug in Traceur. On Mon, Dec 29, 2014, 11:35 Gary Guo nbdd0...@hotmail.com wrote: From the specification I saw `yield` is being explicitly declared as an possible Identifier in non-strict mode, and there `let`, `static` are parsed as identifier first. However, I did not see anyway to distinguish `let` identifier and `let` keyword. `let=1` is parsed as illegal in traceur, and so does `static=1`. Is this a bug of traceur or it is intended? It would be incompatible in non-strict mode if this is intended. (And if this is intended, there will be no reason for keep `let` and `static` non-reserved-word during lex stage) ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss , ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Can `let`, `static` and `yield` still be used as Identifier?
This is a bug in Traceur. On Mon, Dec 29, 2014, 11:35 Gary Guo nbdd0...@hotmail.com wrote: From the specification I saw `yield` is being explicitly declared as an possible Identifier in non-strict mode, and there `let`, `static` are parsed as identifier first. However, I did not see anyway to distinguish `let` identifier and `let` keyword. `let=1` is parsed as illegal in traceur, and so does `static=1`. Is this a bug of traceur or it is intended? It would be incompatible in non-strict mode if this is intended. (And if this is intended, there will be no reason for keep `let` and `static` non-reserved-word during lex stage) ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
