Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57023 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51145 invoked from network); 22 Dec 2011 19:31:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Dec 2011 19:31:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:35869] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 64/CE-12618-67583FE4 for ; Thu, 22 Dec 2011 14:31:02 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 1CB904056C; Thu, 22 Dec 2011 14:31:00 -0500 (EST) X-Virus-Scanned: OK Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id A613F4033F; Thu, 22 Dec 2011 14:30:59 -0500 (EST) Message-ID: <4EF38573.6060305@sugarcrm.com> Date: Thu, 22 Dec 2011 11:30:59 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Dmitri Snytkine CC: 'Sebastian Bergmann' , "internals@lists.php.net" References: <2095305E-D4E3-4D7E-8218-32EE99688E0C@GMAIL.COM> <2C90FB94-38C4-4270-8C6A-B89304BA8ED8@gmail.com> <159A7CA2-8561-40DA-9434-CAAE12304DDB@gmail.com> <005701ccc0b3$58c8dee0$0a5a9ca0$@alliantinternet.com> <20111222145159.GY25857@alliantinternet.com> <006101ccc0ba$46b81160$d4283420$@alliantinternet.com> <4EF379D8.9000206@lerdorf.com> <4EF37C29.1010206@php.net> <4EF37D19.8080207@alliantinternet.com> <007e01ccc0dc$985f1cd0$c91d5670$@alliantinternet.com> <4EF38297.5040507@alliantinternet.com> <008001ccc0df$3c8faa70$b5aeff50$@alliantinternet.com> In-Reply-To: <008001ccc0df$3c8faa70$b5aeff50$@alliantinternet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Return Type Hinting for Methods RFC From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > What I mean is that you can catch recoverable fatal error in your error > handler and at least be notified of what happened. Yes, you cannot go back > in your script to corrent anything after that but you can show a detailed > error message and send error email to developer. > > Just the same thing you can do when you hint class name for your input > parameter - it will generate catchable fatal error if object is not an > instance of expected class. Exactly, strict typing has same flaws everywhere, and this is exactly the reason it's not a solution for the problem it is presented to be - it does not make your code more robust or fail less or saves you effort on development - it just produces different error messages. While the case of wrong object type is rare enough to warrant application failure in case it happens - the case for scalar types is completely different. It was discussed many times on the list. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227