Re: possible excessive proxy invariants for Object.keys/etc??

2012-11-24 Thread Mark S. Miller
+1. I think this is a really effective extension of the direct proxy approach, and I don't know why we didn't see it earlier. It's weird that this preserves all the flexibility of fully virtual configurable properties even though it insists that even these be made into real properties on the target

Re: possible excessive proxy invariants for Object.keys/etc??

2012-11-24 Thread Dean Tribble
I am looking forward to proxies in JavaScript, and had a thought on the issues below. You could extend the the "direct proxy" approach for this. When the Proxy receives getOwnPropertyNames, it 1) notifies the handler that property names are being requested 2) the handler adds/removes any properti

Re: New ES6 draft now available

2012-11-24 Thread Brendan Eich
David Bruant wrote: Hi, I haven't been following very closely some of the most recent discussions, so I appologize if my comments have been addressed already Le 23/11/2012 18:48, Allen Wirfs-Brock a écrit : Changes include: • Reorganized Chapter 8 into separate language type and specificati

Re: A new function name property proposal

2012-11-24 Thread Brendan Eich
Jorge Chamorro wrote: On 24/11/2012, at 07:14, Brendan Eich wrote: Programmers do intentionally replace a function's name in its scope, e.g. to auto-memoize. Oh, how does that work? I've written memoizers but never needed to overwrite a name. http://osteele.com/posts/2006/04/one-line-javascr

Leap second clarification

2012-11-24 Thread Yusuke Suzuki
Hello, About 4 months ago, a leap second is inserted. And it reveals that there are many implementation diversity for leap seconds. For example, JavaScriptCore accepts the leap second in Date#toString format[1], but rejects it in ISO 8601 format. On the other hand, SpiderMonkey rejects it in Date

Re: The ES6 MOP (Was: New ES6 draft now available)

2012-11-24 Thread Allen Wirfs-Brock
On Nov 24, 2012, at 9:54 AM, David Bruant wrote: > Le 24/11/2012 18:10, Allen Wirfs-Brock a écrit : >>> * [[Enumerate]], [[Keys]] and [[OwnPropertyKeys]] are very close operations >>> * So are [[PreventExtensions]]/[[Freeze]]/[[Seal]] on one side and >>> [[IsExtensible]]/[[IsFrozen]]/[[IsSealed]

Re: A new function name property proposal

2012-11-24 Thread Jorge Chamorro
On 24/11/2012, at 07:14, Brendan Eich wrote: > Jorge Chamorro wrote: >> >> >> Bind the name inside the function *too*. > > That's not a compatible change, and unmotivated by any actual foot damage. > >> The footgun (1) is to have the name bound *only* in the outer scope. > > We need evidence t

Re: The ES6 MOP (Was: New ES6 draft now available)

2012-11-24 Thread David Bruant
Le 24/11/2012 18:10, Allen Wirfs-Brock a écrit : * [[Enumerate]], [[Keys]] and [[OwnPropertyKeys]] are very close operations * So are [[PreventExtensions]]/[[Freeze]]/[[Seal]] on one side and [[IsExtensible]]/[[IsFrozen]]/[[IsSealed]] I'm afraid that making them distinct operations increases

Re: New ES6 draft now available

2012-11-24 Thread Allen Wirfs-Brock
On Nov 24, 2012, at 8:43 AM, David Bruant wrote: > Le 24/11/2012 14:58, Axel Rauschmayer a écrit : • MOP changes: Added [[GetInheritance]]/[[SetInheritance]] as internal methods for accessing [[Prototype]] internal prototype chain. >>> Why not [[GetPrototype]] and [[SetPrototype]]? We

Re: New ES6 draft now available

2012-11-24 Thread Allen Wirfs-Brock
On Nov 24, 2012, at 6:23 AM, Herby Vojčík wrote: > > > David Bruant wrote: >> >> Hi, >> >> I haven't been following very closely some of the most recent >> discussions, so I appologize if my comments have been addressed already >> >> Le 23/11/2012 18:48, Allen Wirfs-Brock a écrit : >>> Chang

The ES6 MOP (Was: New ES6 draft now available)

2012-11-24 Thread Allen Wirfs-Brock
(Changing Subject to better identify what is probably an important topic.) On Nov 24, 2012, at 5:31 AM, David Bruant wrote: > Hi, > > I haven't been following very closely some of the most recent discussions, so > I appologize if my comments have been addressed already (The "possible excessi

Re: New ES6 draft now available

2012-11-24 Thread David Bruant
Le 24/11/2012 14:58, Axel Rauschmayer a écrit : • MOP changes: Added [[GetInheritance]]/[[SetInheritance]] as internal methods for accessing [[Prototype]] internal prototype chain. Why not [[GetPrototype]] and [[SetPrototype]]? We have a absurd number of excellent resources (including but not li

Re: New ES6 draft now available

2012-11-24 Thread David Bruant
Le 24/11/2012 15:23, Herby Vojčík a écrit : David Bruant wrote: Hi, I haven't been following very closely some of the most recent discussions, so I appologize if my comments have been addressed already Le 23/11/2012 18:48, Allen Wirfs-Brock a écrit : Changes include: • MOP changes: Added

Re: New ES6 draft now available

2012-11-24 Thread Herby Vojčík
David Bruant wrote: Hi, I haven't been following very closely some of the most recent discussions, so I appologize if my comments have been addressed already Le 23/11/2012 18:48, Allen Wirfs-Brock a écrit : Changes include: • MOP changes: Added [[GetInheritance]]/[[SetInheritance]] as inte

Re: New ES6 draft now available

2012-11-24 Thread Axel Rauschmayer
>> • MOP changes: Added [[GetInheritance]]/[[SetInheritance]] as internal >> methods for accessing [[Prototype]] internal prototype chain. > Why not [[GetPrototype]] and [[SetPrototype]]? We have a absurd number of > excellent resources (including but not limited to Dmitry Soshnikov and Axel >

Re: New ES6 draft now available

2012-11-24 Thread David Bruant
Hi, I haven't been following very closely some of the most recent discussions, so I appologize if my comments have been addressed already Le 23/11/2012 18:48, Allen Wirfs-Brock a écrit : Changes include: . Reorganized Chapter 8 into separate language type and specification type sub sections