Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41503
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5A.30.00734.70AF6094@pb1.pair.com>
To: internals@lists.php.net
Date: Tue, 28 Oct 2008 11:39:48 +0000
Reply-To: nathan@kraya.co.uk
Organization: Kraya - Web Development in Edinburgh
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
References: <69907CB6763C4164A1AE82D659B80286@pc>
In-Reply-To: <69907CB6763C4164A1AE82D659B80286@pc>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Clarifying the resolution rules
From: nathan@kraya.co.uk (Nathan Rixham)

Stan Vassilev | FM wrote:
> Opinions about how disruptive a mandatory backslash for global symbols *in namespaces* would be, are welcome. Keep in mind that making the backslash optional will lead to code breakage (such as for above drop-in replacements, class autoloading etc.) and slower performance (runtime resolution of function calls).

personally not very disruptive, and after a few hours I think it would 
become second nature.

I'm sure there will be a few comments about this, but.. why not move all 
  internal functions and classes to a php namespace so that everything 
has to be in a namespace by default - ie no code that isn't in a namespace.

ie
php\file_get_contents(__FILE__);
instead of
\file_get_contents(__FILE__);

major major change but nice and strict