Hi,
I created a strawman page to host possible extensions to harmony:proxies:
http://wiki.ecmascript.org/doku.php?id=strawman:proxy_extensions
It currently hosts two extensions:
- enabling proxies to trap instanceof
- standardizing the default no-op forwarding handler
At least the first will be
Jeff Walden:
Check out the ES5 erratum -- steps 5 and 7 have been removed.
http://wiki.ecmascript.org/doku.php
Thank you for the link, but I have some question about this. Now I can
pass array like object with strange length property and this is not
cause an Error. For example:
length = -1;
2010/10/27 Brendan Eich bren...@mozilla.com
David Ungar raised this as a question from the audience after Tom's Proxies
talk at DLS. One would expect no less from David, who indeed cited Self,
which allows more intercession than harmony:proxies enables.
This is not something I'm trying to
The aim has been consistency. All Array generic own methods that explicitly
use the length property have the same behavior:
- Let lenVal be the result of calling the [[Get]] internal method of O with
argument length.
- Let len be ToUint32(lenVal).
Function.prototype.apply now behave the same
In ES5-15.4 is clearly defined what is an index and what conditions must
verify length
A property name P (in the form of a String value) is an array index if and
only if ToString(ToUint32(P)) is equal to P and ToUint32(P) is not equal to
2^32-1
Every Array object has a length property whose
Actually, es5-disc...@mozilla is the preferred place to post such issues. They
have more chance of being lost if you post them here.
Allen
From: es5-discuss-boun...@mozilla.org [mailto:es5-discuss-boun...@mozilla.org]
On Behalf Of Mark S. Miller
Sent: Wednesday, October 27, 2010 10:22 PM
To:
If we assume “Array like object” is an object that can serve as the this value
of the Array.prototype methods then pretty much any object is “Array like”.
The Array.prototype methods generally iterate based upon the value of the this
object’s length property. They use ToUint32 to interpret
Mark S. Miller wrote:
On Wed, Oct 27, 2010 at 7:24 PM, Michael Dyck jmd...@ibiblio.org wrote:
So I'm asking here: what's the best means (and form) for giving feedback
on the ES5 spec to TC39?
This lack of explanation is a serious problem. Thanks for bringing it to
our attention.
I have concerns about weak refs and weak maps, one concern related to
usability, one related to performance bugs, and another other related to
changing the complexity of the GC algorithm.
Usability
Weak maps act as a GC API and in doing so violate GC's greatest strength: the
user does not
On Oct 28, 2010, at 2:10 PM, Hudson, Rick wrote:
I have concerns about weak refs and weak maps, one concern related to
usability, one related to performance bugs, and another other related to
changing the complexity of the GC algorithm.
Hi Rick, your comments are on target, but I'll differ
Hi Brendan,
I think we all agree that EcmaScript, the language, should not contain threads
with shared memory constructs such as locks or transactions. We seem to
disagree as to whether EcmaScript, the implementation, should be multithreaded.
If bridge builders, compiler writers, GC
On Oct 28, 2010, at 5:41 PM, Hudson, Rick wrote:
Hi Brendan,
I think we all agree that EcmaScript, the language, should not contain
threads with shared memory constructs such as locks or transactions. We seem
to disagree as to whether EcmaScript, the implementation, should be
12 matches
Mail list logo
