Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37005
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.175 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=N6I8kemJZPBRPQfoidylEq9kkZVzkwheBIrVBGUH8MyWiIwzt6GbmV8V2xx87N+Hq7vIEtrNb7lb/OErjicmd8IjXIwl8fxR+hYFfEjmWIzBwqLK7DengBtHPYuJNVecNjBoOv/Mx8sB68h4ndBq5buYeXq8XGKg5HWW1/GvEFg=
Message-ID: <e2e02fe0804141004o9fa215cxb53e05466145950d@mail.gmail.com>
Date: Mon, 14 Apr 2008 10:04:23 -0700
To: "Christian Schneider" <cschneid@cschneid.com>
Cc: internals@lists.php.net
In-Reply-To: <48036A0C.7070203@cschneid.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_6004_3453544.1208192663881"
References: <1207539695.5736.42.camel@pena>
	 <8d7b8c130804062157j60871630r6c3b27c4d3245cb9@mail.gmail.com>
	 <alpine.DEB.0.98.0804071543580.4652@kossu.ez.no>
	 <1207576676.5331.49.camel@felipe> <47FA507D.2070108@cschneid.com>
	 <5CB53203-F3E5-46F2-89A8-F331B2CB9017@pooteeweet.org>
	 <47FA60F8.7060702@zend.com>
	 <37C655F0-D212-420C-9320-7953A69C5EDB@pooteeweet.org>
	 <e2e02fe0804132006g1a58dcabrbc37b93ddeb92981@mail.gmail.com>
	 <48036A0C.7070203@cschneid.com>
Subject: Re: [PHP-DEV] Return type hints
From: chrisstocktonaz@gmail.com ("Chris Stockton")

------=_Part_6004_3453544.1208192663881
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You are missing the point, why be strict on return types, and liberal on
parameters? Be strict consistently or be liberal consistently. Or, keep php,
php. I could care less as long as things are consistent, although I think
only supporting scalar is silly regardless of type juggling.

-Chris

On Mon, Apr 14, 2008 at 7:28 AM, Christian Schneider <cschneid@cschneid.com>
wrote:

> Chris Stockton schrieb:
>
>  Why on earth would you have int, string, resource, etc "return type
> > hints"
> > and then turn around and suggest for parameter hinting just add a scalar
> > type? That makes no sense and is so inconsistent.
> >
> > static int function retarded(scalar $value) {
> >    return (int) $value; // lol....
> > }
> >
>
> Let me turn your question around: Why on earth would someone restrict a
> function to int when string works just as well?
>
> function int foo_flexible(scalar $x) { return $x + 42; }
> $foo = foo_flexible($value);
>
> function int foo_retarded(int $x) { return $x + 42; }
> $foo = foo_retarded((int)$value);       # :-(
>
> That said, I'll be using
> function foo($x) { return $x + 42; }
> anyway and let PHP warnings take care of the rest ;-)
>
> - Chris
>
>

------=_Part_6004_3453544.1208192663881--