Re: __call overload detection

Stanislav Malyshev 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().

I agree. All we really need a central standard that people can adhere too and I think this is within the scope of internals, but it does not need to be handled by the engine itself. regards, Lukas