My take is simpler than this. If Parrot should be included in 2.5, then remove the old parser and use it. If it's for 3.0, then it should not belong to the 2.5 beta, or it should be an external dependency (possibly tested by adding a jar manually).
2017-01-17 9:57 GMT+01:00 Søren Berg Glasius <soe...@glasius.dk>: > 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 <glafo...@gmail.com> wrote: > >> This is a beta, not the final release, though. >> >> On Tue, Jan 17, 2017 at 9:54 AM, Cédric Champeau < >> cedric.champ...@gmail.com> 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. >> >> 2017-01-17 <20%2017%2001%2017> 9:48 GMT+01:00 Daniel Sun < >> realblue...@hotmail.com>: >> >> 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: +45 40 44 91 88 <+45%2040%2044%2091%2088>, Skype: sbglasius > --- Press ESC once to quit - twice to save the changes. >
