Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109837 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 73634 invoked from network); 25 Apr 2020 00:37:00 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 25 Apr 2020 00:37:00 -0000 To: internals@lists.php.net References: <5ea1aab8.1c69fb81.72671.791bSMTPIN_ADDED_MISSING@mx.google.com> Date: Sat, 25 Apr 2020 00:09:15 +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: 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] PHP Namespace Policy From: marandall@php.net (Mark Randall) Message-ID: On 25/04/2020 00:00, Michael Morris wrote: > So, in steps: > > 1. Take the current function roster - all of it - and put it in > \PHP\Legacy\. So the formal name of strpos would become > \PHP\Legacy\strpos. > 2. The root namespace would be empty BUT... > 3. An INI directive set globally or per directory can set which namespace > is bound to root. Initially this would be "\PHP\Legacy", so all legacy > code would not have to change - it would run in the new version and find > all of its functionality without incident. This is critical - as this > directive would likely need to stay as is for two majors minimum, possibly > more. Thank you for the contribution. However, such a change would never, ever be accepted. With good reason. Mark Randall marandall@php.net