Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116443
Date: Thu, 18 Nov 2021 10:32:43 +0100
Reply-To: Luca Petrucci <luca@lucapetrucci.net>
To: internals@lists.php.net
Message-ID: <20211118093243.t7i2langi4celapv@lucapetrucci.net>
References: <20211118074647.muibn4mgfezzy75b@lucapetrucci.net>
 <CAGBsUrdhDPZmu7xZzpT-khcv1JfLG8qmRPsEOcVSVhRmRdpCQw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGBsUrdhDPZmu7xZzpT-khcv1JfLG8qmRPsEOcVSVhRmRdpCQw@mail.gmail.com>
Subject: Re: [PHP-DEV] Proposal: &$result_code=null parameter in shell_exec()
From: internals@lists.php.net ("Luca Petrucci via internals")

On Thu, Nov 18, 2021 at 08:19:36AM +0000, Kamil Tekiela 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
Hi,
PHP code that use the backtick operator or shell_exec() will behave identically.
The reason is that when omitting the optional parameter $return_code, the
function call shell_exec("command", null) is executed, which will
execute the "command" and return its output just like it does right now.

Thanks,
Luca