Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103829 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64514 invoked from network); 24 Jan 2019 17:40:43 -0000 Received: from unknown (HELO scarlet.netpirates.net) (188.94.27.5) by pb1.pair.com with SMTP; 24 Jan 2019 17:40:43 -0000 Received: from p579cd2c4.dip0.t-ipconnect.de ([87.156.210.196] 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 1gmfqG-0005fu-Ja for internals@lists.php.net; Thu, 24 Jan 2019 15:18:52 +0100 To: internals@lists.php.net References: Message-ID: Date: Thu, 24 Jan 2019 15:18:51 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] New custom object serialization mechanism From: sebastian@php.net (Sebastian Bergmann) Am 24.01.2019 um 15:09 schrieb Marco Pivetta: > Not really fussed about having another implicit interface for serialization > (via magic methods). I second that emotion.