Why is it hard to add to the build? Is it a bootstrapping issue?
On 23 February 2016 at 09:26, Cédric Champeau
wrote:
> Hi Jochen,
>
> I need more context too. What changes are you talking about? It seems very
> abstract so far. I would be in favor of a joint compiler without stubs in
> Groovy c
;
> On 23.02.2016 11:03, Alessio Stalla wrote:
>
>> Why is it hard to add to the build? Is it a bootstrapping issue?
>>
>
> right now we have 2 steps, build the compiler, then use the new compiler
> to build tests and runtime as well as modules. Since I need part of the
> run
I'm not really answering your question, but, AFAIK, Groovy is not the only
JVM language to use exceptions for control flow. Maybe it is using too many
of them, too often, I don't know. Anyway, not filling the stack trace can
help a lot with exception performance, so that may be a cheap solution.
O
Sorry if outsiders are not meant to chime in :)
Why not
- 2.5 as Cédric proposed (so Java 7 + macros)
- 3.0 with Java 8 and Parrot
- 4.0 with Java 9 and Jigsaw?
This way Groovy versions and Java versions are nicely aligned. To let
people try Parrot early, there could be a 3.0 early access rele
But are users confused by GString today? Or would they be confused if its
behaviour changed and their code stopped working? Also, which users do you
have in mind, noobies, experts, DSL writers, ...?
I for one would like GString to stay the way it is. The examples you
presented don't show problems
Yes, but a toString method with side effects is a really bad coding
practice that won't be fixed simply by reducing the power of GString. Far
from it. Actually it will manifest in even worse ways. GString merely makes
it visible.
Rather, a compiler warning or IDE warning about side effects in metho
hod itself. Which /is/ really poor practice.
On Mon, Sep 10, 2018, 20:33 Jochen Theodorou wrote:
> On 10.09.2018 18:51, Alessio Stalla wrote:
> > Yes, but a toString method with side effects is a really bad coding
> > practice that won't be fixed simply by reducing
Jochen,
what's wrong with
String s = "this is a GString literal"
for people who want a String?
If the problem is type inference, then in
def s = "this is a GString literal"
s could be inferred to be a String, while in
GString s = "this is a GString literal"
s would be a GString. Similarly for para
ing that people expect
>
> def s4 = "x=$x"
>
> to give a String, which of course it currently does not:
>
> [s0, s1, s2, s3, s4].eachWithIndex { final o, final int i ->
> println "$i) ${o.getClass()}: $o"
> }
>
> 0) class java.lang.String: x=abc
Hello folks,
is there a timeframe for Java 11 support in Groovy? Right now it barfs on
JDK 11 classes due to ASM not properly supporting them.
Thanks,
Alessio
Oh, thank you. I was fouled by a failing test, but it was my fault.
On Wed, 24 Oct 2018 at 15:41, Daniel.Sun wrote:
> 2.5.3 supports Java11 and is released.
> 3.0.0 alpha-4 supports Java11 too but not released yet.
>
> P.S. 2.6 is not maintained anymore.
>
>
> Cheers,
> Daniel.Sun
>
>
>
>
>
It says 2.5.4 in the title but 2.5.3 in the actual article.
On Mon, 12 Nov 2018 at 13:07, Remko Popma wrote:
> Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-4-released
>
> Please share on social media.
>
> On Monday, November 12, 2018, Paul King wrote:
>
>> Dear community,
>>
>> The
For 4. (sponsoring individual developers and encouraging developers to
participate) have you considered BountySource?
On Fri, 11 Jan 2019 at 00:46, MG wrote:
> Some thoughts from my side:
>
>1. Do we know of any other ASF projects who gathers donations ? Would
>be surprising if we were t
Great job folks!
Looking forward to including Groovy 3 in Portofino 6! :)
On Tue, 11 Feb 2020 at 04:37, Andrei Karneyenka / Claz.org
wrote:
> Congratulations to all us Groovy users :-) This is truly a great moment.
> Thanks to the Groovy team and to contributors for your hard work and
> dedicati
You wouldn't want to run @Retry({System.exit(0)}) on your server, I presume.
On Mon, 24 Feb 2020 at 00:39, Saravanan Palanichamy
wrote:
>
>
> On 2020/02/23 23:14:32, Paul King wrote:
> > Just for future reference, I'd probably start out with such a question on
> > the users mailing list. There
I think that despite what we engineers like to pretend, languages rise and
fall not much because of their features, but because of the platform they
allow you to program.
Groovy used to be bigger because it was pretty much the only dynamic
language to program on the JVM without going too far from
Well, perhaps it ought to be "black" people who get to say whether they
feel offended by white/blacklist, and in that E. Kemokai's answer is very
valuable.
If we're doing this because someone is being hurt by some offending
language, then +1.
If we're doing this to "be on the right side", then -1 f
ANTLR provides reasonably good error messages most of the time, but
sometimes you have to tweak error handling a bit (in this case, searching
for some more meaningful context to report), and/or refactor the grammar in
a way that causes error reports to be more accurate.
On Thu, 29 Apr 2021 at 17:5
Dates are not something to mess with lightheartedly. All kinds of weird
exceptions exist. In some dates in some timezones, midnight (i.e. 00:00)
does not exist:
https://stackoverflow.com/questions/18489927/a-day-without-midnight
These kinds of implicit conversions may look like they simplify things
Is the year 2001 "before" the date 2001-06-01? I'd say no, I'd say the year
2001 "contains" any date with year = 2001 so it cannot be logically
"before" or "after" it. Suppose you're sorting people by birth date, and
they can enter either the full date or just the year. How would you
meaningfully c
20 matches
Mail list logo
