On Tue, Mar 24, 2009 at 1:17 PM, Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Mon, Mar 23, 2009 at 4:16 PM, Ian Hickson <ian@hixie.ch> wrote:<br>
> On Mon, 23 Mar 2009, Jonas Sicking wrote:<br>
>><br>
>> And that's not even touching on the stack space limitations that you're<br>
>> quite likely to run in to when you have an API specifically for nesting.<br>
><br>
> I think any sane implementation of this would have to be non-recursive.<br>
> That's part of why I think it'd be so hard to implement.<br>
<br>
</div>Indeed, that'd be really hard to implement in the generic case. For<br>
example a navigator.yield() inside an event handler, or inside a<br>
callback.<br>
<br>
We'd basically have to redesign all the code that implements the DOM<br>
and all other APIs that are exposed to javascript.<br>
<br>
Or rewrite our code in a language that supports continuations, which<br>
C/C++ doesn't do. (no, setjmp and longjmp doesn't count :) ).<br></blockquote><div><br>Not necessarily, it depends on the semantics. For example, you might retain the option for "yield" to do nothing (i.e. it offers no liveness guarantees). In that case you would have the option of not yielding in difficult situations like event handlers or callbacks, or if recursion gets too deep. Or a spec could say which script executions allow yielding and which don't.<br>
</div></div><br clear="all">Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>