Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122228
MIME-Version: 1.0
References: <kii8EchCRNKJRI1IgoTQGYbxr2d0_BNN6dm4QrEFnWNaWLaH68cG-GioF5j6ebhIJv5wAVKdHojWk5XJqk9z_yL4cA0Fmb1KD0P19VrCiXU=@gpb.moe>
 <344c3e06-3822-4b20-9a6f-a58fb64929a7@app.fastmail.com>
In-Reply-To: <344c3e06-3822-4b20-9a6f-a58fb64929a7@app.fastmail.com>
Date: Mon, 22 Jan 2024 15:11:24 -0600
Message-ID: <CAJp_myUA1O9-9WBoncdQ5EyCPG_q5V5HfpuDXACjTjignpFggQ@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005ce1e7060f8f46d5"
Subject: Re: [PHP-DEV] [RFC] Deprecate implicitly nullable parameter type
From: mweierophinney@gmail.com ("Matthew Weier O'Phinney")

--0000000000005ce1e7060f8f46d5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 22, 2024 at 12:54=E2=80=AFPM Larry Garfield <larry@garfieldtech=
.com>
wrote:

> I am in support of this change.  My only concern is timeline.  This RFC
> would deprecate it in 8.4, and presumably support would be removed in 9.0=
.
> While we haven't discussed a timeline for 9.0, historically the pattern i=
s
> every 5 years, which would put 9.0 after 8.4, which means only one year o=
f
> deprecation notices for this change.
>

This is... not true. There is literally no established pattern for when
major releases take place, either by length of time, or number of minor
releases.

PHP 3 had no minor releases. PHP 4 had 4 minor releases before PHP 5
dropped, and then a minor release happened AFTER PHP 5 was already in the
wild (4.4). PHP 5 had 7 minor releases, with MULTIPLE YEARS between some of
the minor releases before the current process was adopted towards the end
of its lifecycle.

We are moving TOWARDS a fairly standard process, but there's no definite
plans for PHP 9 to follow after 8.4 as of yet, and the process does not
require it.


>
> Given the massive amount of code that built up between 5.1 and 7.1, and
> 7.1 and today, I worry that a year won't be enough time for legacy code t=
o
> clean up and it would be another "OMG you broke everything you evil
> Internals <expletive deleted>!" like the "undefined is now warning" chang=
es
> in 8.0.  (In both cases, well-written code any time from the past decade
> has no issue but well-written code is seemingly the minority.)
>

But I DO agree with the above. So this might be a time for us to start
discussing if/when we want a PHP 9 to occur.

>
>

--=20
Matthew Weier O'Phinney
mweierophinney@gmail.com
https://mwop.net/
he/him

--0000000000005ce1e7060f8f46d5--