Re: [PHP-DEV] [RFC][VOTE] Objects as Keys

Hi! > Luckily, we have SplObjectStorage, which maybe makes that rather less > urgent as well. SplObjectStorage doesn't do this - SplObjectStorage uses objects' identity, which means two GMP(1)'s are different objects. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Develop

[PHP-DEV] Merging PHP5/PHP7

Hi, the native-tls branch was just merged into master. As all the TSRMLS_* occurrences was removed, some more merge conflicts are to expect when it comes from PHP5 to PHP7. I would like to suggest a merge strategy to minimize the negative effects. Also this will be useful to port the existing patc

Re: [PHP-DEV] [RFC][VOTE] Objects as Keys

On 18/12/14 09:03, Stanislav Malyshev wrote: >> Luckily, we have SplObjectStorage, which maybe makes that rather less >> > urgent as well. > SplObjectStorage doesn't do this - SplObjectStorage uses objects' > identity, which means two GMP(1)'s are different objects. Silly question time again ...

Re: [PHP-DEV] Re: [RFC] pecl_http

On 18/12/14 01:38, Pierre Joye wrote: > > On Dec 17, 2014 5:26 PM, "Michael Wallner" > wrote: >> >> Just a minor update: the two PECL depencies have been ported to ZE3. >> > > Btw, I still wonder if their features could be provided as part of php > instead of having to add 3

Re: [PHP-DEV] Merging PHP5/PHP7

On Thu, Dec 18, 2014 at 10:25 AM, Anatol Belski wrote: > > Hi, > > the native-tls branch was just merged into master. As all the TSRMLS_* > occurrences was removed, some more merge conflicts are to expect when it > comes from PHP5 to PHP7. I would like to suggest a merge strategy to > minimize the

[PHP-DEV] [RFC][accepted] Native TLS

Hi, The vote on the RFC https://wiki.php.net/rfc/native-tls#vote is now closed. The RFC was accepted by 100% of the voters and is merged into master. Regards Anatol -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [RFC][VOTE] Objects as Keys

Lester Caine wrote: > On 18/12/14 09:03, Stanislav Malyshev wrote: >>> Luckily, we have SplObjectStorage, which maybe makes that rather less urgent as well. >> SplObjectStorage doesn't do this - SplObjectStorage uses objects' >> identity, which means two GMP(1)'s are different objects. > > S

Re: [PHP-DEV] [VOTE][RFC] Native TLS

On Wed, Dec 17, 2014 at 8:27 PM, Anatol Belski wrote: > > Hi, > > On Wed, December 10, 2014 20:04, Anatol Belski wrote: > > Hi, > > > > > > hereby the voting on https://wiki.php.net/rfc/native-tls#vote is opened. > > The vote starts on 12/10/2014 at 21:00 CET and ends on 12/17/2014 at > > 21:00 >

Re: [PHP-DEV] [VOTE] Abstract final / Static classes

On 12/12/2014 17:12, guilhermebla...@gmail.com wrote: Patches are now complete and voting phase starts now and will be active until 12/19/2014. https://wiki.php.net/rfc/abstract_final_class Hi, After speaking about this RFC with other members of AFUP, we would be on the -1 side for this. S

[PHP-DEV] Fwd: PHPStorm Open Source License 2014-2015

Forwarding to internals and docs, no-one* reads the webmaster list. (* exaggeration for dramatic effect) -- Forwarded message -- From: Peter Cowburn Date: 5 December 2014 at 21:17 Subject: PHPStorm Open Source License 2014-2015 To: php-webmas...@lists.php.net Hi folks, I don’t

[PHP-DEV] Re: [RFC] IntlChar class and intl_char_*() functions

On Mon, Nov 24, 2014 at 8:47 PM, Sara Golemon wrote: > While playing around with Andrea's unicode literals syntax proposal, I > was reminded of just how little of ICU is exposed. I've put up a > short proposal for adding IntlChar exporting these APIs as static > methods (with a matching non-oop i

[PHP-DEV] Re: [VOTE][RFC] Unicode Codepoint Escape Syntax

> On 8 Dec 2014, at 23:51, Andrea Faulds wrote: > > I’m opening voting on the Unicode Codepoint Escape Syntax RFC. There’s been > some discussion in the last two weeks since I introduced the RFC, but there’s > nothing left which I feel needs changing. For the character name syntax > suggestio

[PHP-DEV] Update your git client

Hi, Quick head up in case you missed it: Update your git client asap https://github.com/blog/1938-git-client-vulnerability-announced Cheers, Pierre