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

2015-01-02 Thread Till Schneidereit
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

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

2015-01-02 Thread Gary Guo
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 +

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

2015-01-02 Thread Rick Waldron
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

Re: Why does Symbol.for and Symbol.keyFor are limited to strings?

2015-01-02 Thread Allen Wirfs-Brock
On Jan 2, 2015, at 9:18 AM, Michał Wadas wrote: What is reason behind restricting entries in global symbol registry to be indexed only by strings? What are the use cases for anything other strings? Allen ___ es-discuss mailing list

Why does Symbol.for and Symbol.keyFor are limited to strings?

2015-01-02 Thread Michał Wadas
What is reason behind restricting entries in global symbol registry to be indexed only by strings? ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Re: Octal escape sequences in string and regexp literals

2015-01-02 Thread Caitlin Potter
I think there are a few reasons why you wouldn't want these. First and foremost, octal escapes (\nnn) are just an alternative equivalent to hex escapes (\xnn). Most software developers spend a lot more time dealing with hex when it comes to byte values, and very little time with octal literals

Re: Implicit coercion of Symbols

2015-01-02 Thread Caitlin Potter
One reason it might make sense to throw, is people converting values to string names for use as object properties. Reason you'd want to throw would be to prevent accidentally making the key useless (different from its original Symbol value). Haven't paid attention to the rationale, but that

Re: Implicit coercion of Symbols

2015-01-02 Thread Rick Waldron
On Fri Jan 02 2015 at 7:53:22 PM Brendan Eich bren...@mozilla.org wrote: Caitlin Potter wrote: One reason it might make sense to throw, is people converting values to string names for use as object properties. Reason you'd want to throw would be to prevent accidentally making the key

Octal escape sequences in string and regexp literals

2015-01-02 Thread Claude Pache
Hi, Current web browsers implement octal escape sequences of the form \52, representing the character of code 0o52, in string literals in sloppy mode only, and in regexps (at the condition there is less than 52 capturing groups) in both sloppy and strict mode. (In order to avoid confusion: I

Re: Octal escape sequences in string and regexp literals

2015-01-02 Thread Claude Pache
Le 2 janv. 2015 à 22:08, Caitlin Potter caitpotte...@gmail.com a écrit : (...) More important, octal escape sequences are a bit liberal, in that they can be of several lengths, with a pretty wide range of delimiters. This, I think, results in many cases where octal escape sequences are

Re: Implicit coercion of Symbols

2015-01-02 Thread Axel Rauschmayer
One reason it might make sense to throw, is people converting values to string names for use as object properties. Reason you'd want to throw would be to prevent accidentally making the key useless (different from its original Symbol value). This is exactly the reason. Of course,

Implicit coercion of Symbols

2015-01-02 Thread Rick Waldron
Kyle Simpson brought this up on Twitter today and I think it deserves one last look. Here's an example of the issue: var sym = Symbol(description); sym + ; // Throws Meanwhile... var sym = Symbol(description); String(sym); // Symbol(description) * (* appears to be the convention that

Re: Implicit coercion of Symbols

2015-01-02 Thread Brendan Eich
Caitlin Potter wrote: One reason it might make sense to throw, is people converting values to string names for use as object properties. Reason you'd want to throw would be to prevent accidentally making the key useless (different from its original Symbol value). This is exactly the reason.

Re: Implicit coercion of Symbols

2015-01-02 Thread Boris Zbarsky
On 1/2/15 9:33 PM, Axel Rauschmayer wrote: Do people ever compose a property key for an object out of several pieces? On the web? All the time. -Boris ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Implicit coercion of Symbols

2015-01-02 Thread Boris Zbarsky
On 1/2/15 9:40 PM, Axel Rauschmayer wrote: Can you give an example? get: function( num ) { return num != null ? // Return just the one element from the set ( num 0 ? this[ num + this.length ] : this[ num ] ) :

RE: Why does Symbol.for and Symbol.keyFor are limited to strings?

2015-01-02 Thread Gary Guo
Why not? Symbol's [[Description]] internal slot is string Date: Fri, 2 Jan 2015 18:18:55 +0100 Subject: Why does Symbol.for and Symbol.keyFor are limited to strings? From: michalwa...@gmail.com To: es-discuss@mozilla.org What is reason behind restricting entries in global symbol registry

Re: Implicit coercion of Symbols

2015-01-02 Thread Axel Rauschmayer
Can you give an example? On 03 Jan 2015, at 03:34, Boris Zbarsky bzbar...@mit.edu wrote: On 1/2/15 9:33 PM, Axel Rauschmayer wrote: Do people ever compose a property key for an object out of several pieces? On the web? All the time. -Boris