On 27/03/2008, Lukas Stadler <[EMAIL PROTECTED]> wrote: > This could lead to all sorts of harmful behavior, like exiting a > monitor twice, etc. Should this be possible, or will only a > restricted case be implemented? There would have to be a big red > sign (and possibly some kind of verifier) with all the things that > aren't allowed in such code. > I recently looked at the apache commons Javaflow library - they > implement storing the current stack state using only bytecode > instrumentation and a small and unintrusive runtime framework. (I > can write a short summary of how they're doing this if anyone is > interested.) I think that, as their implementation is inherently > safe, we could partly adopt its behaviour.
Hi Lukas, I'd like to hear how the Javaflow works at the byte level and what they do with monitor entry/exit. I assume they implement multi-shot continuations? Cheers, Steve. _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
