Hi Levi,
On Sat, Mar 19, 2016 at 5:56 AM, Levi Morrison wrote:
>> At least that's not what it says in the docs.
>
> I meant: at least according to the docs:
> http://php.net/manual/en/language.namespaces.rationale.php
>
>> Namespace names PHP and php, and compound names starting with these names
Quick update:
https://github.com/jedisct1/libsodium/commit/20bf121fcde3104babede887980be835e07b10dd
Looks like libsodium 1.0.9 will be out soon, which means ext/sodium
1.0.3 will follow, and then we can get the RFC fleshed out and ready
for voting soon after.
(As a reminder from the previous thr
On Sat, Mar 19, 2016 at 4:30 AM, Fleshgrinder wrote:
> On 3/18/2016 9:56 PM, Levi Morrison wrote:
> >> At least that's not what it says in the docs.
> >
> > I meant: at least according to the docs:
> > http://php.net/manual/en/language.namespaces.rationale.php
> >
> >> Namespace names PHP and ph
Hi all,
On Thu, Mar 17, 2016 at 2:57 AM, Fleshgrinder wrote:
> On 3/15/2016 11:02 PM, Yasuo Ohgaki wrote:
>> Hi Scott,
>>
>> On Wed, Mar 16, 2016 at 2:40 AM, Scott Arciszewski
>> wrote:
>>> Question: If this extension is adopted, which syntax would you prefer?
>>>
>>> \Sodium\func()
>>>
On 3/15/2016 11:02 PM, Yasuo Ohgaki wrote:
> Hi Scott,
>
> On Wed, Mar 16, 2016 at 2:40 AM, Scott Arciszewski
> wrote:
>> Question: If this extension is adopted, which syntax would you prefer?
>>
>> \Sodium\func()
>> Sodium::func()
>> sodium_func()
>
> I prefer both of
>
> Sod
On 3/18/2016 9:56 PM, Levi Morrison wrote:
>> At least that's not what it says in the docs.
>
> I meant: at least according to the docs:
> http://php.net/manual/en/language.namespaces.rationale.php
>
>> Namespace names PHP and php, and compound names starting with these names
>> (like PHP\Class
> 1. PHP already has its reserved namespace, the global one *\*.
> 2. Is it *\PHP* or *\Php*? This opens a huge can of worms.
We've technically only reserved PHP and php but it is case insensitive
anyway. PHP *does not* reserve the global namespace. At least that's
not what it says in the docs.
-
> At least that's not what it says in the docs.
I meant: at least according to the docs:
http://php.net/manual/en/language.namespaces.rationale.php
> Namespace names PHP and php, and compound names starting with these names
> (like PHP\Classes) are reserved for internal language use and should
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
>
> \ModuleName\function_name
>
> for all extension functions, indeed
Noted and agreed.
On Mar 15, 2016 9:56 PM, "David Zuelke" wrote:
> 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 wrote:
> >
> > Link to RFC: https://wiki.php.net/rfc/libsodium
> >
> > I'd like to bump t
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 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 mcryp
Hi Scott,
On Wed, Mar 16, 2016 at 2:40 AM, Scott Arciszewski wrote:
> Question: If this extension is adopted, which syntax would you prefer?
>
> \Sodium\func()
> Sodium::func()
> sodium_func()
I prefer both of
Sodium::func()
sodium_func()
IMO, we are better to provide bot
On Tue, Mar 15, 2016 at 1:59 PM, Fleshgrinder wrote:
> 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 thi
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?
>
> \So
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 current
15 matches
Mail list logo
