I agree we should also try the new parser on a handful of other popular
projects, as it'd ensure the parser can parse even more of Groovy that is
in the wild.
Le dimanche 9 octobre 2016, Thibault Kruse a
écrit :
> Should the new parser also pass tests for the most-used frameworks
> before being
this email, your message will be added to the discussion below:
http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735942.html
To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click
here<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=
On 07.10.2016 18:09, daniel_sun wrote:
Jochen, you can see the test result at:
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_Antlr4grammar
thanks... but there are 3 tests failing. Are those the test you have a
local fix for?
bye Jochen
r.
>
> 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-tp5735725p5735940.html
To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, cli
Should the new parser also pass tests for the most-used frameworks
before being merged? Grails, Gradle, Spock and Geb come to my mind.
On Fri, Oct 7, 2016 at 8:40 PM, Jochen Theodorou wrote:
>
>
> On 07.10.2016 13:35, daniel_sun wrote:
>>
>> I see.
>>
>> Feel free to merge the new parser back whe
dded to the discussion below:
http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735891.html
To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click
here<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=unsubs
d at least 3(?) this year.
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-tp5735725p5735891.html
To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click
h
On 07.10.2016 13:35, daniel_sun wrote:
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.
Before that I would li
arser. 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.
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 Fri, Oct 7, 2016 at 8:16 PM, Thibault Kruse wrote:
> On Tue, Oct 4, 2016 at 1:22 AM, daniel_sun wrote:
>> 2)
>> subprojects/groovy-groovysh/src/main/groovy/org/codehaus/groovy/tools/shell/commands/DocCommand.groovy(TODO
>> confirm: https://github.com/danielsun1106/groovy-parser/issues/5);
>
>
On Tue, Oct 4, 2016 at 1:22 AM, daniel_sun wrote:
> 2)
> subprojects/groovy-groovysh/src/main/groovy/org/codehaus/groovy/tools/shell/commands/DocCommand.groovy(TODO
> confirm: https://github.com/danielsun1106/groovy-parser/issues/5);
So the current Groovy parser could handle this case?
t;>
>> PS: The new parser requires Java8 because streams and lambda expression
>> are
>> used.
>>
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>> 发件人: Graeme Rocher-2 [via Groovy]
>> 发送时间: 2016年10月6日 18:27
>> 收件人: daniel_sun
>> 主题: R
;>
>> PS: The new parser requires Java8 because streams and lambda expression
>> are
>> used.
>>
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>> 发件人: Graeme Rocher-2 [via Groovy]
>> 发送时间: 2016年10月6日 18:27
>> 收件人: da
t;
> 发件人: Graeme Rocher-2 [via Groovy]
> 发送时间: 2016年10月6日 18:27
> 收件人: daniel_sun
> 主题: Re: 答复: [PROGRESS REPORT 20161004]groovy-parser
>
> Hi Daniel,
>
> Yes I have seen that before, it happens when Travis runs out of memory
> since each Travis
because streams and lambda expression are
> used.
>
>
> Cheers,
> Daniel.Sun
>
>
> 发件人: Graeme Rocher-2 [via Groovy]
> 发送时间: 2016年10月6日 18:27
> 收件人: daniel_sun
> 主题: Re: 答复: [PROGRESS REPORT 20161004]groovy-parser
>
> Hi Daniel,
&g
hanks,
> Daniel.Sun
> ________
> 发件人: Graeme Rocher-2 [via Groovy]
> 发送时间: 2016年10月6日 17:29
> 收件人: daniel_sun
> 主题: Re: [PROGRESS REPORT 20161004]groovy-parser
>
> That is awesome, keep up the good work.
>
> Cheers
>
> On Wed, Oct 5, 2
_
> 发件人: Graeme Rocher-2 [via Groovy]
> 发送时间: 2016年10月6日 17:29
> 收件人: daniel_sun
> 主题: Re: [PROGRESS REPORT 20161004]groovy-parser
>
> That is awesome, keep up the good work.
>
> Cheers
>
> On Wed, Oct 5, 2016 at 5:57 AM, daniel_sun <[hidden email]>
10月6日 17:29
收件人: daniel_sun
主题: Re: [PROGRESS REPORT 20161004]groovy-parser
That is awesome, keep up the good work.
Cheers
On Wed, Oct 5, 2016 at 5:57 AM, daniel_sun <[hidden
email]> wrote:
> Thanks :)
>
>
>
> --
> View this message in context:
> http://groovy.32
That is awesome, keep up the good work.
Cheers
On Wed, Oct 5, 2016 at 5:57 AM, daniel_sun wrote:
> Thanks :)
>
>
>
> --
> View this message in context:
> http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735778.html
> Sent from the
I'm trying to set the new parser as the default to build and test, *13396
tests completed, 6 failed, 9 skipped*
https://travis-ci.org/danielsun1106/groovy
--
View this message in context:
http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735777.html
Thanks :)
--
View this message in context:
http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735778.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
;
> At last, I want to thank *Jochen Theodorou* and *Paul King*, who
> provide me many suggestion and help while developping the new parser.
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> View this message in context: http://groovy.329449.n5.
> nabble.com/PROGRESS-REPORT
Excellent, well done!
From: daniel_sun [realblue...@hotmail.com]
Sent: 03 October 2016 17:22
To: d...@groovy.incubator.apache.org
Subject: [PROGRESS REPORT 20161004]groovy-parser
Hi List,
Currently the new parser can parse almost all groovy source
,
Daniel.Sun
--
View this message in context:
http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
25 matches
Mail list logo
