ES Discuss - Message History

Norbert Lindenberg (2013-12-12T02:47:59.000Z)

Go to Source

On Dec 11, 2013, at 11:43 , Allen Wirfs-Brock <allen at wirfs-brock.com> wrote:

> So why didn't the first edition of ECMA-402 provide a new definition for Array.prototype.toLocaleString?  Was that intentional or an oversight?

I don't remember it ever coming up in our discussions, so an oversight, or negligence.

> It think it should and it should probably do so in a new edition of 402 that is released simultaneously with ES6  (there are probably a few other minor ES6 related cleanups that should also be incorporated).  Then ES6 could handle A.p.toLocaleString exactly like it is handling N.p.toLocaleString and D.p.toLocaleString.

Sounds reasonable; I've filed
https://bugs.ecmascript.org/show_bug.cgi?id=2383.

There is a ticket already for alignment of ECMA-402 with ES6 in general; if you come across additional cleanups needed, please add them:
https://bugs.ecmascript.org/show_bug.cgi?id=1260

> WRT O.p.toLocaleString it is essentially a fall back implementation for objects that don't have any locale specific toString behavior. I don't think it should every be over-ridden by ECMA-402.  Since that default  implementation doesn't use the arguments, I don't know if there is any need to specify them.  Perhaps I should provide a NOTE that essentially says this. 

The note should probably mention that there are overrides that expect specific parameter values for the first two parameters.

Thanks,
Norbert

domenic at domenicdenicola.com (2013-12-18T03:38:03.519Z)

On Dec 11, 2013, at 11:43 , Allen Wirfs-Brock <allen at wirfs-brock.com> wrote:

> So why didn't the first edition of ECMA-402 provide a new definition for Array.prototype.toLocaleString?  Was that intentional or an oversight?

I don't remember it ever coming up in our discussions, so an oversight, or negligence.

> It think it should and it should probably do so in a new edition of 402 that is released simultaneously with ES6  (there are probably a few other minor ES6 related cleanups that should also be incorporated).  Then ES6 could handle A.p.toLocaleString exactly like it is handling N.p.toLocaleString and D.p.toLocaleString.

Sounds reasonable; I've filed
https://bugs.ecmascript.org/show_bug.cgi?id=2383.

There is a ticket already for alignment of ECMA-402 with ES6 in general; if you come across additional cleanups needed, please add them:
https://bugs.ecmascript.org/show_bug.cgi?id=1260

> WRT O.p.toLocaleString it is essentially a fall back implementation for objects that don't have any locale specific toString behavior. I don't think it should every be over-ridden by ECMA-402.  Since that default  implementation doesn't use the arguments, I don't know if there is any need to specify them.  Perhaps I should provide a NOTE that essentially says this. 

The note should probably mention that there are overrides that expect specific parameter values for the first two parameters.

Edit