Indeed great to have a little update on the progress! How is it possible to help? For example giving some new examples of code and see how they are parsed (if parsed successfully or not, etc)? Is the "fail" folder where we can contribute things that are not yet parsed but should work ultimately, or is this for things we expect to to fail parsing? I was thinking that perhaps we need three distinct sets: 1) stuff we expect to be parsed successfully, 2) stuff we would like to get parsed successfully, and 3) stuff we don't want to be parsed, ie. that fail parsing with proper error reporting?
Guillaume On Tue, Sep 6, 2016 at 11:12 AM, Graeme Rocher <graeme.roc...@gmail.com> wrote: > Interesting project Daniel Sun, good luck with it and look forward to > following your progress. > > Cheers > > On Sat, Sep 3, 2016 at 10:27 AM, 孙 岚 <realblue...@hotmail.com> wrote: > > Hi List, > > > > > > The groovy-antlr4-grammar project is very hard to maintain and the > > performance is terrible, so I am rewriting the > > parser(https://github.com/danielsun1106/groovy-parser), which is based > on > > the Java grammar provided by the antlr offical and introduced some good > idea > > from the old grammar. The Java parser generated by antlr4 is proved > > efficient in the most of senarios, so Groovy parser will be efficient > too if > > monitoring the performance from the beginning. > > > > > > The groovy-parser project is now stand-alone in order to develop > > rapidly. When the project is mature enough, I will make a PR to replace > > groovy-antlr4-grammar. BTW, groovy-parser requires Java 8. > > > > > > Currently groovy-parser supports all statements, most of > > expressions(except method call expression, command expression, etc.). I > wish > > the groovy-parser could be done before the end of this year(2016). > > > > > > Any suggestion and help is appreciated. > > > > > > Cheers, > > > > Daniel.Sun > > > > -- > Graeme Rocher > -- 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>
