Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41506
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.171 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=vJaG6ddIEC/Gm3JMDF6YtSNQqdJwZXItAv1iEV9b5zwstbw5rpl+9teqGyuDXhLrCI
         Bgr5HYlTaIXcFqga75TCVkwEqrSzUYxd0ma/fJ0b9ashQeNqJ6/j4POvYXYGQAAiAK87
         ef3kft+6Cf5pb09dMMA590AJ7LG9XoQKrozMM=
Message-ID: <6fef9b880810280535j43bcbdbvef2531f471578697@mail.gmail.com>
Date: Tue, 28 Oct 2008 23:05:07 +1030
To: nathan@kraya.co.uk
Cc: internals@lists.php.net
In-Reply-To: <5A.30.00734.70AF6094@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <69907CB6763C4164A1AE82D659B80286@pc>
	 <5A.30.00734.70AF6094@pb1.pair.com>
Subject: Re: [PHP-DEV] Re: Clarifying the resolution rules
From: josh.sickmate@gmail.com (Josh)

We are going to ignore the inherit problems that calling
file_get_contents(__FILE__); would cause...

Also, I disagree with a PHP namespace. the looseness of the language
is one of its strong points. Some things should be made strict, I
agree, bit it start with a php namespace and where does it end? If
your not careful you end up with c# or java where doing anything
requires going through hundreds of classes and packages.

Josh


On Tue, Oct 28, 2008 at 10:09 PM, Nathan Rixham <nathan@kraya.co.uk> wrote:
> 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>