Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117857 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38162 invoked from network); 5 Jun 2022 20:55:38 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Jun 2022 20:55:38 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 59CE01801FD for ; Sun, 5 Jun 2022 15:40:59 -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=3.0 required=5.0 tests=BAYES_50, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLACK 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-ej1-f53.google.com (mail-ej1-f53.google.com [209.85.218.53]) (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 ; Sun, 5 Jun 2022 15:40:58 -0700 (PDT) Received: by mail-ej1-f53.google.com with SMTP id s12so18526523ejx.3 for ; Sun, 05 Jun 2022 15:40:58 -0700 (PDT) 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:cc:content-transfer-encoding; bh=EgHj5F/yTwR9jHNoprkxCOujcTh4axOUa/+61kk942Y=; b=UbVfUvfp5VGjxDtNxddEG/+kGeonSLkb9dMyw2EvHdJ/CzxuXzFz1O2WMMY+fnn9sD wBGFaosGp4RgLorJ8UhoY1Zpqk1wuw2PbK8lf8zoPQBxwfQiI1T1MGf+SWYeCvBxj+OF iUI2eotJiSZ8cuC3x6KAI79eRwGuE54QlST1/fFtM7qhbUFvmqWMa8Ob0GaOZGrN2wNb 0eS5dGEH1Dtjd5QdKjuZwmEYP6+y7BTDIes6aVUq5dViOU9eTdPFWWv8kmBR/+U4X5Em rnZmlQT0BV4ZMkpxHPJx8/Oqiy3ruVN2DQmKmwq8RW+sa4sfVPE2oDZdyZv6xbcPGwY9 qLHw== X-Gm-Message-State: AOAM531yrpqy0YvMvQ81r2n0OtS6A8DFimno//t/3yO5jKVsbHBOYZy4 r8s6GtCi9VpJtNLzMP7yyRuSQUmh0MYWgA== X-Google-Smtp-Source: ABdhPJxf73M1kEL07XUTxwLfuCEVVyzwVpzyGrHxD1nrqaKsccWdUxrK7PS/A17FNPEDQMCCaDxDbQ== X-Received: by 2002:a17:907:a410:b0:70b:db4d:784d with SMTP id sg16-20020a170907a41000b0070bdb4d784dmr16186611ejc.185.1654468857668; Sun, 05 Jun 2022 15:40:57 -0700 (PDT) Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com. [209.85.128.54]) by smtp.gmail.com with ESMTPSA id gg1-20020a170906e28100b006f3ef214da9sm5705811ejb.15.2022.06.05.15.40.57 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 05 Jun 2022 15:40:57 -0700 (PDT) Received: by mail-wm1-f54.google.com with SMTP id m39-20020a05600c3b2700b0039c511ebbacso140273wms.3 for ; Sun, 05 Jun 2022 15:40:57 -0700 (PDT) X-Received: by 2002:a7b:c4cb:0:b0:39c:35b3:e8c1 with SMTP id g11-20020a7bc4cb000000b0039c35b3e8c1mr17173153wmk.183.1654468856976; Sun, 05 Jun 2022 15:40:56 -0700 (PDT) MIME-Version: 1.0 References: <30e5ca33-cfc7-3ea6-a161-cdb103a08c8c@demon-angel.eu> In-Reply-To: <30e5ca33-cfc7-3ea6-a161-cdb103a08c8c@demon-angel.eu> Date: Mon, 6 Jun 2022 07:40:45 +0900 X-Gmail-Original-Message-ID: Message-ID: To: mark@demon-angel.eu Cc: internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Adding new closing tag =?> for keeping trailing newline From: sji@sj-i.dev (shinji igarashi) Hello! > It should behave exactly the same as the existing closing tag, except that it does not erase the trailing newline character. Thanks! -- Shinji Igarashi 2022=E5=B9=B46=E6=9C=886=E6=97=A5(=E6=9C=88) 6:54 Mark Baker : > > On 05/06/2022 10:23, shinji igarashi wrote: > > I'd like to propose adding a new closing tag `=3D?>` to the language. > > > > PHP currently removes the newline character immediately following > > the closing tag `?>`. > > So we would have 4 possible combinations that developers could apply in > their code, two existing open/close settings > > > > > > and two new combinations, the first you explain > > > > but also > > > > What should PHP do when it encounters this combination of > opening/closing tags? > > > -- > Mark Baker > > _________ > |. \ \-3 > |_J_/ PHP | > || | __ | > || |m| |m| > > I LOVE PHP > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php >