Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26520
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain bitxtender.com from 80.237.132.12 cause and error)
In-Reply-To: <4554C945.3000509@velum.net>
References: <4554AE0D.4080600@caedmon.net> <D268FFAD-6916-4EDE-9511-31F5BC774318@prohost.org> <4554B9B5.5090305@caedmon.net> <DA611470-FC2C-48DE-AE6B-29EC4554A298@prohost.org> <4554C2C7.9070502@caedmon.net> <4554C945.3000509@velum.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <9A0C1085-5569-4883-ADAC-B0DF9965EA1C@bitxtender.com>
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Sat, 11 Nov 2006 17:14:46 +0100
To: Hans Lellelid <hans@velum.net>
Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take
From: dz@bitxtender.com (=?ISO-8859-1?Q?David_Z=FClke?=)

Am 10.11.2006 um 19:47 schrieb 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.


Very wall said, Hans, and I totally agree. It's much needed, and I  
believe any FOSS project that is OO based would applaud the  
introduction of namespaces.


David