Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49303 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4005 invoked from network); 11 Aug 2010 00:53:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2010 00:53:37 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.113 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.113 smtp113.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.113] ([67.192.241.113:36355] helo=smtp113.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3E/03-20356-194F16C4 for ; Tue, 10 Aug 2010 20:53:37 -0400 Received: from relay11.relay.dfw.mlsrvr.com (localhost [127.0.0.1]) by relay11.relay.dfw.mlsrvr.com (SMTP Server) with ESMTP id 0CA8F180030; Tue, 10 Aug 2010 20:53:35 -0400 (EDT) Received: by relay11.relay.dfw.mlsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 6273917FF00; Tue, 10 Aug 2010 20:53:29 -0400 (EDT) Message-ID: <4C61F488.1090806@sugarcrm.com> Date: Tue, 10 Aug 2010 17:53:28 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 MIME-Version: 1.0 To: Kalle Sommer Nielsen , Internals , Derick Rethans References: <4C61D401.3050006@sugarcrm.com> <20100811002328.GB26237@mig9.immomigsa.ch> In-Reply-To: <20100811002328.GB26237@mig9.immomigsa.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Strict typing From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Might be the time to rename what we currently call "type hinting" then. > Because what we currently have is strict typing as well. Maybe. The term "hint" was inexact from the start, as hint means (Collins English Dictionary): 1. a suggestion or implication given in an indirect or subtle manner he dropped a hint 2. a helpful piece of advice or practical suggestion 3. a small amount; trace That's clearly not what is going on - there's nothing subtle or indirect there and there's not a suggestion - it's a strict and unequivocal definition of type expected for the function call. But with its use in 5.3 it didn't matter since it was clear what we are talking about and there was no possibility of confusion. Right now what we have is a classic strict typing, albeit not required for all places but f(int $f) in PHP would be the same as f(int i) in C, so calling them differently would only lead to confusion. Maybe we should have called it "parameter typing" or something like that from the start. It didn't seem important back then because everybody agreed what it means. Obviously it is no longer the case. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227