On 09.01.24 22:53, MG wrote:
Hi Jochen,
we do not use any of these Groovy features - why is that information
relevant to you ?
I was playing around with some thoughts for me the biggest problem
are per instance meta classes really.
If you are gauging if you can remove some potentially
Hi Jochen,
we do not use any of these Groovy features - why is that information
relevant to you ?
If you are gauging if you can remove some potentially unused features
from Groovy, it might be best to state so - nothing to get people to
take the time to reply, than to tell them an important
Jochen,
> On 8. 1. 2024, at 22:12, Jochen Theodorou wrote:
... ... ...
> if we would go and say a class gets its meta class only once, but you
> can control what it is if you must, then you have no problem... well
> performance wise maybe
Precisely. Thanks a lot!
OC
> On 8. 1. 2024, at 22:12,
On 08.01.24 20:42, OCsite wrote:
[...]> - the extension class list is collected compile-time and (eventually
when my build script creates the application) automatically added to the
/org.codehaus.groovy.runtime.ExtensionModule/ manifest, so that they
just-work without any extra ado.
So your
Jochen,
> On 8. 1. 2024, at 16:10, Jochen Theodorou wrote:
> I would like to know from users on this list mostly if they are using
> specific features of the meta class system and MOP, but especially what for.
>
> (1) categories
> ...
> use (CategoryClass) {
> // some code and callstack here
I myself use @POJO almost everywhere.
On Mon, Jan 8, 2024, 09:11 Jochen Theodorou wrote:
> Hi all,
>
> I would like to know from users on this list mostly if they are using
> specific features of the meta class system and MOP, but especially what
> for.
>
>
> (1) categories
>
>
