On Thursday, March 26, 2020 6:19 PM Guilliam Xavier
wrote:
>> If the concat operator is not overloaded, the behavior is like now, and the
>> objects are converted implicitly to strings (so $a . $b actually means
>> (string) $a . (string) $b).
>> Furthermore an notice is triggered, hinting the
On 26.03.2020 at 18:18, Guilliam Xavier wrote:
> On Thu, Mar 26, 2020 at 5:37 PM wrote:
>>
>> The overloaded concat operator has higher priority than the __toString()
>> method.
>> So if Class A overloades the concat operator, then calling $a . $b means
>> ClassA::__concat($a, $b); (Note that
On Thu, Mar 26, 2020 at 5:37 PM wrote:
>
> The overloaded concat operator has higher priority than the __toString()
> method.
> So if Class A overloades the concat operator, then calling $a . $b means
> ClassA::__concat($a, $b); (Note that both operands are passed in their
> original form)
>
On Thursday, March 26, 2020 3:50 AM Jakob Givoni wrote:
> On Wed, Mar 25, 2020 at 6:28 AM Christoph M. Becker wrote:
>
>> It seems to me that the RFC is not sufficiently specific enough
>> regarding the concatenation of instances of classes which implement
>> __toString().
>
> Exactly what I
On Wed, Mar 25, 2020 at 6:28 AM Christoph M. Becker wrote:
>
> It seems to me that the RFC is not sufficiently specific enough
> regarding the concatenation of instances of classes which implement
> __toString().
Exactly what I was thinking too. Would be nice with some examples on this.
> So if