I see. Feel free to merge the new parser back when you think it is mature and ready to go home ;) Currently The parser is lack of some syntax checks(e.g. continue should only be used in loop) and friendly messages for developers.
Cheers, Daniel.Sun 在 "Jochen Theodorou [via Groovy]" <ml-node+s329449n5735888...@n5.nabble.com>，2016年10月7日 19:03写道： On 07.10.2016 08:52, daniel_sun wrote: > How about providing a jar file containing the new parser, which is > compiled by Java8. When developers use Java8, they can try the new > parser by turning on the switch. I think for the time being we could make the new parser just a subproject that depends on main. Then this subproject can be java8, while the remainder of the project is java7. We need to ressurect/repair/activate the antlrparser plugin mechanism, but otherwise there should be no big problem.... Of course java7 would then not be able to use the new parser. WE can still think about porting or not, once we have it merged back. bye Jochen ________________________________ If you reply to this email, your message will be added to the discussion below: http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735888.html To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click here<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5735725&code=cmVhbGJsdWVzdW5AaG90bWFpbC5jb218NTczNTcyNXwxMTQ2MjE4MjI1>. 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/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735890.html Sent from the Groovy Dev mailing list archive at Nabble.com.
