Re: Re: Validation class comments

Hello, On 05/29/2002 03:40 AM, Limbourg Arnaud wrote:

Another thing, if you do not minimize class dependencies you may be turning your applications into bloatware because you may be including single classes that have chained dependencies on many others that will be loaded even if you do not used the chained classes functions at all.

You're right, coupling has to be kept low. For performance reasons it can be more efficient to duplicate code but maintenance becomes a nightmare (well IMHO of course ;) It's always the big problem between perfs/maintenance/evolution:etc.

Not in my experience of more that 3 years with that class that I use. It came to a point that it hardly needs any maintenance because it provides all the basic services that I need. The class has now almost 13.000 users and it has been time since anybody made a feature request. So, I think it is pretty much done.

I think there should be core classes available at all times like validation, algorithms ... which we know will be here because there are used by other classes.

The main types of validation are too trivial to compensate the overhead of putting them in separate classes. -- Regards, Manuel Lemos