Difference between revisions of "Cpp Coding Standards/DESIGN/CyclDep"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
m (thusly is not standard English, "thus" is the better choice)
Line 1: Line 1:
Avoid unnecessary dependencies (because they increase coupling, and thusly (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 dependency inversion principle to break cyclic dependencies.
 
Use the dependency inversion principle to break cyclic dependencies.

Revision as of 13:44, 16 February 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.

Personal tools