Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26480 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68381 invoked by uid 1010); 10 Nov 2006 18:20:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 68366 invoked from network); 10 Nov 2006 18:20:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2006 18:20:00 -0000 Authentication-Results: pb1.pair.com header.from=sean@caedmon.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sean@caedmon.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain caedmon.net from 69.60.120.90 cause and error) X-PHP-List-Original-Sender: sean@caedmon.net X-Host-Fingerprint: 69.60.120.90 iconoclast.caedmon.net Linux 2.4/2.6 Received: from [69.60.120.90] ([69.60.120.90:44873] helo=iconoclast.caedmon.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/25-27611-EC2C4554 for ; Fri, 10 Nov 2006 13:20:00 -0500 Received: from localhost ([127.0.0.1]) by iconoclast.caedmon.net with esmtp (Exim 3.35 #1 (Debian)) id 1Giaxm-00070F-00; Fri, 10 Nov 2006 13:18:51 -0500 Message-ID: <4554C2C7.9070502@caedmon.net> Date: Fri, 10 Nov 2006 13:19:51 -0500 User-Agent: Thunderbird 1.5.0.7 (X11/20060918) MIME-Version: 1.0 To: Ilia Alshanetsky CC: internals References: <4554AE0D.4080600@caedmon.net> <4554B9B5.5090305@caedmon.net> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take From: sean@caedmon.net (Sean Coates) > PHP 6 is not yet out and probably won't be production quality for quite > some time. Which means that migration to it en mass is probably not > going to happen this decade :-). I'm not talking about forcing everyone to use namespaces tomorrow. I'm trying to plan for a future where there's a sensible way to avoid symbol collision. As for everyone developing on PHP $release-1 until 50% market saturation, I believe that to be the case in widely-distributed PHP apps (such as FUDForum), but you seem to be forgetting about the large number of PHP applications that are developed for internal use. I don't know of anyone currently using PHP 4 to develop new PHP apps unless they're for external distribution. > I think there is far more > demand for a fast & stable PHP then for syntatic sugar features which > seem extremely useful, but in the end prove to carry too much baggage. Nothing has been proven either way.. at least not publicly.. unless I just missed it. S