Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109453
MIME-Version: 1.0
References: <CAL+t6cFeiGzLbfaQB0o2JKSx1OdfYYbY+k6QTG0V3H344XbCEA@mail.gmail.com>
 <CAG9XoMTHn6-Cu47w5PdFb4oYFtRYQahB72ZgNxVsEYWdjyTv8g@mail.gmail.com> <CAESVnVoCLJUosHkvbd7xV-a+4CDB7CpCMp+Az=dhVCAqS_63mw@mail.gmail.com>
In-Reply-To: <CAESVnVoCLJUosHkvbd7xV-a+4CDB7CpCMp+Az=dhVCAqS_63mw@mail.gmail.com>
Date: Mon, 30 Mar 2020 16:06:12 +0200
Message-ID: <CAG9XoMTfB0W+3g_1FiGnBvKsVi8++N9adpAodAw-9NDyjSs4LA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Sherif Ramadan <theanomaly.is@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004dd0a705a212f575"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Change var_export() array syntax to
 use short hand arrays
From: benjamin.morel@gmail.com (Benjamin Morel)

--0000000000004dd0a705a212f575
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> "Then why not use brick/varexporter?"


As much as I'm pleased that people use this library, I consider it a shim,
waiting for PHP to ultimately provide the same functionality.
See the (object) cast for stdClass, that was supported by varexporter but
was later added to var_export().
I don't see a reason not to follow with the short array syntax; the only
expectation of people using var_export(), AFAIK, is to get valid PHP code;
they don't care about the syntax, which will be retro-compatible as far as
PHP 5.4, if that's even a consideration when PHP 8.0 is released.

=E2=80=94 Benjamin

--0000000000004dd0a705a212f575--