Don't Inherit Code
I learned a long time ago that there are essentially three different kinds of relationship between two classes. They are, in order of increasing tightness:
Published at DZone with permission of Kevin Rutherford, author and DZone MVB. (source)- Uses, in which I care only about your public API;
- Creates, in which I also need to know your class;
- Inherits/extends, in which I can also see some of your workings and I become part of you.
Don’t do that last one. Ever.
Many of the GoF patterns help move code up this list, from tight towards loose coupling. Except TemplateMethod, which not only encourages inheritance, it also creates a circular dependency by having the superclass only “work” in the presence of extensions. Bad.
Don’t inherit code. Bad.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Tags:
Comments
Euwe Max replied on Wed, 2013/01/23 - 4:23pm
Um... why not?