Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101831
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 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: Sun, 11 Feb 2018 22:45:08 -0600
Message-ID: <CAEUnE0ciY1CdvDC3hi=TP_GXaQabKjTPZQo5mXUo_AKOrnKDGg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a1141e72ee8c3630564fc8ab5"
Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator
From: tendoaki@gmail.com (Michael Morris)

--001a1141e72ee8c3630564fc8ab5
Content-Type: text/plain; charset="UTF-8"

On Sun, Feb 11, 2018 at 1:41 PM, Wes <netmo.php@gmail.com> wrote:

> Hello PHPeople, I present to you... the shortest RFC ever.
>
> https://wiki.php.net/rfc/deprecate-backtick-operator
>
> Let me know what you think!
>

-1, not that my vote matters, but huge -1.

Nothing of value is gained by doing this. If there is something of value in
doing this, or some far future feature this clears the way for, please
enlighten me. But from where I sit this does nothing but break code for no
reason. And yes, emitting E_DEPRECATED is a breaking issue for any code
base that prides itself in being about to run all it's units with E_ALL set.

If we are going to go about removing stupid operators in PHP, the current
use of @ as an error suppression operator is much higher on the list since
encourages people to write bad code by sweeping problems under the rug, and
removing it would allow the operator to be reassigned to use as an
annotation operator as seen in Java and other language.  I'm not holding my
breath for that to be done either.

--001a1141e72ee8c3630564fc8ab5--