Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33879
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net, greg@chiaraquartet.net
Message-ID: <475B4F1D.5060601@gmail.com>
Date: Sat, 08 Dec 2007 21:12:45 -0500
User-Agent: Thunderbird 1.5.0.12 (X11/20070530)
MIME-Version: 1.0
References: <93ED589E60BA254F97435FE6C97F2C6702B9222A@leedsmet-exch1.leedsmet.ac.uk>
In-Reply-To: <93ED589E60BA254F97435FE6C97F2C6702B9222A@leedsmet-exch1.leedsmet.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: AW: [PHP-DEV] A rebuttal to Re: RFC: Dropping Namespace
From: jrhernandez05@gmail.com (Jessie Hernandez)

Hi Greg,

How about this: any non-namespaced file that uses "use" statements is 
implicitly put into the __php__ namespace (or whatever other name is 
chosen, or having the namespace name be the path of the file)? With 
this, "use" will never import any symbols into the global namespace.


Regards,

Jessie


Ford, Mike wrote:
> On 07 December 2007 17:36, Gregory Beaver wrote:
> 
>> The suggestion to make "namespace __php__;" implicit is very
>> interesting, but would defeat its purpose, which is to separate
>> declarations from use. 
> 
> Oh, I missed that little wrinkle -- I did say I was only skimming! I guess it could still be done, but at somewhat greater cost in the engine than I was imagining, which probably isn't worthwhile.
> 
> 
> Cheers!
> 
> Mike
> 
> ---------------------------------------------------------------------
> Mike Ford,  Electronic Information Services Adviser,
> JG125, The Headingley Library,
> James Graham Building, Leeds Metropolitan University,
> Headingley Campus, LEEDS,  LS6 3QS,  United Kingdom
> Email: m.ford@leedsmet.ac.uk
> Tel: +44 113 812 4730          Fax:  +44 113 812 3211 
> 
> 
> 
> 
> To view the terms under which this email is distributed, please go to http://disclaimer.leedsmet.ac.uk/email.htm