Remember, we both found, independently, that combining separate files
yields from a 10-30% performance increase. I have only talked to 2
On synthetic benchmarks. On real apps, which do databases, calculations,
network, etc. that would be probably no more than 5%, probably even
less. And I don't see any application shipping in this format.
This is a very problematic issue - adding a feature into a language that
serves only very specific very narrow performance scenario but which
will inevitably be widely abused in cases which have nothing to do with
that scenario.
the feature unnecessary. If you'd like, I could put you in contact with
developers who have been struggling with combining files for several
years now.
Why were they "struggling" - only problem existing with it is
namespaces, and they certainly couldn't try to use namespaces for years?
If they had other problems, they will keep having them and multiple
namespaces per file are not going to help them.
Anecdotally, I heard of a recent file-combining optimization to a very
popular CMS that resulted in a 45% performance improvement. Improving
Did they use bytecode caching?
Anyway, I have hard time believing PHP include is so broken, but if it
is - it should be fixed, not through creating syntax-level workarounds
but directly.
> really the only reason not to implement the multiple namespaces per-file
I think I described my reasons now multiple times.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
