Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122003
MIME-Version: 1.0
References: <95b03bd5-08c5-4fec-b33e-6a617e55a74e@mail.ru>
In-Reply-To: <95b03bd5-08c5-4fec-b33e-6a617e55a74e@mail.ru>
Date: Thu, 14 Dec 2023 12:12:23 +0100
Message-ID: <CADyq6sLhEUhL3Ku+NbaVVZXq_J0UGuX81_Pvgz19fS2=HB_U-w@mail.gmail.com>
To: "petrov.boris.v@mail.ru" <petrov.boris.v@mail.ru>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000004f7099060c765cf3"
Subject: Re: [PHP-DEV] Are warnings guaranteed?
From: ocramius@gmail.com (Marco Pivetta)

--0000000000004f7099060c765cf3
Content-Type: text/plain; charset="UTF-8"

Hey Boris,

On Thu, 14 Dec 2023 at 11:39, petrov.boris.v.mail.ru via internals <
internals@lists.php.net> wrote:

> The above code confuses a reader with issues 1) isn't the only possible
> return value is now true? 2) if it throws on failure, then how can it
> return anything?
>

Just worth mentioning that
https://github.com/thecodingmachine/safe/tree/3a6e43b4be3d3d65b272c2660300a50658ce168b
maps out all warning-emitting PHP functions to usable variants :-)

There's also a PHPStan integration to prevent people from shooting
themselves in the foot while using the php-src provided legacy functions
(which will likely keep emitting warnings for a while, due to BC concerns).

Marco Pivetta

https://mastodon.social/@ocramius

https://ocramius.github.io/

--0000000000004f7099060c765cf3--