Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107325
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <CAF+90c99w6Uk+P8rm_p0Pd3iKsBKQqAbBjs2Zzwb5vGW9-snhQ@mail.gmail.com>
Date: Thu, 26 Sep 2019 10:31:35 +0200
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <FD053AC9-B174-4A90-8F3C-CECD5F2CFC9F@cschneid.com>
References: <CAF+90c_Ds+UNZB4hAi1989SRafb=d1JkP2q4pdwkUUXfcHrLCw@mail.gmail.com>
 <CAF+90c99w6Uk+P8rm_p0Pd3iKsBKQqAbBjs2Zzwb5vGW9-snhQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [VOTE] Reclassifying engine warnings
From: cschneid@cschneid.com (Christian Schneider)

Am 26.09.2019 um 09:41 schrieb Nikita Popov <nikita.ppv@gmail.com>:
> * Remainder: 54 yes, 3 no. Accepted with 95% majority.

Just for the record:
The one I'm most concerned about here is the foreach on undefined =
variables throwing an exception.
While this was already promoted to a warning at an earlier stage it =
still allowed a program to finish with a well-defined result (looping =
over nothing does nothing).
Now this code will stop with an Exception and possibly won't produce its =
output.

I noticed this before the vote but as the mailing list was already =
flooded with the 'undefined variables' discussion I feared that there =
was no place to bring this up without getting personally attacked like I =
was for the undefined variables stuff.

Anyway, the vote is done, I said my piece and will shut up about it now,
- Chris