Hi all,
I have a program that calls via require statements several other files in order to avoid repeated code. This code is on a production web environment that may have hundreds of users accessing the same code at the same time. The external files of code (which I will call library files) have numerous sub statements (functions) inside of them. Now, in order to maintain this codebase better one idea was to break up every single function into its own file, so that when modifying such function, only one file was deployed, thus, reducing QA time. So, basically I want to know if I can expect a performance hit if I open up several files, since they will all be called within the program. Here is a sample to illustrate my point
Program_1: require "Program_2.pl"
OR
Program_1: require "Program_2.pl"
require "Program_3.pl"
require "Program_4.pl"
require "Program_5.pl"
require "Program_6.pl"
In the first example, I have Program_2 which has all 5 functions contained in files Program_2 to 6. On the second, each function has its own file. The advantages to scheme 2 are the ones outlined above, but since my program will always require everything, is it faster to have everything on one file VS multiple files? I hope I make sense and I will appreciate any input.
Regards,
Javier Moreno
==============
Softtek/GXS
EFS NearShore - TradeWeb 2nd Tier
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
- Sherlock Holmes
