Which is a better technique, More modules, few routines in each modules

[mark hansen]

As I trying to get my coding better, I've been searching for advice regarding which is a better technique. More Modules, each with a unique name referring to the (perhaps) one to five related modules, or fewer modules with more routines in each module.

I have figured out it's easier to have a "Basic stuff" module I put in every project with the commonly used routines and functions... But I was wondering about all of the other project specific code.

Thanks for any advice,
Mark

 

[Joe4]

I think a lot of it is personal preference. I like to arrange my code into logical modules (what makes the most sense, from a logical standpoint). I often have a module named something like "Public Code", which is code I may use in multiple places in my other code (i.e. generic functions).

I think it is best not to bog down any one module with too much code (i.e. one module with 50 procedures!). Likewise, you wouldn't want 50 modules, each with one procedure each.

 

[mark hansen]

Thanks for the insight Joe, it's always helpful to have another view on things. I can certainly understand the excessive modules or procedures in modules...

Mark