Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112455 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 49820 invoked from network); 7 Dec 2020 15:20:10 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Dec 2020 15:20:10 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D4D321804CA for ; Mon, 7 Dec 2020 06:49:07 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from v-smtpout3.han.skanova.net (v-smtpout3.han.skanova.net [81.236.60.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 7 Dec 2020 06:49:06 -0800 (PST) Received: from [192.168.7.5] ([213.64.245.126]) by cmsmtp with ESMTPA id mHp2kKXbfMkHRmHp2kj4ZY; Mon, 07 Dec 2020 15:49:04 +0100 To: Nikita Popov References: Cc: PHP internals Message-ID: <283eb44a-d6f9-b91b-115e-cc95e9523c30@telia.com> Date: Mon, 7 Dec 2020 15:49:04 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-CMAE-Envelope: MS4wfM6Fq1DbKa/DnPxoHNSEPUxjxtRdK2U8eJVRmwEj/RP4ujAOiC7mno0xuHnVI32dXvDZ2w982brD4IIz6z6R+hyvt74LYz3YsObUJC4w9I1RsDotOiif RclUWRUQwMr8mweSeD0v5e9MRjfPNHzfcZKbMu6X8tLcKcY6+7TInhWvBoNePsHuVT/zPyr/S4oqnsTsRD8QPqXA5G3HlHMGwcAgEkkpLq93G0+2rU7g+Si1 Subject: Re: [RFC] Phasing out Serializable From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2020-12-07 kl. 15:11, skrev Nikita Popov: > Hi internals, > > Picking up a loose thread: > https://wiki.php.net/rfc/custom_object_serialization introduced a > replacement for Serializable in PHP 7.4, so it's time to think about > deprecating and removing the old mechanism: > > https://wiki.php.net/rfc/phase_out_serializable > > This RFC follows a rather conversative approach. In PHP 8.1 there will be a > deprecation warning if Serializable is implemented without also > implementing __serialize() and __unserialize(). In PHP 9.0, support for > Serializable is dropped internally, and only the interface retained. In PHP > 10.0 the interface is dropped as well. > > Regards, > Nikita Given that 10.0 lies maybe ten years in the future if we have a similar timeline like for 7.0 to 8.0. Is it then realistic to have such a long-term planning? For me it feels a bit more prudent to remove it completely in 9.0. Otherwise +1! r//Björn L