Le 30/06/2015 19:26, stepharo a écrit :
+1
Thierry we are talking API substituability here.
Yes I know.
Thierry
Le 30/6/15 11:30, Tudor Girba a écrit :
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:
http://www.objectmentor.com/resources/articles/lsp.pdf
Cheers,
Doru
On Tue, Jun 30, 2015 at 11:21 AM, Thierry Goubier
<[email protected] <mailto:[email protected]>> wrote:
2015-06-30 11:00 GMT+02:00 stepharo <[email protected]
<mailto:[email protected]>>:
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
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
