Also note that the same Runnable object is normally kept in the ostack as well, as most of the time local variable #0 is used for the 'this' variable.IMO, this makes it somewhat useless to introduce the 'runnable' variable,as you won't be able to change it and expect that the stack restorescorrectly --- the only thing you'll be able to do is to inspect the value,which could be just as well done by defining the 'getRunnable' method that checks for the top of the rstack.
An explicit runnable makes it possible to start the stack recording further down the call stack. We need this for cocoon were the Invoker is not being instrumented. So the runnable should not really be on the stack. cheers -- Torsten
PGP.sig
Description: This is a digitally signed message part
