Hi!
In other words, with the current implementation, you can just do "use Foo::Exception;" and it works, but if you *forget* to do the use statement, you can get unpredictable behavior with no warning until your
You get previctable behavior in all cases, there's no randomness in the engine.
to "use ::Exception", then your code is simply slightly slower (1 extra call to autoload if it exists), but still works properly. It also tilts
It's not slightly slower, it's *A LOT* slower - exhaustive search of whole include path for *EACH* call mentioning internal class. That means you have to declare *EACH* internal class - even if no clashes ever existed - for *EACH* use. Basically, it's the same as always using ::Class only implemented in a way that its disastrous effects are hidden until you check performance of your code. Then you have to go back and add use statement for each internal class in each of your files. Lot's of fun that would be.
-- 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
