Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98561
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPhkiZymJHQT4vmqa30Qg3UPseF=q+fwqdtWXciHd=NfHB_1OQ@mail.gmail.com>
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>
 <CAObuZdsk7m13SU91o_7n6b0icybH9jApUaiD6SYccwV5ZKOwWg@mail.gmail.com>
 <CADyq6sK+wcfJtP7h3bPONRmOi4sY=hK83=M70dmK=FjGN_1_Sg@mail.gmail.com>
 <CAObuZds5bF4r7x99VCK9KxkkpMGjkxyw3YaNZpO0sheyAM8x1g@mail.gmail.com>
 <CADyq6sKEex_d9m3Coat6aRMz+Ao9f9nHvOVKmoJCZC2=wZGrpw@mail.gmail.com>
 <CAPhkiZx0bf-3e_ULz3LSf_2dEfw70PiSq1M0t18tjmqOyQDs-g@mail.gmail.com>
 <CADyq6s+sqr5r+1p75CSWEcWhPiHMSLVbLpjR8TAVdEa+JPLOQw@mail.gmail.com>
 <CAPhkiZwWg9Nec7LZwMCK-sVhYhKWAxsZaB6cNpxEdFUR=9-s1w@mail.gmail.com> <CAPhkiZymJHQT4vmqa30Qg3UPseF=q+fwqdtWXciHd=NfHB_1OQ@mail.gmail.com>
Date: Thu, 16 Mar 2017 01:32:57 +0100
Message-ID: <CADyq6sJhJ1bJ0S=HaSxJFwLKOCfvv73AyMtVSbVG-OcO4c4adA@mail.gmail.com>
To: Andrey Andreev <narf@devilix.net>
Cc: Ryan Pallas <derokorian@gmail.com>, Kalle Sommer Nielsen <kalle@php.net>, 
	=?UTF-8?Q?Beno=C3=AEt_Burnichon?= <bburnichon@gmail.com>, 
	internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a113f40f4e674b7054ace3332
Subject: Re: [PHP-DEV] Add __toArray() method to objects that would be called
 on cast to array
From: ocramius@gmail.com (Marco Pivetta)

--001a113f40f4e674b7054ace3332
Content-Type: text/plain; charset=UTF-8

As just told: existing code hinting against generic `object` breaks. This
is a change in semantics in an existing operator. It is just sane to
consider it a BC break, since the operator cannot be relied upon for a
certain family of problems: invent a new operator.

That's basically the path to follow anytime something could be overloaded,
but shouldn't due to BC constraints.



On 16 Mar 2017 1:22 a.m., "Andrey Andreev" <narf@devilix.net> wrote:

>
>
> On Mar 16, 2017 2:01 AM, "Marco Pivetta" <ocramius@gmail.com> wrote:
>
> What changes is the interface of the `(array)` operator.
>
>
> I understand what you mean, I just disagree that it constitutes a BC break
> in the sense that no existing code would break/misbehave by simply updating
> to a PHP version including the feature.
>
> That's just the only sane criteria by which to label changes as BC breaks,
> because if we don't stick to that, there'd be an argument to be made that
> literally every change is. And that would mean the term loses its meaning
> and becomes useless.
>
> Cheers,
> Andrey.
>

--001a113f40f4e674b7054ace3332--