Re: unreflectGetter and static class initialization

On Oct 24, 2012, at 3:32 PM, John Rose wrote: > On Oct 24, 2012, at 1:08 PM, Jochen Theodorou wrote: > >> what do you suggest as workaround? > > You could force the class to be initialized when the MH is created. This can > be done with Class.forName. It would not exactly give you the seman

Re: unreflectGetter and static class initialization

On 10/29/2012 05:03 PM, Christian Thalinger wrote: > > On Oct 24, 2012, at 3:32 PM, John Rose > wrote: > >> On Oct 24, 2012, at 1:08 PM, Jochen Theodorou wrote: >> >>> what do you suggest as workaround? >> >> You could force the class to be initialized when the MH is

Re: unreflectGetter and static class initialization

I once heard that there might me plans to push Unsafe to the public APIs... Does anybody have informations about this? - Julien Le 29 oct. 2012 à 17:29, Remi Forax a écrit : > On 10/29/2012 05:03 PM, Christian Thalinger wrote: >> >> On Oct 24, 2012, at 3:32 PM, John Rose >

Re: unreflectGetter and static class initialization

On 10/29/2012 05:45 PM, Julien Ponge wrote: > I once heard that there might me plans to push Unsafe to the public APIs... > Does anybody have informations about this? sun.misc.Unsafe is already supported by a lot of Java compatible (or not) environment, so it's a kind of de facto standard. Now,

Re: unreflectGetter and static class initialization

On Oct 29, 2012, at 9:29 AM, Remi Forax wrote: > On 10/29/2012 05:03 PM, Christian Thalinger wrote: >> >> On Oct 24, 2012, at 3:32 PM, John Rose > > wrote: >> >>> On Oct 24, 2012, at 1:08 PM, Jochen Theodorou wrote: >>> what do you suggest as workaround? >>

Re: unreflectGetter and static class initialization

Hi Christian, On Mon, Oct 29, 2012 at 10:13 PM, Christian Thalinger < christian.thalin...@oracle.com> wrote: > [...] > > I'm sure that Jochen will be happy to move to jdk8 but I'm also sure > > that all Groovy users will not be happy to do the same :) > > What version of Groovy uses JSR 292? > G