Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52084
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=WZ/mF/WYeKcwPmpRnStFsDR0hWyl4IaG2A5Rao/obDAl09L6CW2W+dmxJLVQA0MMjs
         IO4X5da3gYpbRlnUiDYmXlEqu9N831btKnuY+E77VCYMygm5BhIzeH9k7VwIhdJxTGpt
         jibJbb3v0YZEWK1qMl0ripysR4rSSETxuC5kQ=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <4DBA46FD.5090106@sugarcrm.com>
References: <AANLkTimDdM4Udx53qW8jU4NuP3kU8+vmU6y4ZgXRVn+X@mail.gmail.com>
	<BANLkTinMW_iqqOPJCuLnCB+-VEKxapPdGg@mail.gmail.com>
	<4DB923E6.3020307@sugarcrm.com>
	<BANLkTi=4FzRJuYpK3C_ZD=JYZq2xq6hzJw@mail.gmail.com>
	<4DB9A7BE.6010307@sugarcrm.com>
	<20110428181630.GA8496@phcomp.co.uk>
	<4DBA46FD.5090106@sugarcrm.com>
Date: Fri, 29 Apr 2011 11:09:23 +0200
Message-ID: <BANLkTik1na=_UwxopfABcLJi9kS45mUkRA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e0cb4e6fff6fa9367204a20b07aa
Subject: Re: [PHP-DEV] [RFC] Return type-hint
From: info@tyrael.hu (Ferenc Kovacs)

--e0cb4e6fff6fa9367204a20b07aa
Content-Type: text/plain; charset=UTF-8

>
>
>  Which might be acceptable for some applications. For those where it is not
>> then this feature may not be useful. This is an *optional* declaration,
>> not mandatory - so if it does not suit your purpose -- don't use it.
>>
>
> You are talking about pretty big change in language nature - introducing
> strict typing. "It's just option, don't use it if you don't want" doesn't
> really sound good in this case. If it's in the language, it should make
> sense and sit well with the rest of the language.
>
>
sorry, where would we intrudoc strict typing?
as I mentioned before, the proposed implementation would "sit well with the
rest of the language" in this aspect.
eg. would work the same as the argument type hinting does.

what Alain said, that there would be a possible to use the provided type
information before actually calling the function.
the fact that HipHop can use this information and Zend not (yet, or only for
trivial cases) wouldn't change this fact, or the language itself.

Tyrael

--e0cb4e6fff6fa9367204a20b07aa--