Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117426
To: PHP internals <internals@lists.php.net>
Cc: Ilija Tovilo <tovilo.ilija@gmail.com>
Date: Fri, 25 Mar 2022 15:38:08 +0100
Message-ID: <10558027.nUPlyArG6x@arnaud-t490>
In-Reply-To: <CAPyj-LCXYjsjtDr1zPmH6t37pQS7aeGACG6kCex=fnsEJmNmVg@mail.gmail.com>
References: <CAPyj-LCXYjsjtDr1zPmH6t37pQS7aeGACG6kCex=fnsEJmNmVg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [PHP-DEV] [RFC][Under discussion] Arbitrary string interpolation
From: arnaud.lb@gmail.com (Arnaud Le Blanc)

Hi Ilija

I find that sprintf() is easier to read in most cases. One reason for this is 
that the text is separated from the code. It's also easier to review for 
humans and linters.

The strtoupper example would look like this with sprintf:

    $world = 'world';
    echo sprintf('Hello %s!', strtoupper($world));

Longer examples can be nicely split in multiple lines:

    echo sprintf(
        'Received HTTP status code %d (reason phrase: %s)',
        $response->getStatusCode(),
        $response->getReasonPhrase(),
    );

And this also works with heredoc:

    echo sprintf(
        <<<'HTML'
        <html>
            <head>
                <title>%s</title>
            </head>
        </html>
        HTML,
        htmlspecialchars($title),
    );


-- Arnaud

On jeudi 17 mars 2022 23:27:30 CET Ilija Tovilo wrote:
> Hi everyone
> 
> I'd like to start discussion on a new RFC for arbitrary string
> interpolation. https://wiki.php.net/rfc/arbitrary_string_interpolation
> 
> Let me know what you think.
> 
> Ilija