I totally agree to deprecate and remove it in 8.0. Some reasons:
It usage is very rare (actually, I don't remeber the last time that I see that in use). Even in old codes. It too could causes confusion with single-quote in some fonts, sizes and styles. Is more easy to identify shell_exec() than backtick usage, anyway. It have exactly the same behaviour than shell_exec(). Do not need adapt usage beyond of the replacement itself. Some keyboard layouts (like mine, ABNT2) requires to press shift+backtick key then space to print a single backtick. Other option is I print two backticks at sametime (is what I do when I work with Markdown). Backtick inside backtick requires a most rare slash backtick to escape it: `\`` (actually, I even know if it works haha) Bonus/curiosity: is hard to find the definition of backtick if you don't know the name of this symbol in english. In portuguese it is called "acento grave" (something like "grave accent"). The remotion of this "feature" will allow use the backtick character to another thing futurely (which could be decided carefully). Or even unused forever. Em 12 de fev de 2018 5:43 PM, "Wes" <netmo....@gmail.com> escreveu: > Again, the reason is: in case in future PHP wants to use backticks for > unicode strings, like javascript. > If the community think it's feasible, in PHP 9, 10, whatever, it must be > deprecated asap. > If you think PHP should use a different syntax for unicode strings in > future, you vote no. > It's as simple as that. I am asking to reserve a particular syntax for > something that could be needed in some years. >
