Re: Can `let`, `static` and `yield` still be used as Identifier?

Thu, 01 Jan 2015 17:18:06 -0800

 
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" <[email protected]>:


On Wed Dec 31 2014 at 2:45:57 PM Alex Kocharin <[email protected]> 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
 
 
 Rick
 
 
 
29.12.2014, 17:39, "Erik Arvidsson" <[email protected]>:

This is a bug in Traceur.


On Mon, Dec 29, 2014, 11:35 Gary Guo <[email protected]> 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
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
,

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to