Difference between revisions of "Cpp Coding Standards/DESIGN/CyclDep"
From Apache OpenOffice Wiki
m (added link) |
m |
||
| 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 [ | + | Use the [[Cpp_Coding_Standards/Design/DIP|Dependency Inversion Principle]] to break cyclic dependencies. |
Revision as of 13:34, 12 April 2007
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.
