About extracting common methods to reduce the size of class files

2018-01-22 Thread Daniel Sun
Hi all, `$getStaticMetaClass`, `getMetaClass`, `setMetaClass`, `invokeMethod`, `getProperty`, `setProperty`, etc. are generated for all groovy classes(implements `groovy.lang.GroovyObject`). In order to reduce the size of class files and speed up generating class files, I suggest extracting

Re: About extracting common methods to reduce the size of class files

2018-01-22 Thread Paul King
Obviously for 3.0. I like the idea in general. I'd check with Jochen on whether he thinks any future MOP work might change which methods we'd want to extract. Cheers, Paul. On Mon, Jan 22, 2018 at 11:12 PM, Daniel Sun wrote: > Hi all, > >`$getStaticMetaClass`, `getMetaClass`, `setMetaCl

Re: About extracting common methods to reduce the size of class files

2018-01-22 Thread Daniel Sun
Looking forward to Jochen's feedback too ;-) Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: About extracting common methods to reduce the size of class files

2018-01-22 Thread Jochen Theodorou
And now with Jochen's feedback ;) $getStaticMetaClass can I think not be put in an interface. It needs static information about the exact class this method is in and there is supposed to be one for each Groovy class we create... if memory serves me right. Moving the others to GroovyObject wo

Re: About extracting common methods to reduce the size of class files

2018-01-22 Thread Daniel Sun
Hi Jochen > $getStaticMetaClass can I think not be put in an interface. It needs > static information about the exact class this method is in and there is > supposed to be one for each Groovy class we create... While I investigated the implementation of the instance method `$getStaticMetaClas