Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109856
Return-Path: <marandall@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 21174 invoked from network); 26 Apr 2020 21:22:33 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 26 Apr 2020 21:22:33 -0000
To: internals@lists.php.net
References: <CANOvohpz5OzHZSxdABncBXRQfeF-XnKqpK8BBDQ8OeT+jBL96w@mail.gmail.com>
Date: Sun, 26 Apr 2020 20:55:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <CANOvohpz5OzHZSxdABncBXRQfeF-XnKqpK8BBDQ8OeT+jBL96w@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: [RFC] PHP Namespace Policy
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-109856@news.php.net>

On 15/04/2020 12:21, Mark Randall wrote:
> https://wiki.php.net/rfc/php_namespace_policy

As it has come up a few times, I wanted to provide examples of where 
programming languages mount their own standard libraries inside a main 
namespace:

Java (java.*)
https://en.wikipedia.org/wiki/Java_Platform,_Standard_Edition

.NET (System.*)
https://docs.microsoft.com/en-us/dotnet/api/system?view=dotnet-plat-ext-3.1

C++ (std::*)
https://en.cppreference.com/w/cpp/header

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.

Mark Randall