Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94772 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15617 invoked from network); 1 Aug 2016 07:21:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Aug 2016 07:21:47 -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:36646] helo=mail-yw0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 04/00-15377-988FE975 for ; Mon, 01 Aug 2016 03:21:46 -0400 Received: by mail-yw0-f177.google.com with SMTP id u134so165095486ywg.3 for ; Mon, 01 Aug 2016 00:21:45 -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=t8kUtsEP7BIQepp5cvTqij0KMPT8kB0hAmLU2uCJzeU=; b=00aMWuECTSWzh1Se3Hd9ZU7YzLlxy110aWCnssnv29uE3PmrpAft20wr0cxQ/6k1OC iiBuQ3Q7NMZ4t5lzoQiNE6YATT5bOtW+7U5v+0vlRrhxNqhCJKTZXdWxIIpT3mupTlk9 z2EDKBSkWUKiX9bMSD0EGr3s9ZVaMAjr7Hl6GPlSowyKr7aPqQRGSBqsK2zqCJnxzx/O 3xNCLE+KbYoNXP+c3taIW/bo0WGx7LE+ijLCZticaeT5jWpmO/PvddVfcemoiPdQ8Et4 Me8+dVTgzGEL5sbURf+jJtyC5KUe5G+0KfRvgS77wKL3PhpUh42sbY8km9sNBjpfcyoI 2F8Q== 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=t8kUtsEP7BIQepp5cvTqij0KMPT8kB0hAmLU2uCJzeU=; b=DuAJYnSf3Lb8VCXuyHzszNd46ACyklCHrYEZWJeKNvF6PAPcNlNukvLfLA981s0p2m mfQFf0JeZhoxL+XcihRB1ZvYDzKv3lsSwtV1GbOpSRysPiKYssqv9DQ6V+klBMtxAPDS Wa9Tg65DKwXjnCPAjjG0JRO/K2RRiEm9/191vHcOKF3zJk1jOlQuUuRkFrNL68rI7zOJ K27bsP2CG9DYNhw7KRXFpM5mpUoRESreqMfV5h84JKBzqzB/J2hOGgdSKti4h5AbEfw2 40xrRYrTdldkqVI0ZHaffuaLfYpA0Uo7xGCWMQVe3sMy1Z8m9zz33hBVo4/tOqebLqVo 9LYg== X-Gm-Message-State: AEkoouvZHIcuVNGSzxJ3Fxgs5hWcwiIGjwZ6sVq7jaXZcx0viaZu2JTennVp0q0bI+RStRqleGAGW7bZ9hR2vQ== X-Received: by 10.129.51.215 with SMTP id z206mr43374757ywz.251.1470035656376; Mon, 01 Aug 2016 00:14:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.230.83 with HTTP; Mon, 1 Aug 2016 00:14:15 -0700 (PDT) X-Originating-IP: [89.242.231.216] In-Reply-To: References: Date: Mon, 1 Aug 2016 08:14:15 +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, On 31 July 2016 at 20:31, David Walker wrote: > So I want to solicit for more discussion given previous talks. My > first-attempt RFC for this is at: > https://wiki.php.net/rfc/notice-for-non-valid-array-container > I've very likely to support this RFC, however the section on 'Backward Incompatible Changes' needs to be filled out, as this RFC would make code that currently emits no notices, start emitting notices. cheers Dan