Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68329 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23066 invoked from network); 27 Jul 2013 13:58:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2013 13:58:06 -0000 Authentication-Results: pb1.pair.com smtp.mail=jakub.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=jakub.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.171 as permitted sender) X-PHP-List-Original-Sender: jakub.php@gmail.com X-Host-Fingerprint: 209.85.216.171 mail-qc0-f171.google.com Received: from [209.85.216.171] ([209.85.216.171:59239] helo=mail-qc0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/91-02804-BE1D3F15 for ; Sat, 27 Jul 2013 09:58:04 -0400 Received: by mail-qc0-f171.google.com with SMTP id n1so2083527qcw.30 for ; Sat, 27 Jul 2013 06:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EmvhA3FKLFPQlxDM3NnpLUgIjpNjuCalZbjO3hE2F9Y=; b=G16X/gM366SVhdN7gzQbuipnBPr+sv8F7WZ9pkmNqI92+TTJBsBK+RneRNZIz/NTHo SkrR26NwNEA/7HXe7rULRMIay3PJYN8zNLhkK2EfsxBEPTpWSDIA/Gl3ZF01QUjthIQZ YLBlGYkvBa/nRCG4GM9uTJr967mfQVp9Hx3pcKOCIxIw1bRLhVvS6W3BwIODfyiswdKp DfxSx23I3OY3HcqTnxuMV6k0sbxTt1OuC7q/FOSCuqUYd9lOQwg9+0rhrQtJwp1dlh4L MtIcJVjtDVkv93fHzdFpXXu1ZwUYFfzUzn2IHzmT+B0nCEi+7eDX8tlEJcuCjb+Z7deX jLWQ== MIME-Version: 1.0 X-Received: by 10.224.138.8 with SMTP id y8mr13674188qat.27.1374933481011; Sat, 27 Jul 2013 06:58:01 -0700 (PDT) Sender: jakub.php@gmail.com Received: by 10.224.178.69 with HTTP; Sat, 27 Jul 2013 06:58:00 -0700 (PDT) In-Reply-To: <51F2E53E.1040707@sugarcrm.com> References: <51F177E7.3020103@sugarcrm.com> <51F182D2.7030007@sugarcrm.com> <1374793278.3605.1436.camel@guybrush> <1374833069.3605.2106.camel@guybrush> <1374838415.3605.2211.camel@guybrush> <1374847163.3605.2377.camel@guybrush> <51F2E393.5090206@nebm.ist.utl.pt> <51F2E53E.1040707@sugarcrm.com> Date: Sat, 27 Jul 2013 14:58:00 +0100 X-Google-Sender-Auth: ap2Xj0K3_Ui-xGdQc7opKHdejVU Message-ID: To: Stas Malyshev Cc: Gustavo Lopes , =?ISO-8859-1?Q?Johannes_Schl=FCter?= , Nikita Popov , PHP internals list , "nikic@php.net" Content-Type: multipart/alternative; boundary=001a11c25262b9bd3204e27ea549 Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized From: bukka@php.net (Jakub Zelenka) --001a11c25262b9bd3204e27ea549 Content-Type: text/plain; charset=ISO-8859-1 > > > Alternatively, could the problem perhaps be mitigated by making > > available some utility functions for serializing native types? > > We could definitely make some parts of serializer API-accessible, or > even make serializer as a whole to be more API-friendly, I think it'd be > a nice idea if making implementing Serializable would be made easy by > reusing serializer code and combining pieces. If now it's hard making it > easier definitely a good idea, much better than creating one more API IMHO. > I was thinking about that and it could actually be done in a way that would resolve the problem. I have just created RFC that specify the API. https://wiki.php.net/rfc/internal_serialize_api It's backward compatible and allow portable object generation in more abstract way. It's just draft so I am happy to do changes. Jakub --001a11c25262b9bd3204e27ea549--