<http://www.javaworld.com/javaworld/jw-01-2002/jw-0118-aspect.html>
The series is focused on AspectJ, of course, but it's giving me some insight into how to use aspects and when they would be useful.
As I study aspects, I am beginning to conceive of aspects as "execution monitors with the capability of changing the monitored-program's flow or state". That is to say, they monitor events in the execution of the "aspected" program and intervene in its execution, possibly changing the flow (redirecting or vetoing function calls) or changing the values of variables or function arguments. Initially, this may seem too invasive to merit serious consideration (as in, "but I thought that encapsulation was a good thing"), but the articles elaborate on when and why it is appropriate.
Art Eschenlauer wrote:
Software Development Magazine had a series of two articles on Aspect Oriented Programming (AOP) by Ivar Jacobson (to access these copyrighted articles you need a free login - sorry):
<http://www.sdmagazine.com/documents/s=8899/sdm0310e/sdm0310e.html>
<http://www.sdmagazine.com/documents/s=8939/sdm0311d/sdm0311d.html>
There have been efforts at IBM and Xerox Parc to create AOP support for Java, described respectively at
<http://www.alphaworks.ibm.com/tech/hyperj>
and
<http://aspectj.org>
Has anyone on the list found a personal favorite introduction to AOP?
Has anyone thought of how AOP might be implemented in Unicon (preferably by using existing language features rather than adding new ones)?
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
