Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91688
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.48 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
In-Reply-To: <CAKws9z2e+GvX9gDJLPqTwio=Sr8i=0yQoCWVeyzvLh5Es24Kpg@mail.gmail.com>
Date: Wed, 16 Mar 2016 02:56:14 +0100
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Message-ID: <178E5B3C-3374-4185-8814-982761E95650@heroku.com>
References: <CAKws9z2e+GvX9gDJLPqTwio=Sr8i=0yQoCWVeyzvLh5Es24Kpg@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Subject: Re: [PHP-DEV] [RFC] Libsodium (bump)
From: dz@heroku.com (David Zuelke)

I think I've said this before; please call it ext-sodium, not ext-libsodium.

David


> On 15.03.2016, at 18:40, Scott Arciszewski <scott@paragonie.com> 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>