On 03/15/2011 08:58 AM, Jochen Theodorou wrote:
> Hi all,
Hi Jochen,
> assuming I have a method call x.foo(a,b), where x is of class X, a of
> class A and b of class B. And let us assume I will create a MethodHandle
> MH: X#foo(A,B). Is it now the case, that unless I don't keep a hard
> reference
Thanks for the update, Stephen.
I'm trying to update to the latest bsd-port, but the build there is broken.
This is delaying normal fixes to the mlvm patch queue.
A bit of good news: In the mea time, the 6839872 and 7012648 patches for the
JVM have been pushed to jdk7/hotspot-comp/hotspot and
There were two updates to jdk I just pulled in but I am still getting 2 passing
and four failing tests for mlvm:
Passed: java/lang/invoke/ClassValueTest.java
FAILED: java/lang/invoke/InvokeDynamicPrintArgs.java
FAILED: java/lang/invoke/InvokeGenericTest.java
FAILED: java/lang/invoke/JavaDocExampl
Hi all,
assuming I have a method call x.foo(a,b), where x is of class X, a of
class A and b of class B. And let us assume I will create a MethodHandle
MH: X#foo(A,B). Is it now the case, that unless I don't keep a hard
reference to MH anymore, that X, A and B cannot be garbage collected?
If I