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

Quoting Sascha Schumann <sascha@schumann.cx>: > With your proposal, all areas would have to include all class > definitions of all areas. I don't think that is sensible. I agree that you should be able to use a single session and let users move between pieces of the site that use different code, without including your entire class hierarchy in each page. It lets you do a much cleaner, more elegant design. Another, rather different solution to the problem would be for pages to be able to specify what pieces of session data they wanted. That way, page1.php could use classes foo and bar, and ask only for the variables that were instances of foo and bar, while page2.php could use class qux, and only ask for variables that were instances of qux. Related to this: could the unserialization code be smart enough to _know_ when an object originally didn't have a type (ie, $foo = (object)array(), or some such), and to not throw an error in those cases? I know I could just use a hash, and I might do that, but it seems reasonable to allow that usage. -chuck -- I won't die for Fernando Poo