Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49304
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.161.42 cause and error)
MIME-Version: 1.0
In-Reply-To: <4C61F488.1090806@sugarcrm.com>
References: <AANLkTim7sNwZWyo8dQz-o6S=Tta-OGYqnDM0cDJX3A49@mail.gmail.com>
	<4C61D401.3050006@sugarcrm.com>
	<20100811002328.GB26237@mig9.immomigsa.ch>
	<4C61F488.1090806@sugarcrm.com>
Date: Tue, 10 Aug 2010 21:41:56 -0400
Message-ID: <AANLkTi=KbxOZbDYdXhD3vkDWAn8hKaEy4yd8m+JOA7Od@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Kalle Sommer Nielsen <kalle@php.net>, Internals <internals@lists.php.net>, 
	Derick Rethans <derick@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Strict typing
From: ilia@prohost.org (Ilia Alshanetsky)

Sounds like a reasonable name change. PHP never really had
"type-hinting" since even array or Object type "hints" would throw out
any value that didn't precisely match the requested type by the
method/function declaration.

On Tue, Aug 10, 2010 at 8:53 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>