Re: RFC [Discussion]: Improve unserialize() error handling
| From: | Tim Düsterhus | Date: | Sat, 10 Sep 2022 11:46:05 +0000 |
| Subject: | Re: RFC [Discussion]: Improve unserialize() error handling | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-118595@lists.php.net to get a copy of this message | ||
Hi
On 9/10/22 13:03, Paul Dragoonis wrote:
Do give it more thought regarding the callbacks what Nikolas said, sleep on it.Are you referring to 'unserialize_callback_func' or to the unserialize handlers (i.e. __wakeup, __unserialize, Serializable::unserialize)? If the former, I am currently waiting for an explanation of the use cases from someone who uses it, to be able to make an educated decision.
Not saying it matters, but also double check how error handling MAY differ when in a Class::_unserialize() context. Maybe it doesn't diff, I haven't checked in a while, but food for thought.I'm afraid, this is a little vague. What possible difference (and difference to *what*) do you have in mind?
In any case, good cleanup initiative. Best regardsTim Düsterhus