Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111077
MIME-Version: 1.0
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
In-Reply-To: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
Date: Mon, 20 Jul 2020 17:58:06 +0200
Message-ID: <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000024349d05aae19341"
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: mike@php.net (Michael Wallner)

--00000000000024349d05aae19341
Content-Type: text/plain; charset="UTF-8"

Hi Larry!

Larry Garfield <larry@garfieldtech.com> schrieb am Mi., 24. Juni 2020,
02:30:

> Greetings, Internalians.
>
> *dons flame retardant suit*


Thank your for your efforts, but I'm about to cast a negative vote on this
policy.

Distilled down, I just cannot see any huge benefit out of a (or two) root
namespace(s). As a project we rightfully own the root namespace, and
putting everything beneath PHP just doesn't make any sense to me.

Also, most code more than a handful of files is already vendored, and if
not a common idiom I see often used, is a simple 'app' or '<appname>'
namespace.

Closing, just let me ensure that it is not because one of my extensions
accidentally provides a class beneath a 'php' namespace.

Regards,
Mike

--00000000000024349d05aae19341--