Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72483 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48647 invoked from network); 11 Feb 2014 22:10:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2014 22:10:52 -0000 Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.212.178 as permitted sender) X-PHP-List-Original-Sender: cryptocompress@googlemail.com X-Host-Fingerprint: 209.85.212.178 mail-wi0-f178.google.com Received: from [209.85.212.178] ([209.85.212.178:48909] helo=mail-wi0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F6/62-62230-AEF9AF25 for ; Tue, 11 Feb 2014 17:10:52 -0500 Received: by mail-wi0-f178.google.com with SMTP id cc10so5494608wib.17 for ; Tue, 11 Feb 2014 14:10:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7yQXSKJlZ6JBKuEXrpSE9g9V7hQDsRqxWdSY+SJwoB0=; b=yhg1Ljggq6Sq0YsQsikzaypxakLzF64Wt7Ag68ZimYOmq7xFRXAKVDzIkzYsZ+uTSP Tt/9sZIr1B0FuD45pSgpg/oelANsx9ZCKg2t4zQDZtjblnIHvswRVXJyC18GWbn602Qo be2aixDRWRr/A3DfpV0ZogajiCqEtfBojTkFz7DoQQkaTZeA+Phx64QAD4NKR/o/mO1f T1xccK08xto8EKlUSpcfWUjDM8XpRJteJEGyGRCIUWdjb5OLdROVjx5GSEoQ4+Lvppru w5NkxNp13MiTNd9TwOVvgoV0BC4Bt9jXjPfjDJOnEFcW9VMyRU2l+iL25kBkzPR/6409 4f4Q== X-Received: by 10.180.164.73 with SMTP id yo9mr205241wib.29.1392156646945; Tue, 11 Feb 2014 14:10:46 -0800 (PST) Received: from [192.168.1.115] (mnch-5d8774be.pool.mediaWays.net. [93.135.116.190]) by mx.google.com with ESMTPSA id pm2sm1076158wic.0.2014.02.11.14.10.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Feb 2014 14:10:45 -0800 (PST) Message-ID: <52FA9FD3.6000008@googlemail.com> Date: Tue, 11 Feb 2014 23:10:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: Derick Rethans , PHP Developers Mailing List References: <52F00437.7010903@googlemail.com> <52FA71FE.8060808@googlemail.com> <1392151967.3990.11.camel@guybrush> <52FA90B3.5040205@googlemail.com> <1392153156.3990.13.camel@guybrush> <52FA99C4.5080006@googlemail.com> <1392155891.3990.15.camel@guybrush> In-Reply-To: <1392155891.3990.15.camel@guybrush> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [VOTE] __debugInfo() From: cryptocompress@googlemail.com (Crypto Compress) Am 11.02.2014 22:58, schrieb Johannes Schlüter: > On Tue, 2014-02-11 at 22:44 +0100, Crypto Compress wrote: >> Sorry! We talk at cross purposes: >> - reflection is not changed >> - (array)$this is possible >> >> This is currently not needed nor related to var_dump(). This RFC changes >> var_dump/print_r output without a bypass option. Hacks are needed to get >> current behavior back. Indeed it may be possible to replace >> var_dump/print_r with something. This discussion is about this issue. > Yes that is the purpose of this RFC and that voters have to decide > about: evaluate risk of abuse vs. making unreadable results usable. > > johannes > > No, it's not about risk of abuse. There can be *only* abuse! This hook is only intended to hide debug information. If you don't want to hide info, you don't need this hook. Debug info is *important*! Do not hide it without a option to bypass! Why not make it an enhancement to poor man's debugger and add a proper/easy/fast bypass option in this RFC? Am 05.02.2014 21:54, schrieb Sara Golemon: > On Wed, Feb 5, 2014 at 12:11 PM, Crypto Compress > wrote: >> It's not easy nor fast to change output of a whole object graph. >> > Oh, I see what you were getting at now. Yeah, that would be onerous > if you found yourself in that position. Might be a good idea to do a > followup RFC to introduce an INI setting. I'm not keen on adding a > new method, that kind of misses the point of the original hook. > > -Sara