Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41117
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <51.23.20632.4C707F84@pb1.pair.com>
To: internals@lists.php.net
Date: Thu, 16 Oct 2008 11:22:09 +0200
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
References: <48F653FF.5010106@chiaraquartet.net>
In-Reply-To: <48F653FF.5010106@chiaraquartet.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: my last attempt at sanity with namespaces
From: karsten@typo3.org (Karsten Dambekalns)

Hi Greg, everyone.

Greg Beaver wrote:
> http://wiki.php.net/rfc/namespaceissues
> 
> Read it and discuss.  Let's be clear people: the technical problems in
> namespaces are limited and solvable.  The problems in the political
> environment surrounding them may not be.  Wouldn't politics be a
> stupid-ass reason to remove namespaces?

Oh, yeah, absolutely!


"Conflict between namespaced functions and static class methods"

I would prefer #1, but am equally happy with #3.

Note: Rewriting what we currently have to make it work with changes in 
namespaces would be something we happily attack as soon as we know the 
direction.


"Resolving access to internal classes"

Great.

And the autoload-for-internal classes issue would be no issue if (like 
we currently do) one explicitly refers to them like "::Exception" anyway.


Regards,
Karsten

PS: We are still in Berlin at a TYPO3 core developer meeting, and I am 
happy to see this issue (almost) resolved. The same is true for the 
others here. Long live PHP!