Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90086 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65696 invoked from network); 5 Jan 2016 11:57:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 11:57:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.45 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.213.45 mail-vk0-f45.google.com Received: from [209.85.213.45] ([209.85.213.45:35645] helo=mail-vk0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/1C-24214-ABFAB865 for ; Tue, 05 Jan 2016 06:57:48 -0500 Received: by mail-vk0-f45.google.com with SMTP id k1so137952474vkb.2 for ; Tue, 05 Jan 2016 03:57:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zend-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=NwFJPyRw4GedzQ+qvTeT0BQC9cb9Q0SRB7zqyod7jHs=; b=KDPUjkr3K4GA/s1ld0CxrG7zmHReMf2O2wIWnG7DdbXrfq/qzHMedSC/J8ZBxUC+j9 RWTFG1KgrnN2wjDo0ft8VaHRZ+76T3GrINXnNjLfko9phAEZPwpiRDSponHva/Tvj9/u LuRBdcXIhIY9Cpxb2tbDHqTEMR3Joue+MBIbdqV4PzTIoa4E204Zt/kr2USfxiTvJb8p eAf/rsOZiamy+jw1yBGXD/79gR4u5yiz6LohTcyXhYeH66J8nsP0WRIh1bYfsDPH3emX dgB82cCP9zrx7ffuCcPbbCqwYui2jhppQOp8jPI0D3KQtpG0iR0sp/g9PELdgCQSvxxI 9vFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=NwFJPyRw4GedzQ+qvTeT0BQC9cb9Q0SRB7zqyod7jHs=; b=FIzRnP4wpuRJWlhM5pViLckYyN7vElAyP4RhdZSbFLP863W/zQiZOycqIgAZ9uxJCz VVF5KS3zLP1IDnLwGz1fddEDzrA2cZKbYatTXw4IFntfVOj7RE7VyUN9RkTGniWiwVyv 9wr7SHUvK6PmapxiGXzlPDzeoRXeWeGAOAhd0qXrAXFBqP/I/FNjaJcKlW/ISVrEU+OR UL3pmeo/KU64BHr/s4hZ5ysz/5AD02J8aK2UIrSLHwKSJBV2d3V12BVUUNzmv/MnXQzN WEV33gJZoPhHzIzIyr6be9y3WT8X7fELPZwl8YwfX50UAJItizP7KWXxatRen1DHBoNG i0Jg== X-Gm-Message-State: ALoCoQlvcK9/+iwaSFxiP0ofNqssjHIeilMXdXdAOnFmabUPBQfV5xut4Ohq7zL9Hp6rIkR/HI/cQuRAgzBbkk7F88pSQAJGCU1/c2dAlN/6EUwglx6pxkdvRfUjLjVV0AoEOuBvZZR5NO2wGN6IiG3+y99N13JFCxf1UYS7WMy4xzqEJ4iK94dNXKd50CIbLg9YKT+TJbIKqsgL0KFaMVWFRcyTVgB3KQ== X-Received: by 10.31.153.85 with SMTP id b82mr29151925vke.121.1451995063352; Tue, 05 Jan 2016 03:57:43 -0800 (PST) References: In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQMJBqo1qnQD/nq+9hU9B/h7PCSF7AHxTsJ2Agx7FWUBqJV1MJxQH/kg Date: Tue, 5 Jan 2016 13:57:42 +0200 Message-ID: To: Derick Rethans , Michael Heap Cc: Sara Golemon , Junade Ali , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol) From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Derick Rethans [mailto:derick@php.net] > Sent: Tuesday, January 05, 2016 12:57 PM > To: Michael Heap > Cc: Sara Golemon; Junade Ali; PHP internals > Subject: Re: [PHP-DEV] Deprecation of the Error Control Operator (@ > symbol) > > On Tue, 5 Jan 2016, Michael Heap wrote: > > > > > On Tue, Jan 5, 2016 at 5:45 AM, Sara Golemon wrote: > > > > > On Thu, Dec 31, 2015 at 6:52 AM, Junade Ali wrote: > > > > I am looking to submit an RFC in order to remove the error > > > > suppression operator in PHP, namely the @ symbol. > > > > > > > Forwarding a suggestion twitter/@Beryllium9: > > > > > > How about a global "disable error suppression" setting? That way a > > > project lead could enforce it for their codebase (and guarantee that > > > devs "aren't lazy"), but PHP doesn't lose its pragmatism? > > > Sounds like the xdebug.scream or the Scream PECL extension ( > > https://pecl.php.net/package/scream) to me. > > > > +1 for baking this functionality into core > > That's going to mean an INI setting.. that hosters could abuse. Having an INI > setting like this as part of core is IMO not a great idea. I agree. Perhaps through a declare() statement instead? We could easily make it file-based, so that the declare() statement only affects the local file, or we could make it global for the entire request. Zeev