Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47229 invoked from network); 29 Jul 2013 12:00:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jul 2013 12:00:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.174 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.217.174 mail-lb0-f174.google.com Received: from [209.85.217.174] ([209.85.217.174:46002] helo=mail-lb0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/51-34264-A5956F15 for ; Mon, 29 Jul 2013 08:00:27 -0400 Received: by mail-lb0-f174.google.com with SMTP id x10so4109443lbi.5 for ; Mon, 29 Jul 2013 05:00:24 -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=cky/kFu/pJN86XohAypGd1ExNQgtympj6b9n2gdDaUE=; b=GcuLQwuD3k+d8P/sbvSgyoGNkg6Ab/NIUISsvZqYAMDM3b3txYuH0qFesbpBkHakW3 ZUJFrlrCAFhaqmSdSFgJDNFmz1V81oovrMm2GG436gsWhwENra7vLX3/F9QypHzswT7p hms1XZ+jyWT9/10800DjkQLuGviOgLh3bEZGwWq31N+5WoDsnSIttbxOOgw30TfZyUKU 4BwdU04vQn+X8rtt7KrHZH05D9p4lH3W7NpU+Q1e9oUYxfX8fN57f1H2Xq8qFEZf14yd BHpciQxbFAguShZvDTEvJ98bWIhZnT1pGSJO57k4F9OhJofAIEXfQvUHusavnpF+388B mugA== MIME-Version: 1.0 X-Received: by 10.152.10.71 with SMTP id g7mr4093801lab.60.1375099223969; Mon, 29 Jul 2013 05:00:23 -0700 (PDT) Sender: mike.php.net@gmail.com Received: by 10.114.184.19 with HTTP; Mon, 29 Jul 2013 05:00:23 -0700 (PDT) In-Reply-To: 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: Mon, 29 Jul 2013 14:00:23 +0200 X-Google-Sender-Auth: lTXIcLoK6cFXGY9-5-z36PnAI7s Message-ID: To: Jakub Zelenka Cc: Stas Malyshev , Gustavo Lopes , =?UTF-8?Q?Johannes_Schl=C3=BCter?= , Nikita Popov , PHP internals list , "nikic@php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized From: mike@php.net (Michael Wallner) On 27 July 2013 15:58, Jakub Zelenka wrote: >> >> > 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. What's about unserialization? Where does the state come from when recursively calling serialize? -- Regards, Mike