Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110260 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 92832 invoked from network); 22 May 2020 20:08:32 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 22 May 2020 20:08:32 -0000 To: internals@lists.php.net References: <5ec80c51.1c69fb81.bdcbc.bb92SMTPIN_ADDED_MISSING@mx.google.com> <607f00a8-bfe5-4562-37ce-b372ba73c57d@gmail.com> Date: Fri, 22 May 2020 19:47:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <607f00a8-bfe5-4562-37ce-b372ba73c57d@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] Re: [RFC][VOTE] PHP Namespace in core From: marandall@php.net (Mark Randall) Message-ID: On 22/05/2020 19:32, Rowan Tommins wrote: > * They might even prefer your RFC, which is still marked "Under > Discussion": https://wiki.php.net/rfc/php_namespace_policy Even though the two RFCs were seperate and created without each others knowledge, I don't know how people would feel about holding a similar one if this one was voted down. If this one passed it was my intention to immediately vote on my own, which would change the policy to require sub-namespaces and limit it to autoloadable components. Which wouldn't make sense if \PHP was still denied.