Hi,
On 08/01/2015 21:28, Andrea Faulds wrote:
The vote on the PHP 5.7 RFC has closed. By 19 votes to 14, the RFC
has been rejected. This means we won’t be having a PHP 5.7 release,
unless another RFC is made and voted on.
I am still convinced that it was premature to open the voting on the 5.7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 08/01/2015 20:13, Anthony Ferrara a écrit :
> That test is bogus and is testing undocumented functionality.
Thanks for your explanation.
Horde test suite have be fixed by upstream.
Remi.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 08/01/2015 20:20, Adam Harvey a écrit :
> On 8 January 2015 at 10:24, Remi Collet
> wrote:
>> Is this expected ?
>>
>> Notice the diff between (see attachement) : - - 5.4.35 and 5.4.36
>> show 5 changes, - - 5.5.20 and 5.521RC1 show only 2 - - 5.6
Hi all,
I cannot access snaps.php.net while.
I guess snaps.php.net is closed infavor of github download.
However, bugs.php.net referes to it.
https://bugs.php.net/bug.php?id=68679
If snaps.php.net is closed, bugs.php.net should be fixed.
Shouldn't it be announce somewhere? (Or I missed)
Can any
On Fri, 2015-01-02 at 12:05 -0500, Scott Arciszewski wrote:
> Right now, the libsodium PECL package is in the beta channel. Would it be
> possible to include libsodium as a core extension in PHP 7? If so, what
> hurdles would need to be cleared before that happens?
This should be an FAQ, maybe som
You're right, a cursory Google search reveals that someone is maintaining a
php5-nacl package that uses libsodium. This simplifies instructions
greatly! :D
On Jan 9, 2015 6:11 AM, "Johannes Schlüter" wrote:
> On Fri, 2015-01-02 at 12:05 -0500, Scott Arciszewski wrote:
> > Right now, the libsodium
Hi,
Just wanted to say: +1 on this and thank you for proposing a patch.
I myself created a feature request for it on bugs.php.net some time
ago, now closed as duplicate: https://bugs.php.net/bug.php?id=62315
Cheers,
Andrey.
On Fri, Jan 9, 2015 at 2:08 AM, François Laupretre wrote:
> Hi,
>
> I
> De : François Laupretre [mailto:franc...@tekwire.net]
>
> I just created the RFC :
>
> https://wiki.php.net/rfc/cyclic-replace
Just added full array multi-level recursion support to the RFC.
Still debugging the code and adding new tests.
> Please also give me your opinion about implementing a
All,
As identified in the previous thread, there is an issue when providing
invalid salts to crypt() where it will silently fall back to STD_DES.
This was evidenced by a fix to crypt() when upgrading blowfish to 1.3.
Causing a failing test for Horde_Auth:
$ php -r 'var_dump(crypt("foobar", "*0Oay
> The implementation misses support for reflection.
> I think, it doesn't make a lot of sense to introduce Reflection support for
> return types but not for argument types.
> Probably, it's better to provide a single and consistent RFC for both.
There is a draft RFC for this that Sara and I have e
yeah, I remember I saw something :)
Lets do the core work first and then decide how the Reflection should look
like.
Thanks. Dmitry.
On Fri, Jan 9, 2015 at 9:26 PM, Levi Morrison wrote:
> > The implementation misses support for reflection.
> > I think, it doesn't make a lot of sense to introduc
On Thu, Jan 8, 2015 at 5:44 PM, Pierre Joye wrote:
> The fact that hhvm implements a significant part of the extensions (or
> other areas) using PHP+additional syntax as well as adding cleaner
> APIs or mechanisms for the C parts only confirms me one thing: the
> very 1st problem we have to solve
> De : François Laupretre [mailto:franc...@tekwire.net]
>
> > I just created the RFC :
> >
> > https://wiki.php.net/rfc/cyclic-replace
>
> Just added full array multi-level recursion support to the RFC.
Final (?) patch pushed to PR. In sync with RFC.
> > Please also give me your opinion about i
Hey Sara,
> On 10 Jan 2015, at 01:10, Sara Golemon wrote:
>
> Funny to see you mention this. I literally just pulled together a
> meeting today to discuss HHVM's admittedly unstable extension API.
> One idea to emerge from this was to design a new extension API
> agnostic of underlying implemen
On Fri, Jan 9, 2015 at 5:41 PM, Andrea Faulds wrote:
> Three APIs for TheFacebook under the sky,
> Seven for the Zend-lords in their halls of stone,
> Nine for the Engines doomed to die,
> One for the Dark Lord on his dark throne,
> In the Land of Native where the Undefined Behaviours lie.
> One A
On 10 Jan 2015 01:10, "Sara Golemon" wrote:
>
> On Thu, Jan 8, 2015 at 5:44 PM, Pierre Joye wrote:
> > The fact that hhvm implements a significant part of the extensions (or
> > other areas) using PHP+additional syntax as well as adding cleaner
> > APIs or mechanisms for the C parts only confirms
On Fri, Jan 9, 2015 at 5:48 PM, Paul Dragoonis wrote:
> Somewhat Pie in the sky but at the same time also achievable with good
> planning and design. I'd support this definitely and this abstraction layer
> would solve constant maintainability of extensions by not having to update
> themselves con
On Jan 10, 2015 8:35 AM, "François Laupretre" wrote:
>
> > De : François Laupretre [mailto:franc...@tekwire.net]
> >
> > > I just created the RFC :
> > >
> > > https://wiki.php.net/rfc/cyclic-replace
> >
> > Just added full array multi-level recursion support to the RFC.
>
> Final (?) patch pushed
18 matches
Mail list logo
