Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103824 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38620 invoked from network); 24 Jan 2019 16:37:07 -0000 Received: from unknown (HELO shout02.mail.de) (62.201.172.25) by pb1.pair.com with SMTP; 24 Jan 2019 16:37:07 -0000 Received: from postfix01.mail.de (postfix02.bt.mail.de [10.0.121.126]) by shout02.mail.de (Postfix) with ESMTP id 1FCDDC01FD; Thu, 24 Jan 2019 14:15:15 +0100 (CET) Received: from smtp02.mail.de (smtp02.bt.mail.de [10.0.121.212]) by postfix01.mail.de (Postfix) with ESMTP id 0767DA00B5; Thu, 24 Jan 2019 14:15:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.de; s=mailde201610; t=1548335715; bh=buBfI0pS6vMaavK3ld0gsgoAgTB028eO2vGnwD9DXOw=; h=From:To:Cc:Subject:Date:From; b=g8Ap9De2N8b1+HKN+3orsoac1QoTqJVWnxx8ILN7qL+oaQ2rYDg2X8H29RAqgAA1z BE2rIBNVua4ksGRgk5NhVWHe1DPacX8Zw9iREN1N57QK0XLsY+9blBXWXfoX2CHVfx 9T6AIFNp08Ik506eiBSq7tLIfRLfsPZj9ZXNWQFM= Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp02.mail.de (Postfix) with ESMTPSA id CD9051000DB; Thu, 24 Jan 2019 14:15:14 +0100 (CET) To: nikita.ppv@gmail.com Cc: internals@lists.php.net X-Priority: 3 Date: Thu, 24 Jan 2019 14:15:14 +0100 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline MIME-Version: 1.0 Message-ID: <20190124131514.CD9051000DB@smtp02.mail.de> X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate: clean X-purgate-size: 1226 X-purgate-ID: 154282::1548335714-00001E9E-DEEFA41A/0/0 Subject: Re: [PHP-DEV] [RFC] New custom object serialization mechanism From: naitsirch@e.mail.de On Thu, Jan 24, 2019 at 13:27 Nikita Popov =0Awrot= e:=0A=0A> Hi internals,=0A> =0A> I'd like to propose a new custom object= serialization mechanism intended to=0A> replace the broken Serializable= interface:=0A> =0A> https://wiki.php.net/rfc/custom_object_serializatio= n=0A> =0A> This was already previously discussed in https://externals.io= /message/98834,=0A> this just brings it into RFC form. The latest motiva= tion for this is=0A> https://bugs.php.net/bug.php?id=3D77302, a compatib= ility issue in 7.3=0A> affecting Symfony, caused by Serializable. We can= 't fix Serializable, but=0A> we can at least make sure that a working al= ternative exists.=0A> =0A> Regards,=0A> Nikita=0A=0AHi.=0A=0AWhat happen= s if both `__serialize()` and `__wakeup()` are implemented?=0A=0AAnd ano= ther idea for the naming: Maybe one could use `__normalize()` and `__den= ormalize()`. Because the methods do not serialize themself, like the nor= malizer in the Symfony serializer component. =0A=0ABest regards=0A------= ------------------------------------------------------------------------= -------------------=0AFreeMail powered by mail.de - MEHR SICHERHEIT, SER= IOSIT=C3=84T UND KOMFORT