Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.221.203 cause and error)
Cc: Jeff Griffiths <jeffg@activestate.com>,
 PHP internals <internals@lists.php.net>
Message-ID: <46789C0F-A9A4-4B7C-92DF-A1F65471D069@prohost.org>
To: Andrei Zmievski <andrei@gravitonic.com>
In-Reply-To: <4A53B578.6040204@gravitonic.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 7 Jul 2009 20:21:42 -0400
References: <2D0F5226-EBCA-4B45-BF01-8ED1C643976C@prohost.org> <4A53825F.1080006@gravitonic.com> <4A53832E.6030105@gravitonic.com> <4A538775.3060305@activestate.com> <B2E7D611-05B2-440B-AEE2-D4941D2CB608@prohost.org> <4A53B578.6040204@gravitonic.com>
Subject: Re: [PHP-DEV] Type hinting/casting request for vote
From: ilia@prohost.org (Ilia Alshanetsky)

Andrei,

PHP represents a major change on every aspect of the language, I think  
you gotta appreciate it that even if it were to be released today  
there would be sometime before it can certified as production ready in  
terms of stability and performance. I'd go on a limb and say that PHP6  
is probably 3-4 years away from being production material and that's  
assuming it gets released in the next 8-12 months. During that time  
people still need to develop applications, which are getting  
increasingly complex and any helpful tool/feature would be an asset.


On 7-Jul-09, at 4:52 PM, Andrei Zmievski wrote:

> Ilia Alshanetsky wrote:
>> PHP 6 is too far off in a practical sense (sorry Andrei) from the  
>> time where I can see myself using it in production or other people  
>> benefiting from this function. The (simpler) variant of provided  
>> patch is what is currently being used on production, if it can go  
>> into 5.3, which I see myself using soon, then there is a tangible  
>> benefit from making this a public feature (reduce the amount of  
>> custom patching) and spending the time to refine it for public  
>> consumption and making it PHP 6 ready. If it can only be added in  
>> PHP6, then the amount of interest I personally have towards further  
>> evolution of this feature is very minimal.
>> So for me personally, the practically of the feature's deployment  
>> is critical.
>
> Ilia, I understand what you're saying, but with this kind of  
> attitude PHP 6 might never arrive if we all keep putting only the  
> things that are practical for our (personal) usage into 5.3, 5.4,  
> etc. The best way to shorten the time horizon of 6 is to treat it as  
> the primary target of the development effort.
>
> -Andrei