Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41013
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.145 as permitted sender)
Message-ID: <003401c92e30$d33c6bb0$3ffc1f3e@foxbox>
To: "Stanislav Malyshev" <stas@zend.com>
Cc: <internals@lists.php.net>
References: <652122.8719.qm@web708.biz.mail.mud.yahoo.com> <48F4D832.7010708@zend.com> <033701c92e24$d9ca3d60$3ffc1f3e@foxbox> <48F4DF7E.1070202@zend.com> <038301c92e29$aa8f3aa0$3ffc1f3e@foxbox> <48F4E5B3.2030000@zend.com> <002201c92e2f$3c37f2d0$3ffc1f3e@foxbox> <48F4ECE3.1090202@zend.com>
Date: Tue, 14 Oct 2008 20:12:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] namespaces and alpha3
From: steph@php.net ("Steph Fox")

>> What would happen if we give the namespace implementation a chance to 
>> mature is that it can be delivered as a fully-fledged language element 
>> rather than a partially-fledged and potentially flawed one.
>
> What do you mean by "chance to mature"? Only chance for it to mature is 
> people actually starting using it and not another week of discussing 
> separators on internals.

OK, bad choice of terminology. I really mean "a chance for the likelier 
problems to be ironed out".

> And people can't start using it if it's not only not released but there 
> are developers rooting for it to be removed.

Suddenly nobody uses CVS? I think if we were to ask explicitly for namespace 
testers on php.net once there's a full implementation we're all reasonably 
happy with, we'd find them.

- Steph