Re: __call overload detection
| From: | Marcus Boerger | Date: | Wed, 04 Jan 2006 17:10:59 +0000 |
| Subject: | Re: __call overload detection | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21421@lists.php.net to get a copy of this message | ||
Hello Stanislav,
the point is integration but i see no point for further dicussion
unless you are willing to reread the thread and accept what we were
talking about here.
Wednesday, January 4, 2006, 6:02:41 PM, you wrote:
MB>>> having non supported dynamic calls behave in the same way as build
MB>>>in or user code methods.
> As defined code methods? Make your __call always return true and that is
> what you'd get, not? Or you want it to behave as undefined methods? Then
> make your __call to throw and error once it can not call a function and
> you get the same.
Best regards,
Marcus