Jochen, you can see the test result at:
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_Antlr4grammar
在 "Jochen Theodorou [via Groovy]"
,2016年10月7日 下午7:40写道:
On 07.10.2016 13:35, daniel_sun wrote:
> I see.
>
> Feel free to merge the new
I'll try to review over the next little while too. Looks very
promising at first glance! Exciting to see a good start!
Paul.
On Fri, Oct 7, 2016 at 9:17 PM, Guillaume Laforge wrote:
> For reference, here's the PR:
> https://github.com/apache/groovy/pull/439
>
> On Fri, Oct
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
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]"
For reference, here's the PR:
https://github.com/apache/groovy/pull/439
On Fri, Oct 7, 2016 at 1:00 PM, Sergei Egorov wrote:
> Hey Mario,
>
> Wow! This is great! Didn't know you're working on it. I'll be happy to
> review :)
>
>
> Cheers,
> Sergei
>
> On Fri, Oct 7, 2016 at
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
Hey Mario,
Wow! This is great! Didn't know you're working on it. I'll be happy to
review :)
Cheers,
Sergei
On Fri, Oct 7, 2016 at 1:53 PM Mario Garcia wrote:
> Hi all:
>
> I sent a WIP with some groovy-macro documentation. The main problem with
> the PR is that there're
Hi all:
I sent a WIP with some groovy-macro documentation. The main problem with
the PR is that there're two tests failing. I've been checking tests code
and I can't see anything that may cause these tests to fail.
I'll be reviewing the whole thing during the weekend but it would be better
if
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
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.
Cheers,
Daniel.Sun
在 "paulk_asert [via Groovy]"
,2016年10月7日 上午4:55写道:
I didn't
On Thu, 2016-10-06 at 21:18 -0700, John Wagenleitner wrote:
> […]
> If memory serves me, updating the asciidoctor-gradle-plugin from
> 1.5.2 to
> 1.5.3 fixed the build issue but introduced a formatting issue with
> tables
> [1]. The formatting issue affected all builds not just jdk9 builds.
>
>
11 matches
Mail list logo