Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109655 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97012 invoked from network); 15 Apr 2020 15:17:29 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 15 Apr 2020 15:17:29 -0000 To: internals@lists.php.net References: Date: Wed, 15 Apr 2020 14:47:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] [RFC] PHP Namespace Policy From: marandall@php.net (Mark Randall) Message-ID: On 15/04/2020 14:20, Remi Collet wrote: > Le 15/04/2020 à 13:21, Mark Randall a écrit : > Extension (pecl or other) can be include in core later > or core extension dropped and move to pecl. Quoting the RFC: Once approved, a namespace that is a child of \PHP will remain exclusively for the originally assigned purpose, even if the associated code is moved out of core, unless a 2/3rds vote is held to withdraw that namespace. By design this RFC does NOT propose moving anything existing into the \PHP namespace at this time, nor does it REQUIRE future development uses it, only that the policy is set that it is the preferred mechanism for future development where suitable to do so.