You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MethodCallMethodVisitor has one draw back/problem: In a constructor it cannot mutate creations of the super class as they do not differ from the own constructor call:
does not result in any mutation because the visitor cannot distinguish
between "super()" and "new B()". I don't have a solution to this
problem. Both method calls can only be distinguished by their
context/position.
A use case for that issue would be an object used as lock:
publicclassMyThreadSafeClass { // note: extends java.lang.ObjectprivatefinalObjectlock;
publicMyThreadSafeClass() {
super();
this.lock = newObject();
}
// some code using lock in synchronized blocks
}
From stefan.p...@googlemail.com on February 29, 2012 21:43:38
The MethodCallMethodVisitor has one draw back/problem: In a constructor it cannot mutate creations of the super class as they do not differ from the own constructor call:
does not result in any mutation because the visitor cannot distinguish
between "super()" and "new B()". I don't have a solution to this
problem. Both method calls can only be distinguished by their
context/position.
A use case for that issue would be an object used as lock:
Original issue: http://code.google.com/p/pitestrunner/issues/detail?id=34
The text was updated successfully, but these errors were encountered: