Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113281
MIME-Version: 1.0
References: <CAF+90c-CEZycXeigN9zqsFyZGMxDWVT_YU6h_OMrvORE_qLk3A@mail.gmail.com>
In-Reply-To: <CAF+90c-CEZycXeigN9zqsFyZGMxDWVT_YU6h_OMrvORE_qLk3A@mail.gmail.com>
Date: Fri, 26 Feb 2021 12:17:59 +0100
Message-ID: <CAG9XoMTTxP2B=dcZYr5GUnMPMWksaFgP-82mx44AR6KxHm4GPA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000066e48b05bc3b6c63"
Subject: Re: [PHP-DEV] [RFC] Namespaced in bundled extensions
From: benjamin.morel@gmail.com (Benjamin Morel)

--00000000000066e48b05bc3b6c63
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you for this RFC, Nikita. This is a necessary first step in the right
direction.

Even though this is out of scope for this RFC, I hope that moving standard
functions to namespaces will be an opportunity to fix inconsistencies in
parameter order, like:

array_map($callback, array)
array_filter($array, $callback)

and not just an alias under a namespace!

 =E2=80=94 Benjamin

On Thu, 25 Feb 2021 at 21:26, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> The question of namespaces in the stdlib has been coming up a lot recentl=
y,
> so I'd like to present my own stab at resolving this question:
>
> https://wiki.php.net/rfc/namespaces_in_bundled_extensions
>
> Relative to a number of previous (declined) proposals, the main differenc=
e
> is that I do not propose a top-level "PHP\" vendor namespace, and instead
> recommend the use of "ExtName\", in line with existing practice for
> extensions. I believe this addresses the primary concern with previous
> proposals.
>
> Regards,
> Nikita
>

--00000000000066e48b05bc3b6c63--