[groovy-dev] Re: Annotation closures available in trunk

> This AST xform generates an inner class for the first prop, it casts the
closure to a PropertyChangeListener on the second case.
I'd be cautious about the second case; it seems to be turning invalid into
valid Groovy code, which will likely break tools (IDEs in particular) and
joint compilation.

> But I guess that as long closures as values are supported in a case by
> case basis... then Griffon is fine.
What do you mean by that?

AST transforms playing their own games with annotation closures should be
fine because groovyc won't touch the closures until phase class generation.
Ideally, transforms would keep replacing the closure with a class literal to
prevent generation of another inner class.

Cheers,
Peter
--

-- 
View this message in context: http://groovy.329449.n5.nabble.com/Annotation-closures-available-in-trunk-tp512450p512466.html
Sent from the groovy - dev mailing list archive at Nabble.com.

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

    http://xircles.codehaus.org/manage_email