Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38639
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <78783688F8684F4DAD79123AE457B330@pc>
To: "internals Mailing List" <internals@lists.php.net>
References: <10845a340806260209g5d22c986tbd14b4234d079590@mail.gmail.com> <4863B271.2080300@php.net>
Date: Thu, 26 Jun 2008 18:57:25 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] How bad would it be to say/enforce that namespacing can only apply to classes and not normal functions?
From: sv_forums@fmethod.com ("Stan Vassilev | FM")

>> How bad would it be to say that namespacing can only apply to classes and
>> not normal functions?
>
> Lame, very lame.  It would make them unusable for many distributed 
> projects that are not 100% OOP.  Wordpress comes to mind.  My own Phorum 
> as well.
>

I agree, namespaces need to work for all definition types.
I don't see a problem here:

1) ns1::ns2::class::static()  and  ns1::ns2::namespace::func()  is a 
collision
2) why is it a collision? because we have a class and subnamespace in the 
same namespace, with the same names.
3) solution therefore is to NOT allow this collision, and end with an error.

[Example 1]

namespace a::b::c;
function foo() {}

namespace a::b;
class c {}  // FATAL ERROR: class collision with existing namespace 
"a::b::c"

[Example 2]

namespace a::b;
class c {}

namespace a::b::c; // FATAL ERROR: namespace collision with existing class 
"a::b::c"
function foo() {}

So now, while the syntax may still be ambiguos if a codeline is cut and 
pasted alone in a blank text file, at least *in context* it can do only one 
thing: call whatever the user defined/imported/included. If there's a 
collision, he'll see the error, and take action.