On Mon, 29 Sep 2008 19:30:00 +0300, "Vesselin Kenashkov" <[EMAIL PROTECTED]> wrote:
> My proposal is (if possible/reasonable/performance wise of course) to have > a > fatal error thrown when during the parse time the engine discovers > duplicates like the one described above. What is the point to name in the > same way a class and a static method and a namespace and a function in the > same way? In my (very humble) opinion this is the best solution, because > we > keep the :: operator that we are familiar with, the ambiguity is resolved > (just not allowing it) and (I guess) the php 5.3 will not be delayed much. There's nothing "familiar" about :: to 99.99% of PHP developers who haven't already been playing with the alphas. It has no magical significance in namespace mythos. If the reuse of a symbol is causing problems, change the symbol to one that doesn't cause problems. Finding a symbol that doesn't cause problems may not be a simple task, but please don't pretend that "" has any special significance to namespaces in concept. --Larry Garfield -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
