I'll chime in on the "What evidence do you have that this is not widely-used" ... in fact, I have seen through my PHP career this used very regularly, and training/workshop/class sessions at conferences still regularly teach this as the 'standard way' to handle shell commands.
So I think that this would have a huge impact on existing code, and I am similarly a huge -1. Is it funky that random backticks cause a shell action to happen? Yes. But there are a million funky things about PHP, and we strive for backward compatibility when at all possible. And there is no direct gain/need to remove this feature. Eli On Mon, Feb 12, 2018 at 8:16 AM, CHU Zhaowei <m...@jhdxr.com> wrote: > Hello, > > >But that being said, I do support the proposal. I understand people > >opposed to removing features for no reason, but nobody needs this to > >be an operator, it's not a widely-used one, and we all know if it was > >proposed for addition today it would have 0 chance of acceptance. > > > > How do you conclude that this is not a widely-used one? > > > > btw, you already hit the most important point. Why do we deprecate or > remove feature for no good? > > > > > in case PHP decided in future to use backtick enclosed strings for > Unicode strings > > > AFAIK, since PHP7, we have no plan for unicode string. > > > > Best regards, > CHU Zhaowei
