On Tue, Mar 24, 2009 at 1:17 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Mar 23, 2009 at 4:16 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 23 Mar 2009, Jonas Sicking wrote:
And that's not even touching on the stack space limitations that you're
quite likely to run in to when you
On Tue, 24 Mar 2009, Robert O'Callahan wrote:
I think a better construct might be some sort of yield which
explicitly returns to a (nested) browser event loop and basically acts
as a script completion point. Even browsers that only use a single
thread can run the event loop there so that
On Mon, Mar 23, 2009 at 2:45 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 24 Mar 2009, Robert O'Callahan wrote:
I think a better construct might be some sort of yield which
explicitly returns to a (nested) browser event loop and basically acts
as a script completion point. Even browsers that
On Mon, 23 Mar 2009, Jonas Sicking wrote:
And that's not even touching on the stack space limitations that you're
quite likely to run in to when you have an API specifically for nesting.
I think any sane implementation of this would have to be non-recursive.
That's part of why I think it'd
On Mon, Mar 23, 2009 at 4:16 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 23 Mar 2009, Jonas Sicking wrote:
And that's not even touching on the stack space limitations that you're
quite likely to run in to when you have an API specifically for nesting.
I think any sane implementation of this
