Re: Proposal: &$result_code=null parameter in shell_exec()
| From: | Hans Henrik Bergan | Date: | Thu, 18 Nov 2021 08:48:30 +0000 |
| Subject: | Re: Proposal: &$result_code=null parameter in shell_exec() | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-116441@lists.php.net to get a copy of this message | ||
> then the backtick operator will not behave identically anymore. Am I
correct?
yeah kindof-correct, the backtick operator would then behave identically to
giving shell_exec() only 1 argument, or null as the 2nd argument
(btw i'm the guy that made the linked bugs.php.net feature request)
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?
On Thu, 18 Nov 2021 at 09:19, Kamil Tekiela <tekiela246@gmail.com> wrote:
> Hi Luca,
>
> How will this change be reflected in its alias, the backtick operator? If
> the plan is to change the signature of shell_exec() then the backtick
> operator will not behave identically anymore. Am I correct?
>
> Regards,
> Kamil
>