What he means is that just because subclassing is available as a technical mechanism, we should only use it for modeling subtyping and not implementation reuse (only in very few cases this is actually useful in the long run).
For reference, this goes under the name of Liskov substitution principle and one nice article that explains it is this one:
Cheers,Doru
On Tue, Jun 30, 2015 at 11:21 AM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
2015-06-30 11:00 GMT+02:00 stepharo <stepharo@free.fr>:
What I mean is that this is not good to have subclassing when we can use subclassing.
Are you sure you mean that? *confused*
Thierry
--