Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116444
Message-ID: <f7505852-8ce5-cc8f-4a09-ee4439d96d4a@gmx.de>
Date: Thu, 18 Nov 2021 11:43:21 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.3.1
Content-Language: de-DE
To: Hans Henrik Bergan <divinity76@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <20211118074647.muibn4mgfezzy75b@lucapetrucci.net>
 <CAGBsUrdhDPZmu7xZzpT-khcv1JfLG8qmRPsEOcVSVhRmRdpCQw@mail.gmail.com>
 <CAJmy8YFXGxiHw_XXMmM5uDV+RA6YNN+S93SO85aXK+obK7nWDQ@mail.gmail.com>
In-Reply-To: <CAJmy8YFXGxiHw_XXMmM5uDV+RA6YNN+S93SO85aXK+obK7nWDQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Proposal: &$result_code=null parameter in shell_exec()
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 18.11.2021 at 09:48, Hans Henrik Bergan wrote:

> while we're on the topic of shell_exec(), does anyone happen to know why
> shell_exec() pipes in *text mode*/binary-corruption-mode on windows?

I guess that is for historic reasons, where CRLF vs. LF really mattered
on Windows, and it's more common to get textual results with that
function.  There has been an RFC part[1] to change that, but it was
rejected.

[1] <https://wiki.php.net/rfc/deprecations_php_8_1#t_fopen_mode>

=2D-
Christoph