Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37971
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <FC54BE3A288243D381487D1E9F675360@pc>
To: <internals@lists.php.net>
References: <462e563f0805280927w46cb0a3fra8b546e8219dd9ab@mail.gmail.com>
Date: Wed, 28 May 2008 19:50:14 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Name resolution rules
From: sv_forums@fmethod.com ("Stan Vassilev | FM")


Hi,

You examples are showing some quite horrible situations with namespaces. 
Agreed, the least thing, an error should be thrown on collision.

Regards,
Stan Vassilev


>I find the namespace resolution rules quite confusing. It's become quite
> difficult to tell if I'm calling a static method or a function, or
> namespaced static method or namespaced function, and so on. I don't quite
> fully understand or appreciated the point of namespaces. If some one could
> help me out here.
>
> -- google.php --
> <?php
> namespace Google;
>
> function search() {
>  return 'namespace google search';
> }
>
> -- test.php --
> <?php
> require('google.php');
>
> class Google {
>  public static function search() {
>    return 'class google search';
>  }
>
>  public static function test() {
>    return 'class google test';
>  }
> }
>
> function search() {
>  return 'global function search';
> }
>
> use Google as Other;
>
> echo '1 '.__FILE__.' #'.__LINE__.' '.search().'<br/>';
> echo '2 '.__FILE__.' #'.__LINE__.' '.Google::search().'<br/>';
> echo '3 '.__FILE__.' #'.__LINE__.' '.Google::test().'<br/>';
> echo '4 '.__FILE__.' #'.__LINE__.' '.Other::test().'<br/>';
>
> 1. behaved as I expected it to.
> 2. didn't do what I thought it should have done, now the class is broken,
> but wouldn't though any exception.
> 3. behaved as I expected it to.
> 4. wow strange I've managed to rename my class though namespace resolution
> rules.
>
> I feel that namespaces are going to cause some big problems. Shouldn't it
> wait for PHP6 rather than backport to PHP5.
> This is only one of the problems I've come across with namespaces.
>
> Is it going to be possible to get to the google class search method? I 
> find
> it terrible that now a name *DOES* clash, but this time with out so much 
> as
> an error! I preferred it to highlight the fact that I had a class with the
> same name.
>
> Any thoughts?
>
> /James
>