Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26484 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82042 invoked by uid 1010); 10 Nov 2006 18:47:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 82027 invoked from network); 10 Nov 2006 18:47:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2006 18:47:37 -0000 Authentication-Results: pb1.pair.com header.from=hans@velum.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=hans@velum.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain velum.net from 216.86.168.178 cause and error) X-PHP-List-Original-Sender: hans@velum.net X-Host-Fingerprint: 216.86.168.178 mxout-03.mxes.net FreeBSD 4.6-4.9 Received: from [216.86.168.178] ([216.86.168.178:4891] helo=mxout-03.mxes.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A6/86-27611-849C4554 for ; Fri, 10 Nov 2006 13:47:37 -0500 Received: from [192.168.0.54] (unknown [66.7.145.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id DBCA75193B for ; Fri, 10 Nov 2006 13:47:33 -0500 (EST) Message-ID: <4554C945.3000509@velum.net> Date: Fri, 10 Nov 2006 13:47:33 -0500 User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: internals References: <4554AE0D.4080600@caedmon.net> <4554B9B5.5090305@caedmon.net> <4554C2C7.9070502@caedmon.net> In-Reply-To: <4554C2C7.9070502@caedmon.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take From: hans@velum.net (Hans Lellelid) >> 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. > I haven't talked to a single developer a large-scale PHP tool, application, etc. that wouldn't switch their trunk to using namespaces tomorrow if they were adopted in the engine. We [in] PHP developers who are building "enterprise" open-source components and frameworks really will use this feature -- and I think we'd all argue that we really need this feature. I hope that namespaces would be more than syntactic sugar -- e.g. providing an import/using keyword that would declare namespace context -- but even if they were only "syntactic sugar" they would at minimum provide a naming standard for PHP packages to avoid collisions. Namespaces certainly got a lot of mention at Int'l PHP Conference (in form of request and, during the panel, applause from audience when mentioned); it was clear that this is a very anticipated PHP6 feature. None of us non-C developers are trying to say we think this should be easy, or trying to otherwise minimize the problems that have been presented in the past or the reasons why it hasn't been implemented so far, but let there be no confusion that this is a really, really important feature for us. Thanks, Hans