Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53115
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
         :cc:content-type;
        b=HKzQ25x5c3YiJSTynF7KukJzW03XniMIjPPxw4HWkRljm+EwKqUMvHlrMP/SOkravp
         6Ek+5s7EnHvqEyBEeMkvSmHg6N/Yddl/dDgBzCMyygs6UpjF39Mafs73rx1zaJd6HVKu
         VrNnrOD/NeZjElDl3orYaXRJ5gixxm4KsNWEo=
MIME-Version: 1.0
In-Reply-To: <4DED5C77.8040209@sugarcrm.com>
References: <BANLkTimU6DxovPQFP6cOXE0sKTDchx5Ltg@mail.gmail.com>
	<4DED3A29.1090209@sugarcrm.com>
	<BANLkTimWtZOvu4LZAtpJsuZg1SXHdYYHxg@mail.gmail.com>
	<4DED43D4.4070006@sugarcrm.com>
	<DF.F3.23189.2B15DED4@pb1.pair.com>
	<4DED5C77.8040209@sugarcrm.com>
Date: Mon, 6 Jun 2011 23:50:44 -0300
Message-ID: <BANLkTikaLgMoB1RE2A6Og=2kMcSSeVa+Gw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: "Matthew Weier O'Phinney" <weierophinney@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=90e6ba53b07053494804a5164950
Subject: Re: [PHP-DEV] Callable typehint
From: martinscotta@gmail.com (Martin Scotta)

--90e6ba53b07053494804a5164950
Content-Type: text/plain; charset=ISO-8859-1

 Martin Scotta


On Mon, Jun 6, 2011 at 8:02 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> Hi!
>
>
>  The point, though, is that with such a typehint available, we can reduce
>> boilerplate code like the following:
>>
>
> Sure. How about reducing boilterplate code like this:
>
> if(is_readable($foo)) {
>  $var = file_get_contents($foo);
> } else {
>  throw  InvalidArgumentException();
> }
>

trol?



>
> Why won't we make language construct to do that too? I don't think these
> things belong in the language syntax.
>
>
>
>>     public function addCallback($callback)
>>     {
>>         if (!is_callback($callback)) {
>>             throw new InvalidArgumentException();
>>         }
>>
>> The typehint makes this simpler:
>>
>>     public function addCallback(callback $callback)
>>
>>
> You understand that these two pieces of code are completely different - for
> one, you can't catch failing strict type check upstream of addCallback and
> recover.
>
>
>  which allows us to rely on PHP's native error handling. I, for one,
>> would love to see this.
>>
>
> I wouldn't love it a bit, frankly, as "rely on PHP's native error handling"
> in this context means "bombing out in runtime without any idea what went
> wrong". When you have exception, you could make it print what happened and
> recover, if you want. When you have fatal error, you can't do much at all.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--90e6ba53b07053494804a5164950--