Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52049
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 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=fxtu0WW4DF8BahCKYslECh1/R1abPawz1CX6PQiiwbZJWVuZj8xWuq9OZ76z2Hh3Im
         H7+5JnfCTH55IEJ/u2v5kF+U1ftChJHIFKERXT/Yru5uMGtX55Mcf1ubiXMzirBVYCkb
         7YIv1OliBdiGg0SLZTIS2CvWkArItp5F0rjZ8=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <4DB923E6.3020307@sugarcrm.com>
References: <AANLkTimDdM4Udx53qW8jU4NuP3kU8+vmU6y4ZgXRVn+X@mail.gmail.com>
	<BANLkTinMW_iqqOPJCuLnCB+-VEKxapPdGg@mail.gmail.com>
	<4DB923E6.3020307@sugarcrm.com>
Date: Thu, 28 Apr 2011 10:52:34 +0200
Message-ID: <BANLkTi=4FzRJuYpK3C_ZD=JYZq2xq6hzJw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Felipe Pena <felipensp@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30363ac3ac692304a1f6ade1
Subject: Re: [PHP-DEV] [RFC] Return type-hint
From: info@tyrael.hu (Ferenc Kovacs)

--20cf30363ac3ac692304a1f6ade1
Content-Type: text/plain; charset=UTF-8

>
>
>
> The RFC doesn't explain it either beyond "here how you can have some nice
> errors".
> But why would I want to see these errors? How they would make anything
> easier or better?
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>

maybe we should improve on the rfc.
I see many advantages of the introduction of return type hinting.
- you can guarantee that your methods returns only what is explicitly stated
(or else it blows up, the same as for arguments)
- it can save you from having to define the return type in phpdoc, your code
can define it's behavior
- I think maybe the language itself could use that information, for
performance, etc. improvements (we know that the return value will be
created runtime, but we can throw it away if it doesn't match the return
type or something), maybe we can use that information to throw errors on
compile time if we find a non runtime decided return value which doesn't
match with the return type.

I'm sure that others have and will come up with more use cases.

Tyrael

--20cf30363ac3ac692304a1f6ade1--