m (Reverted edits by Andres67rosario (Talk); changed back to last version by Andrew) |
|||
| Line 1: | Line 1: | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
An '''aspect''' is a modular representation of a ''crosscutting concern''. In an AO "programming" language an aspect is a module. In practice, this means it is the module that holds declarations that "identify join points" and "semantic effects at join points". For example, in AspectJ, this can include pointcuts and advice, or inter-type declaration signatures and bodies. In an AO modeling system, it would hold different kinds of structures that identify join points and semantics of those join points. | An '''aspect''' is a modular representation of a ''crosscutting concern''. In an AO "programming" language an aspect is a module. In practice, this means it is the module that holds declarations that "identify join points" and "semantic effects at join points". For example, in AspectJ, this can include pointcuts and advice, or inter-type declaration signatures and bodies. In an AO modeling system, it would hold different kinds of structures that identify join points and semantics of those join points. | ||
Current revision
An aspect is a modular representation of a crosscutting concern. In an AO "programming" language an aspect is a module. In practice, this means it is the module that holds declarations that "identify join points" and "semantic effects at join points". For example, in AspectJ, this can include pointcuts and advice, or inter-type declaration signatures and bodies. In an AO modeling system, it would hold different kinds of structures that identify join points and semantics of those join points.
![[Main Page]](/wiki/skins/common/images/AOSDWikiLogo.gif)