Re: release process

FYI, Jesper has ported Parrot to Java 7(https://github.com/apache/groovy/pull/485) 在 "Graeme Rocher-2 [via Groovy]" ，2017年1月31日 下午3:19写道： I am in agreement with doing a 3.0 compatible with Groovy 2.x and making 3.x into Groovy 4.x Groovy 2.x users

Re: [VOTE] Apache Groovy Roadmap

Hi Cédric, > Because macro groovy doesn't have to be bound with breaking changes. If program has already used "macro" method name, what will happen? Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/VOTE-Apache-Groovy-Roadmap-tp5738250p5738271.html Sent

Re: [VOTE] Apache Groovy Roadmap

Hi Cédric, 72h has gone. The result is ? Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/VOTE-Apache-Groovy-Roadmap-tp5738250p5738451.html Sent from the Groovy Dev mailing list archive at Nabble.com.

答复: [VOTE] Apache Groovy Roadmap

?? Cheers, Daniel.Sun 发件人: Jochen Theodorou [via Groovy]<mailto:ml-node+s329449n5738471...@n5.nabble.com> 发送时间: 2017年2月7日 22:23 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: [VOTE] Apache Groovy Roadmap On 07.02.2017 14:44, Daniel Sun wrote: > Hi Cédric, > > I

答复: Lambda vs. Closure (was: [VOTE] Apache Groovy Roadmap)

发送时间: 2017年2月7日 23:44 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: Lambda vs. Closure (was: [VOTE] Apache Groovy Roadmap) On 7 Feb 2017, at 16.27, Daniel Sun <[hidden email]> wrote: To fully support *real* lambda expression, (to be honest)currently I have no

答复: Lambda vs. Closure

:ml-node+s329449n5738489...@n5.nabble.com> 发送时间: 2017年2月8日 0:53 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: Lambda vs. Closure On 07.02.2017 16:44, Jesper Steen Møller wrote: [...] > Generating faster/tighter code for lambdas (or even closures) can be > implemented

答复: Lambda vs. Closure (was: [VOTE] Apache Groovy Roadmap)

49n573848...@n5.nabble.com> 发送时间: 2017年2月7日 23:44 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: Lambda vs. Closure (was: [VOTE] Apache Groovy Roadmap) On 7 Feb 2017, at 16.27, Daniel Sun <[hidden email]> wrote: To fully support *real* lambda expression, (to be honest

答复: Lambda vs. Closure (was: [VOTE] Apache Groovy Roadmap)

Hi Jesper, Gotcha  For me, I don’t like two versions of lambda expression… it will confuse developers. Cheers, Daniel.Sun 发件人: Jesper Steen Møller [via Groovy]<mailto:ml-node+s329449n573848...@n5.nabble.com> 发送时间: 2017年2月7日 23:44 收件人: Daniel Sun<mailto:realblue...@hotmai

Re: [VOTE]About the implementation of lambda expression

-- On 07.02.2017 17:39, Daniel Sun wrote: [...] > > * We have a basic choice: 1) Use Java-lambda semantics or 2) > Groovy-closure semantics. As a variation on 2, we can add some help > for people pasting Java code into a Groovy program. > > > Ag

Re: [VOTE] Apache Groovy Roadmap

As to the new features of Java 8, Parrot provides the same syntax but the backend is based on the existing groovy runtime. The approach can make some differences between Groovy and Java 8. Whether these differences are allowed or not depends on GLS. Like the inner class behaves a bit

Re: Parrot and the ++ and -- operators

Hi Joe, I've added your sample code as test cases(https://github.com/danielsun1106/groovy-parser/commit/9914682e53fb2fe3d4bb335c8153e61066cea317). Parrot has same result with the old parser ;) Cheers, Daniel.Sun -- View this message in context:

Re: About array initializer of Java style for Groovy 3

closure 在 "Guillaume Laforge [via Groovy]" <ml-node+s329449n5737945...@n5.nabble.com>，2017年1月24日 16:54写道： What happens for def a = { 2 }, is it parsed as a closure or an array initializer? On Tue, Jan 24, 2017 at 9:52 AM, Daniel Sun <[hidden email]> wrote: Hi Andr

About array initializer of Java style for Groovy 3

Hi all, Java supports specifing initial values while creating arrays, e.g. `new int[] {1, 2, 3}`, `new String[] { hello(), world() }`, etc. I plan to add this syntax for Groovy 3 to improve the compatibility between Groovy and Java. Any thoughts? Cheers, Daniel.Sun -- View

Re: About array initializer of Java style for Groovy 3

Hi Andres, Parrot can parse ` def a = {1, 2, 3}` properly, but it can not parse `{1, 2, 3}`, which is not supported by Java too. This is the initial implementation :) https://github.com/danielsun1106/groovy-parser/commit/96e6c923a4d09d48448f8731a314c918ee6c0e7c Cheers, Daniel.Sun

Re: About array initializer of Java style for Groovy 3

or we just support new int[] {1,2,3} ？ 在 "Guillaume Laforge [via Groovy]" <ml-node+s329449n5737945...@n5.nabble.com>，2017年1月24日 16:54写道： What happens for def a = { 2 }, is it parsed as a closure or an array initializer? On Tue, Jan 24, 2017 at 9:52 AM, Daniel Sun <[hidde

Re: About array initializer of Java style for Groovy 3

> wrote: I think we should support only explicit array initilization with array type, that is "new int[] { 2 }" for compatibility's sake. Sent from my iPhone On 24 Jan 2017, at 09:59, Daniel Sun <[hidden email]> wrote: or we just support new int[] {1,2,3} ？ 在 "Guill

答复: Array initializer of Java style for Groovy 3

Thanks ?? 发件人: Cédric Champeau [via Groovy]<mailto:ml-node+s329449n5737956...@n5.nabble.com> 发送时间: 2017年1月24日 20:18 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: Array initializer of Java style for Groovy 3 Great work! 2017-01-24 13:12 GMT+01:00 Daniel Sun <[hidden

Array initializer of Java style for Groovy 3

Hi all, The new parser Parrot support array initializer of Java style, e.g. new int[] {1, 2, 3}, new int[][]{new int[]{1, 1.plus(1)}, new int[] {2.plus(1), 4}}, new String[] {'hello', 'world'} More examples can be found at

答复: About the "implies" operator(GROOVY-2576)

, no approach can deal with it. Thanks for your suggestion  Cheers, Daniel.Sun 发件人: Jesper Steen Møller [via Groovy]<mailto:ml-node+s329449n5738122...@n5.nabble.com> 发送时间: 2017年1月26日 19:24 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: About the "implies" operator(G

Re: Standard "for" loop statement for Groovy 3

BTW, the old parser just supports limited "for" loop statement, e.g. for (int i = 0; i < 10; i++) {..} Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Standard-for-loop-statement-for-Groovy-3-tp5738199p5738200.html Sent from the Groovy Dev mailing list

Re: 答复: About the performance of the test builds

happening on the box after the main JDK7/8 builds - which will slow down whatever runs next. Cheers, Paul. On Mon, Jan 30, 2017 at 3:12 AM, Daniel Sun <[hidden email]> wrote: Hi Jochen, > hardware is the same for all. afaik the parrot branch under the "JDK 7 > build" is tested w

Re: Traits and protected properties

Hi Graeme, Here is my test code, which fails: trait A { public static String m() { return '123' } } A.m() error messages: groovy.lang.MissingMethodException: No signature of method: static A.m() is applicable for argument types: () values: [] Possible solutions: is(java.lang.Object),

Re: release process

Hi Jesper, > I recognise that the Antlr4 parser AST building looks really neat in Java > 8, but easthetics aside That's why I choose Java 8 to rewrite the parser :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/release-process-tp5737841p5738020.html

Re: Traits and protected properties

Hi Cédric, > having a protected property just cannot work Could you tell me why trait does not support protected property? Thanks, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Traits-and-protected-properties-tp5738002p5738019.html Sent from the Groovy Dev

Re: Traits and protected properties

OK. I see. Thanks :) BTW, the interface with default methods is based on Traits, I found Traits does not support static methods too... So maybe we should generate bytecode for default methods and static methods of interface as Java 8 do. Cheers, Daniel.Sun -- View this message in context:

Re: About the "implies" operator(GROOVY-2576)

6日 上午3:20，"Jochen Theodorou [via Groovy]" <ml-node+s329449n5738042h6 On 25.01.2017 17:50, Daniel Sun wrote: > Hi all, > >The "implies" operator "=>" was suggested many years ago, here is the > replated JIRA issue( GROOVY-2576 > <https://i

答复: About the "implies" operator(GROOVY-2576)

Hi Cédric, Here is the background of the “implies” operator, which is well known in the mathematical logic ?? http://mathworld.wolfram.com/Implies.html 发件人: Cédric Champeau [via Groovy]<mailto:ml-node+s329449n5738104...@n5.nabble.com> 发送时间: 2017年1月26日 17:12 收件人: Dani

Re: 答复: One more new operator "implies" ( => ) for Groovy 3

Since 30% of 76 developers don't like the new operator, it will be postponed to merge into Apache Groovy util most of us like it. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/One-more-new-operator-implies-for-Groovy-3-tp5738103p5738162.html Sent from

答复: One more new operator "implies" ( => ) for Groovy 3

Hi Jochen, => has lower priority than &&, ||, &, | Cheers, Daniel.Sun 发件人: Jochen Theodorou [via Groovy]<mailto:ml-node+s329449n5738113...@n5.nabble.com> 发送时间: 2017年1月26日 18:42 收件人: Daniel Sun<mailto:realblue...@hotmail.com> 主题: Re: One more new operator &q

答复: 答复: About the "implies" operator(GROOVY-2576)

Hi Jochen, Some like it, some don’t. Understanding the new operator needs some knowledge of mathematical logic. Cheers, Daniel.Sun 发件人: Jochen Theodorou [via Groovy]<mailto:ml-node+s329449n5738114...@n5.nabble.com> 发送时间: 2017年1月26日 18:44 收件人: Daniel Sun<mailto:realblue...@hotmai

About the performance of the test builds

Hi all, I noticed that test builds that use JDK 8 cost different time, they run tests from master and parrot branch(contains all commits from master)(http://ci.groovy-lang.org/project.html?projectId=Groovy), e.g. BUILDTESTS COUNTCOSTED

About a new annotation Groovydoc

Hi all, I am going to add a new annotation Groovydoc(Retention: RUNTIME), which is configurable(e.g. -Dgroovy.attach.annotation.groovydoc=true) and can be attached to target element at compilation time automatically. Groovydoc can be got easily even if Groovy source code is compiled

Re: About a new annotation Groovydoc

Hi Guillaume, > what about a special GroovyDoc annotation? The original purpose to add Groovydoc annotation is to store groovydoc at runtime and get groovydoc easily by accessing the annotation as usual. If it is GroovyDoc annotation, how can we store groovydoc and get it at

Re: [VOTE] Release Groovy 2.4.9

Hi Paul, If the PR(https://github.com/apache/groovy/pull/504) for fixing GROOVY-8085 is merged, +1 from me. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/VOTE-Release-Groovy-2-4-9-tp5738742p5738747.html Sent from the Groovy Dev mailing list

Re: About a new annotation Groovydoc

If groovydoc exists and is related to the target element, @Groovydoc will be attached to the target element(i.e. Not all target elements). Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/About-a-new-annotation-Groovydoc-tp5738721p5738733.html Sent from

Re: 2.4.9 release

Hi Paul, I've fixed it: https://github.com/apache/groovy/pull/504 Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/2-4-9-release-tp5738711p5738746.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: The order of modifiers and annotations

> def is by now to be thought of as an alias for Object OK. I see. Thanks :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/The-order-of-modifiers-and-annotations-tp5737808p5737813.html Sent from the Groovy Dev mailing list archive at Nabble.com.

The order of modifiers and annotations

Hi all, Currently the old parser allows mixing modifiers and annotations, e.g. *Current* @interface Test1 {} @interface Test2 {} @Test1 final @Test2 a *Suggested* @interface Test1 {} @interface Test2 {} @Test1 @Test2 final a In addition, the order of modifiers is arbitrary too,

Re: The order of modifiers and annotations

I'll take a look at the issue later. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/The-order-of-modifiers-and-annotations-tp5737808p5737818.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: The order of modifiers and annotations

I verified that the new parser Parrot does not have the issue( GROOVY-4757 ), the following test case was added in the parrot branch. And I'll resolve the JIRA issue later.

Re: The order of modifiers and annotations

You're welcome :) -- View this message in context: http://groovy.329449.n5.nabble.com/The-order-of-modifiers-and-annotations-tp5737808p5737826.html Sent from the Groovy Dev mailing list archive at Nabble.com.

The priority of .. and . (GROOVY-3240)

Hi all, I'm taking a look at GROOVY-3240 , which was raised by me some years ago. I wonder whether .. has higher priority than DOT(.) or not. Cheers, Daniel.Sun -- View this message in context:

Re: The priority of .. and . (GROOVY-3240)

ess breaking change. Integer.metaClass.foo = { delegate + 1 } assert 3.foo()..4.foo() == 4..5 ​ ​ On Thu, Jan 19, 2017 at 1:25 PM, Daniel Sun <[hidden email]> wrote: Hi all, I'm taking a look at GROOVY-3240 <https://issues.apache.org/jira/browse/GROOVY-3240> , which was raised by me some years ago.

Re: The order of modifiers and annotations

Thanks :) 在 "Marcin Erdmann [via Groovy]" <ml-node+s329449n5737886...@n5.nabble.com>，2017年1月20日 下午5:09写道： Awesome! On Thu, Jan 19, 2017 at 11:01 AM, Daniel Sun <[hidden email]> wrote: I verified that the new parser Parrot does not have the issue( GROOVY-4757 <https

Re: [VOTE] Release Groovy 2.4.9

> Doesn't appear to address GROOVY-4721 from my initial check. Yeah, the old issue GROOVY-4721 still exists. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/VOTE-Release-Groovy-2-4-9-tp5738742p5738775.html Sent from the Groovy Dev mailing list archive

Re: Safe index for Groovy 3

groovy-all-2.5.0-SNAPSHOT jar file used by groovy-parser is a bit outdated, the following usual code can not be executed too(but it can be executed by 2.4.7...), so the static complication test cases will be added later :) @CompileStatic int cs() { List a = [1, 2, 3] return a[0]; } cs();

Re: Safe index for Groovy 3

Yeah, I like the idea too :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Safe-index-for-Groovy-3-tp5736558p5736562.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: Safe index for Groovy 3

Hi OC, IMHO, 'full safe' switch will change the semantic of existing '.', which may reduce the maintainability and readability of program, so the explicit '?' is necessary. Thanks for your suggestions :) Cheers, Daniel.Sun -- View this message in context:

About the parrot branch of apache/groovy

Hi all, In order to not impact the existing branches as possible as I can, I created a branch named "parrot" and put the new parser(Parrot) at the new branch, which is based on antlr4 branch and synchronized the changes from master. Currently there are 3 failed test cases waiting for

Re: Negative relational operators for Groovy 3

dAST SEVERE: Failed to build AST org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: ConsoleScript18: 9: Unexpected input: 'assert'; Expecting RPAREN @ line 9, column 1. assert 3 !in [] ^ 1 error I did build with -PuseAntlr4=true though. Guillaume On Fri, Nov 18, 2016 at 1:45 PM, Daniel Sun <[hidden email]> wrote

Re: Proposal - Pattern matching elixir way

Hi Jorge, First of all, thanks for your proposal. I wonder why do you want the feature? What senarios make the code such as "@When('!file || !new File(path).exists()')" overwhelm existing features of groovy(e.g. switch statement)? Cheers, Daniel.Sun -- View this message in

Re: [PROPOSAL]new operator ?=

Hi Jochen, > Maybe we should start a vote of ?= or not... maybe on the user list... > then we see what people think. Daniel might have been a bit too fast here I'd like to start the vote of ?=;) Just ask whether like it or not? Or like Andres's vote, ask which operator do you like:

[PROPOSAL]new operator ?=

Hi all, Marcin Erdmann proposed the new operator ?=, e.g. a ?= "foo" is equivalent of a = a ?: "foo". I like his idea, what do you think about it? Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/PROPOSAL-new-operator-tp5736886.html Sent

回复： Re: [PROPOSAL]new operator ?=

; <ml-node+s329449n5736900...@n5.nabble.com> 已发： 2016年11月23日 上午12:47 收件人： "Daniel Sun" <realblue...@hotmail.com> 主题： Re: [PROPOSAL]new operator ?= On 22.11.2016 15:25, Guillaume Laforge wrote: > It's a feature that's often be requested. > I think Ruby's got an equivalent with ||=,

Re: Negative relational operators for Groovy 3

> === and !=== are available for Groovy 3, so "!is" is not necessary. The identity operators should be === and !==:) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Negative-relational-operators-for-Groovy-3-tp5736809p5736834.html Sent from the

Re: Negative relational operators for Groovy 3

Hi Guillaume, === and !=== are available for Groovy 3, so "!is" is not necessary. Currently only "!in" and "!instanceof" are supported with sticky style: https://github.com/danielsun1106/groovy-parser/commit/69023a63446d14add54f43d3d7797c9dd2a7f903 If it is ok, I'll merge it into

Re: Negative relational operators for Groovy 3

Hi Jochen, I've modified the implementation according to your suggestions that ONLY support !in and !instanceof with sticky style. In addition, !in and !instanceof are REAL operators now(https://github.com/danielsun1106/groovy-parser/commit/87e2c41763422a6642414028d84efdccb90bfcda)

Re: Negative relational operators for Groovy 3

Hi Jochen, > "a !&& b" for a nand instead of "!(a && b)" or instead of "!a || !b" > then there is also ~& and !& Looks good. They've been added to my TODO list :) Cheers, Daniel.Sun -- View this message in context:

Re: groovy parsers as subprojecs

Hi Jochen, The "I)" variant looks better than other variants, which works fine now. BTW, glad to see you again in the mailing list :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/groovy-parsers-as-subprojecs-tp5736808p5736812.html Sent

Re: Negative relational operators for Groovy 3

Hi Jochen, > oh... and one question... is "! in" the same as "!in"? Yeah, the negative relational operators are combined operators, which will be transformed to normal NotExpression :) Cheers, Daniel.Sun -- View this message in context:

Re: Negative relational operators for Groovy 3

Hi Jochen, > I think !instanceof and !in are ok. The others... not sure here. Right > now a*=b, which means !< is >=. And in this > case I actually prefer >=. Sometimes we write code like "!(a > b)", now we can write "a !> b" instead, which is much close to our mind :) Cheers,

Re: Negative relational operators for Groovy 3

05 PM, Guillaume Laforge <[hidden email]> wrote: On Fri, Nov 18, 2016 at 1:58 PM, Jochen Theodorou <[hidden email]> wrote: On 18.11.2016 13:45, Daniel Sun wrote: Hi all, The new parser(Parrot) supports negative relational operators now, which is proposed by Guillaume Laf

Re: Negative relational operators for Groovy 3

OK. I see :) 在 Cédric Champeau [via Groovy] <ml-node+s329449n5736817...@n5.nabble.com>，2016年11月18日 下午9:18写道： I agree with Jochen and Guillaume: +1 to !instanceof and !in, but I don't like the other variants. 2016-11-18 14:11 GMT+01:00 Daniel Sun <[hidden email]>: Hi Jochen,

Re: Negative relational operators for Groovy 3

ed it but another of our operators) and probably 'is' too. If we do is, I don't see why we wouldn't do it for all methods (that return boolean), e.g. assert 'a'.!isUpperCase() and I am a little hesitant about such a notation. Paul. > On Fri, Nov 18, 2016 at 2:25 PM, Daniel Sun <[hidden email]>

Negative relational operators for Groovy 3

Hi all, The new parser(Parrot) supports negative relational operators now, which is proposed by Guillaume Laforge :) Here are some example

Re: About the parrot branch of apache/groovy

erge the PRs too? Are is there a particular issue with those? On Fri, Nov 11, 2016 at 4:48 PM, Daniel Sun <[hidden email]> wrote: Hi all, In order to not impact the existing branches as possible as I can, I created a branch named "parrot" and put the new parser(Parrot) at the new

Re: About the parrot branch of apache/groovy

e! Le vendredi 11 novembre 2016, Daniel Sun <[hidden email]> a écrit : Hi Guillaume, Currently I am not familiar with macro, so I will try to merge the PR into parrot branch and run test cases again. Cheers, Daniel.Sun 在 "Guillaume Laforge [via Groovy]" <ml-node+[hi

Re: About the parrot branch of apache/groovy

Hi Paul, I used "gradlew -PuseAntlr4=true console" to launch groovyConsole. It's OK for me now. Can you reproduce the issue? In addition, the groovyConsole uses the old parser even if option "-PuseAntlr4=true" applied. I'll fix it later :) Cheers, Daniel.Sun -- View this message

Default Method for Groovy 3

Hi all, The new parser(Parrot) supports default method now. You can find the new feature at the enhancedInterface branch of groovy-parser project (

Re: Default Method for Groovy 3

Java code, felt limiting. On Thu, 8 Dec 2016 at 17:40, Daniel Sun <[hidden email]> wrote: Hi all, The new parser(Parrot) supports default method now. You can find the new feature at the enhancedInterface branch of groovy-parser project <https://github.com/daniels

Re: Welcome to our new committer : Sergei Egorov

Hi Sergei, Congratulations! I believe Groovy will be much more powerful because of your endless effort :-) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Welcome-to-our-new-committer-Sergei-Egorov-tp5737173p5737178.html Sent from the Groovy Dev

Re: About SimpleHTTPServer

Hi Jochen, Given we have a directory containing some web pages and want to access these pages via http protocal(e.g. we want to test WebRTC app), we have to run a httpserver to provide http service. In the past, we have to use Python to achieve the requirement because its SimpleHTTPServer

Re: About SimpleHTTPServer

Hi Sébastien, The SimpleHTTPServer will be implemented with NO 3rd part library, so it will not impact existing production systems. In addition, it is recommended to be used to provide http service for convenience(such as testing WebRTC app). If we want to deploy our static web site, the

Re: About SimpleHTTPServer

Hi Remi, Your reply is always so helpful :-) As far as I remember, Sun introduced the http server in Java6. It's lucky for us that it's included in the OpenJDK too. Cheers, Daniel.Sun -- View this message in context:

Re: About SimpleHTTPServer

Yeah, I think so too, but I'm not sure whether Groovy already has some similar function or not... Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/About-SimpleHTTPServer-tp5737191p5737196.html Sent from the Groovy Dev mailing list archive at Nabble.com.

SimpleHTTPServer for Groovy 3( Maybe Groovy 2.5.0? )

Hi all, SimpleHTTPServer has been implemented(http://bit.ly/2hsKm0V), it supports serving files not only under directory but also in the zip file. Here is the usage: "-lh listen on a port and provide http service", e.g. *serve files under current directory*: groovy -lh 8000

Re: SimpleHTTPServer for Groovy 3( Maybe Groovy 2.5.0? )

> groovy -m com.sparkjava:spark-groovy -c "serve(port: 8080, path: 'd:\\temp')" How many characters will we type... to be frank, I am not that patient to type such a long command. Cheers, Daniel.Sun -- View this message in context:

Re: groovy git commit: Add option -lh to launch SimpleHTTPServer

OK. I will revert them later. Cheers, Daniel.Sun 在 "Graeme Rocher-2 [via Groovy]" <ml-node+s329449n5737248...@n5.nabble.com>，2016年12月15日 15:49写道： Agreed. "parrot" should be kept about the gramma and not adding new features. Cheers On Wed, Dec 14, 2016 at 1:

Re: Gramma around annotations

Hi Graeme, It should be feasible in theory. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Gramma-around-annotations-tp5737249p5737255.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: About SimpleHTTPServer

Hi Sébastien, > My concern is that an HTTP server built into groovy would come with its > potential risks – even it is not used directly. To be frank, I can not figure out... Could you tell me some exact potential risks? > Having to redeploy an > app where groovy is embedded because

Re: About SimpleHTTPServer

Thanks for your suggestion, mrhaki :) In order to avoid maintaining the httpserver, I'd like to use the built-in httpserver of JDK. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/About-SimpleHTTPServer-tp5737191p5737213.html Sent from the Groovy Dev

Re: About SimpleHTTPServer

That's great :) -- View this message in context: http://groovy.329449.n5.nabble.com/About-SimpleHTTPServer-tp5737191p5737216.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: About SimpleHTTPServer

Hi Paul, The built-in httpserver of JDK suggested by Remi seems better for us, it is stable and does not require 3rd party library: http://hg.openjdk.java.net/jdk9/jdk9/jdk/file/tip/src/jdk.httpserver/share/classes/com/sun/net/httpserver/package-info.java As to hooking to the

Re: Default Method for Groovy 3

there is no flag for specifying a default method in the JVM spec, hence no ACC_DEFAULT flag in ASM, a default method is just a non abstract method in an interface. Also default and static methods in interface can be either public or private. cheers, Rémi - Mail original ----- > De: "Daniel S

Elvis Assignment for Groovy 3

Hi all, The new parser "Parrot" supports Elvis Assignment(i.e. ?=) now. Here are some examples: def a = 2 a ?= 1 assert a == 2 a = null a ?= 1 assert a == 1 a = null a ?= a ?= 1 assert a == 1 P.S. supports static compilation as well. Cheers,

Re: Elvis Assignment for Groovy 3

My pleasure ;) Cheers, Daniel.Sun 在 "Marcin Erdmann [via Groovy]" <ml-node+s329449n5737109...@n5.nabble.com>，2016年12月3日 下午5:01写道： Awesome, thanks for implementing it Daniel. On Sat, Dec 3, 2016 at 7:59 AM, Daniel Sun <[hidden email]> wrote: Hi all, The new pa

Re: About actor syntax for Groovy 3

Yeah, << is a better choice ;) 在 Jesper Steen Møller [via Groovy] <ml-node+s329449n5737577...@n5.nabble.com>，2017年1月8日 上午1:31写道： But Wouldn’t << be a natural choice which would work today? -Jesper > On 7 Jan 2017, at 18.16, Daniel Sun <[hidden email]> wrote: >

Re: About actor syntax for Groovy 3

operators are pushing Groovy in that direction. Cheers Andres Sent from my primitive Tricorder > On Jan 7, 2017, at 6:21 PM, Daniel Sun <[hidden email]> wrote: > > class ActorTest { >def counter = new Counter() >counter.start() > >for (i in 0 .. 1

About actor syntax for Groovy 3

Hi all, As we all know, GPars is awesome in concurrency programming. How about introducing a new syntax for GPars's actor(http://www.gpars.org/guide/guide/actors.html) to support concurrency programming better like Erlang and

Re: About actor syntax for Groovy 3

very sad to see Groovy become a pale shade of Scala. Custom syntax and new operators are pushing Groovy in that direction. Cheers Andres Sent from my primitive Tricorder > On Jan 7, 2017, at 6:21 PM, Daniel Sun <[hidden email]> wrote: > > class ActorTest { >def counter

Re: About actor syntax for Groovy 3

Hi Jochen, I'm looking for a new syntax for concurrency programming, which should be able to hide complex for developers. As you said, the actor syntax is not necessary. I agree with you, because it just replaces 'send' method with '<<', but I wish the topic could let us think about the

The new annotation Groovydoc for Groovy 3

Hi all, The new annotation Groovydoc has been added in the parrot branch, it can hold groovydoc even at runtime. The usage is very simple, just add @Groovydoc at the beginning of the content of groovydoc, then the Parrot parser will attach Groovydoc annotation to the target element,

Re: master branch has had the 'parrot' branch merged

Hi Paul, We can place these zip files in some site and make gradle download them before testing. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/master-branch-has-had-the-parrot-branch-merged-tp5739796p5739809.html Sent from the Groovy Dev

Re: master branch has had the 'parrot' branch merged

Hi Paul, Thanks for your setting aside some time to merge parrot into mater when you are still on holidays. If I got your words, zip files containing other project source code should be excluded in the source distribution, right? When Groovy 3 is applied by these projects,

Re: Welcome John Wagenleitner to the Groovy PMC

Congratulations to John :) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Welcome-John-Wagenleitner-to-the-Groovy-PMC-tp5739577p5739582.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: About code coverage of Groovy

Thanks, John. Can we check the code coverage for Groovy on travis-ci by default? It will report current code coverage for every commit and PR. Actually, I'm looking for something like this: https://coveralls.io/github/danielsun1106/groovy-parser Cheers, Daniel.Sun -- View this message in

Re: The new annotation Groovydoc for Groovy 3

Hi Mario, Here is the background of the new annotation: About a new annotation Groovydoc http://groovy.329449.n5.nabble.com/About-a-new-annotation-Groovydoc-tp5738721.html Cheers, Daniel.Sun -- View this message in context:

Re: The new annotation Groovydoc for Groovy 3

We can call it "Runtime Groovydoc". -- View this message in context: http://groovy.329449.n5.nabble.com/The-new-annotation-Groovydoc-for-Groovy-3-tp5739731p5739733.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: build requirements for Groovy and language level in master

> And then there is the matter of going to JDK8 master is supposed to be Groovy 3 did we say we want to go to JDK8 here? I think that would be nice... and of course if JDK8 is the minimum could start thinking about having indy enabled by default. Here too I would to hear what people think It

Re: finally success again on JDK9

Glad to hear the good news ;) Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/finally-success-again-on-JDK9-tp5739646p5739649.html Sent from the Groovy Dev mailing list archive at Nabble.com.

  1   2   3   4   >