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

AZ>> No, it'd be pretty easy. All PHP will do is register another class AZ>> similar to stdClass. This new class, let's call it, stsSessionClass will AZ>> implement function overloading so that any attempt to call its methods AZ>> will result in an error message. Then all we have to do to change AZ>> deserializers is to substitute 'stdSessionClass' instead of AZ>> 'stdClass'. WHY????? You keep avoiding answering my point. Why user needs to see fake objects at all? You can call it object of stdSessionClass or stdFooBarClass, you can catch or not catch the methods - but you don't need to do anything of it if you just don't put this object in userspace. And here I'm trying for half a day to get a single reason why that object of undefined class has to be seen by user. Just one simple reason. Why? -- Stanislav Malyshev stas@zend.com +972-3-6139665