Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111194
To: internals@lists.php.net
References: <9d620b19-f1b0-4ebf-abd9-f73380c47f24@www.fastmail.com>
Date: Sun, 26 Jul 2020 17:48:27 +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: <9d620b19-f1b0-4ebf-abd9-f73380c47f24@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] [Vote] PHP namespace policy
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-111194@news.php.net>

On 26/07/2020 17:24, Larry Garfield wrote:
> The vote on the PHP namespace policy is now open: 
> https://wiki.php.net/rfc/php_namespace_policy

Thanks to Larry for putting in a lot of effort with this RFC.

I would like to think this RFC provides a solution to a legitimate 
long-term problem.

1. It will allow the logical grouping of related classes and symbols 
within namespaces, as is considered best practice in userland. So far as 
naming goes, there is no reason to believe what is applicable to 
userland is not equally applicable to php-src and its extensions.

2. It will prevent us needing to "fake" namespaces by prefixing future 
symbols with Php or the extension name.

3. It provides for bundling and unbundling extensions without the need 
to change symbols.