Difference between revisions of "Cpp Coding Standards/DESIGN/CyclDep"
From Apache OpenOffice Wiki
m (Cpp Coding Standards/Design/CyclDep moved to Cpp Coding Standards/DESIGN/CyclDep: simplicity) |
B michaelsen (Talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
Avoid unnecessary dependencies (because they increase coupling, and thus (re)compile time). Cyclic dependencies are even worse: they glue two (or more) seemingly unrelated units together, into something larger, whose parts cannot be used (or tested, or deployed) in isolation. | Avoid unnecessary dependencies (because they increase coupling, and thus (re)compile time). Cyclic dependencies are even worse: they glue two (or more) seemingly unrelated units together, into something larger, whose parts cannot be used (or tested, or deployed) in isolation. | ||
| − | Use the [[Cpp_Coding_Standards/ | + | Use the [[Cpp_Coding_Standards/DESIGN/DIP|Dependency Inversion Principle]] to break cyclic dependencies. |
| + | [[Category:Coding Standards]] | ||
Latest revision as of 17:07, 14 December 2009
Avoid unnecessary dependencies (because they increase coupling, and thus (re)compile time). Cyclic dependencies are even worse: they glue two (or more) seemingly unrelated units together, into something larger, whose parts cannot be used (or tested, or deployed) in isolation.
Use the Dependency Inversion Principle to break cyclic dependencies.
