Re: __call overload detection
| From: | Andi Gutmans | Date: | Wed, 04 Jan 2006 00:41:44 +0000 |
| Subject: | Re: __call overload detection | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21383@lists.php.net to get a copy of this message | ||
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:Best regards, MarcusCurrently 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. Is this a reasonable request? Thoughts? Regards, Andrew -- Andrew Yochum Plexpod andrew@plexpod.com 718-360-0879 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php