Re: [aspectj-users] Compile-time signature

2018-03-12 Thread Andy Clement
I’ve made some modifications - basically changed all the thisJoinPoint and thisEnclosingJoinPoint code generation for all join point kinds. These are in the 1.9.0.BUILD-SNAPSHOT build available from the repository: maven.springframework.org http://maven.springframework.org/snapshot or

Re: [aspectj-users] Compile-time signature

2018-02-26 Thread Fabian Bergmark
Ok! Yes sure! On Feb 26, 2018 20:31, "Andy Clement" wrote: > I did do some initial exploration work and it turned out to be bigger > impact than I’d hoped. Doesn’t mean it won’t happen - just that it’ll take > longer. If I did get you a snapshot build with prototype code in it, would > you be ab

Re: [aspectj-users] Compile-time signature

2018-02-26 Thread Andy Clement
I did do some initial exploration work and it turned out to be bigger impact than I’d hoped. Doesn’t mean it won’t happen - just that it’ll take longer. If I did get you a snapshot build with prototype code in it, would you be able to try it out and see if it behaves in your situation? cheers,

Re: [aspectj-users] Compile-time signature

2018-02-26 Thread Fabian Bergmark
Any progress? Cheers, Fabian 2018-01-10 19:48 GMT+01:00 Andy Clement : > The proper optimization here is to use the LDC byte code that takes a > constant class, rather than the string variant and then class loading. The > original AspectJ used the string form because LDC didn't take a class > ori

Re: [aspectj-users] Compile-time signature

2018-01-10 Thread Andy Clement
The proper optimization here is to use the LDC byte code that takes a constant class, rather than the string variant and then class loading. The original AspectJ used the string form because LDC didn't take a class originally. Over the years a few places have been updated but not everywhere ( this