Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91751
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.28.124 cause and error)
Reply-To: internals@lists.php.net
References: <CAKws9z2e+GvX9gDJLPqTwio=Sr8i=0yQoCWVeyzvLh5Es24Kpg@mail.gmail.com>
 <CAGa2bXaQaBUi=C=MzhQYYznqRGJ06gR7oE+0nvuT6EKL6hN0gA@mail.gmail.com>
 <56E99E97.2050102@fleshgrinder.com>
 <CAGa2bXZYeTf7Hz5Doq+xf_vtM6=jxojx9SZb4gKMKaZKmvvMmQ@mail.gmail.com>
To: internals@lists.php.net
Message-ID: <56EC5F02.60105@fleshgrinder.com>
Date: Fri, 18 Mar 2016 21:03:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAGa2bXZYeTf7Hz5Doq+xf_vtM6=jxojx9SZb4gKMKaZKmvvMmQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="F9KTSj8tIbroAQEToC7kdkB2JiNMp5ClC"
Subject: Re: [PHP-DEV] [RFC] Libsodium (bump)
From: php@fleshgrinder.com (Fleshgrinder)

--F9KTSj8tIbroAQEToC7kdkB2JiNMp5ClC
Content-Type: multipart/mixed; boundary="VpQ1V16Jp8o9bwJbdD3UIwe3vbEmpgIkE"
From: Fleshgrinder <php@fleshgrinder.com>
Reply-To: internals@lists.php.net
To: internals@lists.php.net
Message-ID: <56EC5F02.60105@fleshgrinder.com>
Subject: Re: [PHP-DEV] [RFC] Libsodium (bump)
References: <CAKws9z2e+GvX9gDJLPqTwio=Sr8i=0yQoCWVeyzvLh5Es24Kpg@mail.gmail.com>
 <CAGa2bXaQaBUi=C=MzhQYYznqRGJ06gR7oE+0nvuT6EKL6hN0gA@mail.gmail.com>
 <56E99E97.2050102@fleshgrinder.com>
 <CAGa2bXZYeTf7Hz5Doq+xf_vtM6=jxojx9SZb4gKMKaZKmvvMmQ@mail.gmail.com>
In-Reply-To: <CAGa2bXZYeTf7Hz5Doq+xf_vtM6=jxojx9SZb4gKMKaZKmvvMmQ@mail.gmail.com>

--VpQ1V16Jp8o9bwJbdD3UIwe3vbEmpgIkE
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 3/17/2016 4:04 AM, Yasuo Ohgaki wrote:
> The only problem with this is "It looks inconsistent with existing
> module functions". We may consider how we are going to use namespaces
> for extensions in general. I like the idea
>=20
> \ModuleName\function_name
>=20
> for all extension functions, indeed.
>=20
> Question is whether we should use something like
> "\PHP\ModuleName\function_name" or "\ModuleName\function_name". I'm
> not sure which one is better in the long run.
>=20
>=20

I think that this is not necessary. The existing system does not seem to
pose any problems, changing the coding standard now only creates a
mixture. There are still many extension who are not even in conformance
with the coding standard and such a change would make it even worse.
Let's first try to clean things up; which is already a super hard task
because many people are completely against, as we've seen it in the
*var* deprecation thread.

That being said, *\PHP\ModuleName\function_name* is a very bad choice
for multiple reasons:

1. PHP already has its reserved namespace, the global one *\*.
2. Is it *\PHP* or *\Php*? This opens a huge can of worms.

And even if it is *\ModuleName\function_name*:

3. The amount of *use* statements will explode and the situation becomes
equal to the one we had in the past with the millions of
*require(_once)* lines in the preamble of each file. It requires more
management on the userland side.

TL;DR the current system works just fine so why change? Just because it
is sexy right now? Will it be sexy in 10 years?

--=20
Richard "Fleshgrinder" Fussenegger


--VpQ1V16Jp8o9bwJbdD3UIwe3vbEmpgIkE--

--F9KTSj8tIbroAQEToC7kdkB2JiNMp5ClC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW7F8MAAoJEOKkKcqFPVVr5S0QAJZSqZBvlGNsi0WmT0aiscEC
/doM06T7pzqiMOsueEzTpjyM4j1RMK2shT+U8OIuGfWJsGDoltq6T2T8hB5xS1wx
feL4h0OFiLi6roUPxKE5K+M+ta8mcbtc6oPUpm5zuXp5/cr2Y4duDcZDup+VbG9V
0ay6ERxUAD02PXNMpGtNyMgBVj9nKE5fJFSqcGYE4JKNDptH+5tbkyqOn3/9sljq
vCmq1kRtB97EcZHLAUcjzHertCTF7CVCyc9JqoXknhOgeUbRMRGvfP1SR2W/Z07S
ouAUllA50BttAEEwfFKjmAfknbIQGVoeKosBnyqVNtIjLSr7rA9HMujyyhjtvdfk
OKJgZ9Qdrqx0e0vTMq+xsdVJEvcWiHsiYxzKoGHU5eyXk3YDgrvye0saEIgipS6c
KMEalqhCRQ1bG1NieA6ve/OQn6HPx13J72lzQ379yhv3ZaGbM2yQDi8DgOt8YDfC
H8dv6jlNYZ6VwK5iGHMeNXbLPYaOdqAvz7GYmWqCrXNZcvOZLrz/K0zTl0NkXkMw
G6nIHPrQgL+id3DUzXwvnih1qADyQRxTjyBLWac6vbhcga6SvfAnkvVKsy2fEmTB
Tto+QJV++eXSIk1yiW1slHEMbg2gEWan9Lf3qJ2NGlEA2WOXNCM8X9w0GAQrVceN
pWOx+wANMYKsvxeqrjeX
=jIdr
-----END PGP SIGNATURE-----

--F9KTSj8tIbroAQEToC7kdkB2JiNMp5ClC--