Re: [RFC] [VOTE] __debugInfo()
| From: | Yasuo Ohgaki | Date: | Wed, 05 Feb 2014 00:24:15 +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-72226@lists.php.net to get a copy of this message | ||
Hi all,
On Tue, Feb 4, 2014 at 10:16 PM, Tjerk Meesters <tjerk.meesters@gmail.com>wrote:
> > some more questions:
> >
> > 1. Can this hook be bypassed or disabled (global/temporary)?
> > e.g. real_var_dump(), ini setting, some other flag?
> >
> > 2. What will be affected by this hook beside "var_dump"?
> > e.g. xdebug output, var_export, ...
> >
> > 3. How would this behave (segfault?):
> > public function __debugInfo() { var_dump($this); return []; }
> >
>
> Yeah, there doesn't seem to be any recursion protection, just like:
>
> public function __toString() { return (string)$this; }
It is the same as
function f() {
f();
}
User may do that, but it's a documentation problem.
It would be not obvious as function call recursion.
and must be documented, probably.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net