Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107028
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A38A4F01-BD03-4CC6-B628-5A7C1B171CD2"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 12 Sep 2019 15:02:30 -0700
References: <076701d56978$86020910$92061b30$@php.net>
 <CADyq6sK4HektgfDpCCFR3=bumyPaf9vn=-WdvaboHybBQKd53g@mail.gmail.com>
 <078e01d5697c$5512bc10$ff383430$@php.net>
 <CAKws9z1EBSqCFy2wD3cEV49KDSJOd6tT04PrCkxG8+3Hb6WpTA@mail.gmail.com>
 <CAPKYkKw1EU3Qp6W7b19r4kMKPD1HntH+7NQSxSiDNcLXqPERMA@mail.gmail.com>
 <CAKuGYLRWF9jnS-Zs+uRFNN1pgRSvHFpW-FChgNq9Rk282AFFGA@mail.gmail.com>
 <CAPKYkKxUyeWWZY5OyDLtAYiDUYLkwyMjuc_Wq2Y++3C9CP6G1w@mail.gmail.com>
 <CANS-=pc7Av0+jSKNebb-iae+BpTt6_72kRSHSowb-hon4rxUgQ@mail.gmail.com>
 <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net>
 <CANS-=pexJhtBS=me8RDvg0+BjXWVqmONU4CDVyrGgcsia40YGA@mail.gmail.com>
To: Lynn <kjarli@gmail.com>,
 PHP Internals List <internals@lists.php.net>
In-Reply-To: <CANS-=pexJhtBS=me8RDvg0+BjXWVqmONU4CDVyrGgcsia40YGA@mail.gmail.com>
Message-ID: <9A26711E-5745-4F17-A006-5DE00B96DCE2@newclarity.net>
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_A38A4F01-BD03-4CC6-B628-5A7C1B171CD2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> Whenever one of these errors will occur, you can initialize either the =
array key or variable with null and it will work again without changing =
behavior.=20

Whatever the case, changing warnings to errors would require fixing =
working code. And for many people, that would requiring investing lots =
of money.

> However, I think most people agree that the quality of Wordpress code =
and Plugins is highly debatable.

That is probably very true, but it is orthogonal to whether or not =
certain potential changes in PHP would cause expense changes to be =
implemented in order for WordPress users to upgrade to an incompatible =
PHP8.

> If anything, Wordpress shouldn't be an argument to not improve PHP, =
though I think it's important to consider the impact of a change, =
including for the Wordpress community.
> I don't like the idea of not being able to progress because Wordpress =
users won't upgrade PHP.=20

I am not making that argument. I am simply pointing out that the changes =
being considered will almost certainly break a large percentage of =
WordPress sites and fixing those site will likely be very costly for =
site owners. =20

So it is up to those who have a vote on the future of PHP to decide if a =
large number of broken WordPress matters to them or not.  I am just a =
messenger.

-Mike=

--Apple-Mail=_A38A4F01-BD03-4CC6-B628-5A7C1B171CD2--