Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <55769B13.9060904@gmx.org>
References: <1D591AA4-1D89-4B24-903B-7FA0538125BC@selskabet.org>
	<55745455.6000204@gmx.net>
	<CAPeninaDqi49s2YANRvwpp9yzSyt8hMs70HrUrtgy71p1MrfPw@mail.gmail.com>
	<FBD71EEA-5A74-4B8A-839B-A99B5E8E7276@selskabet.org>
	<55769B13.9060904@gmx.org>
Date: Tue, 9 Jun 2015 09:55:05 +0200
Message-ID: 
 <CAJ2HCd_0gynJ5UOadOGhDxLDyCcWf=PCkxfTfDuu6ZHsZU3dmg@mail.gmail.com>
Subject: Re: Antlr4 Groovy parser
From: Guillaume Laforge <glaforge@gmail.com>
To: dev@groovy.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113318389458d40518111343

--001a113318389458d40518111343
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

So Jesper should be working off of the java migration branch from Pavel I
guess?
(rather than what we currently have in our antlr4 branch)

Guillaume

2015-06-09 9:51 GMT+02:00 Jochen Theodorou <blackdrag@gmx.org>:

> Am 08.06.2015 23:50, schrieb Jesper Steen M=C3=B8ller:
>
>> Hello Pavel,
>>
>> I'll take a look at those. Are these being ported to java for
>> performance-reasons, or bootstrappability?
>>
>
> all parts that the parser itself uses should be in Java because we have n=
o
> groovy bootsrapping process for that. Tests don't need to be ported
>
> bye blackdrag
>
> --
> Jochen "blackdrag" Theodorou
> blog: http://blackdragsview.blogspot.com/
>
>


--=20
Guillaume Laforge
Groovy Project Manager
Product Ninja & Advocate at Restlet <http://restlet.com>

Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>

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

<div dir=3D"ltr">So Jesper should be working off of the java migration bran=
ch from Pavel I guess?<div>(rather than what we currently have in our antlr=
4 branch)</div><div><br></div><div>Guillaume</div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">2015-06-09 9:51 GMT+02:00 Jochen The=
odorou <span dir=3D"ltr">&lt;<a href=3D"mailto:blackdrag@gmx.org" target=3D=
"_blank">blackdrag@gmx.org</a>&gt;</span>:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><span class=3D"">Am <a href=3D"tel:08.06.2015%2023" value=3D"+33806201523=
" target=3D"_blank">08.06.2015 23</a>:50, schrieb Jesper Steen M=C3=B8ller:=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello Pavel,<br>
<br>
I&#39;ll take a look at those. Are these being ported to java for<br>
performance-reasons, or bootstrappability?<br>
</blockquote>
<br></span>
all parts that the parser itself uses should be in Java because we have no =
groovy bootsrapping process for that. Tests don&#39;t need to be ported<br>
<br>
bye blackdrag<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
-- <br>
Jochen &quot;blackdrag&quot; Theodorou<br>
blog: <a href=3D"http://blackdragsview.blogspot.com/" target=3D"_blank">htt=
p://blackdragsview.blogspot.com/</a><br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><di=
v><div dir=3D"ltr">Guillaume Laforge<br>Groovy Project Manager</div><div di=
r=3D"ltr">Product Ninja &amp; Advocate at <a href=3D"http://restlet.com" ta=
rget=3D"_blank">Restlet</a><br><div><br></div><div>Blog:=C2=A0<a href=3D"ht=
tp://glaforge.appspot.com/" target=3D"_blank">http://glaforge.appspot.com/<=
/a><div><div>Social: <a href=3D"http://twitter.com/glaforge" target=3D"_bla=
nk">@glaforge</a>=C2=A0/ <a href=3D"https://plus.google.com/u/0/11413097223=
2398734985/posts" target=3D"_blank">Google+</a></div></div></div></div></di=
v></div></div></div></div>
</div>

--001a113318389458d40518111343--