Martin C. Martin schrieb: [...]

well, unlike Ruby you can in Groovy not change variables in the local context by for example an eval. So unless there is an assignment, which is statically known, there is no change to value. This applies even for closures.. of course they make it a bit more difficult, but not impossible I think. But you would not get much of a speed up for properties and such...

ah, did mean the MetaClass... sorry. In general I can not prove that before calling the function, but I can test it after the call. For MOP 2.0 I have the vision of a constant MetaClass handle, that will not be changed and that will always point to the actual MetaClass. If this is there, then we can cache this handle, bypass the registry completely and get an easy way to check if there is a change we have to be aware of.

In general.. without knowing the bytecode... I think that is really impossible ;)

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