Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69971
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEKnhAH3rF22zJ=9=XGR77Rqn0sGjW3vuX-5KiRhU5aX7g-Zsg@mail.gmail.com>
References: <CAEKnhAH3rF22zJ=9=XGR77Rqn0sGjW3vuX-5KiRhU5aX7g-Zsg@mail.gmail.com>
Date: Wed, 30 Oct 2013 22:46:48 +0100
Message-ID: <CAF+90c_7skiGLHpbwTRL+=O1ebmx3TpA_Km6XYdNy=GSKieHHA@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: "nikic@php.net" <nikic@php.net>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1d8d22db0ee04e9fc4503
Subject: Re: GMP serialization
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c1d8d22db0ee04e9fc4503
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 30, 2013 at 10:37 PM, Jakub Zelenka <bukka@php.net> wrote:

> Hi,
>
> There is a new patch that is changing serialization in GMP:
>
>
> http://git.php.net/?p=php-src.git;a=commitdiff;h=4218e89f8df4ca3897e3aad595e0c2c9cf4c3aca
>
> It fixes the bug but it also introduces BC break for serialized string
> (custom serialization replaced the std object serialization). The problem
> is that there can be users (one big user is WordPress) that saves the
> serialized into DB which can lead to the difficulties when updating PHP
> version.
>

As already pointed out on the php-cvs mailing list, this is not a backwards
compatibility break because it only changes implementation details of a
feature introduced in master (PHP 5.6). GMP numbers were never serializable
in any released version of PHP. Ability to serialize was added as part of
https://wiki.php.net/rfc/operator_overloading_gmp.

Nikita

--001a11c1d8d22db0ee04e9fc4503--