Re: Re: [RFC] PHP Namespace Policy
| From: | Rowan Tommins | Date: | Mon, 27 Apr 2020 08:25:27 +0000 |
| Subject: | Re: Re: [RFC] PHP Namespace Policy | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-109857@lists.php.net to get a copy of this message | ||
On Sun, 26 Apr 2020 at 20:55, Mark Randall <marandall@php.net> wrote:
> I would be interested in hearing arguments why such a strategy adopted
> with great success by many of the most popular and well-developed
> languages, is inappropriate for PHP.
>
To me, the answer to that is quite simple: we have several hundred
functions, and several dozen classes and interfaces, which are not in such
a namespace; and we have millions of lines of code out in the world using
them. So either we need a strong rationale and a concrete plan to move all
of those into the namespace, or we need a consistent policy on what goes in
and what stays out. It wouldn't make much sense, for instance, to have
PHP\str_contains but no plan to move str_replace.
The decisions you can make in version 8 of a language are inevitably
different from those you can make prior to version 1.
Regards,
--
Rowan Tommins
[IMSoP]