Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44788 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34003 invoked from network); 7 Jul 2009 19:01:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jul 2009 19:01:37 -0000 X-Host-Fingerprint: 64.8.134.189 unknown Received: from [64.8.134.189] ([64.8.134.189:23473] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E7/50-32505-09B935A4 for ; Tue, 07 Jul 2009 15:01:36 -0400 To: internals@lists.php.net,Ilia Alshanetsky Message-ID: <4A539B8D.409@gmail.com> Date: Tue, 07 Jul 2009 14:01:33 -0500 User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 References: <2D0F5226-EBCA-4B45-BF01-8ED1C643976C@prohost.org> In-Reply-To: <2D0F5226-EBCA-4B45-BF01-8ED1C643976C@prohost.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 64.8.134.189 Subject: Re: Type hinting/casting request for vote From: rpanning@gmail.com (Ryan Panning) Ilia Alshanetsky wrote: > Last week or so there was a fairly detailed discussion on the internals > list regarding type hinting based on my original patch. Since then the > patch has been revised to address the major concerns that were > identified (breakage of binary compatibility) as well extended with > additional functionality (object hint, type casting, reflection support, > etc...). > > The final patch is available here: http://ilia.ws/patch/type_hint_53_v2.txt > The test suit is available here: http://ia.gd/patch/type_hint_tests.tar.bz2 > > I would like to ask all developers to voice their opinions of whether it > makes sense to add this to 5.3 or to throw it away (either one is fine > btw). To keep the process simple & flamewar free, please restrict > yourself to +/- (1/0), next week monday I'll run a tally of the votes > and based on the result we can determine how to proceed further. > > Ilia +1 As for when, I'd say it should wait for the next "major" release, 5.4 or 6.0. But then again, I don't want to wait several years for a feature being discussed now, so I'll go with 5.3.x.