Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119861
Date: Mon, 10 Apr 2023 17:10:32 +0200 (CEST)
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>,
	Craig Francis <craig@craigfrancis.co.uk>,
	PHP internals <internals@lists.php.net>
Message-ID: <603015689.2450961.1681139432060@email.ionos.de>
In-Reply-To: <88aa408c-6941-bedd-792d-f8265f57bd00@bastelstu.be>
References: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
 <CAGBsUrcQWKc+JD2adprcgdqNAKr==McFeoYO3WF3pR2qxgon2g@mail.gmail.com>
 <CAMXcktN64EsoErjbFzdWe+qzM5RVYNR98WO8xcLOYxeYCK=NiA@mail.gmail.com>
 <CADK1yXJMgSrjCahW2_G-C=ye=mBiuWtQAKyJrbFc-W4ODL6fZw@mail.gmail.com>
 <CAGBsUrd=X6d8eZsSjaz+hQYLTCPCHPExhsawWhr8BWD=prEb1Q@mail.gmail.com>
 <E1957E21-F069-4E78-98F1-DAF14EE3D92E@craigfrancis.co.uk>
 <114465957.2449454.1681137473474@email.ionos.de>
 <88aa408c-6941-bedd-792d-f8265f57bd00@bastelstu.be>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
UI-OutboundReport: notjunk:1;M01:P0:DglKHfzy5ME=;UmJydh7qEw5VymlifckjSNX79ys
 aOIEkWCirv/WuLfvsEayix6TQ0HreEVxbw3REbmSvj9tihuooMUkaEzHb2G5XcBBcq1iXcWsF
 XczQ01VNyedkIydW5GYWQvIF/VxJuyMuFhwnU5ICjCpfEOZOcNhi0tAuxwuFRVX7LrWHq91um
 cWWUR7qIbsQ3lS9p0vJT48wfxxmIzL993L4mv9ITABtzLExOmra/2XOQAC0dSDl4QIHikqz+2
 cBDgGKaug3h+aov6ekGKQTX98CVHsdB+u0ZYlxSw/uC3X2/bpBh1p9QIoOr8QKOZhSlXi2uIb
 ta/r++AT9effrk69xlcX5NprN741RQ0s2+AX1WrMlevk0ufe5U06+LanPmCMyd5bJtUy5WSuD
 sepjb985U1YVbXd7bhIcIt2Qeq8vEywJvyUYY5pTEBOgC6+RYxB8pEgJtgW1Z9KClr8ZTV9Mj
 Rsc2VJiPPga+8CQoavFr4XWTTf5Vs0bneG+1jJDQAOWwxwmjBXpLKYvygguvH031VYQK0TTkq
 0KNDXLY9ylU5T+KXwEP3VtX61LKPt9eRBLePOaAR7hG0jd4WNl6AYePGMksgoVQ4f4gvTarbX
 aYggfaa/qqNPpgs9O40Ng+n7OdVYnFD2QormMEWOCVLHuAlotIXxp5A+oslDEYbzE5l+5h0Ty
 c+8X38B+qyKROHJXnKOfL6+N/3eo3z19SClDwAvYwg==
Subject: Re: [PHP-DEV] Future stability of PHP?
From: mails@thomasbley.de (Thomas Bley)

I don't want to say that everything in old code bases makes sense, I just w=
ant to say that mixing null and empty string was quite common in the past, =
mostly coming from accessing undefined array keys. PHP has always been good=
 to create new business value quickly. The problem now is that bringing all=
 code into new standards does not bring new business value, so companies tr=
y to delay or refuse the upgrades as long as possible (also thanks to docke=
r and others). Also many developers don't like upgrading code since it's ei=
ther too boring or too challenging. The first thing done is mostly silencin=
g deprecation messages, which makes the gap bigger when upgrading to the ne=
xt major version.
So having support for multiple php versions inside one binary would be a gr=
eat thing, same as modern web browsers still support html 4 even though htm=
l 5 is out for so many years.

Regards
Thomas

  =20

> Tim D=C3=BCsterhus <tim@bastelstu.be> hat am 10.04.2023 16:48 CEST geschr=
ieben:
>=20
> =20
> Hi
>=20
> On 4/10/23 16:37, Thomas Bley wrote:
> > Regarding compatibility promise, I'd also like to mention that things a=
re quite complex now, e.g.
> >=20
> > https://3v4l.org/VfAr4
> >=20
> > has 4 different outputs between php 7.x and 8.x. From userland perspect=
ive, having <?php8 or <?php9 would make things a lot easier and more produc=
tive.
>=20
> No, it has two different outputs, one for PHP 7, one for PHP 8.
>=20
> It also has two different deprecation notices, one concerning the=20
> behavioral change between PHP 7 and PHP 8 we're seeing and one=20
> concerning an upcoming behavioral change with PHP 9.
>=20
> However in all PHP versions the function call clearly is non-sense,=20
> because 'null' clearly cannot be a substring of a string, as it is a=20
> completely unrelated data type.
>=20
> Best regards
> Tim D=C3=BCsterhus
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php