Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123584
Precedence: bulk
MIME-Version: 1.0
References: <CAPyeZ4O2rK+2ApuE-YLc7j_Z2LcT29yHcLYXvB0oGs-D_zTSag@mail.gmail.com>
 <D0449280-7113-48A3-979B-7995051B622C@php.net> <CAAKU0ukrRTWiaNXgD+OLHYGaUaE9V4k4m4Xxi=CLN8Te03UMTw@mail.gmail.com>
 <CAPyeZ4MqsTD=xdC=gnHmOrQqg3SW5JOLfhaNywj8gy3VZx7QkA@mail.gmail.com>
In-Reply-To: <CAPyeZ4MqsTD=xdC=gnHmOrQqg3SW5JOLfhaNywj8gy3VZx7QkA@mail.gmail.com>
Date: Tue, 11 Jun 2024 09:40:31 -0600
Message-ID: <CAAKU0un0gqFDvN6hTMbw2gNL6YnaSnF50Ea165zjHD0yJvfPKw@mail.gmail.com>
Subject: Re: [PHP-DEV] Revisiting case-sensitivity in PHP
To: Valentin Udaltsov <udaltsov.valentin@gmail.com>
Cc: Ben Ramsey <ramsey@php.net>, php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: levi.morrison@datadoghq.com (Levi Morrison)

> Could you, please, elaborate on why you propose to target 9.0? That would=
 make perfect sense if PHP strictly followed semver, but we always have som=
e BC breaks in minor releases (https://www.php.net/manual/en/migration82.in=
compatible.php, https://www.php.net/manual/en/migration83.incompatible.php)=
. So, is there a real difference between 8.4 and 9.0 for this case? Or do y=
ou mean that this BC break is way too big for 8.4?

Generally, the allowed backwards compatibility breaks in minor
versions are also minor breaks. These are mostly changes in extensions
rather than the core language. This change is in the main language and
it's potentially quite a big one.

Additionally, if this RFC were to pass, we would want extra time to
revisit the casing of suspect items for the same version. For example,
`Pdo` vs `PDO`. There's just not enough time for PHP 8.4 to do this.

> Levi, if we bundle namespaces, classes and functions in a single change, =
will that be easier to implement? Basically to remove lowercasing and put t=
he original type names in the lookup tables?

Yes, doing it all in one pass is easier to implement, and would
provide minor CPU and memory improvements.