On 10/14/2009 06:36 PM, Mike Shaver wrote:
Our implementation of String.prototype.match checks the context in
which it's called, to see if it need bother with the expense of
constructing the result array (it needn't, if the match call is being
used simply as a test, which isn't unheard of on
Operator overloading was discussed here before:
Mark Miller's strawman proposal (double dispatch)
https://mail.mozilla.org/pipermail/es-discuss/2009-January/008535.html
Christian Plesner Hansen's symmetric operator overloading
On 10/15/2009 07:23 AM, Maciej Stachowiak wrote:
The latter, if truly allowed by the spec, makes source-to-source
transformers, even something as simple as a pretty-printer,
potentially unsound. That seems like a much less bounded form of
insanity.
I think this point is well-taken.
In
On 10/15/2009 09:29 AM, Jason Orendorff wrote:
I sort of doubt that everyone who touches the
compiler is even aware of the constraint.
/me tries to look inconspicuous
___
es-discuss mailing list
es-discuss@mozilla.org
I'm not particularly defending IE's legacy enumeration order, we were initially
on board with ES5 adopting the de facto order used by other browsers. My
recollection is that the decision to table defining a strict enumeration order
for ES5 was made after we discovered that Opera for its
-Original Message-
From: es-discuss-boun...@mozilla.org [mailto:es-discuss-
boun...@mozilla.org] On Behalf Of Jim Blandy
...
In the case of 'eval', ES5 requires an implementation to inspect the
context of the call. A direct call to eval runs the code in the call's
environment; indirect
On Oct 15, 2009, at 10:54 AM, Mike Shaver wrote:
On Thu, Oct 15, 2009 at 1:47 PM, Allen Wirfs-Brock
allen.wirfs-br...@microsoft.com wrote:
Is the Mozilla document.all optimization contingent upon the
occurrence of the text document.all?
No, but it's contingent on the property lookup being
On Thu, Oct 15, 2009 at 2:29 PM, Maciej Stachowiak m...@apple.com wrote:
Just as a minor point of technical correction - this will actually alert
not IE in Firefox because the right-hand sign of an assignment is
considered a detecting access. (Just tested to confirm.)
Thank you! I see that I
On Oct 15, 2009, at 10:23 AM, Allen Wirfs-Brock wrote:
I'm not particularly defending IE's legacy enumeration order, we
were initially on board with ES5 adopting the de facto order used by
other browsers. My recollection is that the decision to table
defining a strict enumeration order
On Oct 15, 2009, at 11:31 AM, Mike Shaver wrote:
On Thu, Oct 15, 2009 at 2:29 PM, Maciej Stachowiak m...@apple.com
wrote:
Just as a minor point of technical correction - this will
actually alert
not IE in Firefox because the right-hand sign of an assignment is
considered a detecting
-Original Message-
From: es-discuss-boun...@mozilla.org [mailto:es-discuss-
boun...@mozilla.org] On Behalf Of Maciej Stachowiak
Sent: Thursday, October 15, 2009 7:23 AM
...
On Oct 14, 2009, at 5:04 PM, Jim Blandy wrote:
...
It could just be organizational bias, but reluctant properties
If I recall correct, Opera has a weird behaviour where it follows a
certain predictable ordering - unless you're deleting/removing a
property (or use prototype functions that do that in their operation)
on an object, which radically changes the sorting order in a way that
is only predictable with
On 10/15/2009 02:18 PM, Allen Wirfs-Brock wrote:
Maciej's thought experiment touches upon the fundamental evil of host objects.
In the presence of host objects there is no firm foundation for understanding
the semantics of an ECMAScript program. Adding some additional restrictions on
host
13 matches
Mail list logo
