Re: [RFC] [VOTE] __debugInfo()
| From: | Johannes Schlüter | Date: | Tue, 11 Feb 2014 20:52:47 +0000 |
| Subject: | Re: [RFC] [VOTE] __debugInfo() | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72472@lists.php.net to get a copy of this message | ||
On Tue, 2014-02-11 at 19:54 +0100, Crypto Compress wrote:
> > __ method names are reserved for internals. There is no BC break.
>
> Yes, there is however an expectation break but thats not the Point. May
> even be useful.
>
> Imagine a mock library:
>
> Usecase #1: end-user
> Sees only immediate useful data. No cluttered object graph. Very useful!
>
> Usecase #2: new maintainer
> Hunting bug in mock object. No way to var_dump object internals at all.
> Wait what?
This is still no BC break in PHP but probably bad usage. You can still
see "the truth" via reflection and by using a proper debugger (like
xdebug, I assume)
johannes