Bugzilla – Full Text Bug Listing
| Summary: | Support lazyTjp for around advice | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Peter Kvokacka <kvokacka> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | amil |
| Version: | 1.6.9M1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
I would also like this optimization to be implemented. See http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg12031.html and http://aspectj.2085585.n4.nabble.com/lazyTJP-optimization-for-around-advice-td4650646.html#a4650651 (for use with @AspectJ) |
I'd like to use lazyTjp for around advice. It would be really nice to have this feature supported in one of future releases. It allow you to use if() construct like this: public class A { public void m() { } } aspect X { void around(): execution(* m(..)) && if(1==3) { System.out.println(thisJoinPoint); } } It'll improve performance and lower memory consumption when aspect is "turn off" by a condition in if() guards joinpoint construction.