Program to interface

From: andy (andy_wil_at_dot.com)
Date: 03/20/04 

Date: Sat, 20 Mar 2004 19:07:56 GMT

One principle of object-oriented design is "Program to an interface, not an
implementation."

Could somebody elaborate further on this with some examples adhering to the
principle and others violating it?

Thanks in advance!

Relevant Pages

  • Re: OO Design induces an existential crisis
    ... use of a conceptual basis for creating interface boundaries. ... So, if we pick on the Open-Closed principle, would that be enough to break ... > move it to a different node on the tree and reshuffle the hierarchy. ... Or is factoring out duplication NOT one of ...
    (comp.object)
  • Re: OO Design induces an existential crisis
    ... > use of a conceptual basis for creating interface boundaries. ... >> And, some of the are vague, such as Open-Closed Principle. ... >> move it to a different node on the tree and reshuffle the hierarchy. ... Or is factoring out duplication NOT one of ...
    (comp.object)
  • Re: Disadvantages of Dependency Inversion?
    ... principle does not imply layering is a similarly basic principle. ... I accept the explicit seperation of interface from implementation does ... a subset of their interface conforms to CI (type substitutability). ... for me subtype is short for substitutable type. ...
    (comp.object)
  • Re: Disadvantages of Dependency Inversion?
    ... principle does not imply layering is a similarly basic principle. ... MN>B....component B is dependent on component A for an interface. ... created, an existing dependency is changed, and a new dependency appears. ... a subset of their interface conforms to CI (type substitutability). ...
    (comp.object)
  • Re: Disadvantages of Dependency Inversion?
    ... The value should be that the principle ... Being coupled to the name of an interface implementation is effectively ... what DIP is. ... It is *modularity*. ...
    (comp.object)