Re: [RFC] [VOTE] __debugInfo()

From: Date: Tue, 11 Feb 2014 21:44:36 +0000
Subject: Re: [RFC] [VOTE] __debugInfo()
References: 1 2 3 4 5 6 7 8  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
Am 11.02.2014 22:12, schrieb Johannes Schlüter:

On Tue, 2014-02-11 at 22:05 +0100, Crypto Compress wrote:

You can still see "the truth" via reflection and by using a proper debugger (like xdebug, I assume)


Reflection is mentioned in RFC. Sadly it does not solve the problem.
Replaced output is *not* bypassable without external tools
(xdebug/phpdbg). If i'am wrong correct me.

ReflectionObject provides access to an object and its properties. This
is not going to change in case this is accepted. It will be extended toe
able to *also* provide this debug info, this doesn't affect
ReflectionObject::getProperty() etc., though.

johannes




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.

Thread (55 messages)

« previous php.internals (#72479) next »