Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107405 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 4289 invoked from network); 8 Oct 2019 05:49:40 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 8 Oct 2019 05:49:40 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 9BF202D1FAB for ; Mon, 7 Oct 2019 20:31:57 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FORGED_SPF_HELO,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8075 40.64.0.0/10 X-Spam-Virus: No Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-oln040092003091.outbound.protection.outlook.com [40.92.3.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Mon, 7 Oct 2019 20:31:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DF2oOsocqmy+hnMUJxfnegq5ycMhkknezAci9OCs/Bykgzts3aSeokAf9x5dx05Eoj0J98dGmXskMEHecur1esvXbZAPEHaA27LQx8v4bVROd4SjKyzn2ZIEI0fEv/hX07P7mi0Bl55u5H6qCD6KLpxZJH5t/Qn7UlCZeIBqecsOvS5eii+2csLdZT7KCZFFCd2j2q6CWyICTm8lvDi+K3AQaAE3xSObngmKgxA+O+27GoRPq6H1uacLWW9jPYi8et7Qn3szZTZYCaCf04+ZYcfpUrqN/WFvG5fJ3WqXpZJENxxXmlyGyVf/1xVQjeQpKSYhjJ8vR8BrYLHJlAEjow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D/I/mRz3CxAKG7TbwQnKn9JIds4LfPEFvg5hpf4XhZA=; b=R1gIaN22CKUDLnuEM8wimUqtkRoeD/F7lSE9X+fWyBFJ6JOyDwXPHsRe+ezWkuZ4EJlzOKIXQuExdvj2243Ud6yZt5IBLFvh+hMgD/ANd/ubOltHxFNJG8tOiaqMpnu+d9L5p+m9jrfbxBOK/Oe0VXfXFWFE7iCvHvbuK8WJegu8uUAz5EdG0LQx9jAW0LHeQlJk2IlgWeeK2utIVT8y+5kL6+LnaejAJM5Ce1xYZ1r935ecxn6VbegDrfI+c5F4kWGceii+AbFD3NB1rg5sxAVgYvQAO7HUe0bK7OnxOdhM9Loxv00iTii6yroA2k4eZZsUzauSCWmEzMeu1Dn9gA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D/I/mRz3CxAKG7TbwQnKn9JIds4LfPEFvg5hpf4XhZA=; b=J19Ddfawr6ygloh2Ne3KojBXN537D7IInoRedPwmT89vz1i9/u4rCc9L2phK9i5HJBFR7YdJcadcQJ62jQ51gdd4wK8NdItAb0IHnN/xhbP+AOvlttGZCHgm98+E6OS5yWAs62pGWjkIq3rONBBd2T2q37HOmk9UFbxK2uS3cytnjRrw7eUNt175mkKX8JyK9O8g3GAI3emZdziG0wxLuZWoGiFVuSqQ8J7aPQw7eD+try8+dSC9IvcsXb1IeP5HaSFp22CSCidcoL05dSoB/waPKxp6Gbq1TgN88W5V+fLeQRciwgMwpk5/9AHQf8XDHO2dZWCqtNKle99Z7NbuEg== Received: from CY1NAM02FT060.eop-nam02.prod.protection.outlook.com (10.152.74.56) by CY1NAM02HT029.eop-nam02.prod.protection.outlook.com (10.152.75.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2327.21; Tue, 8 Oct 2019 03:31:52 +0000 Received: from DM5PR06MB2857.namprd06.prod.outlook.com (10.152.74.58) by CY1NAM02FT060.mail.protection.outlook.com (10.152.74.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.21 via Frontend Transport; Tue, 8 Oct 2019 03:31:52 +0000 Received: from DM5PR06MB2857.namprd06.prod.outlook.com ([fe80::b13e:2790:77d7:ec78]) by DM5PR06MB2857.namprd06.prod.outlook.com ([fe80::b13e:2790:77d7:ec78%6]) with mapi id 15.20.2327.026; Tue, 8 Oct 2019 03:31:52 +0000 To: Nikita Popov , Mark Randall CC: PHP internals Thread-Topic: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2) Thread-Index: AQHVfObHTKAn3OaiRE2fNwypPg53F6dQBJrC Date: Tue, 8 Oct 2019 03:31:52 +0000 Message-ID: References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:0E3145ED1B070D5336DDA7995906B1637ECE9166ABFECA790B9F4D07F95077D5;UpperCasedChecksum:82F5706345C47D7C951C18A926C76E2899369ABE8751564637D2E9541829B911;SizeAsReceived:7015;Count:45 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [683Cs9efbF6sXls3v75hMKfm20L8/fWR] x-ms-publictraffictype: Email x-incomingheadercount: 45 x-eopattributedmessage: 0 x-ms-traffictypediagnostic: CY1NAM02HT029: x-ms-exchange-purlcount: 3 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: v0wxFAtY7JO8gjKo0K9LNm0DBt8ph1oCo2BWGTrZy5J+kv6dJ/mZAYbYRS84TmLEmvz49OTAfQW5IbEQ8RNHcWD9zNMsEaSvbkCBXBmJgpU+/KT1x+b1nBhBTszLgZR9gncFrxRLwyx2hSw+vOpZR22aDJ7NqOKuQb3JorHWMHoiS5okCx9Be6FHKi8tQwMxVGSooS/A2aITj+o39iYHt4xxz6NqWwthVrasY8QdhZw= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 10918b1c-cb64-4914-935a-08d74ba00fb1 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2019 03:31:52.5421 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1NAM02HT029 X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2) From: theodorejb@outlook.com (Theodore Brown) On Mon, Oct 7, 2019 at 2:50 AM Nikita Popov wrote:= =0A= =0A= > On Fri, Oct 4, 2019 at 5:45 PM Mark Randall wrote:=0A= > =0A= > > Hi Internals,=0A= > >=0A= > > I put forward the following RFC "Deprecate Backtick Operator (V2)" for= =0A= > > discussion.=0A= > >=0A= > > https://wiki.php.net/rfc/deprecate-backtick-operator-v2=0A= > >=0A= > > I believe it is at least worth a discussion as to the pros and cons of= =0A= > > deprecating this functionality, especially in light of the existence of= =0A= > > better described and more well-known functions exhibiting identical=0A= > > behaviour.=0A= > >=0A= > > This RFC only covers the issuing a deprecation notice, and its complete= =0A= > > removal would be contained within a separate RFC.=0A= > >=0A= > =0A= > Usage of backtick operator in packagist top 2k packages:=0A= > https://gist.github.com/nikic/7b0afaf4d8b1a1087cdb61cd1e776594=0A= > There are 72 occurrences including duplicates.=0A= > =0A= > Make of that whatever you will :)=0A= =0A= =0A= I did some further analysis on the output of Nikita's script.=0A= Ignoring the duplicate WordPress package, all the occurrences=0A= are in just 21 unique projects.=0A= =0A= In 8 of these, the backtick uses are exclusively in test files or other=0A= scripts not part of the library source code. Then there are 11 packages=0A= with one or two uses each, and only 2 packages with more than two occurrenc= es.=0A= =0A= Raw numbers: https://gist.github.com/theodorejb/584f2a1e27e93fb5da2d9b0e8e7= a0d34=0A= =0A= Best regards,=0A= Theodore=