2011/6/8 David Zülke <david.zue...@bitextender.com>:
> On 08.06.2011, at 00:38, dukeofgaming wrote:
>
>> On Tue, Jun 7, 2011 at 4:41 PM, Matthew Weier O'Phinney <
>> weierophin...@php.net> wrote:
>>
>>> On 2011-06-07, dukeofgaming <dukeofgam...@gmail.com> wrote:
>>>
>>>> +1 for "callable", it is really more consistent.
>>>
>>> I was actually agreeing With David and Stas that "callback" was more
>>> consistent, and casting my vote for that.
>>
>> Oh. But then, shouldn't is_callable be deprecated for a more consistently
>> named is_callback?
>
> No, because is_callable() also performs visibility checks.
>
> Which of course begs the question... should the type hint do the same?
>
> David
>
>
+1 to "callback" (and have mercy on docs/translation people, it's too
much work to search/replace for such a minor difference :))
And yes, two similar terms (callback/callable) will make situation worse.
Plus to Johanness question: will it add runtime performance overhead
on code like this:
function(callback $callback = 'non_existent_function') {}
--
Regards,
Shein Alexey
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
