Hello Stanislav, but that is a way of having __call that obviously doesn't fit the real world. In a real world application i only implement a few things with call and dislike having all the others implemented automatically also. And the i have to care about error generation while the engine could help me a lot so that my error messages look and behave just like they would if there is no __call. But that would indeed require some __exists() or __implemented() support().
marcus Wednesday, January 4, 2006, 10:24:20 AM, you wrote: DR>>>That is not fully true, as you can use function_exists() on DR>>>mysql_query, where there is no such possibility for methods that are DR>>>overloaded with __call(). > That's correct, of course - this is the whole point of __call - it makes > _any_ function exist. Now, calling these functions may succeed or fail - > just as calling any other functions may succeed or fail. > -- > Stanislav Malyshev, Zend Products Engineer > [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
