Here is an update on the method handle cracking API.
Though we will probably make some small adjustments, it appears to be
converging.
http://cr.openjdk.java.net/~jrose/8008688/specdiff.02/
http://cr.openjdk.java.net/~jrose/8008688/javadoc.02/
Key points:
- interface MethodHandleInfo (MHI)
Changeset: eabaf978d9ee
Author:jrose
Date: 2013-05-14 22:58 -0700
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/eabaf978d9ee
rebase; split and update meth-info-8008688.patch
+ meth-doc-8014634.patch
! meth-info-8008688.patch
! meth.patch
! series
Hi John,
I peeked at the implementation of HMI.asMember method:
111 +// Helper for default MethodHandleInfo.asMember.
112 +static Member reflectMember(MethodHandleInfo self)
throws ReflectiveOperationException {
113 +int mods = self.getModifiers();
Thanks for looking at that, Peter. You are right. The asMember call needs more
checks and less trust.
-- John (on my iPhone)
On May 15, 2013, at 2:39 AM, Peter Levart peter.lev...@gmail.com wrote:
f MHI objects are not considered security sensitive tokens like MH objects,
then perhaps
Just for my learning, what is the use model for this form of method
handle inspection?
Is there some cool technique that this facilitates?
regards
mark___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
On 05/15/2013 07:27 PM, Mark Roos wrote:
Just for my learning, what is the use model for this form of method
handle inspection?
Is there some cool technique that this facilitates?
yes,
if you crack a method handle, you get the reference to a method (the
constructor etc.)
so you can by
On May 15, 2013, at 10:27 AM, Mark Roos mr...@roos.com wrote:
Just for my learning, what is the use model for this form of method handle
inspection?
What Remi said...
Is there some cool technique that this facilitates?
Yes. A bootstrap method receives 3 required arguments, a Lookup,