Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110889
MIME-Version: 1.0
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com>
In-Reply-To: <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com>
Date: Thu, 9 Jul 2020 09:51:12 +0100
Message-ID: <CA+kxMuS4TwAz9gaZ0GRwsb1yw5=Y+GcarPqxJsb0QC7JY9CFkw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: Danack@basereality.com (Dan Ackroyd)

On Tue, 7 Jul 2020 at 15:47, Larry Garfield <larry@garfieldtech.com> wrote:
>
> This has reached the 2 week mark, but there's not been much discussion.

Unless I'm having a massive reading failure, this RFC has been
announced twice. And feedback was provided before:

https://externals.io/message/109646#109647
https://externals.io/message/109646#109648

From the RFC:
> Every new global class, however, creates a potential namespace collision
> with existing user-space code and thus a potential for backward
> compatibility breaks.

This doesn't appear to be an actual problem for the PHP ecosystem.

The vast majority of code in libraries is in namespaces, which avoids
there being a problem that needs addressing.

> Anyone else want to weigh in?

I still don't think this RFC is a good way to improve the general
situation of PHP.

Rather than having more rules (quite a few of which I don't agree
with), time and effort would be better spent on reviewing code and
using features before releases e.g. to avoid situations like the FFI
api being difficult to use.

cheers
Dan
Ack