rfc:deprecate-backtick-operator-v2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
rfc:deprecate-backtick-operator-v2 [2019/10/31 17:45]
marandall Reference to arguments against in double quotes.
rfc:deprecate-backtick-operator-v2 [2019/10/31 17:46]
marandall
Line 40: Line 40:
 Should the operator eventually be removed, there would be a BC break that would require code using it to be updated to reflect the alternative mechanisms documented in "Program Execution Functions", specifically shell_exec which is functionally identical.  Should the operator eventually be removed, there would be a BC break that would require code using it to be updated to reflect the alternative mechanisms documented in "Program Execution Functions", specifically shell_exec which is functionally identical. 
  
-For most cases, this should be an easy upgrade route as there is a 1-to-1 replacement between `expression` and shell_exec("expression") (Note: As noted in arguments again, inline double quotes must be escaped), and should complete removal eventually become viable, scripts are already available to migrate, such as CS-Fixer with the backtick_to_shell_exec flag, see https://github.com/FriendsOfPHP/PHP-CS-Fixer.+For most cases, this should be an easy upgrade route as there is a 1-to-1 replacement between `expression` and shell_exec("expression") (Note: As noted in arguments against, inline double quotes must be escaped), and should complete removal eventually become viable, scripts are already available to migrate, such as CS-Fixer with the backtick_to_shell_exec flag, see https://github.com/FriendsOfPHP/PHP-CS-Fixer.
  
 ===== Proposed PHP Version(s) ===== ===== Proposed PHP Version(s) =====
rfc/deprecate-backtick-operator-v2.txt · Last modified: 2019/11/15 12:20 by marandall