[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] Philosophical Questions
|
Again, this is something an IDE can help with. The AJDE already knows what methods are affected, it just need to hook into the refactoring / model changes such that methods / join points entering or leaving a PCD should be subject to confirmation with the user. The user can then decide whether to add/remove the point to/from the pointcut. I expect the IDE's to catch up as AspectJ/the plugin matures.
Ken
"Frank Sauer"
<Frank.Sauer@trcinc. To: <aspectj-users@xxxxxxxxxxx>
com> cc:
Sent by: Subject: RE: [aspectj-users] Philosophical Questions
aspectj-users-admin@
eclipse.org
08/07/2003 19:20
Please respond to
aspectj-users
How is that different from metadata in an external file
going out-of-sync in this same scenario?
To me this seems to be a problem in *ANY* weaving tool.
Not with tags though, but I fail to see how that is AOP
because the tags themselves are still a cross-cutting
concern simply by their existence all over the place.
Frank
-----Original Message-----
From: Cedric Beust [mailto:cbeust@xxxxxxx]
Sent: Tuesday, July 08, 2003 2:14 PM
Cc: AspectJ Users
Subject: Re: [aspectj-users] Philosophical Questions
R. Dale Asberry wrote:
> In what way is the pseudo-regexp pointcut matching fragile?
For example, if the developer renames or refactors their methods, the
pointcuts will no longer find them.
And if the concerns are well separated, the developer might not even be
aware that a certain pointcut is being applied to the method they are
modifying, and they will therefore not even have the option to update
the pointcut definition.
--
Cédric
http://beust.com/weblog
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
--
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
