>Hi,
>
>has anyone any experience what's better: Having one large VCX with many classes (about 800) or having many VCXs (about 400) with only two classes.
>
>Are there any instantiation performance penalties doing it one or the other way?
>
>Any comments appreciated!
>
>Armin
For source control, smaller is better: if programmer "A" starts modifying a class in a large class library, programmer "B" can't modify any other classes in the same library.
However, in general, I think the main consideration is to keep organized. Too many classes in a library are difficult to find. On the other hand, try to keep together classes with a related function.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
