Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109929
To: internals@lists.php.net
References: <CANOvohpz5OzHZSxdABncBXRQfeF-XnKqpK8BBDQ8OeT+jBL96w@mail.gmail.com>
 <5ea1aab8.1c69fb81.72671.791bSMTPIN_ADDED_MISSING@mx.google.com>
 <CAEUnE0fjMpGyEwGorseuGvpnB1cJfA6uspRT6MSQX06zCxy0Ow@mail.gmail.com>
 <434969CF-4FD8-4F57-8999-92FAC43358FA@gmail.com>
 <CAEUnE0cqmVdihoAKB1J7XD2AfGS1=DpcQtModfBGy8fK_n6dWw@mail.gmail.com>
Message-ID: <b2f2ef6b-1f62-7876-66f8-725d28800222@gmail.com>
Date: Wed, 29 Apr 2020 15:54:00 +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: <CAEUnE0cqmVdihoAKB1J7XD2AfGS1=DpcQtModfBGy8fK_n6dWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Re: [RFC] PHP Namespace Policy
From: rowan.collins@gmail.com (Rowan Tommins)

On 29/04/2020 15:16, Michael Morris wrote:
> I would like the old "throw it all in" approach to be moved out of \ and
> into \PHP\Legacy.
> ...
> Or is \ itself just going to be legacy? I suppose that could be done


Renaming all the existing functions (and which ones? everything in 
PECL?) to PHP\Legacy\foo and then aliasing them back again would just be 
adding effort for everybody. If we really got to the stage where every 
single function in core had a non-legacy replacement outside the root 
namespace, we could just have a setting that "turned off" the versions 
in the root namespace. But frankly I can't imagine that ever happening; 
it's pretty much the same effort as "let's throw out the language and 
start again".


Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]