Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53182
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.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=df3SK8uPapvvC/AW8WrGaBp4l54OuvVjxR7YXvVIu7yESIV+qsw8GZcHA4EPUCuMHo
         DI4xYiOZ5Iw000Dq04jGWIkDQfamTbWwj/qQuSZmZ0KTA5kGnBIrNXJm8vJYsnzs70GZ
         LH61VJh6cCemrHQUoG9sQuFV1UizokKcz+wXI=
MIME-Version: 1.0
In-Reply-To: <4DEE782E.1020605@sugarcrm.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>
Date: Tue, 7 Jun 2011 22:37:16 +0200
Message-ID: <BANLkTi=bV5SGkgDDk0GpRcj8y6wSgNZ30w@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: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Callable type
From: pierre.php@gmail.com (Pierre Joye)

hi Stas,

I have to say that we should apply our upcoming voting rule here as well.

If we don't, pls count -1 from here anyway.

Cheers,

On Tue, Jun 7, 2011 at 9:12 PM, Stas Malyshev <smalyshev@sugarcrm.com> 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 patch introduces new zval type IS_CALLABLE but zval functions weren't
> updated for it - IIRC at least dtor may end up being called on IS_CALLABLE
> value produced in the parser.
>
> Note also that this pseudo-type is called "callback" in all of our
> documentation, which means we have now documentation that says:
>
> bool array_walk ( array &$array , callback $funcname [, mixed $userdata ] )
>
> and type check that says "callable".
>
> Also, it is not clear what would happen if this type check is made against
> method which is not accessible (e.g. private out of scope). Would it say
> that the argument is invalid (which would be really confusing since it'd say
> something like "callable expected, array given" which it technically correct
> but doesn't explain why this array is not callable) or would allow it? If
> not, then zend_is_callable error information should be used and displayed.
> And the tests need to cover these cases, along with __call and __callStatic.
>
>
> For me personally it makes zero sense that having just removed strict typing
> we are introducing it back through back door, but if everybody likes it so
> be it.
> --
> 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
>
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org