Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113693
MIME-Version: 1.0
References: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
 <F646AB87-032E-4A34-BFC7-BA12C1EABCDF@benramsey.com>
In-Reply-To: <F646AB87-032E-4A34-BFC7-BA12C1EABCDF@benramsey.com>
Date: Mon, 22 Mar 2021 18:27:42 +0100
Message-ID: <CAF+90c_EcwvwNNm7DP7zLQ5c5Abf=yy3nzJ-kNUTAX9cLVgh_Q@mail.gmail.com>
To: Ben Ramsey <ben@benramsey.com>
Cc: PHP internals <internals@lists.php.net>, Rowan Collins <rowan.collins@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000011c94c05be236392"
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.1
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000011c94c05be236392
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 22, 2021 at 3:58 PM Ben Ramsey <ben@benramsey.com> wrote:

> > On Mar 22, 2021, at 04:24, Nikita Popov <nikita.ppv@gmail.com> wrote:
> >
> > Hi internals,
> >
> > It's time for another deprecation RFC:
> > https://wiki.php.net/rfc/deprecations_php_8_1
> >
> > This is a collection of minor deprecations that various people have put
> > together over the last ~2 years. This RFC was formerly targeted at PHP
> 8.0,
> > but was delayed to PHP 8.1 to reduce the amount of changes necessary fo=
r
> > PHP 8.0 compatibility.
> >
> > As usual, each deprecation will be voted in isolation.
> >
> > As we're still early in the release cycle, it's still possible to add
> > additional deprecation candidates, given reasoning for the deprecation,
> as
> > well as available alternatives.
> >
> > Of course, if there are compelling technical reasons why something shou=
ld
> > not be deprecated, we can move things into the "Removed from this
> proposal"
> > section, in which case it will serve as documentation why some
> > functionality should not deprecated.
>
>
> Given Rowan=E2=80=99s thread [1] on `utf8_encode()` and `utf8_decode()`, =
should we
> consider adding these functions to this list or mentioning them in this
> RFC as being handled separately?
>

Sure. Rowan, if you would like to add these functions to this RFC, please
feel free to just edit it directly. Otherwise, having a separate RFC just
for them is also fine.

Regards,
Nikita

--00000000000011c94c05be236392--