Re: __call overload detection
| From: | Marcus Boerger | Date: | Wed, 04 Jan 2006 17:12:13 +0000 |
| Subject: | Re: __call overload detection | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21422@lists.php.net to get a copy of this message | ||
Hello Stanislav,
just again, the point is integration so that you know whether it makes
any sense to call soemthing or not without having to check for errors
after the call.
marcus
Wednesday, January 4, 2006, 5:59:59 PM, you wrote:
MB>>> both will have a function pointer on the c side so the major
MB>>>slowdown you spoke of will only be there if one actually wants it.
MB>>>Otherwise there will be only the pointer check.
> I think you lost me. What exactly you are describing here? I though we
> were talking about implementing something alike __call - which is not C
> side - and implementing it in PHP, which is not C side either. Obviously,
> it is not what do you describe - so can you give some more explanation
> what do you mean?
> --
> Stanislav Malyshev, Zend Products Engineer
> stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115
Best regards,
Marcus