Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104585 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77450 invoked from network); 5 Mar 2019 15:30:29 -0000 Received: from unknown (HELO scarlet.netpirates.net) (188.94.27.5) by pb1.pair.com with SMTP; 5 Mar 2019 15:30:29 -0000 Received: from pd9e63068.dip0.t-ipconnect.de ([217.230.48.104] helo=[192.168.178.42]) by scarlet.netpirates.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h191p-0001e8-Fc for internals@lists.php.net; Tue, 05 Mar 2019 13:18:37 +0100 To: internals@lists.php.net References: Message-ID: Date: Tue, 5 Mar 2019 13:18:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] New custom object serialization mechanism From: sebastian@php.net (Sebastian Bergmann) 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.