Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107370
Return-Path: <marandall@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84512 invoked from network); 4 Oct 2019 18:03:56 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 4 Oct 2019 18:03:56 -0000
To: internals@lists.php.net
X-Mozilla-News-Host: news://news.php.net:119
Date: Fri, 4 Oct 2019 16:45:22 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Posted-By: 5.69.57.161
Subject: [RFC] Deprecate Backtick Operator (V2)
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-107370@news.php.net>

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.

--
Mark Randall