Re: [PHP-DEV] Test for edge cases with __get and property access flags

2009-06-05 Thread John Mertic
Here's that test. I don't have commit rights to that area of CVS so someone will need to do it for me. John Mertic jmer...@php.net On 6/5/09 5:58 AM, Stan Vassilev wrote: 3. When the caller tries to retrieve $object->foo, and foo is a private/protected member the caller has no access to,

Re: [PHP-DEV] Test for edge cases with __get and property access flags

2009-06-05 Thread Eddie Drapkin
I thought this was the expected behaviour as well and I am quite sure that I've used it in an experiment (all class members private and _get() output escapes them) that failed pretty miserably. But I did think this was the expected behavior. Perhaps it ought to throw an E_STRICT? On Fri, Jun 5,

Re: [PHP-DEV] Test for edge cases with __get and property access flags

2009-06-05 Thread Stan Vassilev
3. When the caller tries to retrieve $object->foo, and foo is a private/protected member the caller has no access to, instead of an error, __get is called. I'm not very sure the current behavior on item 3 is the best one (maybe error should be thrown regardless?), but freezing on eith

Re: [PHP-DEV] Test for edge cases with __get and property access flags

2009-06-04 Thread Alexey Zakhlestin
2009/6/4 Stan Vassilev > > 3. When the caller tries to retrieve $object->foo, and foo is a > private/protected member the caller has no access to, instead of an error, > __get is called. > > I'm not very sure the current behavior on item 3 is the best one (maybe > error should be thrown regardles