W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2014

Re: Associating new objects with globals: how to best do it?

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 25 Feb 2014 20:51:29 -0500
Message-ID: <530D48A1.7020704@mit.edu>
To: Allen Wirfs-Brock <allen@wirfs-brock.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>, Bobby Holley <bholley@mozilla.com>
On 2/25/14 7:14 PM, Allen Wirfs-Brock wrote:
> Note that the %foo% notation means the "foo" intrinsic (built-in object) associated with the Realm of the currently active function.

Sure.

> Really? The callback function that will ultimately be invoked has a Realm association

The point was that the argument to that function needs to be created 
before the function is called, which means that it needs to be created 
outside of any obviously running functions.  At least as far as I can tell.

> Take a look at section 8.3 (Tasks and Task Queues) in the latest ES6 draft.

Yes, this is exactly the sort of setup I'm talking about being needed, 
and this is clearly neither a function or global script.  ;)  This setup 
specific to ES tasks, of course; the DOM just needs to either do 
something similar or use ES tasks for its async work if that's feasible.

Looks like we agree yet again: the execution of async steps should use 
the Realm that was current when the async bit was queued.

-Boris
Received on Wednesday, 26 February 2014 01:52:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:51 UTC