Re: __call overload detection

Hello Stanislav, how is this a major slowdown? It would add a simple pointer check at runtime and two places to set the pointer, one place will initialize it to NULL and the other will store some function pointer just like all the other __*()'s do. marcus Wednesday, January 4, 2006, 4:13:02 PM, you wrote: LS>>>well in theory is_callable could also be called before __call() to save LS>>>people from having to duplicate the logic from __callable() and to have the LS>>>engine trigger the error. that is what i meant and like i said i do not > That would be major slowdown - why should engine call additional methods? > In 99.99% of cases you don't need it and actually you would _have_ to > duplicate logic - once for handler that checks the callability and once > for the actual __call(). Best regards, Marcus