Kohsuke Kawaguchi wrote:
Torsten Curdt wrote:
I don't think I understand the instrumentation logic completely,
but from a cursory look, the idea is to evaluate constructor
parameters before the 'new' op (and StackRecorder is used as a
temporary place to store evaluated objects.)
That's
I don't think I understand the instrumentation logic completely,
but from a cursory look, the idea is to evaluate constructor
parameters before the 'new' op (and StackRecorder is used as a
temporary place to store evaluated objects.)
That's true ...Stephan introduced that
to get rid of
Torsten Curdt wrote:
I don't think I understand the instrumentation logic completely,
but from a cursory look, the idea is to evaluate constructor
parameters before the 'new' op (and StackRecorder is used as a
temporary place to store evaluated objects.)
That's true ...Stephan
I've been playing with javaflow and noticed the following.
Suppose I have the following code:
File root = new File(data);
This compiles into the following bytecode:
// local variable 0 is this
// local variable 1 is root
0 new java/io/File
3 dup
4 ldc data
