Just to close out this discussion. The way I proceeded was to finish the
compile, then invoke the compiled closure (if it did not need any parameters)
to get the created object. I can then analyze the object to pull out the
constants needed.
Thanks for all your responses.
On 2020/02/25 09:19:5
:D yes which is why I am using the script to gather intent and not using it as
the runtime. I need to understand the retry parameters of 10 and 20. I gather
this knowledge at the time of creation and compilation which is harmless to
exits
On 2020/02/24 08:15:38, Alessio Stalla wrote:
> You wo
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
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 are more folks subscribed to that list and
> writing closures and transforms (using Groovy) are topics which that list
> covers. If it turned out
Just for future reference, I'd probably start out with such a question on
the users mailing list. There are more folks subscribed to that list and
writing closures and transforms (using Groovy) are topics which that list
covers. If it turned out that Groovy couldn't handle your use case, the dev
li
Hello
Is it possible to do this in the groovy AST transformation ->
a) in a code visitor, visit a closure expression (in the INSTRUCTION_SELECTION
phase)
b) Using the Closure Node, execute this code to determine its results based on
different parameters
Essentially I want to be able to selecti