Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57007 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24789 invoked from network); 22 Dec 2011 18:28:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Dec 2011 18:28:23 -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:57443] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/C8-12618-5C673FE4 for ; Thu, 22 Dec 2011 13:28:22 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id BC2434052A; Thu, 22 Dec 2011 13:28:18 -0500 (EST) X-Virus-Scanned: OK Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 361FE40A8D; Thu, 22 Dec 2011 13:28:14 -0500 (EST) Message-ID: <4EF376BD.8060903@sugarcrm.com> Date: Thu, 22 Dec 2011 10:28:13 -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: Nikita Popov CC: Dmitri Snytkine , Alain Williams , "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> In-Reply-To: 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! > Could we maybe keep this discussion contained to return value type > hints please? Optional variable type hinting is a completely different > topic that would require a separate RFC and implementation. If you are > interested in this you can propose a RFC for this. Actually, as I said many times in previous discussions on the topic, strict typing is useless (and, IMHO, even worse than that) if applied in small parts. If you have strict typing in return values, you'd have to have strict typing in variables, etc. - otherwise you'd have no way to protect yourself from hard-to-find runtime errors. And, actually, after that you'd have to make PHP compiled - since otherwise runtime errors will still be there. So in my opinion restricting discussion to return type strict typing is just deluding yourself. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227