- From: Oliver Hunt <oliver@apple.com>
- Date: Sat, 26 Sep 2009 16:41:44 -0700
- To: Mark S. Miller <erights@google.com>
- Cc: Cameron McCormack <cam@mcc.id.au>, Brendan Eich <brendan@mozilla.com>, "public-webapps@w3.org" <public-webapps@w3.org>, Doug Schepers <schepers@w3.org>, HTML WG <public-html@w3.org>, es-discuss <es-discuss@mozilla.org>
The specific problem is that host objects cannot necessarily match the semantics of ES5, and for that reason the interaction of host objects with the ES5 semantics is unclear. There are additional concerns -- various es5 features expose the underlying implementation mechanisms of the binding -- for instance using get or set properties on a dom binding would require getOwnPropertyDescriptor to expose that implementation detail. --Oliver On Sep 26, 2009, at 4:00 PM, Mark S. Miller wrote: > On Sat, Sep 26, 2009 at 3:48 PM, Oliver Hunt <oliver@apple.com> wrote: >> I would avoid depending on ES5 until there are multiple realworld >> implementations at least, especially because >> the interaction between the es5 meta-object functionality and host >> objects >> is less than clear at present. > > Hi Oliver, it is precisely the need to clarify this interaction, as > you pointed out in some of your previous posts to es-discuss, that got > us to focus on the need for greater coordination at the last > EcmaScript meeting. Since, as you say, this interaction is currently > unclear, isn't this exactly the kind of problem our standards bodies > should be trying to resolve? > > -- > Cheers, > --MarkM
Received on Saturday, 26 September 2009 23:42:48 UTC