[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-dev
Subject:    Re: [groovy-dev] compiled reflector for GeneratedClosure
From:       Jochen Theodorou <blackdrag () gmx ! org>
Date:       2007-08-26 10:23:44
Message-ID: 46D154B0.6060508 () gmx ! org
[Download RAW message or body]

Alex Tkachman schrieb:
> Jochen!
> 
> What do you think about compilation of reflector (and maybe even
> metaclass) for GeneratedClosure not during runtime but during
> compilation phase?

The compilation of reflector should be turned off completly. Atm 
Reflector is mostly not used but it is a technology that will become 
more important in MetaClass 2 versions.

Anyway I thought about precompiling Reflector too, yes.. We already have 
a classlaoder based lookup of these Reflectors, it is just normally not 
used. I thought also about saving additional meta informations. My goal 
for this is to avoid Reflection completely at last in theory.

But of course there are problems with classes written in Java, and 
providing classes for them all is not good. So I thought about doing a 
simulation run where unit tests are used to find out which classes are 
really neded and let groovy write the Reflector to disk.

It is just a thought.

Your goal is surely to improve runtime performance and for 1.1 I think 
turning off the reflector completely is the way to go... ok controlled 
by the property that should really control this is even better ;) 
Metaclass has such property I think

bye blackdrag

-- 
Jochen "blackdrag" Theodorou
Groovy Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/

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

    http://xircles.codehaus.org/manage_email

[prev in list] [next in list] [prev in thread] [next in thread]