Hi Thibault,
The new parser Parrot passes all test cases of Apache Groovy
project(including shouldFail test cases), and the AST generated by Parrot is
identical to the AST generated by the old one except for the AST node
position(Parrot provides more accurate position information). If we think
passing all test cases and owning identical AST as the checking standard, we
could say Parrot is compatible with the old parser ??
BTW, some syntax which does not conform to the GLS(i.e. wild syntax)
could not be covered, so Parrot was tested via some main Groovy projects, e.g.
Grails, Gradle, Spock, Geb. But we are not sure Parrot can cover all *wild*
syntax...
Cheers,
Daniel.Sun
发件人: Thibault Kruse [via
Groovy]<mailto:[email protected]>
发送时间: 2017年1月18日 6:46
收件人: Daniel Sun<mailto:[email protected]>
主题: Re: next releases
Alternatively, groovy-antlr4 could be a separate jar.
If I understand correctly, then we are very confident that the new parser
accepts all programs that the old parser accepted, because that is easy to
test. But we do not know if it rejects all programs that the old parser
rejected, because that is difficult to test. This is no small risk, is it?
Users will have to be testers.
On Jan 17, 2017 5:57 PM, "S?ren Berg Glasius" <[hidden
email]</user/SendEmail.jtp?type=node&node=5737781&i=0>> wrote:
Can the parrot be packaged as separate jar that can be a dependency? That way
it can be included at will
On Tue, 17 Jan 2017 at 09:56 Guillaume Laforge <[hidden
email]</user/SendEmail.jtp?type=node&node=5737781&i=1>> wrote:
This is a beta, not the final release, though.
On Tue, Jan 17, 2017 at 9:54 AM, Cédric Champeau <[hidden
email]</user/SendEmail.jtp?type=node&node=5737781&i=2>> wrote:
I'm reluctant on adding the experimental parser in a release. It requires a
different version of antlr, which means more dependencies than we really need.
We should keep the distribution as clean as possible. Not saying that the new
parser is dirty, but that the size and dependencies of the distribution should
remain as small as possible.
<a href="tel:20%2017%2001%2017" value="+4520170117"
class="m_5805025134488659025gmail_msg" target="_blank">2017-01-17 9:48
GMT+01:00 Daniel Sun <[hidden
email]</user/SendEmail.jtp?type=node&node=5737781&i=3>>:
Hi Paul,
Will the new parser Parrot be included in 2.5.x releases as an
optional parser? If developers want to give it a try, just turn on the
switch "-Dgroovy.antlr4=true".
Cheers,
Daniel.Sun
--
View this message in context:
http://groovy.329449.n5.nabble.com/next-releases-tp5737758p5737761.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
--
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>
--
Best regards / Med venlig hilsen,
S?ren Berg Glasius
Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: <a href="tel:+45%2040%2044%2091%2088" value="+4540449188"
target="_blank">+45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://groovy.329449.n5.nabble.com/next-releases-tp5737758p5737781.html
To unsubscribe from next releases, click
here<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5737758&code=cmVhbGJsdWVzdW5AaG90bWFpbC5jb218NTczNzc1OHwxMTQ2MjE4MjI1>.
NAML<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://groovy.329449.n5.nabble.com/next-releases-tp5737758p5737783.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
