Modules
- From: "WebBiz" <justask@xxxxxxxxxxxxxxxxx>
- Date: Thu, 17 Aug 2006 12:42:34 -0500
In the event that this is not really a 'personal choice' subject, I was
wondering if it really matters the number of modules added to a project.
For example: Is it better to try and organize your code segments into as few
modules as possible, or better to use more modules in order to separate
functionality into groups?
For some years now, I've been creating programs with just a module or two
and lump everything into them, usually for the purpose of routine access
from anywhere in the program. I might have one that is called modGlobals to
hold all my global variables and perhaps everything else my multi-form
program may need to access.
But recently I was wondering if this is just plain poor programming
technique (would not doubt it with all the bad habits I've created for
myself).
Would breaking code into modules, where each module was named for its main
purpose (such as modTextTool for my TextTool routines), have any negative
effect on the code itself? Would this be consider code bloat, too many
modules? Or am I free to create as many of these specific function modules
to my heart's content, with all having just the code related to specific set
of actions?
Thanks.
Rick
.
- Follow-Ups:
- Re: Modules
- From: Jan Hyde
- Re: Modules
- From: Frank Adam
- Re: Modules
- From: Shell
- Re: Modules
- Prev by Date: Re: Write, Move, Delete text on PictureBox
- Next by Date: Re: Write, Move, Delete text on PictureBox
- Previous by thread: Visual Basic and MP3 Sound
- Next by thread: Re: Modules
- Index(es):