Re: __call overload detection
| From: | Marcus Boerger | Date: | Wed, 04 Jan 2006 16:46:34 +0000 |
| Subject: | Re: __call overload detection | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21417@lists.php.net to get a copy of this message | ||
Hello Stanislav,
both will have a function pointer on the c side so the major slowdown you
spoke of will only be there if one actually wants it. Otherwise there will
be only the pointer check.
marcus
Wednesday, January 4, 2006, 5:28:01 PM, you wrote:
MB>>> how is this a major slowdown? It would add a simple pointer check at
MB>>>runtime and two places to set the pointer, one place will initialize it to
MB>>>NULL and the other will store some function pointer just like all the other
MB>>>__*()'s do.
> You would have two PHP functions: __callable() and __call() which would
> both be called and do the same logic on function call. You can not use
> "some function pointer" from PHP.
Best regards,
Marcus