Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112948
MIME-Version: 1.0
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>
In-Reply-To: <18afe2ed-0802-8f76-b094-64d5ff8cf37f@gmail.com>
Date: Wed, 20 Jan 2021 17:19:21 -0600
Message-ID: <CAESVnVowJSrDpgWHVjFtdpeDi3hLx-=WPLC6C0D+10EJnR2j-g@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000003eaff05b95d305f"
Subject: Re: [PHP-DEV] Proposal: short_var_export($value, bool $return=false,
 int $flags=0)
From: pollita@php.net (Sara Golemon)

--00000000000003eaff05b95d305f
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 20, 2021 at 3:44 PM Rowan Tommins <rowan.collins@gmail.com>
wrote:

> On 20/01/2021 20:21, Claude Pache wrote:
> > Or `short_var_export()` could just reuse the existing `__debugInfo()`
> > magic method (which is already used by both `var_dump()` and
> > `print_r`, but not by `var_export()`). The programmer would just need
> > to make sure that `__set_state()` can consume the array produced by
> > `__debugInfo()`.
>
>
> This is an interesting question to explore, but I don't follow how this
> relates to my previous e-mail. I'm saying that having print_r, var_dump,
> var_export, and var_export_short (or whatever we call it) all in one
> language is more confusing than helpful.
>
>
IMO print_r/var_dump should be kept out of this discussion. Those are human
readable outputs for human consumption.   var_export() is about a machine
readable output for recreating initial state within a runtime.  The
requirements presented are wholly different.

-Sara

--00000000000003eaff05b95d305f--