Just like the OOP introductory books that still insist in
talking about Cars and Vehicles, Managers and Employees,
Animals and Bees, always using inheritance as code reuse.
Barely talking about is-a and has-a, and all the issues about
fragile base classes.
--
Paulo
Hear, hear. One of the problems with many introductions to
OOP-paradigmed languages such as C++ is that by having to spend a
lot of time explaining how to implement inheritance, the novice
reader thinks that OOP is the 'right' approach to solving many
problems when in fact other techniques ('prefer composition over
inheritance' springs to mind) are far more appropriate. This is
one of the primary problems I find in code of even more
experienced programmers.
