Am 29.10.2012 17:03, schrieb Christian Thalinger:
[...]
> ...or move to JDK 8 until 7u with an updated 292 is released. Doesn't
> the NoClassDefFoundError bite you anyway?
you want me earnestly to tell the Groovy users that invokedynamic on
JDK7 is useless ;) It is difficult enough to let people
Am 29.10.2012 17:29, schrieb Remi Forax:
[...]
> In my opinion, the best is to use Unsafe.ensureClassInitialized() the
> first time you call the BSM, it should be enough.
That one I did not know so far, interesting. My current work around is
to go with the fallback internal old MOP path... which
Am 29.10.2012 22:13, schrieb Christian Thalinger:
[...]
> What version of Groovy uses JSR 292?
starting Groovy 2.0 you can enable invokedynamic. Though I use it only
for method calls there and the implementation has still many quirks.
Soon we will release Groovy 2.1, in which invokedynamic will
On 10/30/2012 09:59 AM, Jochen Theodorou wrote:
> Am 29.10.2012 17:29, schrieb Remi Forax:
> [...]
>> In my opinion, the best is to use Unsafe.ensureClassInitialized() the
>> first time you call the BSM, it should be enough.
> That one I did not know so far, interesting. My current work around is
>
