Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72287 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62170 invoked from network); 5 Feb 2014 19:36:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2014 19:36:54 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.175 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.175 mail-we0-f175.google.com Received: from [74.125.82.175] ([74.125.82.175:50692] helo=mail-we0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/74-38005-0D292F25 for ; Wed, 05 Feb 2014 14:36:53 -0500 Received: by mail-we0-f175.google.com with SMTP id q59so632594wes.6 for ; Wed, 05 Feb 2014 11:36:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=p1Sf3CwjgLG6dJp8Gtetd5zLT6SRUV0S13nDITcXTbQ=; b=JJEXSykfooDPWs6dqgT9SjWAcZs8VqP6XWb1RzedWzTX5tGe+IrVOsoOW6CNZA3f+V kysvh5ZARaINuHeCEobZmWrYy8qsLwzW4JQSegcZER+Atp17EgYvt7xjekNW4XxAm6+8 bQ12Yl6Jst9aeeqS1naMDOIL9UDyd9ncypV62ZEaX/0RqIQ8T1SPIrWqE6NNoXeICx57 bvokxUAQZyp2EdT/CxKuGl8lPLzPRCgyXLRr4xX3lM3V45BlX7ITmExS97QQwslqvXYb maJD5/057ov2s+lI9FNwNvCXdAIscZ94aGnQpS7SzsvQFl4oKfLr0xRSsvD0qlRFOTnk MD0A== X-Received: by 10.180.12.43 with SMTP id v11mr17956648wib.33.1391629005645; Wed, 05 Feb 2014 11:36:45 -0800 (PST) Received: from [192.168.0.138] ([62.189.198.114]) by mx.google.com with ESMTPSA id h9sm47584629wjz.16.2014.02.05.11.36.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Feb 2014 11:36:44 -0800 (PST) Message-ID: <52F292CB.7040706@gmail.com> Date: Wed, 05 Feb 2014 19:36:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <2D2D996C-9455-4DD1-9669-90AFAF591E32@strojny.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: __set_state (Was: Re: [PHP-DEV] [RFC] __debug_info()) From: rowan.collins@gmail.com (Rowan Collins) Yasuo Ohgaki wrote (on 23/01/2014): >> You seem to misunderstand what __set_state() is for. It is for reliably >> >representing a value so that you can "include" it's contents with >> >var_export(). If 5.6 would suddenly start spitting out >> >Class::__setState() instead of Classs::__set_state() then older PHP >> >versions can't parse/include that outputted data anymore. >> > > I have to check code, but don't we have options for this? > We may use __set_state() for var_export and still have alias as __setState. > People are using var_export exchange PHP data, so we should be careful. > I agree this. Is there a use case for __set_state *other than* var_export()? In other words, if not var_export(), what code would ever include a reference to __setState() if it were added as an alias? -- Rowan Collins [IMSoP]