Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111059
To: internals@lists.php.net
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
 <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com>
 <CAF+90c-rkgOdJMo=NFi1PKAKg+r56R26EmMDotZKQf19+z2Htw@mail.gmail.com>
 <cmu-lmtpd-1317118-1594400773-0@sloti26t05>
 <02b8e816-1f75-48b4-9614-cec236f6bcec@www.fastmail.com>
Message-ID: <b8bc58df-b215-310b-a05f-bb48551c491c@lsces.uk>
Date: Fri, 17 Jul 2020 09:23:49 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <02b8e816-1f75-48b4-9614-cec236f6bcec@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-thewebhostserver-MailScanner-Information: Please contact the ISP for more information
X-thewebhostserver-MailScanner-ID: 1jwLeo-00F5n4-BP
X-thewebhostserver-MailScanner: Found to be clean
X-thewebhostserver-MailScanner-SpamCheck: 
X-thewebhostserver-MailScanner-From: lester@lsces.uk
X-AuthUser: lester@lsces.uk
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: lester@lsces.uk (Lester Caine)

On 16/07/2020 22:42, Larry Garfield wrote:
> After some discussion, the namespacing proposal has been again updated.  Two major changes:
> 
> 1) Only engine code goes in \PHP.  There's a separate \Ext namespace for extensions, whether bundled or PECL.

 From RFC ...
" This RFC does NOT propose moving any existing code into the \PHP 
namespace at this time. That may be done by future RFCs if desired, 
under their own votes. This is a “policy document” only. "

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

> 2) It establishes that an index will be maintained on the Wiki listing what namespaces are already claimed.
> https://wiki.php.net/rfc/php_namespace_policy
> This is probably (I hope) the final edit of consequence before voting.  Speak now or forever hold your peace.:-)

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 ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.uk/wiki/Contact
L.S.Caine Electronic Services - https://lsces.uk
Model Engineers Digital Workshop - https://medw.uk
Rainbow Digital Media - https://rainbowdigitalmedia.uk