Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Is one concrete Class per Class Lib a poor/good idea?
Message
De
06/07/2004 17:00:12
Mike Yearwood
Toronto, Ontario, Canada
 
 
À
06/07/2004 16:44:52
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Divers
Thread ID:
00916585
Message ID:
00921193
Vues:
76
Hi Thomas

>I haven't thought about all the implications,
>but the length of set classlib should be finite.

I've got my application specific subclasses, my company subclasses and MaxFrame which also has layers of classes and subclasses. I don't know how many classes can be in the set classlib at any one time, but it doesn't seem to be an issue.

>Which pulls me straight in the direction of
>"use few classlibs, if you add other/foreign code,
>it will get worse".

I do think we should be using fewer classes overall, but by designing the classes so they have distinct purposes.

>
>Also, searching through fewer classlibs "feels"
>faster, but such a feeling should be substantiated
>with a few measurements.
>Have you done a few of those already and my fears are
>unsubstantiated <g> ?

Actually, your fears are already unsubstantiated. You don't have anything to base them on <g>. I know the name of the class I'm looking for before I ever think about the classlib it is in.

I have a few pens on my desk. I can grab any one of them faster than I can grab one in a desk drawer.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform