Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94784 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77204 invoked from network); 1 Aug 2016 22:27:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Aug 2016 22:27:11 -0000 Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.161.177 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.161.177 mail-yw0-f177.google.com Received: from [209.85.161.177] ([209.85.161.177:35316] helo=mail-yw0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E9/31-03293-EBCCF975 for ; Mon, 01 Aug 2016 18:27:10 -0400 Received: by mail-yw0-f177.google.com with SMTP id j12so185370154ywb.2 for ; Mon, 01 Aug 2016 15:27:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SeGwacWjsU3kdflCnWjHOAcuKkviDIuVM+/wjDq+8+U=; b=ko3P8RcBlTLW5sTDjVqydFC296VkwCO/7Y/piVrEjXo2FRrdPcUygyufAX3KVb3s5a PI+1yVPxSWnUQ7Q5eTxh7j9Ite/Ug2Rtx/WyojvNtkiP1O+e6IfgYgWIyOJkT7llKgnd E9lwVjMvYtOyO+2sH1Y49opJieG7Aa7ORZdip4g5wU2ZnxRPZXEaURVx3lj/Duhzw3G4 QFKxEulb0zdE9Ynxj0ZU2dAuu0Si/DkyiYRHwfZyIqAI8Z7pukUigW1JzV15VPbU6/1o fyzoShx+kEfzcryTWJ1bWRytK/s0Xu1nDhjCpno1Gr+Q2U9eLS858wqqwgv1DkRTG8Cs gFNg== 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:from:date :message-id:subject:to:cc; bh=SeGwacWjsU3kdflCnWjHOAcuKkviDIuVM+/wjDq+8+U=; b=kD4V10TYWSgJuRV2WPCbFDsSHNvvSeuYTdBBlgzWvvCoCdIMA9uAJdNmYuCLzmOa09 zj/Jx8wLObXo14GbftF8lZlHXz3Ui6k3iiLpLdcK1RFhO3yV6MJ1w2eLJv2fsHgEIf9V QVVE6MeAkUYP/vJLe3C3DbPyCqLOOULqCFWEgRuWmM2dHbrnqgg2cyR07WYmetY1mpik MJpdhXv3gW2YLR/18ypWGJ7u/RvyxJAQSoRgj6yGJBDCMlUOzFbcJJRGNiV2AXhWQHcG hTVKJlwVCgkQg2mEb0OWpI/yBJyAV+xpEPDi9k3sQxUO0QK3NHDq0xMviSkQyHgaazRQ /lFg== X-Gm-Message-State: AEkoouvUMh5R+zlBCZxMEt15IR+ov7jqmCU9ljfMCNLHd/dCYBZ7El83I6ANYtbQSs+ujSBi3lK3zLNOawxCRA== X-Received: by 10.129.83.213 with SMTP id h204mr51102666ywb.317.1470090427596; Mon, 01 Aug 2016 15:27:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.230.83 with HTTP; Mon, 1 Aug 2016 15:27:07 -0700 (PDT) X-Originating-IP: [2.99.225.239] In-Reply-To: References: Date: Mon, 1 Aug 2016 23:27:07 +0100 Message-ID: To: David Walker Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] E_NOTICE for invalid array container From: danack@basereality.com (Dan Ackroyd) Hi David, The updated section still doesn't really describe the BC break that well. Some people will need to change their code to avoid having notices raised frequently. How difficult that will be needs to be thought about. Additionally, although the default ini files may turn off notices in production environment, I really don't believe that is best practice. For my machines, in both production and dev all warnings and notices (except deprecation notices in production) are converted into exceptions. Anything else allows mistakes in code to go undetected. cheers Dan