On 13/08/07, Daniels, Troy (US SSA) <[EMAIL PROTECTED]> wrote:
> When looking at source code, it should be fairly easy to define a cutpoint
> that ...
Yes, but you cannot consider source code because AspectJ is woven in
terms of bytecode.
Consider this:
public static void main(String args[]) {
String result = doAllTheStuffInTheWorld();
logger.debug("Result is:" + result);
System.out.println(result);
}
In this case, do you not want to execute doAllTheStuffInTheWorld(),
just because it's result value is logged? Makes no sense, does it?
> Speaking with the blissful ignorance of someone totally unfamiliar with the
> AspectJ source, I expect that it would be possible to create such a point
> cut, but it would only work for compile-time weaving. If the ApsectJ team is
> committed to having compile-time and run-time weaving be interchangeable,
> that means this type of cutpoint is not doable.
This has nothing to do with compile time vs. load time but with
bytecode vs. source code.
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
