Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
If inheritance is a prime reason for OOP, then why...
Message
De
31/12/1998 13:28:59
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Programmation Orientée Object
Divers
Thread ID:
00171748
Message ID:
00171955
Vues:
44
Take pity, Rox < s >!

I'm fascinated by your post. But I would be helped a bit by an example. Do you have a simple one that wouldn't be too big a pain to post? I follow the gist, I believe. If I do, then it is very similar to my approach. I always thought is was rather remedial and that everybody else always knew their superclasses < g >.

I especially agree that if something doesn't seem very reusable, then it's got way, way, way too much *stuff* in it.

Did you read the article "ECM in Color" that DF pointed out a while back (www.oi.com/ecm.htm is the link)?


>...snip
>C) Build a new abstract superclass with the stuff I want to reuse,
...snip
>"Favor object composition over class inheritance".
...snip
>- what I initially thought of as a generic superclass ends up not being so abstract after all and I'm left with nice simple generic ( and often concrete) class with a plug-in aggregate to fit my specific need at runtime flexibility.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform