Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107392
MIME-Version: 1.0
References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 7 Oct 2019 09:50:36 +0200
Message-ID: <CAF+90c9uXdqJsTizLCca-AswenZDv9-6yw=ranATp3XoutHyxw@mail.gmail.com>
To: Mark Randall <marandall@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a3ee9205944d4fd1"
Subject: Re: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2)
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000a3ee9205944d4fd1
Content-Type: text/plain; charset="UTF-8"

On Fri, Oct 4, 2019 at 5:45 PM Mark Randall <marandall@php.net> wrote:

> Hi Internals,
>
> I put forward the following RFC "Deprecate Backtick Operator (V2)" for
> discussion.
>
> https://wiki.php.net/rfc/deprecate-backtick-operator-v2
>
> I believe it is at least worth a discussion as to the pros and cons of
> deprecating this functionality, especially in light of the existence of
> better described and more well-known functions exhibiting identical
> behaviour.
>
> This RFC only covers the issuing a deprecation notice, and its complete
> removal would be contained within a separate RFC.
>

Usage of backtick operator in packagist top 2k packages:
https://gist.github.com/nikic/7b0afaf4d8b1a1087cdb61cd1e776594
There are 72 occurrences including duplicates.

Make of that whatever you will :)

Nikita

--000000000000a3ee9205944d4fd1--