Grouping Included Functions-How much is too much? [RESOLVED]
Posted: Wed Sep 20, 2006 8:12 am
I was just wondering if anyone has any guidelines or rules-of-thumb on how many included functions is too many?
I have about 10 or 12 functions that I use across say 30 pages. Is it better to group them all in one include file, break them up into say 3 or 4 different include files (if possible), or nest them (grouping them by what they do -- i.e., file manip functions, DB functions, etc.) I know this doesn't seem like a lot of includes, but I expect the number to grow substantially and I would like to settle on a general approach before it grows much more.
It would seem that nesting them would be the most orderly way, but would that affect the speed or performance of the scripts?
In other words, is the script slowed down by the functions it does not use or by too many file inclusions?
Thanks,
(P.S., Although this isn't a code question, I wasn't sure it should go in Theory and Design either since the question is not "advanced").
I have about 10 or 12 functions that I use across say 30 pages. Is it better to group them all in one include file, break them up into say 3 or 4 different include files (if possible), or nest them (grouping them by what they do -- i.e., file manip functions, DB functions, etc.) I know this doesn't seem like a lot of includes, but I expect the number to grow substantially and I would like to settle on a general approach before it grows much more.
It would seem that nesting them would be the most orderly way, but would that affect the speed or performance of the scripts?
In other words, is the script slowed down by the functions it does not use or by too many file inclusions?
Thanks,
(P.S., Although this isn't a code question, I wasn't sure it should go in Theory and Design either since the question is not "advanced").