Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114881
To: Stanislav Malyshev <smalyshev@gmail.com>, internals@lists.php.net
References: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
 <28be190c-21ea-b796-cec7-b8db21d14eca@gmail.com>
Message-ID: <b195f5db-cd29-93e6-d371-42ed42486a23@gmx.de>
Date: Tue, 15 Jun 2021 12:33:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <28be190c-21ea-b796-cec7-b8db21d14eca@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.1
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 23.03.2021 at 06:04, Stanislav Malyshev wrote:

>> t fopen mode
>
> I'm afraid there's - despite the warning - a bunch of code for Windows
> that relies on "t" and I don't think we should be breaking it. Is there
> a good reason to drop this mode?

I don't see much need for 't' mode nowadays.  Even Notepad properly
handles LF fine for some years now.  It's not really bad, if it can be
explicitely specified.  However, deprecating 't' mode would pave the way
to sometime change shell_exec() to no longer use 't' mode, what is a
footgun when dealing with binary data.  So when using the backtick
operator on Windows, you always need to keep that in mind.  From my
experience, 't' mode causes more harm than good.

And if there is really the need for LF conversion, that still can be
done with an explicit filter.

=2D-
Christoph M. Becker