MB>> but that is a way of having __call that obviously doesn't fit the real MB>>world. In a real world application i only implement a few things with call MB>>and dislike having all the others implemented automatically also. And the MB>>i have to care about error generation while the engine could help me a lot MB>>so that my error messages look and behave just like they would if there MB>>is no __call. But that would indeed require some __exists() or MB>>__implemented() support().
Nothing prevents you from having __implemented or __whateveryoulike. However, I don't see how engine could know beforehand if your __call would succeed or not, so __implemented has no relation whatsoever to __call, unless you make this relation in your code - and engine can't know you did. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
