Re: PHP 4.0 Bug #5152: Object passed in a session generates errors when member functions are called
| From: | Sascha Schumann | Date: | Wed, 21 Jun 2000 18:49:33 +0000 |
| Subject: | Re: PHP 4.0 Bug #5152: Object passed in a session generates errors when member functions are called | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-21929@lists.php.net to get a copy of this message | ||
> i really don't like a "_super_secret_whatsoever" slot that
> would show up on every var_dump() and would generally be
> visible in "userland". that's why i like the empty class far
> better.
Then you have misinterpreted my initial message which clearly
said that adding a new member to the object is only one way of
many to implement the approach.
I also don't see why it was necessary to commit a change
while we have not reached a consensus yet.
We agree on:
- PHP needs to preserve the name of the class of a
serialized object, even if the class definition is not
available during deserialization.
We do not agree on:
- PHP must stop script execution and output a misleading
error message, if the script defines a class and if this
class was absent on one or more object instantiations.
- Sascha