Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <29.7A.15458.C4880194@pb1.pair.com>
To: internals@lists.php.net
Date: Tue, 04 Nov 2008 11:37:12 -0600
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Namespace Resolution
From: rpanning@gmail.com (Ryan Panning)

First, I want to say thanks for determining the best separator. Even 
though it's not what everyone would like, it's what would work best.

Second, sorry for starting a new thread. To me, continuing the 
resolution discussion in the "namespace separator and whining" isn't the 
correct place.

Third, moderating this list may help the developers keep the noise down 
but user-land people, like myself, need to have some input too. Not sure 
if this was proposed yet but what about a "trial period" where if a 
person shows that they don't "over-post" they get un-moderated.

Finally, down to business. What I would like to see is that any call not 
prefixed with a direct namespace or not "used" at the top, be considered 
a global request. This forces users to either define what they are going 
to "use" or directly define what namespace is requested. Ex:

<?php
namespace NsA\NsB;

class ClassB {
     public function methodB() {
         namespace\func_b();
     }
}

function func_b() {
     print 'I am in NsB';
}
?>

<?php
namespace NsA\NsB\NsC;

function func_c() {
     print 'I am in NsC';
}
?>

<?php
include 'NsB.php';
include 'NsC.php';

use 'NsA\NsB\NsC\func_c()';

$obj = new NsA\NsB\ClassB;
$obj->methodB();
func_c();
?>