Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26477 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59388 invoked by uid 1010); 10 Nov 2006 18:06:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 59373 invoked from network); 10 Nov 2006 18:06:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2006 18:06:01 -0000 Authentication-Results: pb1.pair.com header.from=iliaal@gmail.com; sender-id=pass; domainkeys=good Authentication-Results: pb1.pair.com smtp.mail=iliaal@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.229 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: iliaal@gmail.com X-Host-Fingerprint: 64.233.184.229 wr-out-0506.google.com Linux 2.4/2.6 Received: from [64.233.184.229] ([64.233.184.229:62891] helo=wr-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/F3-27611-68FB4554 for ; Fri, 10 Nov 2006 13:05:59 -0500 Received: by wr-out-0506.google.com with SMTP id 58so362474wri for ; Fri, 10 Nov 2006 10:05:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=T+GcpgmevTO+RTkwy2Z7+rxyEkzk0MPn06m03z3Wj8NQq6Is4WNZFGhvuYwBvqEVar2vvT1rYyvuXVXcoaQ1ZXfs+Q45QIxhuomLyQYZl34Er2mqs3fOTByHrWLx8yOQrmSQvkSfQ0cFPBO2QGlQ5D0sOsi2DLVxLenmZA9zcLw= Received: by 10.65.219.15 with SMTP id w15mr3662909qbq.1163181952449; Fri, 10 Nov 2006 10:05:52 -0800 (PST) Received: from ?192.168.1.6? ( [74.108.69.82]) by mx.google.com with ESMTP id f16sm2476382qba.2006.11.10.10.05.51; Fri, 10 Nov 2006 10:05:51 -0800 (PST) In-Reply-To: <4554B9B5.5090305@caedmon.net> References: <4554AE0D.4080600@caedmon.net> <4554B9B5.5090305@caedmon.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: Cc: internals Content-Transfer-Encoding: 7bit Date: Fri, 10 Nov 2006 13:05:41 -0500 To: Sean Coates X-Mailer: Apple Mail (2.752.3) Sender: Ilia Alshanetsky Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take From: ilia@prohost.org (Ilia Alshanetsky) On 10-Nov-06, at 12:41 PM, Sean Coates wrote: > I don't think namespaces are a magic bullet. As it stands, it's > impossible to use namespaces without a third party patch that may > or may > not work. I strongly believe that if namespaces are implemented in PHP > 6, most of our prefixing/symbol collisions will go away as people > migrate. It's much easier to track down a failed import than to > comment > out a function declaration in the PHP source. 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 :-). If we take 5.x adoption as a benchmark it took it over 2 years to even reach the 10% mark and big PHP apps still (with good reason) focus on the much larger PHP 4 market. Namespacing core classes/function would be a supremely bad idea as it could quite literally break every single application. You also need to consider that until PHP X attains at least 50% or more market penetration few people would be willing to write applications that require this version of PHP to work. This is why many of the projects and companies I am familiar still write new code in PHP 4 rather then in PHP 5, despite that version having numerous perceived advantages. > I also don't deny that there will be a minor performance hit. There > are > a ton of other things in PHP that reduce performance.. the idea is to > find a balance of which ones are worth it (as we did with OOP and > Unicode), and I believe that namespaces are worth it. I also know that > I'm not alone in this. I think adoption rates speak for themselves, 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. Ilia Alshanetsky