Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94774
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.214.53 as permitted sender)
MIME-Version: 1.0
References: <CADVQu1S0FNSqM3AHL3X1_x6TgOKOPR7WxPUPYOLtMdfS_HtOaA@mail.gmail.com>
 <CA+kxMuRYN26YaFWRaSZcsS4D_3xrpSBzEBkjzJ=0jOXHnL=rEA@mail.gmail.com>
In-Reply-To: <CA+kxMuRYN26YaFWRaSZcsS4D_3xrpSBzEBkjzJ=0jOXHnL=rEA@mail.gmail.com>
Date: Mon, 01 Aug 2016 09:03:27 +0000
Message-ID: <CADVQu1QBbW9wpsyxdvLKPaVGQcJdwush1z+qKyR8Qdr6WQ4aQw@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c049e922f39ff0538fee05b
Subject: Re: [PHP-DEV] [RFC] E_NOTICE for invalid array container
From: dave@mudsite.com (David Walker)

--94eb2c049e922f39ff0538fee05b
Content-Type: text/plain; charset=UTF-8

Hi Dan,

I left it blank to go along with default production ini-settings where
notices would be excluded. However, you are probably correct that it should
be noted for development environments as something new. I'll toss it in
there in the morning

Thanks
--
Dave
On Mon, Aug 1, 2016 at 01:14 Dan Ackroyd <danack@basereality.com> wrote:

> Hi David,
>
> On 31 July 2016 at 20:31, David Walker <dave@mudsite.com> 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
>

--94eb2c049e922f39ff0538fee05b--