Re: __call overload detection

On Tue, Jan 03, 2006 at 05:29:11PM -0800, Andi Gutmans wrote: > I think it's different especially as it's complementary to unset() > but I don't intend to get into an argument about it. I see your point there about isset and unset being a matched pair. From my perspective, call is similar to unset. It is implemented as a "black box" and has no complementary introspection method like isset to figure out how the black box works - at least as part of the language. unset has side-effects by nature of its intention, as might use of call. isset is intended to be a no side-effect poke at a property, but no such complement exists for call. > In any case, the tools for Andrew to resolve this programmatically on > the PHP level exist even if the syntax isn't 100% of what he'd like it to > be. 100% agreed and I have done so. I've brought it up for the community's benefit, as I think it is an area that has room for some improvement. I can see it becoming an issue as the frameworks and libraries for 5 continues to build and are integrated. I don't want to argue either - just trying to have productive discussion. Regards, Andrew -- Andrew Yochum Plexpod andrew@plexpod.com 718-360-0879