Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68319
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.54 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <1374833069.3605.2106.camel@guybrush>
References: <CAEKnhAGd=Opdsc88Z0LD8e_fwtoUQe2wpZCYh8VtiwFLOA09NQ@mail.gmail.com>
	<51F177E7.3020103@sugarcrm.com>
	<CAF+90c89OsTJJ6x5MjtmV-e9uEcuL38qnaU63Ep5eNrj0C1HKw@mail.gmail.com>
	<51F182D2.7030007@sugarcrm.com>
	<CAEKnhAFT4VqATgkbbRMAiYb46FKDt--nLacySia6kXo9FxEBog@mail.gmail.com>
	<1374793278.3605.1436.camel@guybrush>
	<CAEKnhAE1vHEx9CexODpgamhew2qCj2r9YU_Ytv+6v=GYOafJQg@mail.gmail.com>
	<1374833069.3605.2106.camel@guybrush>
Date: Fri, 26 Jul 2013 11:58:39 +0100
Message-ID: <CAEKnhAGbbBhmeyZcB28rsfpx1ZxbaSuHiFNzWs5BVZHqNifd=w@mail.gmail.com>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, Nikita Popov <nikita.ppv@gmail.com>, 
	PHP internals list <internals@lists.php.net>, "nikic@php.net" <nikic@php.net>
Content-Type: multipart/alternative; boundary=089e0149cdb474a43a04e2680668
Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized
From: bukka@php.net (Jakub Zelenka)

--089e0149cdb474a43a04e2680668
Content-Type: text/plain; charset=ISO-8859-1

>
> So rather change the engine, which affects way more things and add yet
> another serialisation hook making it even more confusing what to use?
> >
>

Yes I agree that the new hook is confusing. I think that what Gustavo said
would be actually much better. Having some flag that would say what is
the purpose of retrieving properties could be very useful. It's not just
serialization
but also casting object to array. There can be even more use cases
in the future. On top of it the hooks like get_gc and get_debug_info
could be part of it. But I would rather discuss this leter
when I send a patch.


>
> You're solution also depends on an API break and also changes the way
> the objects behave during serialization/unserialization.
>
>
Not sure what you mean by API break and changing the way the objects
behave? When you look to this pach
https://github.com/bukka/php-src/compare/date_serialize there shouldn't be
any difference in object behaviour. Or am I wrong?

By BC I meant the resulted string that you get after using serialize
function. If you use Serializable you get something that is prefixed by C:
. But if you have object, the prefix is O: . Please see this
http://3v4l.org/Sd8aT .

Jakub

--089e0149cdb474a43a04e2680668--