Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117309
Date: Sat, 12 Mar 2022 11:11:16 +0000
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <20220312031138.5e0669a4@platypus>
References: <CAPyj-LDVVfrSx1B3DpW+VjOe78twZVbPsGRv+k96MJ=1A3vCAw@mail.gmail.com> <20220312031138.5e0669a4@platypus>
Message-ID: <A0E06DE1-3F3A-4E1A-B2E7-BBB2B4E35E26@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: =?US-ASCII?Q?Re=3A_=5BPHP-DEV=5D_=5BRFC=5D=5BUnder_discussion?= =?US-ASCII?Q?=5D_Deprecate_=24=7B=7D_string_interpolation?=
From: rowan.collins@gmail.com (Rowan Tommins)

On 12 March 2022 02:11:38 GMT, BohwaZ <php@bohwaz=2Enet> wrote:
>This RFC is confusing two different things:
>
>1=2E variables inside strings (options 1, 2, 3)
>2=2E dynamic variables names (option 4)
>
>The 4th one is very useful=2E
>
>$v =3D ${'param_' =2E $name};
>
>There is no other practical way to do that, so removing that feature
>would mean breaking something useful with no replacement=2E


I don't see anything in the RFC that would break that example=2E The RFC i=
s *only* about how variables are interpolated *inside quoted strings*=2E

As pointed out in the RFC, this syntax looks the same but works subtly dif=
ferently inside a string, such that (string)${foo} !=3D=3D "${foo}" (one de=
references a constant, the other doesn't)=2E

Full handling of variable-variables is available in the full interpolation=
 syntax, "{$=2E=2E=2E}", so "{${foo}}" *does* give the same result as (stri=
ng)${foo}, and "{${'param_' =2E $name}}" gives the same result as (string)$=
{'param_' =2E $name}=2E https://3v4l=2Eorg/aRMaq

@Ilija It might be worth adding the above example to the RFC , to show tha=
t "Option 2" can actually do everything that the other options do and more=
=2E

Regards,=20

--=20
Rowan Tommins
[IMSoP]