On Thu, 10 Aug 2006, Pierre wrote: > On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: > > Yeah. It is problematic that the application has no chance of dealing > > with the errors itself (consider e.g. php-shell which has to go great > > lengths to prevent fatal errors from user code leading to php-shell's > > termination, and still fails at doing this in the general case). > > Why object should act differently than other php variables or > constants? Undefined constant, variable, index or offset do not raise > a fatal error. It should be the same for the object (constants, props, > visibility,...).
He wasn't talking about *undefined variables* at all. The variable *is* defined as private and calling that is ofcourse not allowed. The second thing is that calling normal undefined functions throws a fatal error as well, and it should do that just like calling non existing methods on an object should throw a fatal error. regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
