Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52056
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=okHYYq7lVH96QyMfrKvtxkXHeblmJ774lTmQMq8Oenmeug2nZWZwQcgoWywsS4Xd9u
         +aqwgtJI1+JK2/EoPnpfpCosCZPzbkIdRQPC0MkMKr2oA/zrOEUpoGWLi668Kc38eyBA
         JHwRc+4kngHxsP+tbkauMDhiUekmjsEz0Uk6Y=
MIME-Version: 1.0
In-Reply-To: <20110428095958.GM8496@phcomp.co.uk>
References: <AANLkTimDdM4Udx53qW8jU4NuP3kU8+vmU6y4ZgXRVn+X@mail.gmail.com>
	<BANLkTinMW_iqqOPJCuLnCB+-VEKxapPdGg@mail.gmail.com>
	<4DB923E6.3020307@sugarcrm.com>
	<4DB925D4.5090107@thelounge.net>
	<4DB926B4.5000307@sugarcrm.com>
	<20110428085859.GJ8496@phcomp.co.uk>
	<4DB936C8.2080801@lerdorf.com>
	<20110428095958.GM8496@phcomp.co.uk>
Date: Thu, 28 Apr 2011 10:30:43 -0300
Message-ID: <BANLkTi=RYD2H=zKLcR+uoxwEWyL5f7e93Q@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	Reindl Harald <h.reindl@thelounge.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec51a8e0c695a2f04a1fa90f2
Subject: Re: [PHP-DEV] [RFC] Return type-hint
From: martinscotta@gmail.com (Martin Scotta)

--bcaec51a8e0c695a2f04a1fa90f2
Content-Type: text/plain; charset=ISO-8859-1

Hey All,
I'm really interested on this topic.

What would be the result of this?

function Foo foo($something) {
     if ( $something ) {
          return new Foo;
     }
     // no return implies return null
}

How do you force to return a Type with null allowed?

 Martin Scotta


On Thu, Apr 28, 2011 at 6:59 AM, Alain Williams <addw@phcomp.co.uk> wrote:

> On Thu, Apr 28, 2011 at 02:43:36AM -0700, Rasmus Lerdorf wrote:
>
> > >     function array foo() { .... }
> > >
> > >     $ret = foo();
> > >     foreach($ret as $val)
> > >         ....
> >
> > I don't see this being useful at all. All you are doing is duplicating a
> > runtime warning. We can't possibly know at compile-time whether this
> > return value is an array or not, so there is no compile-time benefit.
>
> The check is not done where foo() is called but within foo() itself, to
> ensure
> that it only returns an array.
>
> There will also be advantages for HipHop which can afford to spend the time
> to
> do static analysis of code -- I know that HipHop is not your baby
> but you now need to recognise that there is more than one PHP
> implementation
> and features that may not had much advantage with Zend may be useful
> elsewhere.
>
> --
> Alain Williams
> Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT
> Lecturer.
> +44 (0) 787 668 0256  http://www.phcomp.co.uk/
> Parliament Hill Computers Ltd. Registration Information:
> http://www.phcomp.co.uk/contact.php
> #include <std_disclaimer.h>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec51a8e0c695a2f04a1fa90f2--