Re: [RFC] [VOTE] __debugInfo()

From: Date: Tue, 11 Feb 2014 22:10:27 +0000
Subject: Re: [RFC] [VOTE] __debugInfo()
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.internals 
Request: Send a blank email to internals+get-72483@lists.php.net to get a copy of this message 
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
<cryptocompress@googlemail.com> 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

Thread (55 messages)

« previous php.internals (#72483) next »