JSR 292 support, minor change to specification

[Rémi Forax]

Hi John,
for item 1.3, I think that defaulting to Object is rough.
Knowing that the diamond operator uses the type of the lhs part of an 
assignation
I wonder if Invokedynamic.foo if no return type is specified should not 
use the same algorithm.

int i = Invokeynamic.foo(2);

should be encoded as invokedynamic (I)I

Rémi


Le 22/04/2010 21:11, John Rose a écrit :
> The JSR 292 EG has made a minor naming change to the signature-polymorphic methods that Java needs to recognize for JSR 292.  I've updated the wiki page, and have enclosed the changed specification here for the record.
>
> http://wikis.sun.com/display/mlvm/InterfaceDynamic (also enclosed)
>
> Key changes to the document:
>
> 1. Split MH.invoke into MH.invokeExact and MH.invokeGeneric, per EG request.
> 2. Specify an explicit marking for these methods, and the InvokeDynamic class, in source code and class files.
> 3. Discuss briefly alternatives to signature polymorphic invocation as currently specified.
> 4. Added a brief discussion about the syntax of exotic identifiers.
>
> Item 1 is the language change.  Item 2 uses an annotation to make the required mark, which is a related language change, but not one which affects any user, since the annotation is private to the java.dyn package.  The main impact is on tools, which may prefer to use the explicit marking instead of matching names.  Items 3 and 4 are rationale.
>
> Best wishes,
> -- John
>
>    
>
>
>
>