Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40975
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.147 as permitted sender)
Message-ID: <014401c92df5$e70d8470$3ffc1f3e@foxbox>
To: <technique@dev-solutions.fr>,
	"James Dempster" <letssurf@gmail.com>
Cc: "PHP Development" <internals@lists.php.net>
References: <3CF765DF-27AF-44FD-9ECF-BEBFC8A0AFCA@pooteeweet.org> <2CA7AC96-AD48-4F5D-B945-2D961B4AB57C@googlemail.com> <462e563f0810140112x3babae20t647a10322e76df8e@mail.gmail.com> <1223973712.7708.10.camel@stephane-dell>
Date: Tue, 14 Oct 2008 13:10:50 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] namespaces and alpha3
From: steph@php.net ("Steph Fox")

>> > On 10 Oct 2008, at 06:03, Lukas Kahwe Smith wrote:
>> >
>> >  1) rip them out
>> >
>> > I'm +1 on this. We simply don't have consensus, and I don't see anyway 
>> > we
>> > can have consensus by the time 5.3 has to be frozen. Once namespaces 
>> > are in,
>> > we're gonna have to stick with whatever we choose, unless we totally 
>> > break
>> > BC.
>>
>> I'd agree with this, leave something with such a big impact to version 6. 
>> At
>> least it gives time to get it right.
>
> I don't agree to this, many of us are waiting for namespaces and have 
> starting to impact some code in prevision.
>
> Don't forget that an annoucement has been done on php.net and a final 
> release of 5.3 without namespaces could be interpreded as a regression.

I'm +1 on ripping out and leaving til 6.0. I don't think there is enough 
time between now and the 5.3.0 code freeze to make major changes to the 
language syntax. Making -> do double duty and adding E_STRICT messages to 
currently legal code really doesn't look like a good option to me, much less 
during a point release and even less during the final moments of a release 
cycle. Leaving as-is, we already know is problematic. There's no consensus 
to pull support for functions/constants, which would make it less 
problematic.

'An announcement has been done on php.net' simply isn't a good enough reason 
to screw up the language; we can write new announcements and even 
explanations. And we already have *most* of a working implementation in 6.0, 
so it's not like ripping it out of 5.3 means starting over from scratch.

- Steph