Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117785 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 2863 invoked from network); 24 May 2022 18:54:46 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 May 2022 18:54:46 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B545D180083 for ; Tue, 24 May 2022 13:37:05 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, 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-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) (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 13:37:02 -0700 (PDT) Received: by mail-qt1-f171.google.com with SMTP id q20so5871041qtw.1 for ; Tue, 24 May 2022 13:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=iGQQ5gC46NVT7omCNCDRe0YnrL6/3BPgAnO5V2B2oGg=; b=IdLK9KKIgNWUhw1IcA7TkBFBQcYV7QiyxoYbjygj9gq8JfobXKPm2pfvitHJlYqkYf ZcxcT0/QBNxPzzAXbgkyuCqC84KA5qxI1U/gnoqV2x9XlHEULQ4q/xFotczzk4ygdzbN YQtCEAEKoB1VP39BTqD5ijnR4ueFG/W0PvLLzogbRpLz2c8lXZXzIzIROlMDxTK28MgD FBpdp/BgIjtq3oVsHhM3XB2WnBCkyXsFNFAzWE7N5wNuakcFWiNPMYbfx+03fnK/RFuA j0oHkLShetaOBUXiytWj6q8A4IZMl3VpriXbggRQmjotUiGAbRMAqSjhPQIEy5xiz7sN CPCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=iGQQ5gC46NVT7omCNCDRe0YnrL6/3BPgAnO5V2B2oGg=; b=m4/q7EPGtSX2vRxi1oAcNzI4eLr3fPmqmOmtWxEo/fuIFqTxjKBShZ1wbNet140S0/ XX6/1xXjnxdZuW7RW0jGT4nV+fkfZdQrIXflPlZv5D9jj0GJFee65mMw8ixNAT/gX/tg loiB3qHqve8Isx3pC0L1i45UF6a2MYVgHth0NkxotTTFBf5H398z2q4oamuXmpZhTw0E 8JXJ7gVAd6SQyAGmUgfikPKfHfIkW6UUU8gXS3BtIzK339i3ZdXWjEUlfvipXcO34KwW YMRNelx0qsxaHX7avJhJSJbcG7Rf1jYA9yu05ZNYyxDDGPTS7/HAAyK+VAN3/Rn+PC28 pzag== X-Gm-Message-State: AOAM5320RncHqt2itMzg5sMySAMWREObYQb/a+6bsBq1wr+uNgjRAE0H ryJ6FOHuUnEoOilKFgLNJGbrQ64QEsXnWvIf9GmBvmzq X-Google-Smtp-Source: ABdhPJzVLUDzIFJpkWG4FPfK1mFhB5R8wTPZBTcplW1VrItpf0QSoS/uTrnk6y2eF5npdyQnpHIOR0CInPHX0LddvSk= X-Received: by 2002:a05:622a:64c:b0:2f9:a4c:b4f0 with SMTP id a12-20020a05622a064c00b002f90a4cb4f0mr22001198qtb.380.1653424621253; Tue, 24 May 2022 13:37:01 -0700 (PDT) MIME-Version: 1.0 References: <628abd5a.1c69fb81.37cfe.4ebbSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Tue, 24 May 2022 15:36:50 -0500 Message-ID: To: internals Content-Type: multipart/alternative; boundary="0000000000003677eb05dfc7eb74" Subject: Re: [PHP-DEV] Re: Removal of ${} string interpolation in PHP 9 From: tendoaki@gmail.com (Michael Morris) --0000000000003677eb05dfc7eb74 Content-Type: text/plain; charset="UTF-8" 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? On Mon, May 23, 2022 at 6:59 AM Robert Landers wrote: > On Mon, May 23, 2022 at 12:46 AM Mark Randall wrote: > > > > On 20/05/2022 10:05, Ilija Tovilo wrote: > > > So unless there are concerns I will amend that in the RFC. > > > > Erroring it out makes sense to me. > > > > As we don't include any target version specification in PHP files, the > > safest bet it so prevent the silent change from potentially leaking > > through the introduction of a parser error. > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: https://www.php.net/unsub.php > > > > > Ilija, > > It might be a good idea to do up another RFC to make it easy to vote. > I suspect it won't be unanimous. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --0000000000003677eb05dfc7eb74--