Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111607
MIME-Version: 1.0
References: <CAPyj-LCozQQEk8o2-Dse3Am+UEKYhEKSfUW3MWN-m6mdboNG=Q@mail.gmail.com>
 <92f3ee69-7b06-4995-546e-95f0218767bb@gmail.com> <CAPyj-LD=9E3vQxLS9xYeUg7y30SQTYf3J3LWJ+E9JcEJYrOX8w@mail.gmail.com>
In-Reply-To: <CAPyj-LD=9E3vQxLS9xYeUg7y30SQTYf3J3LWJ+E9JcEJYrOX8w@mail.gmail.com>
Date: Tue, 18 Aug 2020 10:00:32 +0100
Message-ID: <CALKiJKoyKVD78CLa1Fc3GRwnOSKfr1kmGdejA192rRnUyRi6Qg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006c5b6405ad231faf"
Subject: Re: [PHP-DEV] [RFC] Better string interpolation
From: rowan.collins@gmail.com (Rowan Tommins)

--0000000000006c5b6405ad231faf
Content-Type: text/plain; charset="UTF-8"

Hi Ilija,

On Mon, 17 Aug 2020 at 18:54, Ilija Tovilo <tovilo.ilija@gmail.com> wrote:

>
> sprintf-style modifiers are an interesting idea. But I'm not sure if
> there would be a huge advantage over using number_format.
>
> [...]
>
> Escaping is a nice idea but I'm not sure we want to go that route.
> String interpolation is still a bad fit for many templating things...
>


The above reactions basically mirror my initial reaction to your initial
e-mail: an extended string interpolation feature sounds nice, but how does
it differ from string concatenation and function calls? That's why I
started thinking about additional features to bring in: I was trying to
think of the use cases this new syntax would be for, and what new things it
would make possible (or rather, easier).

If the proposal is to add a completely new string syntax, I feel like it
needs a stronger justification than being able to write $"Hello
#{Foo::bar()}\n" rather than "Hello " . Foo::bar() ."\n"

Regards,
-- 
Rowan Tommins
[IMSoP]

--0000000000006c5b6405ad231faf--