Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117388 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 46178 invoked from network); 21 Mar 2022 08:25:06 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Mar 2022 08:25:06 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 4764B1804AF for ; Mon, 21 Mar 2022 02:51:18 -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,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-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 21 Mar 2022 02:51:17 -0700 (PDT) Received: by mail-wr1-f46.google.com with SMTP id r13so4823054wrr.9 for ; Mon, 21 Mar 2022 02:51:17 -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 :from:to:references:in-reply-to:content-transfer-encoding; bh=wZu5kKa2575DLbAQ4fP9+OJaEnkSunX9WW1FSlcvhWM=; b=UalKOBvw7GOvV5JN7W/tWUyIE87HKxyv1eDwlWjoYPXPPfMi7HbgS4gu3G/jZvT3PU bvh6nPe1l3Ydg9rMjHEkuyqfF/nkLfE6D9ay/mH4JOaqlpJwX2oxHHy+CrMr2ODTh2/G 531wkH/0qQcAJ7SNPgw1mXzaptUulcBXLmVLsAckpd3PkW63ufUVGL79IzM0GyWeqWdq ux/L1POyuVhk1QG/YMl9h2UPxW6819/3PjA6kK6HsfjnicNMqRBtgWfLRLN7Yy/Jlhgd gd90qMt+q5hm0mntnWoPSKwywus+d/Yj7yGuFJZ+7sBUhK1qjBKnrvZsnUtgC+zEWByF dJBQ== 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:from:to:references:in-reply-to :content-transfer-encoding; bh=wZu5kKa2575DLbAQ4fP9+OJaEnkSunX9WW1FSlcvhWM=; b=WgluD4arLllAtbkDG5MEKxBhiWSbPcuXbXijcp9nNfEWR4NcR8rkfohJZW6XDv0fYH TgcTYTKzBz+1Sjv/NO4lj+ZMCiHRUwN1/KGrNcxANpJjQlmelO3KIUwGxdTj0zWMvvz4 bViqKnvOzo/CUTdrQGkO+JNdth9nc4ZVBDfKcdaQ2aASc6bC44Kc8D8R/KEzCdhy1A7A v9qtqXRwkZlNvbf8H+LCATnk85jK0bTcRB1s/WL1xuqhCC5r+d16yl2LPzETcfPQH0fu hzdNC7pPjW9VrBsGvKZXjp1Y4hEXKXPeaaMkONdMLTDP7FwfBk5RGR9PgaSdnMtiatwO nj3w== X-Gm-Message-State: AOAM533AlfjNYMNmblSfTowe8pPp4uf1omudOswdNj3lFEISee4qJeYN PpUqgh3CrutY5yUvxAJLFNFthOOKOwA= X-Google-Smtp-Source: ABdhPJzwfXkyz3b3fGdmdTsrnwg+1UYAAKOsqLeqV1weUB3VbswlRLIpPRSAbvYC1Qf0Xp2dfcLGRw== X-Received: by 2002:adf:eec1:0:b0:1e3:1e0a:72f0 with SMTP id a1-20020adfeec1000000b001e31e0a72f0mr17954604wrp.524.1647856276545; Mon, 21 Mar 2022 02:51:16 -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 i10-20020a5d584a000000b00203e8019f2dsm10858273wrf.61.2022.03.21.02.51.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Mar 2022 02:51:16 -0700 (PDT) Message-ID: Date: Mon, 21 Mar 2022 09:51:15 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-GB To: internals@lists.php.net References: <4AC60E84-B2AD-43F4-9B72-92604FC7BD41@gmail.com> <73550eae-370d-115f-e440-4889e42dbc74@processus.org> <244126ae-f42c-3b53-022e-e69e3e012ded@gmail.com> In-Reply-To: <244126ae-f42c-3b53-022e-e69e3e012ded@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC][Under discussion] Arbitrary string interpolation From: rowan.collins@gmail.com (Rowan Tommins) On 20/03/2022 13:39, Rowan Tommins wrote: > Using a second colon would make ternary expressions slightly awkward; > C# handles this by requiring them to be parenthesised, so "{$:( $test > ? $x : $y )}" would be valid but "{$:$test ? $x : $y}" would not; we > could use some other delimiter, but they'd probably all need something > similar. Thinking about it, a second colon might also cause problems for expressions like "{$: Foo::bar() }", so since we have multiple symbols at the start anyway, how about a prefixed formatting argument, e.g. "{$%10.3f: $x }" Regards, -- Rowan Tommins [IMSoP]