Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90071 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22790 invoked from network); 5 Jan 2016 05:52:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 05:52:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=mdwheele@ncsu.edu; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mdwheele@ncsu.edu; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ncsu.edu from 209.85.217.195 cause and error) X-PHP-List-Original-Sender: mdwheele@ncsu.edu X-Host-Fingerprint: 209.85.217.195 mail-lb0-f195.google.com Received: from [209.85.217.195] ([209.85.217.195:35817] helo=mail-lb0-f195.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/76-24214-61A5B865 for ; Tue, 05 Jan 2016 00:52:32 -0500 Received: by mail-lb0-f195.google.com with SMTP id tz10so17676871lbb.2 for ; Mon, 04 Jan 2016 21:52:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ncsu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CgQLt35MWORTiJXaLJC85mlN7J1Rnrsmk1np4mZa9AQ=; b=D5icGb/9vkYU7HorAtlp+VtvDZmAf7jMEo/VUPTdhKt4PjWZHAAqxPoSAcBcPOkoW+ 7eZe6vMGstPJyN69gfMfxJ66+jmH6rBHlc+Q1mxyS76N7E/9mY0J4GAnrly5ILaEIZqd uCwG0Oko72Ey/yKkdIQPlmNUjDwzaaw8Y5wYLDcWR8XmDdkexQfT5ziZSir84fMpYV/S gb3cv2kCgk4XyFwdPCwTm7q/xjUBrHF83JdIZiQMUUyqQGceMJTb3sy1XaJzDA25ep1s AWbkCkARMysBvr5k7Zb1ejgq5g+a2sCaSKbb0ne6KTSarZIIpbpfOtcADoqG93f8nefh oLAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=CgQLt35MWORTiJXaLJC85mlN7J1Rnrsmk1np4mZa9AQ=; b=IQe6wY+bSOUMYxWM2OVQP1RlcIj0YzK3hVJs3k8UBn3PRbPgJVwTcAfEfwr4ZzwueK NvHIyzpzoQju/FHkw/EIG7aBkxm7jkNaa7uE6bqYRIqrnU111f25FCnu6Esy7YSlMG+J 0/+6327AZJDXEg8EkMYh0G3om5ZUfp5VLVc6Mooh5zQIvDE4laf1ssKRT3B44J1bcrD2 v1fhMWNE5/PiZcp8QlwDsG2vVwh+Fnnz2BWto6gymUCWYE0j48xBBkNjb0Wiu/B3jMfp jEa5QwnN2ujWq6HuBku5/shxk70/pre7XTrkJIVQ8wX0sY+ujnjHdwowqy604ViQnq44 qoXg== X-Gm-Message-State: ALoCoQkQUvzpzB/5aDDYl16Fg8ol8yCm617LJy2OKHCNtBaXm88YoCmGxNajk+tjA/m+9C57fzkOCr8IIqvlgaxe/EpYL/zaWZTqp1oZaBy4pQbXLtLZv1s= MIME-Version: 1.0 X-Received: by 10.112.141.201 with SMTP id rq9mr32082602lbb.4.1451973127172; Mon, 04 Jan 2016 21:52:07 -0800 (PST) Received: by 10.112.164.193 with HTTP; Mon, 4 Jan 2016 21:52:07 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Jan 2016 00:52:07 -0500 Message-ID: To: Sara Golemon Cc: Junade Ali , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol) From: mdwheele@ncsu.edu (Dustin Wheeler) Hi, chiming in from the side, On Tue, Jan 5, 2016 at 12:45 AM, Sara Golemon wrote: > 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? > I think this is an excellent compromise worth discussion and can vouch for usage of this suggestion in our environment, today. I maintain a shared hosting environment of sorts and have many different developer groups working in that environment. This is the sort of configuration we would take advantage of immediately. Thanks twitter/@Beryllium9 (wherever you are!) + Sara, -- Dustin Wheeler | Software Developer NC State University m: mdwheele@ncsu.edu | w: 5-9786 "If you don't know where you're going, it's easy to iteratively not get there."