Content deleted Content added
Line 63:
* Dependency injection<ref>Jakob Jenkov, ''Dependency injection''. http://tutorials.jenkov.com/dependency-injection/index.html</ref> is a longstanding approach to change the functionality of an object at run time by allowing it to "outsource" some of its execution to an external object that can be re-bound at will. Most implementations of dependency injection lead to the [[self schizophrenia]] problem, which implementations of DCI address properly.
* Multi-paradigm design
* [[Aspect-oriented programming]] (AOP) is perhaps the closest historic relative to DCI. However, most use of Aspects is closely tied to the programmer perspective rather than to the end user mental model of use cases. Further, without strong tool support, Aspects usually make code less readable from the perspective of understanding what actually goes on at a given [[pointcut]]. Think of DCI 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 [[
Other recent similar systems...
| |||