Why would you do that? I.e. suppose there's library having namespace
Zend::Controller::Action::Plugin - why would your name your class
Zend::Controller::Action::Plugin and not
Steph::Controller::Action::Plugin?
Why do you assume all third-party software is going to be ZF? Or that code
is going to be written around third-party software in the first place,
rather than some useful lib that doesn't even exist yet might be slotted
into an app 3 or 10 years from now?
As it is now, every call to class::method() not accompanied with use
should produce E_WARNING.
? That's certainly not how I read it.
That's what is says:
If the "use" statement is missing, an E_WARNING should also be thrown to
alert the user to the ambiguity
I assume that's only if there is ambiguity, but I'm not in a position to
test the patch right now so can't say authoritatively (@Greg: speak!)
but Stas - conceptually you aren't a million miles apart in the first place,
so if you're finding that in your tests maybe helping figure a way through
would be more productive. Greg complains that your version gives no
warnings, you complain that Greg's version gives too many... please, guys,
can you work together?
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
