Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101834 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12311 invoked from network); 12 Feb 2018 06:19:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2018 06:19:42 -0000 Authentication-Results: pb1.pair.com header.from=thruska@cubiclesoft.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=thruska@cubiclesoft.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain cubiclesoft.com designates 149.56.142.28 as permitted sender) X-PHP-List-Original-Sender: thruska@cubiclesoft.com X-Host-Fingerprint: 149.56.142.28 28.ip-149-56-142.net Received: from [149.56.142.28] ([149.56.142.28:40306] helo=28.ip-149-56-142.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/D9-18020-4F1318A5 for ; Mon, 12 Feb 2018 01:19:32 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: thruska@cubiclesoft.com) with ESMTPSA id BAF413E885 To: Michael Morris , PHP Internals References: Message-ID: <2d34448e-f3da-16c4-781e-b308fae2302d@cubiclesoft.com> Date: Sun, 11 Feb 2018 23:19:28 -0700 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator From: thruska@cubiclesoft.com (Thomas Hruska) On 2/11/2018 9:45 PM, Michael Morris wrote: > 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 Or people don't like how PHP currently handles errors/warnings/notices and would prefer to handle the messages themselves in the same context of the running code (i.e. not in a global handler). I'd rather see the @ operator become a "most recent" message collector instead of purely an error suppressor. That way, the current behavior wouldn't change for existing applications but users could start taking advantage of whatever associated functionality is added. There are also significant security issues that arise when NOT using the @ operator. -- Thomas Hruska CubicleSoft President I've got great, time saving software that you will find useful. http://cubiclesoft.com/ And once you find my software useful: http://cubiclesoft.com/donate/