Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.179 as permitted sender)
Message-ID: <00a901c92f36$fa464b20$3ffc1f3e@foxbox>
To: "Greg Beaver" <greg@chiaraquartet.net>,
	"PHP Developers Mailing List" <internals@lists.php.net>
References: <48F653FF.5010106@chiaraquartet.net>
Date: Thu, 16 Oct 2008 03:29:11 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] my last attempt at sanity with namespaces
From: steph@php.net ("Steph Fox")

Hi,

> 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?

It sure would :)

"Conflict between namespaced functions and static class methods"

#3 is sheer brilliance IMHO. No BC issues for Karsten and friends, nice
clear warnings on conflict and an easy way to fix them (I saw the draft
patch), no performance hit any place that should matter, and above all -
nobody else even thought of approaching the problem from that end in all
this time, so kudos to you!
Since I've been championing #2 for the last several weeks I obviously
wouldn't object to that solution either, but I think #3 has far more
elegance.

"Resolving access to internal classes"

I'll abstain on this one because I don't feel qualified to weigh the issues
(ie I neither use nor write third-party dev tools).

Thanks Greg!

- Steph