Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108374
Message-ID: <16758978-29D6-491C-8503-D91F147189CC@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2F06032F-16A9-4023-8C88-E353C3A4DD34"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Date: Tue, 4 Feb 2020 08:33:07 -0500
In-Reply-To: <CADyq6s+SPJj_aGhg044XbW4KdRNYrV=bAxGX6ioMpihpg0E2SA@mail.gmail.com>
Cc: PHP Internals <internals@lists.php.net>
To: Marco Pivetta <ocramius@gmail.com>
References: <D5ACEB01-4E1E-407A-8441-D8C6E0D36CCA@gmail.com>
 <CADyq6s+SPJj_aGhg044XbW4KdRNYrV=bAxGX6ioMpihpg0E2SA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC - discussion] __toArray()
From: stevenwadejr@gmail.com (Steven Wade)

--Apple-Mail=_2F06032F-16A9-4023-8C88-E353C3A4DD34
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> `__toArray` as a magic function call when `(array)` cast happen is a =
bad idea: it is a BC break,

Adding a new magic method is not a backwards compatibility break. The =
PHP documentation on magic methods states:

"Caution PHP reserves all function names starting with __ as magical. It =
is recommended that you do not use function names with __ in PHP unless =
you want some documented magic functionality.=E2=80=9D

Any user implementing their own methods prefixed with a double =
underscore is taking the chance that their code could break in the =
future.


> and it removes one of the very few interactions (with objects) that =
didn't cause any side-effects (https://externals.io/message/98539#98545 =
<https://externals.io/message/98539#98545>, =
https://externals.io/message/98539#98567 =
<https://externals.io/message/98539#98567>)=20

PHP 7.4 introduced the "get_mangled_object_vars()=E2=80=9D as a result =
of these concerns.=

--Apple-Mail=_2F06032F-16A9-4023-8C88-E353C3A4DD34--