Re: [RFC] More Appropriate Date/Time Exceptions
| From: | Dan Ackroyd | Date: | Thu, 08 Dec 2022 14:11:42 +0000 |
| Subject: | Re: [RFC] More Appropriate Date/Time Exceptions | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119099@lists.php.net to get a copy of this message | ||
On Tue, 29 Nov 2022 at 17:41, Derick Rethans <derick@php.net> wrote:
>
> I have just published a new "More Appropriate Date/Time Exceptions" RFC
>
>
> Comments?
>
None of the 'Invalid serialization' errors tell the programmer who
reads them what is wrong with the data.
Unless the code was written in such a way that the data was in (and
was logged) in the callstack, that would be a bit frustrating as
someone might need to do quite a bit of work to find the data that was
triggering the problem.
Changing those to be specific error type, that included a method of
'getBadData' could make it easier to fix those issues.
cheers
Dan
Ack