Re: private name objects confusion

2011-07-28 Thread David Herman
Yep. Sorry, editing snafu -- I'd started to call it a non-issue when it occurred to me that proxy authors would still have to know not to string coerce keys. No big deal -- proxy authors should know better than to rely on es5 invariants. Agreed. Throw at the point where a unique name

Re: July TC39 meeting notes, day 1

2011-07-28 Thread David Bruant
Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Proxy handler traps need to receive the proxy as a parameter: first, or last? Last allows trap implementors to leave |proxy| off. It's also a compatible extension to the proposal and its prototype implementations.

Adding methods to {Array,String}.prototype

2011-07-28 Thread Axel Rauschmayer
In general, I’m strongly in favor of adding more methods to these prototypes. I have always been impressed by how many useful data manipulation features were in the standard libraries of functional languages (e.g. Haskell) and in scripting languages such as Python. JavaScript should have more

Re: July TC39 meeting notes, day 1

2011-07-28 Thread David Bruant
Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Another alternative: the proxy could be passed via a data property on the handler. But the only use for the proxy reference is as a key in a weakmap, and if the handler references it, the handler could just as well be

Re: July TC39 meeting notes, day 1

2011-07-28 Thread Juan Ignacio Dopazo
On Thu, Jul 28, 2011 at 1:21 AM, Brendan Eich bren...@mozilla.com wrote: Math functions ... Can I add a request? Math.randomInt(n) returning [0, n) would be a nice addition. Additionally but not necessarily, it could accept an optional extra parameter for Math.randomInt(from, to). Most of the

Re: July TC39 meeting notes, day 1

2011-07-28 Thread Andreas Rossberg
On 28 July 2011 10:35, David Bruant david.bru...@labri.fr wrote: Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Proxy handler traps need to receive the proxy as a parameter: first, or last? Last allows trap implementors to leave |proxy| off. It's also a

Re: July TC39 meeting notes, day 1

2011-07-28 Thread David Bruant
Le 28/07/2011 19:52, Andreas Rossberg a écrit : On 28 July 2011 10:35, David Bruant david.bru...@labri.fr wrote: Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Proxy handler traps need to receive the proxy as a parameter: first, or last? Last allows trap

Re: July TC39 meeting notes, day 1

2011-07-28 Thread Brendan Eich
On Jul 28, 2011, at 1:35 AM, David Bruant wrote: Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Proxy handler traps need to receive the proxy as a parameter: first, or last? Last allows trap implementors to leave |proxy| off. It's also a compatible extension

Re: July TC39 meeting notes, day 1

2011-07-28 Thread Andreas Rossberg
On 28 July 2011 20:34, David Bruant david.bru...@labri.fr wrote: Le 28/07/2011 19:52, Andreas Rossberg a écrit : On 28 July 2011 10:35, David Bruant david.bru...@labri.fr wrote: Le 28/07/2011 06:21, Brendan Eich a écrit : == Handler access to proxies == Proxy handler traps need to receive

Re: Wanted: standard Array function to append an array's elements to another array

2011-07-28 Thread Jeff Walden
On 07/27/2011 10:12 PM, Mark S. Miller wrote: We could debate the pros and cons of this sort of chaining convention in general. However, in this case I think the more important issue is API consistency. I was thinking this might actually be more consistent, to return this. Consider

Re: Wanted: standard Array function to append an array's

2011-07-28 Thread Jeff Walden
On 07/27/2011 01:26 PM, John-David Dalton wrote: @Jeff In reply to https://mail.mozilla.org/pipermail/es-discuss/2011-July/016124.html, which engines have problems with `firstArray.push.apply(firstArray, secondArray)` ? Shouldn't a bug report be filed for the specific JS engine or the spec be