Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109346
To: Guilliam Xavier <guilliam.xavier@gmail.com>, jan.h.boehmer@gmx.de
Cc: Jakob Givoni <jakob@givoni.dk>, PHP internals <internals@lists.php.net>
References: <003701d6013c$9afe9750$d0fbc5f0$@gmx.de>
 <379095fd-ba11-4d84-6cab-89905eeab32a@gmx.de>
 <CAJmjfvXrtC7b8B2F5fYUy+s5Dvao6VohH=kVfODaJZ_CNJ2jRw@mail.gmail.com>
 <004501d6038c$c7870df0$569529d0$@gmx.de>
 <CAC5V6gi6wxCuhjR5qsTF3WkankP-usC-h=hw_wJ-+8rV-_PJxQ@mail.gmail.com>
Message-ID: <9322303a-1f68-d5df-8e93-a06b3839ea39@gmx.de>
Date: Thu, 26 Mar 2020 18:25:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <CAC5V6gi6wxCuhjR5qsTF3WkankP-usC-h=hw_wJ-+8rV-_PJxQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [VOTE] Userspace operator overloading
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 26.03.2020 at 18:18, Guilliam Xavier wrote:

> On Thu, Mar 26, 2020 at 5:37 PM <jan.h.boehmer@gmx.de> wrote:
>>
>> The overloaded concat operator has higher priority than the __toString(=
) method.
>> So if Class A overloades the concat operator, then calling $a . $b mean=
s ClassA::__concat($a, $b);  (Note that both operands are passed in their =
original form)
>> If you want to concat the string representations, you will have to expl=
icitly convert the objects to strings:
>>         $ret =3D (string) $a . (string) $b;
>
> This first part seems legit to me.
>
>> If the concat operator is not overloaded, the behavior is like now, and=
 the objects are converted implicitly to strings (so $a . $b actually mean=
s (string) $a . (string) $b).
>> Furthermore an notice is triggered, hinting the user that he could over=
load the concat operator. (Maybe here a different message than for the oth=
er operators would be useful).
>
> I fear that "hint" notice could break Symfony apps... Couldn't you
> just not trigger it in this case?

Either that (it's what I would prefer), or clearly document that BC
break (even if it's just about a notice).

Thanks,
Christoph