Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAJ2HCd-3B_jMXCrH8h0QVd6uUyOucvVwStx+hZEcZCaqfA9aBA@mail.gmail.com>
References: <sbmp-dontrebrand-1aOs9f-0003Va-Ec-clark@factgem.com>
	<ABB05FFA-9C53-487D-A8E0-EC1FE090C36C@factgem.com>
	<CAMbkE7TCejcbW6OFVWx3rZK+74zNUaiqhiNirGH+s5HZDcVrkQ@mail.gmail.com>
	<7BB17F4C-00F2-4562-BC11-5D391C1BB3D7@factgem.com>
	<CAMbkE7SbTQrXO__y6gPfFWbwobHVF0iZciT6KmsT7ppy8HOhPg@mail.gmail.com>
	<0CCA3790-E2FA-4230-8261-570B51DEBE57@factgem.com>
	<56AAC946.4010503@gmx.org>
	<64238992-F870-4823-A419-2E02021ABA18@factgem.com>
	<56AC7142.4050901@gmx.org>
	<CAJ2HCd-3B_jMXCrH8h0QVd6uUyOucvVwStx+hZEcZCaqfA9aBA@mail.gmail.com>
Date: Sun, 31 Jan 2016 21:29:09 +0100
Message-ID: 
 <CAByu6UW8eH5pBBi_i-KgUOUp9Fzr-GkVTPsXe6+Ceo+KmpGE1Q@mail.gmail.com>
Subject: Re: Groovy 3.0
From: Thibault Kruse <tibokruse@googlemail.com>
To: dev@groovy.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Are Antlr 4 and Jva 8 syntax linked somethow, meaning is there a hard
problem describing certain java8 features using whatever antlr version
is used right now?

I would assume that porting Groovy to Java9 takes precendence over
changing the syntax, so it would be nice to have a roadmap that decide
which version will contain which of those changes. Given the scarce
resources it might be useful to separate these changes, but given that
the API will change in either case, it might be better to have one
avalanche of a change rather than annoying users multiple times.


On Sat, Jan 30, 2016 at 9:31 AM, Guillaume Laforge <glaforge@gmail.com> wro=
te:
> When you put the antlr v4 parser, you also mean the Java 8 constructs, I
> guess?
>
> Because otherwise, that's really my wish list too :-)
>
> On Sat, Jan 30, 2016 at 9:16 AM, Jochen Theodorou <blackdrag@gmx.org> wro=
te:
>>
>> On 29.01.2016 18:05, Clark Richey wrote:
>> [...]
>>>
>>> What do you think about having a page on the web site that
>>> provides at least basic information about the status of on-going Groovy
>>> development?  This will serve the dual purpose of letting people know
>>> that Groovy development isn=E2=80=99t dead and heighten awareness of th=
e current
>>> lack of support for full time development of the language.
>>
>>
>> I can make a wishlist like this:
>>
>> * integrate and complete antlr4 parser
>> * complete spec for and implement MOP 3
>> * add c# inspired asnyc/await to Groovy and see if tight integration wit=
h
>> gpars is possible
>> * new joint compiler
>> * JSR 269 support
>> * java9 jigsaw support
>> * complete macro system
>> ...
>>
>> is that what you wanted?
>>
>> bye Jochen
>>
>>
>>
>>
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+