Re: ignored patches
| From: | Roman Borschel | Date: | Tue, 04 Dec 2007 17:13:35 +0000 |
| Subject: | Re: ignored patches | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-33654@lists.php.net to get a copy of this message | ||
On Dec 4, 2007, at 5:50 PM, Martin Alterisio wrote:
2007/12/4, Roman Borschel <r.borschel@gmx.net>:Sorry, then i don't understand the question.On Dec 4, 2007, at 5:09 PM, Martin Alterisio wrote:Sorry but that still doesn't answer my question. That answer the question of "why use bundling?".1) Why is performance relevant to whether namespaces are implemented one per file or many per file?Because including/requiring 80 files one by one seems to be significantly slower than including/requiring just a few files.
You were right. Namespaces are being introduced to improve code maintainability & readability.I didn't understand. Do you mean that I was wrong?2) I was under the impression namespaces were introduced to improve code maintainability. Was I wrong?Of course. Such bundling processes usually only take place during an automated build process. This is not something thats used for development.
Or that I was right about namespaces purpose, but that's only needed in development? Therefore, shouldn't the bundling process remove the need for namespaces (i.e. the bundling process removes namespaces)?No because the whole code will use namespaces and just removing the namespace declarations during bundling will break the code.