Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0C7B5200BB3 for ; Wed, 19 Oct 2016 04:12:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0A52E160AFB; Wed, 19 Oct 2016 02:12:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 52082160AE5 for ; Wed, 19 Oct 2016 04:12:34 +0200 (CEST) Received: (qmail 941 invoked by uid 500); 19 Oct 2016 02:12:33 -0000 Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.apache.org Delivered-To: mailing list dev@groovy.apache.org Received: (qmail 931 invoked by uid 99); 19 Oct 2016 02:12:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2016 02:12:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6A8BCC0A88 for ; Wed, 19 Oct 2016 02:12:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.572 X-Spam-Level: ***** X-Spam-Status: No, score=5.572 tagged_above=-999 required=6.31 tests=[FORGED_HOTMAIL_RCVD2=1.187, HTML_MESSAGE=2, KAM_UNSUB1=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Bi5JABELqXVy for ; Wed, 19 Oct 2016 02:12:30 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 097C45F201 for ; Wed, 19 Oct 2016 02:12:30 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mbob.nabble.com (Postfix) with ESMTP id 3A33933FC8A8 for ; Tue, 18 Oct 2016 19:05:55 -0700 (PDT) Date: Tue, 18 Oct 2016 19:12:29 -0700 (MST) From: daniel_sun To: dev@groovy.incubator.apache.org Message-ID: In-Reply-To: <5806CC8E.2080308@gmx.org> References: <58065EF3.80504@gmx.org> <5806CC8E.2080308@gmx.org> Subject: Re: Lambda expression for Groovy 3 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21362_2091018039.1476843149259" archived-at: Wed, 19 Oct 2016 02:12:35 -0000 ------=_Part_21362_2091018039.1476843149259 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable (a) That's great! We can get feedback from Groovy developers and refine the= new parser. (b) It's really a hard work. I believe you can achieve it at last :) Cheers, Daniel.Sun =E5=9C=A8 "Jochen Theodorou [via Groovy]" =EF=BC=8C2016=E5=B9=B410=E6=9C=8819=E6=97=A5 =E4=B8=8A=E5=8D=889:3= 0=E5=86=99=E9=81=93=EF=BC=9A 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 them :) (a) I think it would be ok if the new parser is only usable if java8 is used as long as it is not the default. If for example 2.5.0 is going out with the old parser as default, then I see no problem in delivering 2.5.0 with a new parser, that will work only with java8. (b) the MOP2 work I am doing right now is far from complete. The current work is based on what I did 2 years ago already, but was not happy with in the end. You can call it a continuation of that. But it is nowhere usable atm. And I still have one big limitation I would like to be lifted. While I can easily isolate classes and give them their own meta class realm, it is not so easy to do the opposite and let a class participate in a foreign realm, without knowing it. I would like not to rely on a caller sensitive logic if possible. bye Jochen ________________________________ If you reply to this email, your message will be added to the discussion be= low: http://groovy.329449.n5.nabble.com/Lambda-expression-for-Groovy-3-tp5736169= p5736191.html To unsubscribe from Lambda expression for Groovy 3, click here. NAML -- View this message in context: http://groovy.329449.n5.nabble.com/Lambda-exp= ression-for-Groovy-3-tp5736169p5736192.html Sent from the Groovy Dev mailing list archive at Nabble.com. ------=_Part_21362_2091018039.1476843149259 Content-Type: text/html; charset=UTF8 Content-Transfer-Encoding: quoted-printable
(a) That's great! We can get feedback from Groovy develope= rs and refine the new parser.

(b) It's really a hard work. I believe you can achieve it = at last :)

Cheers,
Daniel.Sun



=E5=9C=A8 "Jochen Theodorou [via Groovy]&qu= ot; <ml-node+[hidden email]= >=EF=BC=8C2016=E5=B9=B410=E6=9C=8819=E6=97=A5 =E4=B8=8A=E5=8D=889:30= =E5=86=99=E9=81=93=EF=BC=9A

On 19.10.2016 02:49, daniel_sun wrote:
> The new parser is based on Java8, so it has to target to Groovy3. As f= ar
> 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 them :)

(a) I think it would be ok if the new parser is only usable if java8 is used as long as it is not the default. If for example 2.5.0 is going out with the old parser as default, then I see no problem in delivering
2.5.0 with a new parser, that will work only with java8.

(b) the MOP2 work I am doing right now is far from complete. The current work is based on what I did 2 years ago already, but was not happy with in the end. You can call it a continuation of that. But it is nowhere
usable atm. And I still have one big limitation I would like to be
lifted. While I can easily isolate classes and give them their own meta class realm, it is not so easy to do the opposite and let a class
participate in a foreign realm, without knowing it. I would like not to rely on a caller sensitive logic if possible.

bye Jochen



If you reply to this email, your message wi= ll be added to the discussion below:
http://groovy.329449.n5.nabble.com/Lambda-expression-for-Groovy-3-tp573= 6169p5736191.html
To unsubscribe from Lambda expression for Groovy 3, click here.
NAML
=09 =09 =09
View this message in context: Re: Lambda expressi= on for Groovy 3
Sent from the Groovy Dev mailing list archive at Nabble.com.
------=_Part_21362_2091018039.1476843149259--