Re: method handle cracking API

2013-04-25 Thread Remi Forax
On 04/25/2013 05:18 AM, John Rose wrote: > On Apr 24, 2013, at 7:45 PM, Mark Roos > wrote: > >> Any chance that one could walk the GWT chain from a call site in >> order to build >> a different look up structure or maybe even some specialized code? >> Currently I >> keep t

Re: method handle cracking API

2013-04-25 Thread Remi Forax
On 04/25/2013 08:39 PM, John Rose wrote: > On Apr 25, 2013, at 8:58 AM, "MacGregor, Duncan (GE Energy > Management)" > wrote: > >> I would have thought one of the most common uses of breaking down a >> method >> handle like this would be to immediately turn it int

Re: method handle cracking API

2013-04-25 Thread Mark Roos
Duncan suggested: return the parts that remain (both method handles and bound objects) as I would guess that would be enough for debugging purposes and resource leak hunting. I think that if I could just get a collection of the bound objects in the chain that would be enough to do what I want as

Re: method handle cracking API

2013-04-25 Thread John Rose
On Apr 25, 2013, at 8:58 AM, "MacGregor, Duncan (GE Energy Management)" wrote: > I would have thought one of the most common uses of breaking down a method > handle like this would be to immediately turn it into a java.lang.reflect > object and maybe examine annotations or exception information.

Re: method handle cracking API

2013-04-25 Thread John Rose
On Apr 25, 2013, at 9:42 AM, Christian Thalinger wrote: > John and I referred to this method yesterday as: Lookup.ununreflect() Or perhaps Lookup.rereflect() or Lookup.visitHallOfMirrors(). — John___ mlvm-dev mailing list mlvm-dev@openjdk.java.net ht

Re: method handle cracking API

2013-04-25 Thread Christian Thalinger
On Apr 25, 2013, at 8:58 AM, "MacGregor, Duncan (GE Energy Management)" wrote: > I would have thought one of the most common uses of breaking down a method > handle like this would be to immediately turn it into a java.lang.reflect > object and maybe examine annotations or exception information

Re: method handle cracking API

2013-04-25 Thread MacGregor, Duncan (GE Energy Management)
I would have thought one of the most common uses of breaking down a method handle like this would be to immediately turn it into a java.lang.reflect object and maybe examine annotations or exception information. So although I don't think it should extend Member I do think it should have a standard

Re: method handle cracking API

2013-04-25 Thread Mark Roos
>From John Simple example: Suppose you have a tree of GWTs that a clever implementation compiles into a big hunk of bytecode Actually that would be my dream, that hotspot is clever and I can just let it do the work. Is it? mark___