Re: Re: PHP programming strategy; lots of little include files, or a few big ones?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 7, 2010 at 04:11, Daevid Vincent <daevid@xxxxxxxxxx> wrote:
> I think it's a case by case basis. Generally File I/O is expensive, but
> then again, as you say, having everything in a couple files is also
> sub-optimal for organizing and keeping things modular.

That is easily sorted out using automated build tools like Phing, Ant
or GNU Make.

Either way, I wouldn't worry about the extra I/O unless you've got *a
lot* of traffic.

-- 
Daniel Egeberg

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux