Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57060
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)
References: <2095305E-D4E3-4D7E-8218-32EE99688E0C@GMAIL.COM>
 <CAF+90c-Wtok1fnVxokYUFQhbYnMcNDwWWT63F8NDp+JnxCDMew@mail.gmail.com>
 <2C90FB94-38C4-4270-8C6A-B89304BA8ED8@gmail.com> <CAEZPtU6gneOOehrsz-qVifmNxg6tnyLt9hqfnAwKZmfpXdeC9Q@mail.gmail.com>
 <159A7CA2-8561-40DA-9434-CAAE12304DDB@gmail.com> <4EF3B56A.4040809@gmail.com>
 <-2451498990672032588@unknownmsgid> <4EF3C99F.4010300@gmail.com>
 <4EF3CEFA.4000301@alliantinternet.com> <008801ccc179$74ef1190$5ecd34b0$@alliantinternet.com>
 <9570D903A3BECE4092E924C2985CE48539A1826E@MBX202.domain.local>
In-Reply-To: <9570D903A3BECE4092E924C2985CE48539A1826E@MBX202.domain.local>
Mime-Version: 1.0 (1.0)
Date: Fri, 23 Dec 2011 15:34:00 -0500
Message-ID: <-253406703910979221@unknownmsgid>
To: Clint M Priest <cpriest@zerocue.com>
Cc: Dmitri Snytkine <dsnytkine@ultralogistics.com>, =?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?= <keisial@gmail.com>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Return Type Hinting for Methods RFC
From: will.fitch@gmail.com (Will Fitch)

Im personally not a fan of declaring multiple return values. This
defeats the purpose of being more strict. If your method may return
different values outside of the declared type, then using the standard
"function" keyword would signify mixed.

There's still the matter of whether allowing null to be returned,
regardless of the situation, or using another token to identify that
it could return null. I'd like to know what others think. I see Stas'
argument that you'll still have to check, but I'm not so sure that is
such a bad thing.

Sent from my iPad

On Dec 23, 2011, at 3:07 PM, Clint M Priest <cpriest@zerocue.com> wrote:

> That syntax is pretty readable, would there be alternatives such as:
>
> function foo() returns Class3, array or null {
> }
>
> -----Original Message-----
> From: Dmitri Snytkine [mailto:dsnytkine@Ultralogistics.com]
> Sent: Friday, December 23, 2011 7:48 AM
> To: '=C3=81ngel Gonz=C3=A1lez'; 'PHP Developers Mailing List'
> Subject: RE: [PHP-DEV] Return Type Hinting for Methods RFC
>
> Is this how it's done in Scala?
>
> Dmitri Snytkine
> Web Developer
> Ultra Logistics, Inc.
> Phone: (888) 220-4640 x 2097
> Fax: (888) 795-6642
> E-Mail: dsnytkine@ultralogistics.com
> Web: www.ultralogistics.com
>
> "A Top 100 Logistics I.T. Provider in 2011"
>
>
> -----Original Message-----
> From: =C3=81ngel Gonz=C3=A1lez [mailto:keisial@gmail.com]
> Sent: Thursday, December 22, 2011 7:45 PM
> To: PHP Developers Mailing List
> Subject: Re: [PHP-DEV] Return Type Hinting for Methods RFC
>
>> (I'm unsure about the T_DOUBLE_ARROW, although for parsing, I feel
>> there should be some token there before the class name, though I'm
>> unconvinced on which)
>
> What about this?
>
> function foo (Class1 $a, Class2 $b) return Class3 {
>    /* Do something */
>    return new Class3($a, $b);
> }
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visi=
t: http://www.php.net/unsub.php
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>