> The question is now, if there is any way to prevent the evaluation of
> arguments to method calls. In this case I would very much like to learn how,
Use Haskell instead. :-)
Actually, the only way I can think of doing this is to set up around
advice around the doSomething() method. Something
Holger Hoffstätte wrote:
In short: no. This comes up frequently (unfortunately).
See: http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg06234.html and
especially Eric Bodden's follow-ups.
Thanks for the fast reply. Obviously I didn't search the list
sufficiently thoroughly (wrong keywords
Ahmed, Tarek wrote:
> [snip]
>
> The question is now, if there is any way to prevent the evaluation of
> arguments to method calls. In this case I would very much like to learn
> how,
In short: no. This comes up frequently (unfortunately).
See: http://dev.eclipse.org/mhonarc/lists/aspectj-users/m
Hi all,
I'm a rather unexperienced user of aspectj and would like to share the
following problem with this list because I do not see any solution to it:
In a large project we use log4j for logging and there are, of course,
lots of logger.debug() calls in the code. If I deactivate the debug
l
