James Williams schrieb:
> Another problem other than the classloaders is all the reflection
> classes that Groovy needs to compile(most reside in rt.jar). I think the
> only way to get Groovy working would be to rip out all the dynamic
> classes and MOP. The result would be a language that is not really Groovy.
depends... let us say we have a fixed set of groovy programs and let us
assume we could generate a bunch of support classes. In that case we
might use these support classes to replace the reflective information...
and then most of Groovy would work, only that you could not change a
script or make a new one.... but it would theoretically work. This would
for example still allow a custom MetaClass and other things.
Another way would be to try to make a different generation path, which
works without classcode... in that case we would possibly loose some
java integration, but we might be able to use custom scripts. But I
guess this alternative would be much more complicated than the other one
bye blackdrag
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (
http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/http://www.g2one.com/---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
