Re: namespaces sanity: addition to RFC explaining why Stas'sproposal doesn't work

From:	Stanislav Malyshev	Date:	Thu, 16 Oct 2008 20:50:44 +0000
Subject:	Re: namespaces sanity: addition to RFC explaining why Stas'sproposal doesn't work
References:	1 2 3 4 5 6 7	Groups:	php.internals
Request:	Send a blank email to internals+get-41167@lists.php.net to get a copy of this message

Hi!

<?php Classname::Method(); ?> The proposal does not solve the name conflict. If no one rewrites their
Right, it does not. So doesn't yours - you need to modify the code in both cases.
the solution I proposed emits an E_WARNING on the conflict.

You proposed a number of solutions, apparently. That's why I asked to restrict the number of variants - even people who watch the discussion can't be sure what we are talking about now. Do you propose to _always_ throw E_WARNING even if there was no actual conflict? Then I am against it - in 99.9% of the code this warning would be useless and would only annoy people. If you propose to throw warning only if actual conflict exists - the question stays how do you know it exists. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com