Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21385
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 4 Jan 2006 02:24:50 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1789719273.20060104022450@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>
Cc: Andrew Yochum <andrew@plexpod.com>,
	php internals <internals@lists.php.net>
In-Reply-To: <7.0.0.16.2.20060103164047.043e6900@zend.com>
References: <20060103205728.GF26280@desario.homelinux.net>
	<7.0.0.16.2.20060103154506.043678e8@zend.com>
	<829348376.20060104010548@marcus-boerger.de>
	<7.0.0.16.2.20060103164047.043e6900@zend.com>
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 Andi,

  we didn't saw any necessaty for __isset either.

marcus

Wednesday, January 4, 2006, 1:41:44 AM, you wrote:

> Right but you can do it in user-land. If you're writing __call() you 
> could add an additional method to see if it's mapped. I don't think 
> it's quite as common as isset().



> At 04:05 PM 1/3/2006, Marcus Boerger wrote:
>>Hello Andi,
>>
>>   the point is probably that there is no way in determinig whether a
>>certain function is supposed to work prior to calling it.
>>
>>regards
>>marcus
>>
>>Wednesday, January 4, 2006, 12:45:23 AM, you wrote:
>>
>> > Why not just use Reflection API to check? It seems quite trivial to do so.
>>
>> > At 12:57 PM 1/3/2006, Andrew Yochum wrote:
>> >>Currently there is no way to detect if the __call overloads a particular
>> >>method.  Property overloading has __isset now in 5.1 - maybe for method
>> >>overloading the equivalent should be something like __iscallable.  Maybe
>> >>method_exists should remain as is, as the method won't ever really exist
>> >>but is_callable would/could use it, or perhaps some new function.