Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117854 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32673 invoked from network); 5 Jun 2022 20:09:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Jun 2022 20:09:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 59669180384 for ; Sun, 5 Jun 2022 14:54:30 -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.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS398810 136.175.108.0/24 X-Spam-Virus: No X-Envelope-From: Received: from mail-108-mta108.mxroute.com (mail-108-mta108.mxroute.com [136.175.108.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 5 Jun 2022 14:54:29 -0700 (PDT) Received: from filter006.mxroute.com ([140.82.40.27] 140.82.40.27.vultrusercontent.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta108.mxroute.com (ZoneMTA) with ESMTPSA id 18135dcb301000c327.001 for (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256); Sun, 05 Jun 2022 21:54:25 +0000 X-Zone-Loop: 38b226c7b618a5b6d948896bb1f7b31bbc4920d88b99 X-Originating-IP: [140.82.40.27] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=demon-angel.eu; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:To:Subject:Reply-To:MIME-Version:Date:Message-ID:Sender:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Yq0judQ7/6bwfgcloxH50oDUVnpPnXMe/vvOs0pxHp8=; b=lcDpUrMXRndyoRv+wSlm7N4r3P 8Oox23eyXiqlKXXmW4mYUcIO9lvPyh7ShjuqPEvzM71HejHM5YpdnGZjV+W/D1gX2ZTLj+GuqYfvv m43YEL+cri8bsEbFHlnHZ3ka7jC0ua1VjrcYwS4QenD0Diok/3LvEHlAVzIqUcBXCNIJnO1GuCiaV kU8PgL2/N/FzxjPr5fkeA3LN38H1XOm/cavHGnEi+qd3NLPklSw59utnOHVtz9gaXecEoa3xiUUdo qtMTRvCGMgLS4tqdO6sHS+oMXB/vuYUm9ZxjTRBC6JrThlHz9V4zmLOfm3gYH9i7qg7WJmWws48Z3 TnJxzy4A==; Message-ID: <30e5ca33-cfc7-3ea6-a161-cdb103a08c8c@demon-angel.eu> Date: Sun, 5 Jun 2022 23:54:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Reply-To: mark@demon-angel.eu To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AuthUser: mark@demon-angel.eu Subject: Re: [PHP-DEV] Adding new closing tag =?> for keeping trailing newline From: mark@demon-angel.eu (Mark Baker) On 05/06/2022 10:23, shinji igarashi wrote: > I'd like to propose adding a new closing tag `=?>` 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