Re: [RFC] Libsodium (bump)
| From: | Fleshgrinder | Date: | Tue, 15 Mar 2016 17:59:41 +0000 |
| Subject: | Re: [RFC] Libsodium (bump) | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-91681@lists.php.net to get a copy of this message | ||
On 3/15/2016 6:40 PM, Scott Arciszewski wrote:
> Link to RFC: https://wiki.php.net/rfc/libsodium
>
> I'd like to bump the RFC to make Libsodium a core extension, as per
> Ferenc's suggestion on the mcrypt RFC.
>
> Question: If this extension is adopted, which syntax would you prefer?
>
> \Sodium\func()
> Sodium::func()
> sodium_func()
>
> As it currently stands, the PHP extension in PECL uses a namespace +
> function format.
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>
>
The third option (*sodium_func()*) as per coding standard:
https://github.com/php/php-src/blob/master/CODING_STANDARDS#L110-L125
I do not think that it makes sense to provide a static class for this
functionality, correct me if I am wrong.
It definitely makes no sense to namespace the stuff if you want it in
core and it violate the coding standards (for a good reason).
--
Richard "Fleshgrinder" Fussenegger
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc