Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53196
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.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:content-transfer-encoding;
        b=n9/63rva0PWqZI9Ob52VEuQ+dNscd7GAgr6t9oP5GrGzeI+SBLo7jpjdv84AQSOm37
         SJQnZpdt3iKcOP6vRdo1zd+1f6DcPG/2hrl3A9+UeMMJQuwMud6W6ZFDV1Tiinl/dHb7
         4iFAwMH+zGf+Z9JVlO/lc39Hz9oHz/lkRQ238=
MIME-Version: 1.0
In-Reply-To: <1307489981.23373.31.camel@guybrush>
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>
	<1307489981.23373.31.camel@guybrush>
Date: Wed, 8 Jun 2011 10:38:51 +0200
Message-ID: <BANLkTimOx3xr5t50Wtjxb_HzL6ALc8gW5ghKeTJOeJD5oxQNXA@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, "Matthew Weier O'Phinney" <weierophinney@php.net>, 
	internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Callable type
From: hannes.magnusson@gmail.com (Hannes Magnusson)

2011/6/8 Johannes Schl=C3=BCter <johannes@schlueters.de>:
> On Tue, 2011-06-07 at 12:12 -0700, Stas Malyshev wrote:
>> Hi!
>>
>> > https://wiki.php.net/rfc/callable
>>
>> It is good there's an RFC. However it seems to lack code examples. I
>> understand it may be obvious to the proposers how it looks like, but
>> it'd be nice to have the actual example there as it is done nearly
>> everywhere else.
>
> The RFC is missing information about what happens in codebases which
> already have a "callable" type declared. Will that be prevented or will
> they hit a runtime error? ("callable expected, callable type found")

You mean an interface/class with that name?
The error would be 'expected instanceof callable, string/array/closure reci=
eved.

gettype("strpos") will still return a string, not callable.

A callable wouldn't be fully featured type.

> What about default values? Will
> =C2=A0 =C2=A0function foo(callback $cb =3D 'strpos') { }
> be valid?

No default values, other then NULL allowed.
Otherwise we would need to support array("classname", "methodname")
too, and then people would want default array values for array
typehinting etc etc etc.



> The information on reflection is limited. what shall
> Reflection::Parameter::getTypehint() return? Will that method allow to
> differ between a class type and this "magic"?

There is no such method anymore :)


>
> What about ARGINFO? Will internal functions be able to define this type
> via ARGINFO? How will this be reported in `php --rf function`?

I didn't include arginfo in the patch, but good point. It should
probably be included.
As Felipe pointed out, ext/reflection hasn't been updated.
It should return [ callable $foobar ], just like with any other typehint

-Hannes