Hi! > PHP to new generations. It IS confusing if PHP has more than one way to do > one thing, and if one of them is considered better than the other nowadays,
No it's not. At least no more than anything else in life. There's always alternatives to do something. And PHP has always been a language where having a convenient way of doing something that already has an inconvenient way to do the same has always been welcomed. > the other should be deprecated so that NEW code doesn't use it. Unless I > missed something, nobody in this thread has mentioned REMOVING backticks, This is not true, the RFC itself states: Although the deprecation notice itself will carry no backwards compatibility changes, this RFC is written with the intent that the backtick operator would eventually be removed in a later version. Did you read that part and conclude *nobody* mentioned REMOVING? How did that work? > just DEPRECATING them. You don't HAVE to follow the deprecation with a You don't have to, but the intent of this RFC is specifically stated as such. Also, there's no reason to deprecate it either, for the same reasons. There's absolutely nothing wrong with it except "it could make somebody to look in the manual, potentially, so burn it with fire!" > least you're stopping the bleeding and (mostly) avoiding new code being There's no bleeding and nothing to avoid. > written that uses the legacy feature. Otherwise we'll have this discussion > again in 20 years, with the same outcome. It would be nice if we didn't, but unfortunately I suspect we will. Sigh. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
