Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98242
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.171 as permitted sender)
MIME-Version: 1.0
Date: Tue, 7 Feb 2017 12:25:53 +0100
Message-ID: <CAOv67gvAbo4fCuCjoFMx+fLbrbLdv9T1ouUpotAo--kTE-3Leg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1147e4aecf110a0547ef0216
Subject: [PHP-DEV] Change debug_zval_dump to return the dump unaffected by __debugInfo?
From: netmo.php@gmail.com (Wes)

--001a1147e4aecf110a0547ef0216
Content-Type: text/plain; charset=UTF-8

Hello Internals.
Today I'm fighting with some code that I think uses var_dump() and output
buffering to create the output for __debugInfo... or something like that -
I'm not really interested into finding the cause :P

Anyway, It's not the first time I find myself paralyzed by a slightly
broken __debugInfo, including with code that I've written myself (I hate
that guy).

One big problem is that once you have overriden it in a super class, you
can't revert __debugInfo back to the php's implementation easily; the
following doesn't actually do the same thing:

function __debugInfo(){ return (array)$this; }

But even better, it would be nice if debug_zval_dump() always returned the
debug information unaffected by custom user-defined __debugInfo. This is by
the way what HHVM does: https://3v4l.org/OoJkC

Thoughts?

--001a1147e4aecf110a0547ef0216--