RE: [PHP] Structuring large PHP programs

[Maxim Maletsky]

A large application should be a set of well organized files having one
single include at the top.

And in that include you do all kind of things.
Of course auto_prepend works always better /... but not always possible,
right...

use classes, reuse files ... libraries etc ...

Cheers,
Maxim Maletsky




-----Original Message-----
From: John McCreesh [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 15, 2001 5:25 AM
To: [EMAIL PROTECTED]
Subject: [PHP] Structuring large PHP programs


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]