Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34198
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain iamjochem.com from 194.109.193.121 cause and error)
Message-ID: <476B909F.9070903@iamjochem.com>
Date: Fri, 21 Dec 2007 11:08:31 +0100
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Greg Beaver <cellog@php.net>
CC: Martin Alterisio <malterisio777@gmail.com>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <52dbac0f0712201536s7fab82a7y2a7111ca5a11711e@mail.gmail.com> <476B3C57.6070102@php.net>
In-Reply-To: <476B3C57.6070102@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Maybe a problem? undetected name clash makes static
 method unaccessible through outside static reference
From: jochem@iamjochem.com (Jochem Maas)

Greg Beaver schreef:
> Martin Alterisio wrote:
>> Consider the following code:
>>
>> foo.php:
>> <?php
>> class test {
>>   public static function foo() { echo "I'm foo in class test\n"; }
>>   public static function foo2() { self::foo(); }
>> }
>> ?>
>>
>> foo2.php:
>> <?php
>> namespace test;
>> function foo() { echo "I'm foo in namespace test\n"; }
>> ?>
>>
>> test.php:
>> <?php
>> include 'foo.php';
>> include 'foo2.php';
>> test::foo(); // I'm foo in namespace test
>> use test::foo as dummy;
>> test::foo(); // I'm foo in namespace test
>> test::foo2(); // I'm foo in class test
>> $test = 'test';
>> $test::foo(); // I'm foo in class test
>> call_user_func(array('test', 'foo')); // I'm foo in class test
>> ?>
>>
>> Please review the following observations:
>>
>> There's a name clash that goes undetected: test::foo refers to both a
>> namespaced function and a static method.
>>
>> Once the clash occur there's no way to refer to the static method through a
>> static reference, except when within the class scope where you can refer to
>> the method through self::
>> The static method remains partially hidden by the namespaced function.
> 
> Don't forget about ::test::foo() which refers to class test, method
> foo().  However, this is an issue, and one of the main reasons I dislike
> putting functions and constants in namespaces, as this ends up sort of
> like OO without inheritance and confuses the issue of static methods as
> you pointed out.
> 
> However, having said that, in my experience, developers either use
> functions or OO, very rarely mixing the two on an extensive basis, and
> so name collisions become much less likely between static methods and
> namespaced functions.

why exactly should we need to have this ambiguity and possible naming collision?
I thought namespaces are about avoiding naming collisions?


> 
> Greg
>