Hi Eric,
yea, I got that, that's why I said "In that case a global setting might
/also/ be useful".
But I doubt that the majority of Groovy users out there who want to
quickly check if it is macros that make their code break in Groovy 4
would know that to do so they just need to "add the
In terms of globally disabling macro methods, you can just add the macro
transform class to the disallowed list in CompilerConfiguration. I think Paul
is describing a mechanism where an individual macro method is taken out of
service.
From: MG
Sent: Tuesday, August 4, 2020 9:53 AM
To:
Hi Paul,
thanks for clearing that up :-)
@unforeseen implications: In that case a global
-Dgroovy.macro.enable=false
might also be useful, to do a quick check if it is macros that are
causing the problem (if we do not have that already).
Btw: Do we have a way to hide the macro definitions
Hi mg,
Just on supplying our own macros, we should do this for Groovy 4. We have
been reluctant so far because we have been conservative about unforeseen
implications. However, unless we start using them more widely, we aren't
going to learn those implications.
I'd suggest having them (to start
