Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111069 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56544 invoked from network); 17 Jul 2020 13:27:16 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 17 Jul 2020 13:27:16 -0000 To: internals@lists.php.net References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com> <02b8e816-1f75-48b4-9614-cec236f6bcec@www.fastmail.com> Date: Fri, 17 Jul 2020 13:20: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: 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] [RFC] \PHP namespace usage heuristics From: marandall@php.net (Mark Randall) Message-ID: On 17/07/2020 09:23, Lester Caine wrote: > So does that also apply to \Ext? Currently the selection of extensions > is flexible and most distributions allow the easy repackaging of just > what is available. Creating a 'core' set off extensions under \PHP is > essentially saying 'you will make these available' while \Ext is a > second class citizen? Personally I think every package even if relegated > to PECL deserves to be under \PHP or alternately ONLY the essential core > engine components go under \PHP and everything else is \Ext Things under \PHP will be related to either the engine itself, universal helpers, or PHP as a language. Everything else, including almost all extensions bundled with php-src, would go under \Ext > Many of the 'exotic' functions such as 'reflection' are not essential > for writing good code, so a core \PHP which defines an essential working > set of functions does make sense. What HAS been lost is the development > of better extensions such as a \Ext\String or \Ext|Array extension that > is more 'object orientated' while leaving the legacy functions wrapped > in \PHP ... > Object-orientated styles for strings / arrays provided by the engine would still go in the root.