Re: [RFC] Deprecate Backtick Operator (V2)
| From: | Björn Larsson | Date: | Tue, 08 Oct 2019 10:36:12 +0000 |
| Subject: | Re: [RFC] Deprecate Backtick Operator (V2) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-107414@lists.php.net to get a copy of this message | ||
Den 2019-10-08 kl. 12:24, skrev Christoph M. Becker:
On 08.10.2019 at 11:44, Björn Larsson wrote:Cheers //Björn LDen 2019-10-08 kl. 11:00, skrev Claude Pache:<https://www.php.net/manual/en/language.operators.execution.php>: | The backtick operator is disabled when safe mode is enabled or | shell_exec() is disabled. Thanks, then the third point above is not valid I presume.When evaluating the _unique_ cost of migrating legacy code, it should be balanced with the _continual_ cost of keeping the feature. That includes: * People wondering what that strange syntax does, or, worse, mistaking it with a variation of string literal. * Difficulty to search occurrences ofFor the third one, one idea could be to extend the current directive also working for backticks or create a new one. Would that be an improvement?shell_exec. * People trying to deactivate functions executing external programs (such asshell_exec) using the "disable_function" ini directive, wondering how to deactivate the backtick operator (since there is nodisable_operatordirective).