Re: Difference between inheritance and package use

[jls@netcom.COM (Jim Showalter)]

]>>Which of these is better? Well, there certainly does seem to
]>>be a lot of argument about it. We know more about the first

]>I hardly see that these are contradictory or exclusive.  This is like
]>having an argument in cooking about which is better, cooking things or
]>mixing them together.

Read on. I later point out that arguing over which is
better, inheritance or composition (thanks for the term
"composition", by the way) is as dumb as arguing over
nature vs nurture, or any other black-and-white argument
in a world of grey.

]>Careful, you're starting to use "the world can be divided into two
]>kinds of people" arguments.  Soon somebody will be claiming that
]>preference for inheritance or composition will be based on what part
]>of your brain you use more often.

That would be silly--everybody knows that the real indicator
is not brain usage but, rather, one's astrological sign.

]>   A tractor does not share much interface with a wheel or an engine.
]>Describing a tractor as inheriting from Wheel and Engine, would be
]>stupid.

Agreed, stupid it would be. It would also, by the way, be
a great example of multiple inheritance. ;-)
-- 
*** LIMITLESS SOFTWARE, Inc: Jim Showalter, jls@netcom.com, (408) 243-0630 ****
*Proven solutions to software problems. Consulting and training on all aspects*
*of software development. Management/process/methodology. Architecture/design/*
*reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++.    *