Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112952
Date: Thu, 21 Jan 2021 09:03:05 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAESVnVowJSrDpgWHVjFtdpeDi3hLx-=WPLC6C0D+10EJnR2j-g@mail.gmail.com>
References: <DM6PR07MB66189CC60F94349200D0D02BF9A40@DM6PR07MB6618.namprd07.prod.outlook.com> <22e7ebcf-3f98-ff74-8d84-d2b50cda44b7@gmail.com> <1DF0F205-30A4-4FA3-8A58-703BAC6AD732@gmail.com> <18afe2ed-0802-8f76-b094-64d5ff8cf37f@gmail.com> <CAESVnVowJSrDpgWHVjFtdpeDi3hLx-=WPLC6C0D+10EJnR2j-g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----J5OEMJ3CONUOXDEW3P92L185W3PHVL"
Content-Transfer-Encoding: 7bit
CC: PHP internals <internals@lists.php.net>
Message-ID: <507F150C-A48D-4854-BC0B-4FE0B8822260@gmail.com>
Subject: Re: [PHP-DEV] Proposal: short_var_export($value, bool $return=false, int $flags=0)
From: rowan.collins@gmail.com (Rowan Tommins)

------J5OEMJ3CONUOXDEW3P92L185W3PHVL
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 20 January 2021 23:19:21 GMT, Sara Golemon <pollita@php=2Enet> wrote:
>IMO print_r/var_dump should be kept out of this discussion=2E Those are
>human
>readable outputs for human consumption=2E   var_export() is about a
>machine
>readable output for recreating initial state within a runtime=2E  The
>requirements presented are wholly different=2E


In that case, why are we spending so much time discussing how to make it l=
ook nicer for human consumption?

Of the changes proposed, I think only the leading backslash on class names=
 actually makes a difference to machine readability, and that could probabl=
y just be changed and documented as fixing the existing functionality=2E

What are the requirements of var_dump that *couldn't* be merged with var_e=
xport?

Regards,
--=20
Rowan Tommins
[IMSoP]
------J5OEMJ3CONUOXDEW3P92L185W3PHVL--