Re: [aspectj-users] identifying class not included in pointcut

2014-03-27 Thread mdbgb
Right, I see what you're saying. There is nothing special , as in possessing some kind of built in signifier, about being the first modified method entered from an unmodified method. Unmodified methods just sort of don't exist in that universe at all. So that being the case, it is also a true

Re: [aspectj-users] identifying class not included in pointcut

2014-03-27 Thread Frank Pavageau
It's difficult to know that you're going through an unmodified method without modifying the method. I guess you could maintain a (thread-local) stack of the methods called (by using a call(* *(..)) pointcut) and verifying in the weaved methods (using a execution(* *(..)) pointcut) that it matches

Re: [aspectj-users] identifying class not included in pointcut

2014-03-27 Thread trhouse
If I could know when the program had entered a non instrumented method,that would suffice since I could just throw a global flag of some description, though thinking about it now, that's a lot of flag checking I'm setting myself up for... It seems like a very basic fact about any program utilizing