Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111386
MIME-Version: 1.0
References: <CAESVnVp+Cnk2rKG+4KL+WkC-c0Fk7GGny4uAcHzwSbUwCdF2Yw@mail.gmail.com>
In-Reply-To: <CAESVnVp+Cnk2rKG+4KL+WkC-c0Fk7GGny4uAcHzwSbUwCdF2Yw@mail.gmail.com>
Date: Sun, 9 Aug 2020 05:47:48 +0200
Message-ID: <CADyq6sLUVRpoCYzfh0iXja4jYrdtHfiKBxkThGcvKfOcTjV3FQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005c396705ac69b489"
Subject: Re: [PHP-DEV] Null-safe property access in interpolated strings
From: ocramius@gmail.com (Marco Pivetta)

--0000000000005c396705ac69b489
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 9, 2020, 00:17 Sara Golemon <pollita@php.net> wrote:

> Do we expect this to work?
>
> $foo =3D new stdClass;
> $foo->bar =3D "Hello";
> echo "$foo?->bar world\n";
>
> Because at the moment it doesn't: https://3v4l.org/nLv3l
>
> -Sara
>

Ooof, people still interpolate strings that way?

Good riddance if it doesn't work: this code is questionable (and not just
because of the question mark in it) =F0=9F=91=8D

>

--0000000000005c396705ac69b489--