Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44882 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9424 invoked from network); 9 Jul 2009 19:22:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jul 2009 19:22:09 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.117 us-mr1.zend.com Linux 2.4/2.6 Received: from [63.205.162.117] ([63.205.162.117:35301] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/01-30297-063465A4 for ; Thu, 09 Jul 2009 15:22:09 -0400 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id 686DAE12C7; Thu, 9 Jul 2009 12:10:48 -0700 (PDT) Received: from [192.168.16.83] ([192.168.16.83]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 9 Jul 2009 12:22:47 -0700 Message-ID: <4A56435D.3030006@zend.com> Date: Thu, 09 Jul 2009 12:22:05 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Greg Beaver CC: PHP Developers Mailing List References: <4A5606C8.2040800@chiaraquartet.net> <4A5641D2.1070308@zend.com> <4A56427F.5080108@chiaraquartet.net> In-Reply-To: <4A56427F.5080108@chiaraquartet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jul 2009 19:22:47.0622 (UTC) FILETIME=[A4784660:01CA00CA] Subject: Re: [PHP-DEV] technical issues in type hinting patch are not as big of an issue as it appears From: stas@zend.com (Stanislav Malyshev) Hi! > You assume that cast type hinting will be the implementation chosen. If > the type hinting is in fact validation the way object type hinting is > (strict type hinting), no conversion takes place, and the meaning is > different. I should have said "if strict type hinting is implemented" > in the drawback description to make that clear. If there's only strict typing, there's no reason to make it's syntax to be resembling typecasts. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com