Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117870
MIME-Version: 1.0
References: <CAH19jWht_1VBgZKWL8wfb5EL6oG8JQf1zxGN2nS7dswyVB9Pzg@mail.gmail.com>
 <CAH19jWhCnojDgXDbj+LAHnZk+ROPjmaAK2p1Q9f5TznR98bBTw@mail.gmail.com> <CAPzBOBPvz34-SefmFj3nTaAahqTqGmWm+i3z2VdAfe+FL9NTMw@mail.gmail.com>
In-Reply-To: <CAPzBOBPvz34-SefmFj3nTaAahqTqGmWm+i3z2VdAfe+FL9NTMw@mail.gmail.com>
Date: Tue, 7 Jun 2022 22:34:17 -0500
Message-ID: <CAESVnVrtQADCR6nUqHF-MmLdspuTH8ZE_B5fm1z_aFt7tMxryg@mail.gmail.com>
To: Robert Landers <landers.robert@gmail.com>
Cc: shinji igarashi <shinji.igarashi@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ea6c9305e0e76174"
Subject: Re: [PHP-DEV] Re: Adding new closing tag =?> for keeping trailing newline
From: pollita@php.net (Sara Golemon)

--000000000000ea6c9305e0e76174
Content-Type: text/plain; charset="UTF-8"

On Tue, Jun 7, 2022 at 10:27 AM Robert Landers <landers.robert@gmail.com>
wrote:
> FWIW, I think it makes a lot of sense, having used golang's template
> language (not everyone is generating HTML with PHP). I think you may
> just be dealing with a vocal minority and it would be worth putting to
> an actual vote. Even if it fails, we'll learn something the next time
> someone wants to change something like this.
>

While my gut response for the new end tag is in the "no" column, I do
wonder if we can accommodate "non-html" scenarios in a broader (maybe more
palatable?) way by assuming that if you want the newline to be respected on
one line, you probably want it that way for the whole file.

<?php
declare(ignore_newline_after_close_tag=false); // defaults to true, i.e
existing behavior

This would avoid any new syntax rules, but still provide the ability for
php-as-template-engine to behave in the user's preferred mode.

-Sara

--000000000000ea6c9305e0e76174--