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

On Wed, 21 Jun 2000, Sascha Schumann wrote: > Then you have misinterpreted my initial message which clearly > said that adding a new member to the object is only one way of > many to implement the approach. > > I also don't see why it was necessary to commit a change > while we have not reached a consensus yet. > > We agree on: > > - PHP needs to preserve the name of the class of a > serialized object, even if the class definition is not > available during deserialization. > > We do not agree on: > > - PHP must stop script execution and output a misleading > error message, if the script defines a class and if this > class was absent on one or more object instantiations. I have to say I like Sascha's approach better. It seems logically and practically simpler to store the name of the class in an internal hash and then check that upon serialization. -Andrei * We reason deeply, when we forcibly feel. *