Re: NULL Coercion Consistency
| From: | Robert Landers | Date: | Mon, 09 May 2022 09:06:10 +0000 |
| Subject: | Re: NULL Coercion Consistency | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117703@lists.php.net to get a copy of this message | ||
On Mon, May 9, 2022 at 10:18 AM Rowan Tommins <rowan.collins@gmail.com> wrote:
>
> On 08/05/2022 22:33, Björn Larsson via internals wrote:
> > It's not only ugly code ;) To make your program/application/library 8.1
> > compatible using that codepattern requires en effort, but brings close
> > to zero improvement, except being 8.1 compatible. So the net effect is
> > negative.
>
>
> Important correction: that change is to make your codebase PHP 9.0
> compatible, not PHP 8.1 compatible.
>
> That is the point of deprecation notices, to give advance warning that
> something will become incompatible in the future; when you act on that
> notice is up to you, and not in any sense about "compatibility" with the
> version that raises the notice.
>
> (For my thoughts on the rest of what you're saying, see every other
> message I've sent to this thread.)
>
> Regards,
>
> --
> Rowan Tommins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
> Important correction: that change is to make your codebase PHP 9.0
> compatible, not PHP 8.1 compatible.
If you are writing library code, it is 8.1 compatible to avoid people
opening issues about spamming their logs.