Re: PHP 4.0 Bug #5152: Object passed in a session generateserrors when member functions are called

On Fri, 23 Jun 2000, Stanislav Malyshev wrote: > SS>> > Please don't do it only this way. I feel like I'm preaching to the > SS>> > choir, > SS>> > but please think again: why at all you need to put this object in > SS>> > user-visible space? > SS>> > SS>> I've answered that question before. > > Sorry, must have missed it. Could you shortly repeat? > > SS>> We can overwrite handle_property_get and handle_property_set, > SS>> so that users cannot access properties. This would yield an > SS>> appropiate error description as well. > > OK, so you insist on having object that noone could touch? This is actually a good solution. On on hand, it essentially doesn't break any OO rule - you can't touch or use the object in any way. On the other - it prevents cases in which one programmer (possibly from a different department) adds a new class, that she uses throughout her session code, but isn't used by the session code of someone else, would suddenly break that other person's code. I'm in favour of it. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/