namespace Foo;
import Exception;
Once more, import with one-term argument is a no-op. And will stay so. That's why we have the warning.
I think that either import ::Exception needs to work, or import Exception shouldn't issue a warning.
We'll discuss this one. I wonder if anybody else feels a need for it?
I think you need to envision working in a large team on a large project here, but you may simply not see the need.
I'd say if you have large team which has a possibility of having classes with same names running into each other, why not having them reside in different namespaces?
--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com