unreflectGetter and static class initialization
John Rose
john.r.rose at oracle.com
Wed Oct 24 15:32:50 PDT 2012
On Oct 24, 2012, at 1:08 PM, Jochen Theodorou wrote:
> what do you suggest as workaround?
You could force the class to be initialized when the MH is created. This can be done with Class.forName. It would not exactly give you the semantics you want, since the init would happen early.
Or, you could wrap the buggy MH in a MH which first forces initialization. With a switchpoint you can make it a once-only event (per thread, at least).
— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20121024/1b258b7a/attachment.html
More information about the mlvm-dev
mailing list