. Weird. Shouldn't it be superfluous in
this case?
Anyway, for the moment it seems it is resolved, althougth I regret to admit I
do not understand the mechanism which caused the problem nor the one which
fixed it at all.
Thanks,
OC
> which works without a glitch on my old computer (Java 1.7.0_13 /
or something like that.
All the best,
OC
On 8. 11. 2016, at 15:34, Paul King <pa...@asert.com.au> wrote:
> Hi everyone,
>
> We are hoping to release 2.5 not too far down the track. We are
> working on a revamped release process that is going to dramatically
> improve our abi
,
but triple alas, it is the intended behaviour, as shown in that thread :(
All the best,
OC
On 25. 8. 2016, at 17:54, John Smiljanic <john.smilja...@gmail.com> wrote:
> Groovy 2.4.6
>
> I am trying to override static property access/mutation in a groovy class.
> My objective is to
. Looks like a pair
===
mmc.getAt={ index ->
...
}
mmc.getAt={ String index ->
...
}
===
does the job all right; thanks a big lot again!
All the best,
OC
}
}
}
45 /tmp> groovy q
getAt 1
getAt 3.14
getProperty hi
getAt null
getAt class q
getProperty gstring
46 /tmp>
===
Thanks and all the best,
OC
problems in the, ahem, let's say exciting, world driven by classloaders.
All the best and congrats you have found the culprit,
OC
On 13. 7. 2016, at 18:33, Scott Arnold <sca7...@bjc.org> wrote:
> Good news. I finally figured this out (mostly). It was an issue with dirty
> compi
Jochen,
On 12. 7. 2016, at 12:43, Jochen Theodorou <blackd...@gmx.org> wrote:
> On 11.07.2016 23:26, OC wrote:
>> Hi there,
>>
>> with a pretty complex and heavily AST-transformed code, which, nevertheless,
>> *without typechecking builds and runs all right*, w
hatever code there is at
WideningCategories.java:237 might help; if not, well, I am afraid my report
would be good-for-nothing :(
Thanks and all the best,
OC
> On Tue, Jul 12, 2016 at 7:26 AM, OC <o...@ocs.cz> wrote:
>> Hi there,
>>
>> with a pretty complex
.visitClass(ASTTransformationVisitor.java:134)
at
org.codehaus.groovy.transform.ASTTransformationVisitor$2.call(ASTTransformationVisitor.java:178)
at
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1053)
===
All the best,
OC
Jochen,
On 3. 4. 2016, at 22:29, Jochen Theodorou <blackd...@gmx.org> wrote:
> On 03.04.2016 17:33, OC wrote:
> [...]
>> ===
>> 6 /tmp> > class q {
>> static main(av) {
>>ExpandoMetaClass.enableGlobally()
>>Root.metaClass.static.prop
Jochen,
On 3. 4. 2016, at 7:23, Jochen Theodorou <blackd...@gmx.org> wrote:
> On 01.04.2016 03:48, OC wrote:
>> playing with possibilities of the i/i pattern, I have found one can install
>> a static property to an interface, and then use the property all right --
>
tested :)
Thanks and all the best,
OC
On 2. 4. 2016, at 19:19, Jochen Theodorou <blackd...@gmx.org> wrote:
> On 01.04.2016 21:38, OC wrote:
> [...]
>> ===
>> class Foo {
>> static instance=newInstance()
>> }
>> class Bar extends Foo {
>> static in
ess method Foo.()V from class
Bar
at Bar.(qq.groovy)
at Bar.(qq.groovy)
at qq.run(qq.groovy:4)
87 /tmp>
===
What is the proper way to achieve this?
Thanks a lot,
OC
uadruple ick.
Is there some trick in Groovy which makes this task groovier (or at the very
least reasonably manageable), or am I up to my own source preprocessor and/or
ASTTs (which again would clash with traits :/ )?
Thanks a lot,
OC
process the method, nothing else. Its purpose is to make
it easier for programmer and faster runtime, but the functionality is precisely
the same[**].
Thanks and all the best,
OC
[*] On the other hand, the speed difference should not be that big if the
forwarding is done right, that is, at first f
ough it might
be much faster in the Java world, I did not benchmark it, but I can guess this
probably will be the point of it; along with the problem that dynamically
redirected methods would not work if called from pure Java, which might be
enormously important for someone, luckily, completely irrel
cast object” exception.
That's precisely the terrible mess which causes Java to be one of the worst
languages for learning :(
All the best,
OC
On 28. 3. 2016, at 15:53, frenchy48 <bam...@in2p3.fr> wrote:
> Thanks for replying
> as a side note OOP appear only in chapter 8 of my bo
;'support accented characters all right'
println "${ěěě.class.simpleName} contains $ěěě"
===
As for variables and argument names, you don't need anything at all for the
latter, nothing but 'def' for the former.
All the best,
OC
On 27. 3. 2016, at 17:38, frenchy48 <bam...@in2p3.fr> wrot
We have bumped into this parser issue long long ago, see
http://www.groovy-lang.org/mailing-lists.html#nabble-td5722268
All the best,
OC
On 27. 2. 2016, at 23:19, Bay Batu <batuhanbayra...@gmail.com> wrote:
> Hello,
>
> I tried it and it looks like an issue about firs
19 matches
Mail list logo