Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113202
MIME-Version: 1.0
References: <CAEsg9X3ZiKW5LBNfXWHXjPTUEZa8frDH2Z1wzE6V=OFmjec9qw@mail.gmail.com>
 <CAF+90c8F9=Mp-GTv-E1_stKkLokC8kfeynU_Lwv99Bj=SoSonA@mail.gmail.com>
In-Reply-To: <CAF+90c8F9=Mp-GTv-E1_stKkLokC8kfeynU_Lwv99Bj=SoSonA@mail.gmail.com>
Date: Wed, 17 Feb 2021 23:15:13 -0300
Message-ID: <CAEsg9X3o3fqT1Nv5TwWdjTiyujezfZc77QRYwgoxwmDG5vw_aw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000096255305bb92e8d0"
Subject: Re: [PHP-DEV] preg_replace(string, null) is allowed?
From: david.proweb@gmail.com (David Rodrigues)

--00000000000096255305bb92e8d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks!

There is a reason why it is not supported anymore?

There is a difference in output or performance, maybe?


Atenciosamente,
David Rodrigues


Em qua., 17 de fev. de 2021 =C3=A0s 17:37, Nikita Popov <nikita.ppv@gmail.c=
om>
escreveu:

> 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() i=
s
>> 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 vali=
d,
>> 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=3D1 it already throws.
>
> So no, it is not valid.
>
> Regards,
> Nikita
>
>

--00000000000096255305bb92e8d0--