🚀 go-pugleaf

Rick Langel wrote in message <363bd4bd.76565795@207.126.101.81>...
>OK, where in VB does it use inheritance?  That is 1 of the 3 key tenets of
OO.
>If you can show me where you can inherit an object or class from another,
I'd be
>happy to concede that VB is OO, otherwise, be quiet.

Several weeks ago, a gentleman (Robert Conley?) discussed quite articulately
how to apply design patterns using VB via delegation (aggregation?)  and
interface inheritance.  These seemed to be quite legit methods of
inheritance as presented and justified quite eloquently in Kraig
Brockschmidt's book Inside OLE2 (using classes coded in C++).

If VB is able to resolve an OO model without a significant amount of
invention on the part of the implementor, then it deserves to wear the OO
label without complaint.

I personally have been able to use delagation and interface inheritance in
VB to produce several small "hierarchical" relationships (which I of course
modeled first), some 4 nests deep.  This achieved the desired affect of
reuse.  I did not need to recode (other than the delagation) the properties
and methods in the subclasses - i.e. I reused objects.

As a programmer, I've become expert in many programming languages.  I spent
the first half of my career helping IT organizations construct systems of
various sizes.  The single most important factor in a language should always
be: how easy is it to create reusable discrete units of work (modules or
objects).  The single most important asset of any IT org is simply its
catalog of reusable code units.  Reuse is the only way to dramatically
reduce the maintenance costs of computing.  Reuse is the key to zero defect
code.  Too bad we all can't be as dogmatic about reuse as some of us are
about implementation inheritance.

Of course all the tools discussed here have wonderful support for reuse.  So
it seems a bit odd that everyone is so damn fired up about inheritance...
--
Scott L. Holmes