Oops, belay that, didn't see the followup email -- modifications in that email
look fine.
Jeff
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On 3.8.09 18:39 , Allen Wirfs-Brock wrote:
Such a property would have pretty much the same effect as
Object.defineProperty(obj, propname, { value: undefined})
which creates a readonly, nonenumerable, nonconfigurable property whose value
is undefined. There isn't much (if any, I need to look a
On 31.7.09 08:47, Allen Wirfs-Brock wrote:
javascript:[].indexOf(2,{valueOf: function() {alert(valueof); return -1}})
My quick experiments show that Firefox (3.5.1) does the early exit as currently
spec'ed by ES5 while Chrome (2.0.172.37), Safari (4.0), and Opera (
9.63) exhibit the
Brendan asked me yesterday to look at and comment on the array extras methods
as they exist in ES5, since things are being finalized yesterday and today.
(I'm not sure whether yesterday was the latest to make these comments or
whether today is also acceptable; unfortunately Black Hat
In Array's [[DefineOwnProperty]], what is the rationale for calling the default
[[DefineOwnProperty]] with a Throw argument specified as false, rather than the
Throw provided to the initial call?
In step 6, does same value mean the SameValue spec operation? If so the
expected notation should
I'm working on implementing Object.defineProperty now, so I'm spending some
quality time with ToPropertyDescriptor and [[DefineOwnProperty]].
I find the arcane structure of property descriptors[0], which have a fixed set
of named fields but which might end up omitting any of those fields, very
101 - 106 of 106 matches
Mail list logo
