Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110869
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-ID: <a574c633-2afe-46ff-8c9e-7d6dea5ec79b@www.fastmail.com>
In-Reply-To: <70889678-d469-0f94-3c5e-e86fcd03b22b@gmail.com>
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
 <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com>
 <70889678-d469-0f94-3c5e-e86fcd03b22b@gmail.com>
Date: Tue, 07 Jul 2020 17:04:21 -0500
To: "Miguel Rosales" <m.rosales.sueiro@gmail.com>
Cc: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Jul 7, 2020, at 4:22 PM, Miguel Rosales wrote:
> Larry Garfield wrote on 07/07/2020 16:46:
> > This has reached the 2 week mark, but there's not been much discussi=
on.  Anyone else want to weigh in?
> >
>=20
> I guess I'm missing something obvious here, but the RFC says:
>=20
>  > 5. Component or sub-component namespaces MUST use CamelCase naming=20=

> conventions.
>=20
> But then in the examples you've got e.g. \PHP\DOM\ or \PHP\SPL\... isn=
't=20
> that incorrect?
>=20
> And slightly related, is there any reason to use \PHP=C2=A0 instead of=
 \Php?
>=20
> Sorry if this has been discussed before, I haven't seen it.
>=20
> Cheers,
> Miguel

Mm, mainly because I added the CamelCase clause late and didn't think ab=
out abbreviations.  Whether it should be PHP/XML/DOM or Php/Xml/Dom has =
been an ongoing debate for at least since PHP 5.0.  I have no preference=
 strong enough to die on that hill, though, so whatever voters are willi=
ng to go for I'm good with.

Anyone care enough to offer a bikeshed color?

--Larry Garfield