Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53090
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 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=rGW6nRZIU+dtBDVnOwiq6bD97kLT5mzAoSicMy51k9gr9CzzTmlWvuIvYP678afurd
         4z/iMxT5Z7vlotiQWK3P/vLhAvZQZfDDSn/YSmTqpyEH+qiai0rq4yoXMBPz49uU1/6S
         X0xHCXhzSn31hZzOjMoDDP+w76+N3CFZgdKe4=
MIME-Version: 1.0
In-Reply-To: <DF.F3.23189.2B15DED4@pb1.pair.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>
Date: Tue, 7 Jun 2011 00:26:56 +0200
Message-ID: <BANLkTimabyQEGZb1hm7suxMr-XDGkaq3vg@mail.gmail.com>
To: "Matthew Weier O'Phinney" <weierophinney@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=0016e6de0029ddc06f04a5129914
Subject: Re: [PHP-DEV] Callable typehint
From: pierre.php@gmail.com (Pierre Joye)

--0016e6de0029ddc06f04a5129914
Content-Type: text/plain; charset=ISO-8859-1

How is this argument different than the one in favor of type hinting  (or
whatever was what ended in trunk)?

On 7 Jun 2011 00:16, "Matthew Weier O&apos;Phinney" <weierophinney@php.net>
wrote:
> On 2011-06-06, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>> > Like I mentioned in the other thread (which I probably should had
>> > repeated here), a lot of libs/frameworks are using the 'Closure'
>> > typehint for callbacks.
>>
>> Well, they are wrong (unless they mean to use only closures and not
>> callbacks). But that's no reason to do wrong thing in the language
>> too.
>>
>> > The problem with that is a function name as a string and
>> > array("classname", "functionname") are considered is_callable(). To
>> > get through the intentions of the Closure hint, I would have to wrap
>> > the actual callback in a closure - which doesn't make any sense.
>>
>> "callable" is not actually even a type. If we make it a language
>> construct, then why 'authenticated DB connection', 'name of readable
>> file', 'valid stream URL', 'validated XML', 'string in UTF-8 no longer
>> than 255 characters' or 'balanced binary tree' is not a language
>> construct? I don't think we need to put every data check into the
>> language, especially that it actually makes it worse - you can
>> gracefully handle user-space check, but not a strict typing error.
>
> The point, though, is that with such a typehint available, we can reduce
> boilerplate code like the following:
>
> public function addCallback($callback)
> {
> if (!is_callback($callback)) {
> throw new InvalidArgumentException();
> }
>
> The typehint makes this simpler:
>
> public function addCallback(callback $callback)
>
> which allows us to rely on PHP's native error handling. I, for one,
> would love to see this.
>
> --
> Matthew Weier O'Phinney
> Project Lead | matthew@zend.com
> Zend Framework | http://framework.zend.com/
> PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--0016e6de0029ddc06f04a5129914--