Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109659
MIME-Version: 1.0
References: <CABdc3WoTeO4eTAoHCfqKyy8PWjrn97w9JXXhD88c3O9xPzp7QQ@mail.gmail.com>
In-Reply-To: <CABdc3WoTeO4eTAoHCfqKyy8PWjrn97w9JXXhD88c3O9xPzp7QQ@mail.gmail.com>
Date: Wed, 15 Apr 2020 13:38:49 -0300
Message-ID: <CAOsHV+srDeL3FxcWkKZw3qZ8FaA3oBqOyPuot7fhjeyNZO46rw@mail.gmail.com>
To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] PHP Namespace in core
From: marcio.web2@gmail.com (Marcio Almada)

>
> Hi internals,
>
> I hope you're doing well.
>
> I'd like to announce the PHP Namespace in core RFC for discussion.
> The RFC is authored by me together with George Peter Banyard and it's
> purpose
> is nothing more like to allow the use of PHP Namespace in the core.
>
> The RFC is described at https://wiki.php.net/rfc/php-namespace-in-core
>
> Best Regards,
> Micha=C5=82 Brzuchalski

Hello,

Even though I'm fond to the idea of languages having the official
stdlib contained
into a single space, there seems to be no practicality on a \PHP namespace =
usage
at this point IMMO.

We would be in a situation where things are either mixed in and out
the new namespace
- Should I `use function PHP\{json_encode, json_decode}` or was it in
the root??? - or
everything that already exists must first receive an alias into this
new namespace, to allow
consistency... but then there would probably be no plans ever to
actually move existing stuff
into the new prefix in the future.

With the lack of a feasible roadmap, I'd rather vote on doing nothing for n=
ow :/

Thanks,
M=C3=A1rcio