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

> RL>> Is there anything stopping us from optionally including the class > RL>> definition in the serialization? Wouldn't that make all this go away? > > Yes there is. > 1. THis is plain wrong. Class should be defined by user in PHP, not > carried along in sessions. > 2. How exactly you are going to carry class members, methods, etc., > etc? And why exactly do you need it? > 3. And now the fun thing. Imagine derived class. Now you've got to bring > along all the class tree up to the root with you. Fun, fun, fun. But since the class data is really not much use without the class definition, I don't see the point in separating them. And it wouldn't be that much additional data. It's not like this stuff is getting passes back and forth across the wire. It's all local, so I don't see the size as being any sort of issue. Although for the shared memory backend I guess it is an issue. -Rasmus