Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111078
MIME-Version: 1.0
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
In-Reply-To: <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
Date: Mon, 20 Jul 2020 17:44:14 +0100
Message-ID: <CALKiJKrTH0yjm_bGsJJBTvnrjF0FR18NDu3jW082+CviJ7OnWQ@mail.gmail.com>
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003207ad05aae238a4"
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: rowan.collins@gmail.com (Rowan Tommins)

--0000000000003207ad05aae238a4
Content-Type: text/plain; charset="UTF-8"

On Mon, 20 Jul 2020 at 16:58, Michael Wallner <mike@php.net> wrote:

> Distilled down, I just cannot see any huge benefit out of a (or two) root
> namespace(s). As a project we rightfully own the root namespace, and
> putting everything beneath PHP just doesn't make any sense to me.
>


I will ask you the same question I have asked others, but without much
response: would you vote Yes to an alternative proposal to officially adopt
a policy of _never_ using the PHP\* namespace, to eliminate future debates
about when to use it?

Regards,
-- 
Rowan Tommins
[IMSoP]

--0000000000003207ad05aae238a4--