John,
part of this is a matter of taste - I would personally rather split this
into functions.
BUT: even if you _are_ using functions, you should only include() the
file with the function when you need it, IF this part of the code is
getting large. This way, php will not need to parse code that it won't
need anyway.
Ben
John McCreesh wrote:
>
> What is the best practice for structuring a PHP program which is
> becoming too large to manage as a single file? Should it be broken into
> a number of includes, e.g.:
>
> switch ($whatever) {
> case 0:
> include('case0.php');
> break;
> case 1:
> include('case1.php');
> break;
> case 2:
> include('case2.php');
> break;
> }
>
> or a number of functions:
>
> require('mylib');
> switch ($whatever) {
> case 0:
> case0();
> break;
> case 1:
> case1();
> break;
> case 2:
> case3();
> break;
> }
>
> Any thoughts, references to articles (couldn't find anything in
> PHPBuilder), etc gratefully received...
>
> Thanks - John
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
