Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98553
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.180 as permitted sender)
MIME-Version: 1.0
References: <CAGyGae2yg-NnPmcJEJcPdn3XQTUyS_=Ymg1nrdTDTig9r2rdfw@mail.gmail.com>
 <CADyq6sKASo_nV9SvvG6LXKCEOY-H=ofuQqbSwAA08TMb1T_Rmg@mail.gmail.com>
 <CAJW__o3F1=4ou-Wmfv0JsQnnYNj_CqRLFxzEweNJvM3nZz8t2w@mail.gmail.com>
 <CADyq6sJMTkthzrRkOqwj9M=jkp0Be6T6Ry1kQuwyb7VOEa+N1A@mail.gmail.com>
 <CAObuZdsOFSjBGVNEkNPWtYe1xzdOSto=S_VhwGQnm59rHN7DqA@mail.gmail.com> <CADyq6sLWukWaerw-enD1VMEYiDPr4BPy8Nz9xkN+3o2qLgCzXA@mail.gmail.com>
In-Reply-To: <CADyq6sLWukWaerw-enD1VMEYiDPr4BPy8Nz9xkN+3o2qLgCzXA@mail.gmail.com>
Date: Wed, 15 Mar 2017 22:51:03 +0000
Message-ID: <CAGyGae2pnXmhLjbW4y=X6D-qd-TOL_euNOE_fDkO+d0v-CE7Xw@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>, Ryan Pallas <derokorian@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>, Kalle Sommer Nielsen <kalle@php.net>
Content-Type: multipart/alternative; boundary=f403045d57cc1fa0e0054accc86e
Subject: Re: [PHP-DEV] Add __toArray() method to objects that would be called
 on cast to array
From: bburnichon@gmail.com (=?UTF-8?Q?Beno=C3=AEt_Burnichon?=)

--f403045d57cc1fa0e0054accc86e
Content-Type: text/plain; charset=UTF-8

I was not aware of all that being the only way to distinguish set/unset
properties.
I do agree with Marco on this point that it would be a BC break. It was not
my intention at all and did not foresee that.

Up to now, I thought array casting objects was doing the same as for scalar
values. I was wrong and I think many other developers around too.

On Wed, 15 Mar 2017 at 23:40 Marco Pivetta <ocramius@gmail.com> wrote:

> Which is precisely the BC break: such a library would now throw an
> exception "unsupported class X" when `__toString` is implemented. Also,
> such a library would break silently when this feature is implemented.
>
> Much like the already very broken `__debugInfo()`, this automatic
> type-cast is a giga-Joule footgun.
>

--f403045d57cc1fa0e0054accc86e--