Re: Re: PHP programming strategy; lots of little include files, or a few big ones?
| From: | Daniel Egeberg | Date: | Thu, 07 Jan 2010 11:33:08 +0000 |
| Subject: | Re: Re: PHP programming strategy; lots of little include files, or a few big ones? | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-300879@lists.php.net to get a copy of this message | ||
On Thu, Jan 7, 2010 at 04:11, Daevid Vincent <daevid@daevid.com> 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