Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114631
MIME-Version: 1.0
References: <CAF+90c-7-ohb7-dqjN=jFguxTv_qegRNgZdEa4_vW-yK3sjvpA@mail.gmail.com>
In-Reply-To: <CAF+90c-7-ohb7-dqjN=jFguxTv_qegRNgZdEa4_vW-yK3sjvpA@mail.gmail.com>
Date: Thu, 27 May 2021 13:00:28 +0200
Message-ID: <CAO64rh5d=32CEbQ9L7duHoO-=mpCMhE8FcEQPO6UvaUpPCKbxA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006e637005c34dab4f"
Subject: Re: [PHP-DEV] Escape \0 in var_dump() output
From: harmsmitsdev@gmail.com (Harm Smits)

--0000000000006e637005c34dab4f
Content-Type: text/plain; charset="UTF-8"

Hey,

> whether var_dump() should be performing any escaping at all, and if yes

Well, since var_dump is essentially for debugging purposes, it makes sense
to escape certain characters. Like you mentioned, some IDEs do not
print/support
null bytes. Hence, I am all for it, as it simplifies debugging in that
scenario (which
is the main objective).

> how much we should be escaping. Just \0, both \0 and \ to avoid ambiguity,
or a larger set of control characters?

Probably a larger set of control characters as well. As mentioned before,
var_dump
is for *debugging*, if you can not get full debugging information, it will
only lead to
headaches and frustrations.

Regardless, I do believe we should provide some kind of 'setting' for this
in
php.ini (like precision for example) just so the user can decide what they
want to do.

--0000000000006e637005c34dab4f--