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

On Wed, Jun 21, 2000 at 07:14:56PM +0200, Sascha Schumann wrote: > > Bottom line: please don't do this. This is bad hacky behaviour. In fact, > > even stdClass is bad hacky behavour... I'd promote that warning to error > > and thus forced right usage of session objects, but that could be too > > bondage-and-discipline... > > We are currently discussing an easier method which simply > caches the class name between unserialization and > serialization, so that no extra dummy class needs to be > created. i'm for the class-on-demand creation. i don't think that this will cause any problems. is you include your classs code after session_start() you'll get a "cannot redeclare class-name" this way. (this would also be this 1st step into creating a class-on-demad loading mechanism) if we go with sascha's way (remembering the class-name somewhere) you will be able to create a new class but your sessionized object wouldn't be able to call the methods. tc > > - Sascha > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net -- Thies C. Arntzen "One Big-Mac, Small Fries and a Coke!" Digital Collections Phone +49 40 235350 Fax +49 40 23535180 Hammerbrookstr. 93 20097 Hamburg / Germany