2008/6/24 John Rose <<a href="mailto:John.Rose@sun.com">John.Rose@sun.com</a>>:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div>It would be great if we had really lightweight continuations, with a JVM scheduler (Scheme calls them engines, I think) which keeps running the next one. The part I can't see yet is how to make stack-based and heap-based activation records play together efficiently. (Maybe you JIT two versions of every method, with inlining to remove overheads as usual?)</div>
</div></blockquote><div><br>Is it disastrous for performance to heap allocated all activations? Perhaps it could be an JVM option. Perhaps activations could be abstractly considered "heap allocated" and have the JVM stack allocated when possible.<br>
<br>Is the much research in this area?<br><br>Cheers,<br>Steve.<br></div></div>