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
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
-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 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
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
-Original Message-
From: es-discuss-boun...@mozilla.org [mailto:es-discuss-
boun...@mozilla.org] On Behalf Of Mike Shaver
Sent: Tuesday, October 13, 2009 4:05 PM
To: David-Sarah Hopwood
Cc: es-discuss@mozilla.org
Subject: Re: Strategies for standardizing mistakes
On Tue, Oct 13, 2009 at 7
On 10/13/2009 04:05 PM, Mike Shaver wrote:
On Tue, Oct 13, 2009 at 7:01 PM, David-Sarah Hopwood
david-sa...@jacaranda.org wrote:
I agree with Maciej. The implementation-defined operations have clear
specifications of their parameters. I think that it is highly undesirable
to adopt an
One could characterize the difference by saying that Mozilla has
reluctant properties whereas WebKit has reluctant values. :)
In other words, in WebKit, 'document.all' has a value --- a value that
can be assigned to other variables, stored in data structures, and so on
without changing its
On Wed, Oct 14, 2009 at 7:40 PM, Jim Blandy j...@mozilla.com wrote:
There's one specific kind of contextual information that's being looked at
askance here: knowledge of the expression surrounding the call that invoked
you. Perl lets subroutines check what sort of value their caller is
Brendan Eich wrote:
On Oct 12, 2009, at 12:23 AM, Maciej Stachowiak wrote:
I don't want to get too deep into this, but I question the claim that
[Mozilla document.all] is technically compatible with ES5. Yes, it's
possible for a host object to return any value at any time for a property
14 matches
Mail list logo
