This is Definatley a good conversation... I've realy thought of doing
it this way... but i do agree with the person who said that 'having to
keep track of a ton of different files could get complicated" ... i
can't imagine the performance difference would be that big... but then
again, i suppose it is relative to how big your applicatin is going to
be
Cheers!
Joe
---------- Forwarded message ----------
From: Jay Blanchard <jay.blanchard@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 6 Jan 2005 14:30:23 -0600
Subject: On large application organization [long and possibly boring]
To: PHP Mailing Lists <php-general@xxxxxxxxxxxxx>
Good afternoon gurus and gurettes,
If I have a large app what is the difference, other than having a very
large file, of doing this
switch($action){
/* several dozen cases to follow */
case "foo":
writing out all of the code
break;
}
and this
switch($action){
/* several dozen cases to follow */
case "foo":
include that will handle processing this case
break;
}
Correct me if I am wrong, but includes (and/or requires) will get all of
the code in all of the cases regardless if the case is being processed.
That being the case the code would essentially be the same length. Given
that, would there be an efficieny issue?
This would (the second way) also make the project easier to work on by
multiple programmers at the same time, similar to modular work being
done by programmers on C++ projects.
One of the reasons for doing this is so that global includes and certain
class definitions, such as an error checking function relavent to most
cases, can be included once.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
