Re: some thoughts on ClassValue

2013-05-03 Thread Jochen Theodorou
sorry for answering so late... Am 27.04.2013 23:54, schrieb John Rose: [...] As a simple example: Make a ClassValue object, bind a 1Mb array to Object.class using it, and then throw it all away. (Except Object.class, naturally.) Even if you do this in a loop, you should not get a storage

Re: some thoughts on ClassValue

2013-04-27 Thread Jochen Theodorou
[...] Could you describe in some more detail, what are meta classes in groovy runtime in terms of how they are generated (lazily at runtime or ahead of runtime?), what dependencies they can have and who is dependent on them. I assume they are generated at runtime, since if they were

Re: some thoughts on ClassValue

2013-04-27 Thread John Rose
On Apr 27, 2013, at 2:13 PM, Jochen Theodorou blackd...@gmx.org wrote: per application and imagine the application is loaded and unloaded several times... a meta class is a large structure with a lot of objects. I could very easily write a Groovy script for such an environment that will

Re: some thoughts on ClassValue

2013-04-27 Thread Jochen Theodorou
Am 27.04.2013 23:26, schrieb John Rose: ... Each instance of the Groovy runtime will use a distinct ClassValue instance. If the ClassValue instance goes dead, then all the values (for each class) bound using that instance should go dead also. If they don't it's a bug. well... I assume that

Re: some thoughts on ClassValue

2013-04-27 Thread John Rose
On Apr 27, 2013, at 2:34 PM, Jochen Theodorou blackd...@gmx.org wrote: Am 27.04.2013 23:26, schrieb John Rose: ... Each instance of the Groovy runtime will use a distinct ClassValue instance. If the ClassValue instance goes dead, then all the values (for each class) bound using that

Re: some thoughts on ClassValue

2013-04-27 Thread Peter Levart
On 04/27/2013 11:54 PM, John Rose wrote: On Apr 27, 2013, at 2:34 PM, Jochen Theodorou blackd...@gmx.org mailto:blackd...@gmx.org wrote: Am 27.04.2013 23:26, schrieb John Rose: ... Each instance of the Groovy runtime will use a distinct ClassValue instance. If the ClassValue instance goes

Re: some thoughts on ClassValue

2013-04-27 Thread Peter Levart
On 04/28/2013 12:31 AM, Peter Levart wrote: On 04/27/2013 11:54 PM, John Rose wrote: On Apr 27, 2013, at 2:34 PM, Jochen Theodorou blackd...@gmx.org mailto:blackd...@gmx.org wrote: Am 27.04.2013 23:26, schrieb John Rose: ... Each instance of the Groovy runtime will use a distinct

Re: some thoughts on ClassValue

2013-04-27 Thread John Rose
On Apr 27, 2013, at 3:46 PM, Peter Levart peter.lev...@gmail.com wrote: Perhaps the following could do: Yes, either of those seems a likely way to break the loop. — John___ mlvm-dev mailing list mlvm-dev@openjdk.java.net

some thoughts on ClassValue

2013-04-26 Thread Jochen Theodorou
Hi all, basically ClassValue is there so that my runtime/framework or whatever can store information and bind it to a class. The information is then available as long as the class exists. In Groovy3 I am going to use this for meta classes. Some time ago a user came up with a special need, he

Re: some thoughts on ClassValue

2013-04-26 Thread Peter Levart
On 04/26/2013 09:59 AM, Jochen Theodorou wrote: Hi all, basically ClassValue is there so that my runtime/framework or whatever can store information and bind it to a class. The information is then available as long as the class exists. In Groovy3 I am going to use this for meta classes.