Ilia Alshanetsky wrote:
If you properly pick a
classname you almost never need to rename it let alone the methods
contained with the class. Plus namespaces are going to introduce their
own sets of problems where extension X adds namespace X, which some lib
already decided to use and we are back to where we are at today.
In third party packages that choice isn't up to me.
And as for your extensions using the same namespace...I see that
argument as a bit better reasoning but would it not be easier to fix the
namespace declarations than having to fix ALL the uses of some class?
As a casual observer of this list and proponent of PHP I'd like to see
the namespace issue either get done or die. Many watching the namespace
issue with interest are growing tired of excuses as to why it shouldn't
be done.
Do it. Don't do it. Just choose and be on with it. PHP developers
will deal with the outcome fine. That isn't criticism directed at
anyone but dragging this out is only stirring emotions. I think putting
this behind us all - one way or another - is good for everybody.
--Tony
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
