Re: Private member/method access inconsistency

From: Date: Sun, 11 Jan 2009 12:50:03 +0000
Subject: Re: Private member/method access inconsistency
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-42557@lists.php.net to get a copy of this message
>> Addressing those two points would make things even more consistent. >> I'm adding some testcases to illustrate. > > I fixed the callback case in 5_2. Need to talk to Dmitry about 5_3 and HEAD > because zend_is_callable_check_func() is damn complex now. > > -Andrei > Thanks! I noticed another inconsistency with this new behaviour: since bug 42937 was fixed, calling a non-existent method with the scope resolution operator (::) results in __call() being invoked if the current object scope is compatible with the target scope. I think this should now be adapted to apply when calling a non-visible method with ::. Patch against 5_2 with test case: http://pastebin.com/f7ee7a9fc Regards, Robin

« previous php.internals (#42557) next »