[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-dev] Why 'FileInputStream fstream = new FileInputStream("test.tmp")' can be traced by using call (*.new(
|
execution(..) would be woven at the execution site, i.e. within the
class FileInputStream, which you most likely do not weave into.
call(...) gets woven at the call site, which you do weave into.
Eric
On 15/05/07, Hongfei Zhu <zuhoo@xxxxxxxxxxx> wrote:
Eric and Cptnuss:
Thanks a lot. I have tried the way you told me, 'FileInputStream fstream =
new FileInputStream("test.tmp")' can be traced
by 'call (*.new(..))' (so does 'call(FileInputStream.new(String))'),
but not 'excution(*.new(..))'. I used to use 'execution(*.new(..))' to trace
constructors. I am wondering that what is the difference between
'call (*.new(..))' and 'excution(*.new(..))', for this situation, why one
can work but the other not? Actually, I am still confused with
'call' and 'execution'. Could you guys give me some tips. Thank you again.
Regards,
Zuhoo
________________________________
Connect to the next generation of MSN Messenger Get it now!
_______________________________________________
aspectj-dev mailing list
aspectj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-dev
--
Eric Bodden
Sable Research Group
McGill University, Montréal, Canada
