[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aspectj-users] Refactoring with pointcuts...
|
declare error :
execution(void *.nodeSelected(Node))
: "Refactoring problem!";
/will/ actually do what you need. Although the execution join point
only happens at runtime (obviously), the compiler is smart enough to
realise that a given method declaration will give rise to a matching
execution join point when executed and gives you the match (resulting
in this case in the error message you're looking for).
On 24/08/05, Paulo Merson <pfm@xxxxxxxxxxx> wrote:
> Method declarations are not exposed join points in AspectJ, so I think
> using "call" is the best you can do in a declare statement. If you
> create an advice, you can use "execution" but it won't check it at
> compile-time.
> paulo
>
>
> Eyon Land wrote:
>
> >I was trying to find all locations in my code that
> >called a method nodeSelected(Node). To do this I just
> >used...
> >
> > declare error :
> > call(void *.nodeSelected(Node))
> > : "Refactoring problem!";
> >
> >
> >But when I needed to find all classes that declared a
> >method like..
> >
> >public void nodeSelected(Node node){
> >}
> >
> >I had no idea how to modify the "declare error" above.
> >
> >Can anyone give me a clue?
> >
> >Thanks,
> >Eyon
> >
> >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Read only the mail you want - Yahoo! Mail SpamGuard.
> >http://promotions.yahoo.com/new_mail
> >_______________________________________________
> >aspectj-users mailing list
> >aspectj-users@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> >
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
--
-- Adrian
adrian.colyer@xxxxxxxxx