Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111421
MIME-Version: 1.0
References: <CAESVnVp+Cnk2rKG+4KL+WkC-c0Fk7GGny4uAcHzwSbUwCdF2Yw@mail.gmail.com>
 <24ce93f7-b5b2-fb63-6ea4-032c4e71f049@seld.be>
In-Reply-To: <24ce93f7-b5b2-fb63-6ea4-032c4e71f049@seld.be>
Date: Mon, 10 Aug 2020 13:02:16 +0200
Message-ID: <CAGKNXQFNDoZ-1Rsd4NFJkru0DcmL3nTC=WdrX7FhgrPR12jaUA@mail.gmail.com>
To: Jordi Boggiano <j.boggiano@seld.be>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Null-safe property access in interpolated strings
From: phofstetter@sensational.ch (Philip Hofstetter)

Hi,

On Sun, Aug 9, 2020 at 8:34 PM Jordi Boggiano <j.boggiano@seld.be> wrote:

> Can't say I'm big on interpolation but I'd definitely expect this to
> work because why not?

A reason why not is because it will break backwards compatibility with
existing (though admittedly unlikely) code which also can't be fixed
by easy search and replace:

    $foo = "gnegg";
    echo "$foo?->bar()"

would be fine in PHP < 8 and would blow up with `Uncaught Error: Call
to a member function bar() on string` with this change.

I'm not saying this is a problem because code like this is unlikely to
be written, but it *is* a BC break.

Philip