Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111081
Return-Path: <marandall@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 8003 invoked from network); 21 Jul 2020 01:42:13 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 21 Jul 2020 01:42:13 -0000
To: internals@lists.php.net
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
 <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
Date: Tue, 21 Jul 2020 01:36:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Posted-By: 87.81.129.66
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-111081@news.php.net>

On 20/07/2020 16:58, Michael Wallner 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.

You cannot just "own" the root namespace if you want to use namespaces 
yourself, which we will, it's inevitable, the number of classes and 
interfaces increases more and more each release.

So either you fake namespaces e.g. PhpToken or you trample on userland 
\Tokenizer.

There is one solution to this, and that is to have a vendor namespace 
for the PHP project itself, naturally the one that is reserved, \PHP.

There's a very good reason modern language frameworks claim a couple of 
root level namespaces, e.g. .NET it's System.* and Microsoft.*, for Java 
it's java.*