Re: Is opening a new source file really costly? Was: [PEPr] Comment on RFC::Package naming, file naming and directory structure RFC
| From: | Sergio Carvalho | Date: | Tue, 20 Apr 2004 11:15:42 +0000 |
| Subject: | Re: Is opening a new source file really costly? Was: [PEPr] Comment on RFC::Package naming, file naming and directory structure RFC | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28126@lists.php.net to get a copy of this message | ||
Sorry if I'm being obnoxious. I'll insist a bit more, since I still don't get it. On the bug you presented, the culprit was the loading of Date.php. Looking at the file, we see it is 36KB long. I'd expect parse and compile time to be significant on that one (0.3s on the bug case).
However, my question is: Would dividing Date.php in two files (if possible, naturally), increase the loading time? Parse and compile must be done anyway, and it seems unnatural to me that it takes that much more time processing the same code, just because it is divided between files.
I'd expect parse and compile time to grow linearly with the code size, not file count, as was proposed by Daniel Convissor:
http://aspn.activestate.com/ASPN/Mail/Message/pear-dev/2055682
Am I wrong?
Cheers,
Sérgio Carvalho
Alan Knowles wrote:
This illustrates the issue and the solution quite well.. http://pear.php.net/bugs/bug.php?id=1127 Regards Alan