May be other way to do is to move all the loging code out of mainline source and put it in aspects. That way you can control it better dynamically whether to turn the loggin on or off.
Srini -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seva Popov Sent: Friday, August 10, 2007 1:16 PM To: [email protected] Subject: RE: [aspectj-users] Parameter construction pointcut? Thanks for the quick reply. Regarding my problem: it is a profiler findings that forced me to work on the log.debug() problem :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Bodden Sent: Friday, August 10, 2007 11:06 AM To: [email protected] Subject: Re: [aspectj-users] Parameter construction pointcut? On 10/08/07, Seva Popov <[EMAIL PROTECTED]> wrote: This has come up before... > Please, confirm my assumptions or suggest me any solutions besides > fixing the code itself. Your assumption is correct. > P.S. I understand that AspectJ operates on the bytecode but not on the > source code. But is it theoretically possible to augment the AspectJ > with a parameter construction pointcut? Just curious. That is impossible because it is undecidable in general. Where does parameter construction start in general? Not even a human being could answer that question. W.r.t. your problem: I doubt that parameter construction is a bottleneck in your code if all the construction is as easy as in the case you showed. Maybe a profiler would give you more insight. Eric -- Eric Bodden Sable Research Group McGill University, Montréal, Canada _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
