Re: [RFC] Deprecate Backtick Operator (V2)

On Tue, Oct 8, 2019 at 2:11 PM Stanislav Malyshev <smalyshev@gmail.com> wrote: > Hi! > > > 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 of shell_exec. > > * People trying to deactivate functions executing external programs > (such as shell_exec) using the "disable_function" ini > directive, > wondering how to deactivate the backtick operator (since there is no > disable_operator directive). > > These are not costs, since "people wondering" does not cost anybody > anything. People are free to wonder about anything, it's not a cost on > existing users on PHP. If those people are interested in learning > something, they'd read the manual and know. If they don't, they can keep > wondering, it's not an argument for anything. > > I was going to learn c++, but then I came across these weird operators >> and <<. At first I thought they were heredoc, but, that obviously wasn't the case. My next guess is that they were some sort of strict comparison === is more strict than ==, so I figured >> is more strict than >. That wasn't the case either. After wondering for a while what it could be, I decided to look it up. It ends up that you use it to output text. cout << "Hello World"; It was SO confusing, because they also have printf which can be used to output text. I decided that c++ is obviously a garbage language and gave up. Not sure why anyone would ever use it! > -- > Stas Malyshev > smalyshev@gmail.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Chase Peeler chasepeeler@gmail.com