Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53202
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.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=HsKdOfcYCLWSaCQ4j2NaSbYJd1nGDJdbrZGEOBSBt3pZaKfCR1EoBUI8S67iww9J7N
         qBRxaSrirXwOz8LoVysVwE1Xpq75coaZoFlS4d9Y2aMwoHqGGj1f6sm3OLq7b3eWkBN+
         5/c4sy19UNgMp7iUi5tVh7sv29nbkqxzNWOPk=
MIME-Version: 1.0
In-Reply-To: <BANLkTikPdGSZmeaJNsxUpvCVn5WKUCy0Tw@mail.gmail.com>
References: <BANLkTimU6DxovPQFP6cOXE0sKTDchx5Ltg@mail.gmail.com>
	<4DED3D5B.6030307@oracle.com>
	<BANLkTimEEh7eT7bH4qb9gPro_R2sKw24SyJ7JwWp8j6Ew2fH0Q@mail.gmail.com>
	<F8.04.15404.AAD4EED4@pb1.pair.com>
	<4DEE782E.1020605@sugarcrm.com>
	<7104F8AD-489E-4824-97AA-D9831FAB77AA@bitextender.com>
	<BANLkTi=5V0dfA0oEctOe=5v9iJfXUk--bg@mail.gmail.com>
	<4DEE8ABB.8040503@sugarcrm.com>
	<7E4C6CB6-ED93-4BFC-87B8-94FDEF243896@bitextender.com>
	<17.29.50253.ACD8EED4@pb1.pair.com>
	<BANLkTi=-OuiJtztrncKWrziTWQ=LkKFmLg@mail.gmail.com>
	<41.0E.50253.11B9EED4@pb1.pair.com>
	<BANLkTi=LjB1zgy3zUw0DM04vOEMj_JNgx29wS7bN+CQAqqMDrA@mail.gmail.com>
	<BANLkTimC80cNWj60+ogtNOaXvJaDSokgag@mail.gmail.com>
	<BANLkTikPdGSZmeaJNsxUpvCVn5WKUCy0Tw@mail.gmail.com>
Date: Wed, 8 Jun 2011 12:30:25 +0200
Message-ID: <BANLkTimQJ1c2Dn=P-iBmdr12g921S_YK-wgQ5Qw_jc0y=d9+UA@mail.gmail.com>
To: RQuadling@gmail.com
Cc: Alexey Shein <confik@gmail.com>, "Matthew Weier O'Phinney" <weierophinney@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Callable type
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Wed, Jun 8, 2011 at 12:27, Richard Quadling <rquadling@gmail.com> wrote:
> On 8 June 2011 09:47, Alexey Shein <confik@gmail.com> wrote:
>> 2011/6/8 Hannes Magnusson <hannes.magnusson@gmail.com>:
>>> We have the situation in the docs that parameters declared as arrays
>>> do not follow the typehinting rules, but parameters as class names do.
>>> Re-using the callback from the docs could get confusing when
>>> extensions start to typehint on it, but not the core..
>>>
>>> I think there is a subtle difference between a callback, and a callable.
>>> In javascript for example, callback is something that is executed on
>>> certain events "onsuccess" is the typical example.
>>> There is nothing that says the callable parameter gets executed as a
>>> part of an event, and I think the default usecase would be to execute
>>> it right away (f.e. filtering data).
>>>
>>> I think I would prefer callable, but I could live with either.
>>>
>>
>> Wikipedia defines callback as "a reference to executable code, or a
>> piece of executable code, that is passed as an argument to other
>> code". So there's no "event" meaning put by default, it's just very
>> often seen callback's usage in javascript.
>> I just like "callback" term more :)
>
> An interesting issue here.
>
> Closures, classes with an __invoke method and strings containing
> existing function names all pass is_callable() and can be called using
> ().
>
> But, array('class', 'method') also passes is_callable, but isn't a callback.


It is after Felipes recent commit introducing $array();

-Hannes