True. But it's about "macro" method, aka "MacroGroovy". Its API also wasn't affected, basically, I just reimplemented it as a macro method :)
FYI build is green now: http://ci.groovy-lang.org/viewLog.html?buildId=38463&tab=buildResultsDiv&buildTypeId=Groovy_Jdk8Build_2 On Wed, Mar 29, 2017 at 5:26 PM Guillaume Laforge <glafo...@gmail.com> wrote: > We have some documentation from Mario : > > https://github.com/apache/groovy/blob/master/src/spec/doc/core-metaprogramming.adoc#macros > > On Wed, Mar 29, 2017 at 5:22 PM, Sergei Egorov <bsid...@gmail.com> wrote: > > Jochen, > > This is a good question :) > > I'm going to present them tomorrow on my workshop at Greach, will collect > some feedback and then will start writing the docs. > > The only explanation you can find now is here > https://github.com/bsideup/groovy-macro-methods-proposal > > There are open questions tho. Would be really nice if at least some of you > will provide your opinions on them :) > > FYI the refactorings didn't affect an API. Everything statement from > "groovy-macro-methods-proposal" should be up to date, at least as far as I > remember, so it's definitely a good start to learn about them. > > On Wed, Mar 29, 2017 at 5:16 PM Jochen Theodorou <blackd...@gmx.org> > wrote: > > > > On 29.03.2017 17:06, Sergei Egorov wrote: > > -1 > > We have 1 failing test ( "MacroTest > testNotAMacroCall" ) > > > > Was caused by my recent change when I renamed extension module, sorry. > > > > I pushed a test fix. Assumption was incorrect, see the commit for an > > explanation. > > on a side note... where can I find the current up-to-date documentation > for macros... I mean if there is one ;) > > bye Jochen > > > > > -- > Guillaume Laforge > Apache Groovy committer & PMC Vice-President > Developer Advocate @ Google Cloud Platform > > Blog: http://glaforge.appspot.com/ > Social: @glaforge <http://twitter.com/glaforge> / Google+ > <https://plus.google.com/u/0/114130972232398734985/posts> >
