On Oct 22, 2010, at 4:03 AM, Helmut Eller wrote:
> Why is the name a required and not an optional argument?
The name is part of the fixed structure of CONSTANT_InvokeDynamic, which is
modeled on CONSTANT_Methodref, and therefore contains a CONSTANT_NameAndType.
Whether you want the name or not
* John Rose [2010-10-22 08:43] writes:
> MethodHandle myBSM(MethodHandles.Lookup look, String name, MethodType type);
> MethodHandle myBSM(MethodHandles.Lookup look, String name, MethodType type,
> Object arg);
> MethodHandle myBSM(MethodHandles.Lookup look, String name, MethodType type,
>
On Oct 22, 2010, at 2:19 AM, Rémi Forax wrote:
> And also:
>
> CallSite myBSM(MethodHandles.Lookup look, String name, MethodType type);
> CallSite myBSM(MethodHandles.Lookup look, String name, MethodType type,
> Object arg);
> CallSite myBSM(MethodHandles.Lookup look, String name, MethodTy
Le 22/10/2010 10:43, John Rose a écrit :
> Based partly on our discussions at the Summit about "live constants", and
> also based on the likely requirements of Project Lambda, the JSR 292 EG is
> likely to allow any single invokedynamic instruction to pass one or more
> extra constant values i
