Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
MIME-Version: 1.0
References: <CADRx3POZ+O_A2OsPwQPVdBFUxrjh9KdPJK8xkrXVFL1Egx_qXQ@mail.gmail.com>
 <CAAJdKXkfw8haEPCCyRFPcm5++eXgy1tUWjkcTmnQ0kT4+MJKGA@mail.gmail.com> <24919e0c-8ff7-c53d-c540-9a4168288ba7@gmx.org>
In-Reply-To: <24919e0c-8ff7-c53d-c540-9a4168288ba7@gmx.org>
From: Sergei Egorov <bsideup@gmail.com>
Date: Wed, 29 Mar 2017 15:22:57 +0000
Message-ID: <CAAJdKXmqLp1oMx1P1FTWmQp1Yq+nS0yd78Vt+XojVcpSnr588g@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)
To: dev@groovy.apache.org
Content-Type: multipart/alternative; boundary=94eb2c07adce502bc2054be0278e
archived-at: Wed, 29 Mar 2017 15:23:13 -0000

--94eb2c07adce502bc2054be0278e
Content-Type: text/plain; charset=UTF-8

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 <blackdrag@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
>

--94eb2c07adce502bc2054be0278e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Jochen,<br><div><br></div><div>This is a good question :)<=
/div><div><br></div><div>I&#39;m going to present them tomorrow on my works=
hop at Greach, will collect some feedback and then will start writing the d=
ocs.=C2=A0</div><div><br></div><div>The only explanation you can find now i=
s here=C2=A0<a href=3D"https://github.com/bsideup/groovy-macro-methods-prop=
osal">https://github.com/bsideup/groovy-macro-methods-proposal</a></div><di=
v><br></div><div>There are open questions tho. Would be really nice if at l=
east some of you will provide your opinions on them :)</div><div><br></div>=
<div>FYI the refactorings didn&#39;t affect an API. Everything statement fr=
om &quot;groovy-macro-methods-proposal&quot; should be up to date, at least=
 as far as I remember, so it&#39;s definitely a good start to learn about t=
hem.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Mar=
 29, 2017 at 5:16 PM Jochen Theodorou &lt;<a href=3D"mailto:blackdrag@gmx.o=
rg">blackdrag@gmx.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><br class=3D"gmail_msg">
<br class=3D"gmail_msg">
On 29.03.2017 17:06, Sergei Egorov wrote:<br class=3D"gmail_msg">
&gt; -1<br class=3D"gmail_msg">
&gt; We have 1 failing test ( &quot;MacroTest &gt; testNotAMacroCall&quot; =
)<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Was caused by my recent change when I renamed extension module, sorry.=
<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I pushed a test fix. Assumption was incorrect, see the commit for an<b=
r class=3D"gmail_msg">
&gt; explanation.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
on a side note... where can I find the current up-to-date documentation<br =
class=3D"gmail_msg">
for macros... I mean if there is one ;)<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
bye Jochen<br class=3D"gmail_msg">
</blockquote></div>

--94eb2c07adce502bc2054be0278e--