By hoskinator
via hoskinator.blogspot.com
Published: Jul 20 2006 / 06:02
![]() | |
| HTML5 Canvas | |
| Written by: Simon Sarris | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By hoskinator
via hoskinator.blogspot.com
Published: Jul 20 2006 / 06:02
Comments
Peter Stofferis replied ago:
Good article although I don't agree with everything: the decision of using inheritance/composition and interface/(abstract)classes should be made depending on the solution you want to reach. I like coding against interfaces because it's an abstraction of the concrete class instances you're using. But I don't implement interfaces for everything, I try to decide if it's needed or not. Interfaces don't make (abstract)classes obsolete. Sometimes you need a combination of both to reach a good solution.
To make things easier I always think of interfaces as the interface/contract and (abstract) classes as the concrete implementation.
Voters For This Link (13)
Voters Against This Link (0)