Re: About actor syntax for Groovy 3

2017-01-08 Thread Jochen Theodorou
On 08.01.2017 13:08, Daniel Sun wrote: 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

Re: About actor syntax for Groovy 3

2017-01-08 Thread Daniel Sun
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 con

Re: About actor syntax for Groovy 3

2017-01-07 Thread Jochen Theodorou
On 07.01.2017 18:16, Daniel Sun wrote: 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 Scala(https://rocketeer.

Re: About actor syntax for Groovy 3

2017-01-07 Thread Russel Winder
On Sat, 2017-01-07 at 18:30 +0100, Jesper Steen Møller wrote: > But > > Wouldn’t << be a natural choice which would work today? > > -Jesper > All pull requests against the jdk8 branch will be reviewed. -- Russel. = Dr

Re: About actor syntax for Groovy 3

2017-01-07 Thread Russel Winder
GPars is a library, it can have no special syntax other than what Groovy provides. Given Groovy has no <- operator and no way of creating library defined operators it seems impossible to have this operator. Even though is it a very Go way of doing message passing. On Sat, 2017-01-07 at 18:34 +01

Re: About actor syntax for Groovy 3

2017-01-07 Thread jim northrop
329449.n5.nabble.com/About-actor-syntax-for-Groovy-3- > tp5737574p5737576.html > To unsubscribe from About actor syntax for Groovy 3, click here. > NAML > <http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.

Re: About actor syntax for Groovy 3

2017-01-07 Thread Andres Almiray
n context: > > http://groovy.329449.n5.nabble.com/About-actor-syntax-for-Groovy-3-tp5737574p5737575.html > > Sent from the Groovy Dev mailing list archive at Nabble.com. > > > If you reply to this email, your message will be added to the discussion > below: > http://groovy.329449.n5.nabble.com/About-actor-syntax-for-Groovy-3-tp5737574p5737576.html > To unsubscribe from About actor syntax for Groovy 3, click here. > NAML > > View this message in context: Re: About actor syntax for Groovy 3 > Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: About actor syntax for Groovy 3

2017-01-07 Thread Daniel Sun
As Andres pointed, it is better for GPars to have its own DSL. Cheers, Daniel.Sun 在 "jnorthr [via Groovy]" ,2017年1月8日 上午1:35写道: Russel is working on GPars v2.0 so have asked him if this proposed change is do-able. On 7 January 2017 at 18:28, Andres Almiray <[hidden email]> wrote: This is a

Re: About actor syntax for Groovy 3

2017-01-07 Thread Daniel Sun
Yeah, << is a better choice ;) 在 Jesper Steen Møller [via Groovy] ,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: > > Hi all, > > As we all know, GPars is awesome in concurrency progr

Re: About actor syntax for Groovy 3

2017-01-07 Thread Daniel Sun
Hi Andres, If Scala was the sun, I wish Groovy was an eclipse ;) Maybe adding custom syntax for actor is not good idea for a programming language. But as a programming language, Groovy should learn good things from others to keep evolving and competitiveness. (like C# and Java) Che

Re: About actor syntax for Groovy 3

2017-01-07 Thread jim northrop
Have found this Actor slideshow that may help us a bit ? http://www.slideshare.net/drorbr/the-actor-model-towards-better-concurrency On 7 January 2017 at 18:30, Jesper Steen Møller wrote: > But > > Wouldn’t << be a natural choice which would work today? > > -Jesper > > > On 7 Jan 2017, at 18.16

Re: About actor syntax for Groovy 3

2017-01-07 Thread jim northrop
a nice idea ;-D On 7 January 2017 at 18:30, Jesper Steen Møller wrote: > But > > Wouldn’t << be a natural choice which would work today? > > -Jesper > > > On 7 Jan 2017, at 18.16, Daniel Sun wrote: > > > > Hi all, > > > > As we all know, GPars is awesome in concurrency programming. How >

Re: About actor syntax for Groovy 3

2017-01-07 Thread jim northrop
Russel is working on GPars v2.0 so have asked him if this proposed change is do-able. On 7 January 2017 at 18:28, Andres Almiray wrote: > This is a slippery slope IMHO. > > Adding custom syntax support in core for GPars might sound like a good > idea given the fact that GPars is bundled with cor

Re: About actor syntax for Groovy 3

2017-01-07 Thread Jesper Steen Møller
But Wouldn’t << be a natural choice which would work today? -Jesper > On 7 Jan 2017, at 18.16, Daniel Sun wrote: > > 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.h

Re: About actor syntax for Groovy 3

2017-01-07 Thread Andres Almiray
This is a slippery slope IMHO. Adding custom syntax support in core for GPars might sound like a good idea given the fact that GPars is bundled with core. OTOH what about Spock, Grails, Ratpack and others? Wouldn't they benefit from custom syntax too? probably yes. Are they bundled with core?

Re: About actor syntax for Groovy 3

2017-01-07 Thread Daniel Sun
class ActorTest { def counter = new Counter() counter.start() for (i in 0 .. 10) { counter <- i// send message to the counter actor } } should be modified as: class ActorTest { public static void main(String[] args) { def counter = new Counter()