Re: [PHP4BETA] class serialize/unserialize implementation.

At 01:23 PM 9/15/99 +0200, Thies C. Arntzen wrote:

hi - the problem i see is that you *NEED* to have the class your unserializing defined *BEFORE* you can unserialize i't instance - even though it seems logical i don't know if people will get bitten by this! the benefit is that you get a fully working instance fron unserialize instead of the "dumb" array you got in PHP3 also 'cause i had to put the class-name into the serialized data. it probably won't "unserialize" when using php3. (people that store serialized data in a file/db may get bitten by this!). the next time we come up with a new format (i hope never!) we need to make sure that we have a version number and a magic-cookie - so that we can mark incompatible changes! comments?

Only comment I have is the obvious. Serializing the class name is definitely the way to do it. People have to be disciplined enough to have the class defined before the call to unserialize. Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/