2007/12/4, Gregory Beaver <[EMAIL PROTECTED]>: > > Martin Alterisio wrote: > > 2007/12/4, Gregory Beaver <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>: > > > > Martin Alterisio wrote: > > > 1) Why is performance relevant to whether namespaces are > > implemented one per > > > file or many per file? > > > > Because there is a performance difference between code in separate > > files > > and the same code in a single file. > > > > [snip] > > > > > > As I said to Roman: Sorry but that still doesn't answer my question. > > That answer the question of "why use bundling?". > Yes it does, perhaps you misunderstand the answer? Let me rephrase: > because it is faster to bundle in some circumstances, and in some > circumstances significantly faster than any other possible optimizations.
I just want to have an objective view of the problem. Right now I could care less about namespaces being one per file, many per file, called packages, namespaces, zendspaces or whatever. The only thing I care right now is that, as a fellow php developer, I want to be sure that the ones running the show have objective information to take a decision. The only thing I see lately in this debate is performance comparison of bundled and unbundled code. How's that relevant to decide whether namespaces should be one per file or many per file? Answering "bundling increases performance and performance is better" does not answer this question. If it was just about performance we could just go back to writing CGIs in C. As I see it now, the objection to how namespaces are implemented is biased towards the specific needs of a group of developers. Shouldn't you try first if you can adjust your requirements to the new features rather than adjust the language to your requirements? > Also, what you exposed shows that the bundling process that you're > > currently using needs to be updated to take in consideration the > > inclusion of namespaces in PHP. > see my reply to your other message. You're wrong, it's not possible to > reliably bundle files containing namespace/import statements as > currently implemented. > It's also not possible to reliably bundle files even if you could have multiple namespaces declarations as, correct me if I'm wrong, import statements affect the whole file, there is no way to "unimport", a name clash could still occur.
