Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72300 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86921 invoked from network); 5 Feb 2014 22:11:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2014 22:11:18 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.171 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.171 mail-lb0-f171.google.com Received: from [209.85.217.171] ([209.85.217.171:43748] helo=mail-lb0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 07/99-38005-407B2F25 for ; Wed, 05 Feb 2014 17:11:17 -0500 Received: by mail-lb0-f171.google.com with SMTP id c11so830313lbj.2 for ; Wed, 05 Feb 2014 14:11:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=MmAju8PpZM3AGx/RcKaS2RWcagYkk7xJ7s6R0Tm8QPc=; b=0Ok4qo/2ocz6qg7PtKACiorZwGXMXpFB2aKh1j0Q5gEmkgk6Lbr5/gHyV2BJE5xpM0 H6v5C4CIXYCm7ZEwaQRKUObfHK3FHf8lbf0P9uKumUY2Mx+QEIlc9e/q6Zr0rY4s3C+d xISfHcsXJHq86ktIeNc30X3N63hxaIJTcL8GPqcFl9E0BhRgJzqgcWrB0oZB0PQ1ZAgd kwm8PKaGmicty0UWO+tdHlKeyIHSNhdTf4dhpOPXC6P7VNlbJN1t06Dl9JOme87bysx9 XdU6IrQrj4R0yuZBZUT8pLdxdjj2vjgKQmv28fMKp51cLDS04uoO3tYv0SQGD421re5T U7Mw== X-Received: by 10.112.131.100 with SMTP id ol4mr2553041lbb.38.1391638272451; Wed, 05 Feb 2014 14:11:12 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Wed, 5 Feb 2014 14:10:32 -0800 (PST) In-Reply-To: <52F292CB.7040706@gmail.com> References: <2D2D996C-9455-4DD1-9669-90AFAF591E32@strojny.net> <52F292CB.7040706@gmail.com> Date: Thu, 6 Feb 2014 07:10:32 +0900 X-Google-Sender-Auth: FIN5hzXqOGj7Qv9-s8C7If6L4Lc Message-ID: To: Rowan Collins Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b3441b4e2aa0b04f1b0085a Subject: Re: [PHP-DEV] Re: __set_state (Was: Re: [PHP-DEV] [RFC] __debug_info()) From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b3441b4e2aa0b04f1b0085a Content-Type: text/plain; charset=UTF-8 Hi Rowan, On Thu, Feb 6, 2014 at 4:36 AM, Rowan Collins wrote: > > 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? My bad. var_export() does not specify method, so it can alias safely. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b3441b4e2aa0b04f1b0085a--