two things invokedynamic canbot do

[Rémi Forax]

On 06/26/2012 02:24 PM, Jochen Theodorou wrote:
> Am 26.06.2012 13:37, schrieb Julien Ponge:
>> You may bypass the invokespecial <init>(…)V as a first method
>> invocation within a constructor requirement by launching the JVM with
>> -noverify. As long as you don't do anything stupid in the bytecode it
>> will be just ok and you can call a constructor using indy.
>>
>> Anyway I confess that disabling verification is probably not what you
>> want ;-)
> That is indeed not really what I want ;) No, seriously... we want to be
> able to use Groovy classes in an environment not under our control, even
> in a application server. For those things -noveriffy is surely no option.
>
> bye Jochen
>

BTW, It's usually better to use unsafe.defineClass() than noverify
because you can just ask to not verify some classes.

cheers,
Rémi