Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117786 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 9982 invoked from network); 24 May 2022 20:44:06 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 May 2022 20:44:06 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 92B571804C9 for ; Tue, 24 May 2022 15:26:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 24 May 2022 15:26:26 -0700 (PDT) Received: by mail-wr1-f42.google.com with SMTP id j25so3228492wrb.6 for ; Tue, 24 May 2022 15:26:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=dmrqLljRUSh7WAlluS5GhOXrlp1/w7jKRJYUIuP+Jvc=; b=gBraF3k1Y14RzAk/qoFEEPcABhM/gbqKlrWLb7fdKsHD/0Ogbn/KvQqAa+FCZZ9/qU gO5H/5OpNwhO1sVRl4Sub70TVKMQSTn84Dkr5W/i0HLKv7JHwb904B2+Jre5uRYCI5/0 33DvX6BsHudEDQnd8aKjRbWFYY3PB1VHJff8a+ce0NoW48D0ZdI6eqcn8wAGd+aGUfkI x2LE3PQ6nBgRtjPtQxVpYWZ/UBbjhizOBJXg8LB2CeqSVAlRX0nz+OIM1WOU15kxC4ZD nS/smOwbAhjSB9OmDOV0vUESE5Ltu9TyZARFlrwyKPkP3Cd5EwPqwk7ml3DlXcLVl4li Z11g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=dmrqLljRUSh7WAlluS5GhOXrlp1/w7jKRJYUIuP+Jvc=; b=7YD5F9zehq6NRT/n4qPWUsmK0562e4r11vIRZqqBUT3EViMup2zyzLXyxujqU1An2q FxYtmRFlVEtEPuYeiiPJUXKtyD6P+LiWoXq0+WsJaqRSQ/7DfMr4X61OuHlQGeXeNB4+ WXRzUZMorjTZMwm6YLeGa2FYwHRVPAGGFHIiPDQz3J+MEpRMn3CUE3kt8LSSkZWe8v4W jU9VcK1aQVnafOrKT03LmHHQ2y9nWgIRw4TxP3wqXDAiiEC7NPXUTYPABlx/jqWJ60Vp mYd6fwG2s/sebztYGluXuErUrpfAvi3q9B6+hYweeDBG0f2QI+Y0YwE2IEPx0AeGSqdm g4Zg== X-Gm-Message-State: AOAM531po6+fO4ZVQWr+RZnWUo/jVzBlcnKa1LRfInqxR4hebE6vaHiE 506OgGygVFjaat6kppFbNRsMPV7tU8E= X-Google-Smtp-Source: ABdhPJyjv8ckGI2uN/yYq31RdtgtxyD/FpfGeJRYitrZyRrOc9GTAFcwfmqQaigdZ3hPlU5cJCiPow== X-Received: by 2002:adf:ed0e:0:b0:20d:fd3:de77 with SMTP id a14-20020adfed0e000000b0020d0fd3de77mr24635977wro.213.1653431184873; Tue, 24 May 2022 15:26:24 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id be13-20020a05600c1e8d00b003971fc23185sm94057wmb.20.2022.05.24.15.26.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 May 2022 15:26:23 -0700 (PDT) Message-ID: <1030687d-165d-2514-67a0-f0dc85016ed9@gmail.com> Date: Tue, 24 May 2022 23:26:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Content-Language: en-GB To: internals@lists.php.net References: <628abd5a.1c69fb81.37cfe.4ebbSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Removal of ${} string interpolation in PHP 9 From: rowan.collins@gmail.com (Rowan Tommins) On 24/05/2022 21:36, Michael Morris wrote: > I can understand removing this feature since it is a bit confusing, but are > there any plans to replace it - say with the template literal syntax of > JavaScript? For those needing to refactor having something to switch to > would be preferable than having the feature dropped. Or does PHP have some > goofy use for backtick that would prevent this from happening? There already is something to switch to - the "{$foo}" syntax (which is staying) supports everything the "${foo}" syntax does and more. There has been intermittent talk of adding "even better" interpolation of some sort, but without consensus on exactly what the features should be - search on https://externals.io/ to see previous threads. (And yes, PHP does have a "goofy" use for backtick, inherited from Perl, as an alias for shell_exec. But that's not really relevant because there are plenty of programming languages which have multiple quoting styles without using it, mostly by adding a prefix, e.g. Python's f"...".) Regards, -- Rowan Tommins [IMSoP]