note 57621 modified in function.serialize by aidan
| From: | aidan@php.net | Date: | Sun, 09 Oct 2005 08:29:16 +0000 |
| Subject: | note 57621 modified in function.serialize by aidan | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-96717@lists.php.net to get a copy of this message | ||
[Editor's note: This has been fixed. Protected and private members were serialized with a
leading \0 (zero byte). Bug report here, http://bugs.php.net/29865 - aidan@php.net]
Be careful trying to serialize objects containing private or protected data members. It appears that
the serialization process includes characters in the result string to indicate the visibility of
each member, but the characters used to denote protected or private data are outside the normal
character set and can cause problems as you pass them through applications. I haven't found the
culprit in my particular case, so I can't say that this is a bug in PHP, but it certainly is
causing me some annoyance in my particular situation.
--was--
Be careful trying to serialize objects containing private or protected data members. It appears that
the serialization process includes characters in the result string to indicate the visibility of
each member, but the characters used to denote protected or private data are outside the normal
character set and can cause problems as you pass them through applications. I haven't found the
culprit in my particular case, so I can't say that this is a bug in PHP, but it certainly is
causing me some annoyance in my particular situation.
http://php.net/manual/en/function.serialize.php