Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113200
MIME-Version: 1.0
References: <CAEsg9X3ZiKW5LBNfXWHXjPTUEZa8frDH2Z1wzE6V=OFmjec9qw@mail.gmail.com>
In-Reply-To: <CAEsg9X3ZiKW5LBNfXWHXjPTUEZa8frDH2Z1wzE6V=OFmjec9qw@mail.gmail.com>
Date: Wed, 17 Feb 2021 21:36:54 +0100
Message-ID: <CAF+90c8F9=Mp-GTv-E1_stKkLokC8kfeynU_Lwv99Bj=SoSonA@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f460f205bb8e2eef"
Subject: Re: [PHP-DEV] preg_replace(string, null) is allowed?
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000f460f205bb8e2eef
Content-Type: text/plain; charset="UTF-8"

On Wed, Feb 17, 2021 at 9:28 PM David Rodrigues <david.proweb@gmail.com>
wrote:

> Hello!
>
> I am in doubt if passing null as the second argument to preg_replace() is
> valid. Actually, it works as expected.
>
> https://3v4l.org/0TITS
>
> But doc only accepts array|string.
>
> I am asking for it because PhpStorm will not accept it. So if it is valid,
> I will do a PR to PS stubs.
>

On PHP 8.1.0-dev your example prints:

    Deprecated: preg_replace(): Passing null to parameter #2 ($replacement)
of type array|string is deprecated in %s on line 3

Under strict_types=1 it already throws.

So no, it is not valid.

Regards,
Nikita

--000000000000f460f205bb8e2eef--