Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117874 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 61935 invoked from network); 8 Jun 2022 11:02:02 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Jun 2022 11:02:02 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 391661804C6 for ; Wed, 8 Jun 2022 05:48:02 -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.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,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-yw1-f169.google.com (mail-yw1-f169.google.com [209.85.128.169]) (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 ; Wed, 8 Jun 2022 05:48:01 -0700 (PDT) Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-30ce6492a60so207677817b3.8 for ; Wed, 08 Jun 2022 05:48:01 -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 :cc; bh=HOH4SdI0jDg6nWrqDcNNXdNPhMR8GRhesHZNoN+aUOo=; b=X67Ws8OOepbhbycJb3paU5x82JPLzPVdPYnB/lVweysywmglXzAehjEzhhktGd5uAA 7vPP3jFy0BYsiQvojXnVc+y1hMerKTpztEvj9MYBN2Wsp0RoilAXw5BJnTDbqqncphqT eS3dJKExITJsc9UwzvwrNyPMKcCRchQLQq4Jcu3itpYyjqDd6BHItYPyxTpMBvLzNjf9 t9eB6QCZH3u/S+xC0xxUaFFiZm3nExeByYVc5qlvE07hSLDb1Iyeefi5/QPLdAI9z5R1 co7nqradiakpUHSiAhgWBlTTwpEXwkeDVhsPZoeC1J7lr8XE6/PoZ7mp4yiyAN/VBHwG AVaQ== 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; bh=HOH4SdI0jDg6nWrqDcNNXdNPhMR8GRhesHZNoN+aUOo=; b=meTwEBZCCGWLXk/tAbErOGcBJU/tHuBSy9sxMjBtLtxhGjj3c5bFkKaSlsy0DJc1s2 YYblNojMtXppvMrQ/KxA7AXjSVvY5pBA+j72NC96wFRIKTJQ3k6+OD5qhomBLitxcsML dXCXjRgSXQm0m/can6PEKPqjn5lsvuu+3KJr+vcYqER9+Q+FUs319Uu/ly8XNb5O9Ucy yle90a5bbwQAAL0253wsln/ZdejFZdYWtJqErhL+q59kI7hkFhideFkiiP+kb0Xb+mQ6 lst+ljKE4QB7ZjN/KsXAkoMnpIvWJX+6z24Ludq8bVv7xGH07gveXOmWvu1cdUxXuB9Z FCJg== X-Gm-Message-State: AOAM533m3dwskcODqmHUtYr0cBW/BzjgcnudbAgwFif+hCXY/U1Fm50p a1GARILRpREtj5v1v9RqyxPEpic4K6BphOVTDSfeiZDUnA== X-Google-Smtp-Source: ABdhPJzZruZbBxKYwH/AhPIotpcWD6Kzbz0hZxkAhvIBU2kQXxEOU8oxIEYgFdpXFMDrZyb1JGOpH72D4Vj7kPIh6gw= X-Received: by 2002:a81:c54a:0:b0:2d6:435a:5875 with SMTP id o10-20020a81c54a000000b002d6435a5875mr36018093ywj.181.1654692481225; Wed, 08 Jun 2022 05:48:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 8 Jun 2022 14:47:50 +0200 Message-ID: To: shinji igarashi Cc: internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Re: Adding new closing tag =?> for keeping trailing newline From: guilliam.xavier@gmail.com (Guilliam Xavier) Hi, > https://github.com/php/php-src/pull/8708 > https://www.reddit.com/r/PHP/comments/v5le6h/adding_new_closing_tag_for_keeping_trailing/ Thanks for proposing! this "feature" bothered me more than once... Maybe just 2 days (of internals and Reddit feedback) is a bit early to "give up" (but I won't blame you either). FWIW, the Twig templating engine has distinct delimiters for output ({{ ... }}) and control ({% ... %}), and the former does *not* eat newline; for the latter you can use ~%} (https://twigfiddle.com/54daye), and there are other "whitespace control" options (https://twig.symfony.com/doc/3.x/templates.html#whitespace-control). For PHP, if we could ignore BC, I would rather have ?> not eat newline, and add an optional way to do it; but we can't, so I guess the opposite (e.g. your =?>) is the best we could hope for. Regards, -- Guilliam Xavier