« Return to Thread: Groovy runs code in static initializers during compile

Re: Groovy runs code in static initializers during compile

by Aaron Digulla :: Rate this Message:

Reply to Author | View in Thread

Quoting Charles Oliver Nutter <charles.nutter@...>:

>> hmm... I am currently asking myself if we need to resolve the  
>> classes we create when we compile. I know I had once a strange  
>> problem with this, but I think that was with the ReflectorLoader,  
>> which is very special anyway.
>>
>> hmm... the build seems to be ok with that change...
>
> You shouldn't need to resolve them. JRuby's compiler just leaves them
> as byte[] and dumps them to disk without ever loading them.

Maybe this code was added because the Groovy compiler sometimes  
generates illegal bytecode? I've seen a few cases where a classfile  
couldn't be verified even though Groovy could compile it.

Just wondering: Wouldn't it be more smart to verify the class *before*  
writing it to a .class file instead of verifying it every time it is  
loaded? There is probably a very good reason to do that ... ;-)

Regards,

--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

 « Return to Thread: Groovy runs code in static initializers during compile