Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101838
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAOv67guxH2CN5oAOj=+v_U94D_J42Q2MZJzWgVAmwe519-AOPA@mail.gmail.com>
References: <CAOv67guxH2CN5oAOj=+v_U94D_J42Q2MZJzWgVAmwe519-AOPA@mail.gmail.com>
Date: Mon, 12 Feb 2018 13:43:56 +0200
Message-ID: <CAPhkiZzpKPeJKnR7f+JMQ-8zS87_2g7WWcyhgwwoJNKHz6uf_w@mail.gmail.com>
To: Wes <netmo.php@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator
From: narf@devilix.net (Andrey Andreev)

Hi,

I agree with the criticism towards the RFC contents raised so far.
It's obviously put together with as little effort as possible, and the
cheeky version number doesn't help either ... Treating the RFC process
as a joke doesn't get you support.

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.
Also, I would go for E_DEPRECATED now + removal in 8.0 without further
future scope. IMO, it should be common sense to get rid of obsolete
features, and therefore the token doesn't need to be repurposed for
this to be a good idea.

Cheers,
Andrey.