Re: [VOTE] New custom object serialization mechanism
| From: | Nikita Popov | Date: | Tue, 05 Mar 2019 12:35:25 +0000 |
| Subject: | Re: [VOTE] New custom object serialization mechanism | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104586@lists.php.net to get a copy of this message | ||
On Tue, Mar 5, 2019 at 1:18 PM Sebastian Bergmann <sebastian@php.net> wrote:
> Am 01.03.2019 um 16:08 schrieb Nikita Popov:
> > I have opened voting on
> https://wiki.php.net/rfc/custom_object_serialization.
> > The vote will be open until 2019-03-15.
>
> I voted "No" because this adds a third mechanism without a concrete plan
> to phase out the existing two mechanisms.
>
Good concern. How do people feel about deprecating Serializable in 7.4 and
removing in 8.0 (not as part of this RFC but a separate one)? The
deprecation warning would only be thrown if Serializable is implemented but
the class has no __serialize/__unserialize. The timeline would be a bit
aggressive in that we'd be introducing the replacement in the same release
as the deprecation, something I'd usually try to avoid.
Nikita