Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21376
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 3 Jan 2006 22:50:24 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1462157471.20060103225024@marcus-boerger.de>
To: Andrew Yochum <andrew@plexpod.com>
Cc: php internals <internals@lists.php.net>
In-Reply-To: <20060103213332.GG26280@desario.homelinux.net>
References: <20060103205728.GF26280@desario.homelinux.net>
	<1852411085.20060103220656@marcus-boerger.de>
	<20060103213332.GG26280@desario.homelinux.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] __call overload detection
From: helly@php.net (Marcus Boerger)

Hello Andrew,

  you do not implement __call for a method but you deal with the method name
in any sense you like, which also includes ignoring specific __call
invocations. Reflection gives you the ability to check whetehr a function
is being physically available. If you need more it is up to you to provide
the infrastructure. Remember we will not in anyway allow __call to handle
inheritance.

regards
marcus

Tuesday, January 3, 2006, 10:33:32 PM, you wrote:

> Hi Marcus,

> On Tue, Jan 03, 2006 at 10:06:56PM +0100, Marcus Boerger wrote:
>> Hello Andrew,
>> 
>>   right now you can use reflection.
>> 
>> marcus

> The reflection APIs do not help I believe.  Consider that one may only
> want __call to respond to a computable set of overloaded method names.
> Right now, is_callable returns true for any requested method if __call
> is implemented by the object.  Unless I have missed some magic that the
> Reflection APIs can do, they don't apply here.

> Consider the following:
>     class a {
>         var $callables = array('foo');
>         function __call($name, $args) {
>             if ($this->__is_callable($name)) return 'good call';
>             else return 'bad call';
>         }
>         function __is_callable($name) {
>             return in_array($name, $this->callables);
>         }
>     }

>     $a = new a();
>     print "is_callable: " . is_callable(array($a,'foo'),false, $callable) . " as $callable \n";
>     // prints: is_callable: 1 as a::foo
>     // OK
>     print "is_callable: " . is_callable(array($a,'bar'),false, $callable) . " as $callable \n";
>     // result: is_callable: 1 as a::bar
>     // desired: is_callable: 0 as 
>     // or some other similar behavior if __is_callable is implemented

> If one were to implement a reflection-like method called __iscallable,
> you could get this functionality, but couldn't count on other's code
> using the same convention.  Another downside to doing it yourself is
> that every call to a method must first check __is_callable - this could
> be handled by the language upon a method call.  If I feel it would be a
> good idea to implement this in the lanaguage for standardization and
> simplicity.

> Regards,
> Andrew




Best regards,
 Marcus