Good question.
Does the Framework ~really~ rely heavily on implementaion
inheritance? Sure everything derives from object, but I
mean in a deep or wide way. I think that you'll find the
implementaion inheritance to be pretty light-weight
compart to something like MFC.
It might be interesting (or not) to compare how often a
class (in the framework) derives from another class
and/or how many interfaces it implements.
I guess one thing that has changed is there is support
for interface inheritance in the Common Language
Runtime. If I'm not mistaken (and I may be) there was no
II support in the language (VB).
Implementation inheritance has a certain set of
challenges associated with it. Especially when changes
are made to the base classes. Now Microsoft has to be
careful when it considers changing it's base classes
because we'll all have to live with it.
Hope you get some better answers that this one.
-----Original Message-----
Hi all,
During the COM age, Microsoft's policy was against
implementationinheritance.
Now, it turns 180 degrees and all the .NET Framework
relies heavily onimplementation inheritance.
What's changed?
Thanx,
Adrian.
.