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

From Apache OpenOffice Wiki
Jump to: navigation, search
 
m (added link)
Line 4: Line 4:
  
 
Implement DIP by using abstract interfaces (a class consisting of pure virtual functions only). Typically, provide a public virtual destructor to facilitate polymprphic deletion.
 
Implement DIP by using abstract interfaces (a class consisting of pure virtual functions only). Typically, provide a public virtual destructor to facilitate polymprphic deletion.
 +
 +
See [http://www.objectmentor.com/resources/articles/dip.pdf the original article] for further explanation.

Revision as of 13:31, 12 April 2007

Dependency inversion principle (DIP):

  • high-level modules should not depend on low-level ones. Instead, they should both depend on abstractions.
  • abstractions should not depend on details, but details should depend on abstractions.

Implement DIP by using abstract interfaces (a class consisting of pure virtual functions only). Typically, provide a public virtual destructor to facilitate polymprphic deletion.

See the original article for further explanation.

Personal tools