Hi Paul,
I downloaded the jar file via gradle and the coresponding file can be
found in the repository:
https://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/groovy-all/2.5.0-SNAPSHOT/groovy-all-2.5.0-20160607.103553-603.jar
Cheers,
Daniel.Sun
--
View this message in context:
Hi Jesper,
I'm very glad to know the antlr4 works on Groovy re-launched.
A few days ago, I gave it a try and found it did not support optional
parentheses of invoking method, so I managed to fix it and new a pull
request on the github, pls verify it.
The dev environment
Thank you, Jorge!
--
View this message in context:
http://groovy.329449.n5.nabble.com/About-the-license-of-the-sample-codes-from-Groovy-in-Action-2nd-Edition-tp5732026p5732073.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
Hi List,
Jesper and I are tring to implement Groovy parser via antlr4. Some
typical test cases are required to check the compatibility between the
antlr2 parser and the antlr4 parser. As we all know, Groovy in Action 2nd
Edition is the most definitive book for Groovy and contain many sample
Hi List,
The following code is copied from GinA2, which we use to test the new
parser for Groovy.
class Book {
private String title
Book (String theTitle) {
title = theTitle
}
String getTitle(){
return title
}
}
I have a question about the
I've fixed the issue in the new parser. Thanks for your help, Jochen :)
在 "Jochen Theodorou [via Groovy]"
<ml-node+s329449n5732143...@n5.nabble.com>,2016年4月2日 上午12:02写道:
On 01.04.2016 17:50, daniel_sun wrote:
> Hi List,
>
>The following code is copied from Gi
Hi Groovy-Dev,
Since Jesper reported the progress last time, Jesper and I have refined
the new parser for Groovy programming language in many aspects, which now
can handle almost all source code of Groovy in Action 2nd Edition(633 passed
/ 635 total, including our own 72 test cases). The
+1
--
View this message in context:
http://groovy.329449.n5.nabble.com/GROOVY-5727-removal-of-servlet-api-from-the-zip-distribution-tp5732373p5732396.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
Hi Jochen,
The groovy grammar bases on Java7
grammar(https://github.com/antlr/grammars-v4/blob/master/java/Java.g4) at
the beginning because I noticed the comment of Java8 grammar, which tells us
Java7 has better performance.
In addition, I refine the cache management of antlr4, so
ever
contributed to Groovy core
Cheers
On Thu, Oct 6, 2016 at 12:44 PM, daniel_sun <[hidden email]> wrote:
> Hi Graeme,
>
>
>Thanks for your help! I'll give it a try :)
>
>
> PS: The new parser requires Java8 because streams and lambda expres
Jochen, you can see the test result at:
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_Antlr4grammar
在 "Jochen Theodorou [via Groovy]"
<ml-node+s329449n5735891...@n5.nabble.com>,2016年10月7日 下午7:40写道:
On 07.10.2016 13:35, daniel_sun wrote:
> I see.
>
> F
n5.nabble.com>,2016年10月9日 13:55写道:
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 <[hidden email]> wrote:
>
>
> On 07.10.2016 13:35, daniel_sun
com>,2016年10月9日 15:03写道:
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
loca
quot;
<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
6, 2016 at 10:39 PM, daniel_sun <[hidden email]> wrote:
> As far as I know, Groovy will migrate to Java8 as soon as possible, so it
> will be OK in the near future ;)
>
>
>
> 在 "Graeme Rocher-2 [via Groovy]" <ml-node+[hidden email]>,2016年10月6日
> 下午8:
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.
Hi Rémi,
Groovy can choose the right method to call :)
assert ['1', '2', '3'] == [1, 2, 3].collect(Integer.)
Cheers,
Daniel.Sun
发件人: Remi Forax [via Groovy] <ml-node+s329449n5736203...@n5.nabble.com>
发送时间: 2016年10月19日 19:29
收件人: daniel_sun
Hi Jesper,
> Be careful with that approach, as it won’t work for static methods —
> leading to very different semantics for the two languages.
'.&' can reference the static methods, here is the sample code:
[1, 2, 3].each(Objects.)
> Also, you won’t be able to
Hi Jochen,
I plan to map Java's *::* to Groovy's *.&*, the following code is ok
now. What do you think about it?
[1, 2, 3].stream().forEach(System.out.) // object method,
[1, 2, 3].stream().forEach(System.out::println)
[1, 2, 3].stream().forEach(Objects.) // class method, [1, 2,
[via Groovy]"
<ml-node+s329449n5736171...@n5.nabble.com>,2016年10月18日 00:37写道:
On 17.10.2016 17:40, daniel_sun wrote:
> Hi all,
>
>Lambda expression for Groovy has been completed with a little
> limitation, which is due to the existing closure whose parameter list
[via Groovy]"
<ml-node+s329449n5736189...@n5.nabble.com>,2016年10月19日 上午8:36写道:
Nothing's definitive at all for Groovy 2.5 or 3.0.
It's up for discussion here on the list :-)
On Wed, Oct 19, 2016 at 2:33 AM, daniel_sun <[hidden email]> wrote:
Thanks :)
Guillaume, is there a road m
Thanks :)
Cheers,
Daniel.Sun
在 "Roman Shaposhnik-2 [via Groovy]"
,2016年10月19日 上午7:17写道:
On Tue, Oct 18, 2016 at 4:15 PM, Jesper Steen Møller
<[hidden email]> wrote:
> "Real lambdas" with the full invokedynamic treatment is a big job, and
> requires
orge <[hidden email]>
wrote:
Is it actually Groovy closures? or "real" Java lambdas?
On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou <[hidden email]> wrote:
hah, I knew you can do it ;)
On 18.10.2016 18:34, daniel_sun wrote:
Jochen, lambda expression is fully supported now
午7:47写道:
Thanks for the explanations!
(and great achievement!)
On Wed, Oct 19, 2016 at 1:43 AM, daniel_sun <[hidden email]> wrote:
To be exact, lambda expression of Groovy enhances the syntax of Java lambda
expression, e.g. lambda expression of Java is not callable.
Cheers,
Daniel.Sun
在 "R
uot; Java lambdas?
On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou <[hidden email]> wrote:
hah, I knew you can do it ;)
On 18.10.2016 18:34, daniel_sun wrote:
Jochen, lambda expression is fully supported now :)
https://github.com/danielsun1106/groovy-parser/commit/c380e4230ecef35
:
On 19.10.2016 02:49, daniel_sun wrote:
> The new parser is based on Java8, so it has to target to Groovy3. As far
> I know, there are some amazing features under development or test, e.g.
> MOP2, new Joint compiler, Macro(appears at the snapshot of 2.5.0), etc.
> Looking forward to t
re with the Java syntax.
Rémi
On October 18, 2016 8:21:34 PM GMT+02:00, Guillaume Laforge <[hidden email]>
wrote:
Is it actually Groovy closures? or "real" Java lambdas?
On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou <[hidden email]> wrote:
hah, I knew you can do it ;)
Hi dev list,
The brand new parser for Groovy can parse all groovy code of
*Grails-3.2.0(1150 PASSES / 1150 IN TOTAL)*, almost all groovy code of
*Gradle-3.1(3961 PASSES / 3963 IN TOTAL)*, all groovy code of *Spock(294
PASSES / 294 IN TOTAL)*, all groovy code of *Geb-1.0(409 PASSES / 409 IN
28 matches
Mail list logo