Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116766
MIME-Version: 1.0
References: <CAFv4g+Efz-V5V1uUedXpusNw6z-on=TT3kdWgC66SptSd8kB4g@mail.gmail.com>
 <64e5155a-2ee8-5ae0-5ee4-248712741911@gmx.net>
In-Reply-To: <64e5155a-2ee8-5ae0-5ee4-248712741911@gmx.net>
Date: Sun, 2 Jan 2022 17:55:25 +0000
Message-ID: <CAFv4g+HDkry7iJhuSrf_urFgKMU1JbY-Z5E_2jDP5dvr-EfxuA@mail.gmail.com>
To: Andreas Leathley <a.leathley@gmx.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000007aa1d405d49d1cf7"
Subject: Re: [PHP-DEV] Allowing NULL for some internal functions
From: craig@craigfrancis.co.uk (Craig Francis)

--0000000000007aa1d405d49d1cf7
Content-Type: text/plain; charset="UTF-8"

On Sun, 2 Jan 2022 at 14:22, Andreas Leathley <a.leathley@gmx.net> wrote:

> I don't think the current deprecation notices are a real hindrance in
> upgrading to a newer PHP version.



Nice, but I suspect your code doesen't exactly represents most code :-)

And while these may be "small adaptions", I work with some people where the
quantity is, impressive... and tbh I can't actually explain what the point
for this change is.

As an aside, it is making it even harder for me to get them to use static
analysis, as they keep saying this stuff is elitist bull... I'll leave it
there :-)


I did have some occurances of this deprecation notice in my applications
> when upgrading to 8.1, and each time it was clearly a bug or oversight.
> Removing the deprecation notices would also remove those insights into
> possibly unreliable code.
>


Would you mind sharing some of them, as I've not seen anything like that
myself (that's genuine interest).

Craig

--0000000000007aa1d405d49d1cf7--