Content deleted Content added
→History: NPOV: Use a presentation based on complementarity rather than superiority. (to be cont.) |
m →History: ce |
||
Line 89:
The challenges of object-oriented programming can also be met by addressing its issues on the paradigm level.
* [[Aspect-oriented programming]] (AOP) is perhaps the closest historic relative to DCI. Most use of Aspects is closely tied to the programmer perspective and require strong tool support to provide good understanding of the software's behavivour on any given [[pointcut]]. The main difference is that in DCI, the structure of the algorithm is primary, with a strong emphasis on its isolation from code outside itself, improving code readability. In AOP, the [[pointcut]] and [[Advice in aspect-oriented programming|advice]] carry equal importance and though physically disjoint, must be understood together to understand the code, because the advice is invasive at the [[pointcut]]. While AOP provides an administrative grouping of a related collection of individual local modifications that together cross-cut the primary structure of the code, DCI is a semantic expression of an algorithm with first-class analysis standing that invokes existing object methods. DCI cann be thought of as a way of taking a large [[Advice in aspect-oriented programming|advice]] and allowing parts of it to be injected into a number of regularized [[pointcut]]s.{{citation needed|date=February 2016}}
| |||