Talk:Dependency injection
From Wikipedia, the free encyclopedia
[edit] Links
- A beginner's guide to Dependency Injection by Dhananjay Nene
- Dependency Injection: Vitally Important or Totally Irrelevant? a presentation by Jim Weirich at OSCON 2005
- Dependency Injection in Ruby by Jim Weirich
- Design Patterns: Dependency Injection by Griffin Caprio
[edit] Problems with the term "Dependency Injection" and "Inversion of Control"
"Dependency Injection" is a vague description the practice it refers to. That practice is to externalize connections between components either in a specific third component or by using a configuration file to direct a general configuration component to do it. Injecting the dependency is only a part of the process.
"Inversion of control" as described in that article and elsewhere is clearly a misnomer. If class X depends on class Y then inserting the interface I such that X depends on I and Y implements I, is no inversion. To qualify as inversion Y would have to depend on X, not I. Precision-nazi 09:24, 6 August 2006 (UTC)
It seems that Setter, Constructor and Interface under the list of styles should be more precise about where they point. Setter currently points to the dog, whereas Constructor and Interface point to disambiguation pages; they should all point specifically to pages about the styles of dependency injection. --134.173.86.14 06:37, 24 January 2007 (UTC)
[edit] sans-serif font confused me
loC (L) and IoC (i) can you tell the difference?
I thought it was reusing the acronym for "Lines of Code".
IoC loC IoC loC IoC loC IoC loC IoC loC IoC loC IoC —The preceding unsigned comment was added by 71.103.106.212 (talk) 18:47, 25 January 2007 (UTC).
IOC IOC when all capital, it is clearer that this must be an i, since it (usually) does not make sense for the first letter of an all-capital acronym to be lowercase.
