Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

> > On Jan 20, 2016, at 3:20 PM, Derick Rethans wrote: > > On Wed, 20 Jan 2016, Pavel Kouřil wrote: > >> On Wed, Jan 20, 2016 at 8:04 PM, Derick Rethans >> wrote: >>> >>> I've decided to re-propose the CoC RFC. There are many reasons for it, >>> but there are a few points I want to make. >>

[PHP-DEV] Re: [PHP-CVS] com php-src: Fixed bug #69111 (Crash in SessionHandler::read()). Made session save handler abuse much harder than before.: NEWS ext/session/mod_user.c ext/session/mod_user_clas

Hi all, On Fri, Jan 15, 2016 at 3:50 PM, Yasuo Ohgaki wrote: > Commit:bfb9307b2d679a91e138fd876880470ece60942b > Author:Yasuo Ohgaki Fri, 15 Jan 2016 13:47:45 > +0900 > Parents: d7f8d9e3a9babf0e4f0c1a5590e1feb5e69bd84a > Branches: PHP-5.6 PHP-7.0 master > > Link: > htt

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Jan 21, 2016 2:38 AM, "Paul M. Jones" wrote: > > > > On Jan 20, 2016, at 13:04, Derick Rethans wrote: > > > > Hi, > > > > I've decided to re-propose the CoC RFC. > > Is it a violation of the RFC rules to skip step 1 ("Email internals@lists.php.net to measure reaction to your intended proposal"

[PHP-DEV] Severe safety fail in file access and stream filters

Dear internal developers, I recently discovered several failures in error detection involving file access, stream compression and source inclusion that may bring the program to process missing or invalid data (very severe safety bug) or simply crash without apparent reason. I reported all these is

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi Zeev, Zeev Suraski wrote: I want to point three key concerns that are unrelated to the contents of the updated RFC before addressing the RFC itself (in short). Note that I'm not blaming or otherwise holding you in any negative light in any way, but rather, stating my opinion on the contex

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi! > First, on process. Tangentially related, by pure coincidence I was given today a link to an IETF RFC describing their view on consensus: https://tools.ietf.org/html/rfc7282 While their procedures are substantially different from ours, and for a good reason, I think learning from their exp

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi, Up front, I agree the objective of the COC needs to be clearly stated. There is confusion, whether it's here or externally by observers, as to whether this is intended to fix mailing list toxicity (I assume, for now, not) or intended to state the projects intentions should there be a complaint

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi! > I've decided to re-propose the CoC RFC. There are many reasons for it, > but there are a few points I want to make. > > I strongly believe that a Code of Conduct is required. The amount of > toxic behaviour on this list is in my opinion unacceptable. It drives > people away, it certainly

[PHP-DEV] Re: WIKI: phpng-upgrading

Hi Yasuo, Yasuo Ohgaki wrote: Hi ZendEngine developers, I'm not sure if the wiki page is maintained, but I noticed few errors. https://wiki.php.net/phpng-upgrading#strings phpng-upgrading was written back when it was just phpng and the 64-bit patch wasn't merged. Heck, I don't think phpng w

Re: [PHP-DEV] WIKI: phpng-upgrading

Le 20/01/2016 23:07, Sean DuBois a écrit : On Thu, Jan 21, 2016 at 06:55:41AM +0900, Yasuo Ohgaki wrote: Hi ZendEngine developers, I'm not sure if the wiki page is maintained, but I noticed few errors. https://wiki.php.net/phpng-upgrading#strings has following example. - ZVAL_STRING(zv, str,

Re: AW: [PHP-DEV] [RFC] Allow specifying keys in list()

Hi Robert, for named parameters, I would prefer this syntax over list(): function foo($foo, [a: string $a, b: int &$b, c: bool $c = true]) { ... work with $foo, $a, $b, $c } $b = 42; foo('foo', ['a' => 'bar', 'b' => $b]); function bar($foo, SomeClass {a: string $a, b: int &$b, c: bool $c = tru

Re: [PHP-DEV] WIKI: phpng-upgrading

Hi Nikita, On Thu, Jan 21, 2016 at 7:28 AM, Nikita Popov wrote: > These examples are correct. In PHP 7 ZVAL_STRING always duplicates, which is > what the 1 parameter used to signify. Oh, now I see the example intention. Thank you. -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP Internals - PHP Runt

Re: [PHP-DEV] WIKI: phpng-upgrading

On Wed, Jan 20, 2016 at 10:55 PM, Yasuo Ohgaki wrote: > Hi ZendEngine developers, > > I'm not sure if the wiki page is maintained, but I noticed few errors. > > https://wiki.php.net/phpng-upgrading#strings > has following example. > > - ZVAL_STRING(zv, str, 1); > + ZVAL_STRING(zv, str); > > - ZVA

Re: [PHP-DEV] WIKI: phpng-upgrading

Hi Sean, On Thu, Jan 21, 2016 at 7:07 AM, Sean DuBois wrote: > > I tried to get access to that page as well, but didn't have any luck > would you mind adding the zend_parse_paramaters changes? > > 'l' went from 'long' -> 'zend_long' and 's' went from 'int' -> 'size_t'. > > So many extensions have

[PHP-DEV] GnuPG support for Phar Signatures

With OpenSSL Phar already supports one public/private key algorithm. As using Phars as command line tools is in principle a question of Trust, a Trust based Identity Tool like GnuPG looks like a good match for me. Iam already aware, that it would probably only work for people, who installed the Gn

RE: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

> -Original Message- > From: Derick Rethans [mailto:der...@derickrethans.nl] > Sent: Wednesday, January 20, 2016 9:04 PM > To: PHP Developers Mailing List > Subject: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct > > Hi, > > I've decided to re-propose the CoC RFC. There are many rea

Re: [PHP-DEV] WIKI: phpng-upgrading

On Thu, Jan 21, 2016 at 06:55:41AM +0900, Yasuo Ohgaki wrote: > Hi ZendEngine developers, > > I'm not sure if the wiki page is maintained, but I noticed few errors. > > https://wiki.php.net/phpng-upgrading#strings > has following example. > > - ZVAL_STRING(zv, str, 1); > + ZVAL_STRING(zv, str); > >

Re: [PHP-DEV] [RFC][VOTE] Number Format Separator

Hi Andrea, On Thu, Jan 21, 2016 at 4:18 AM, Andrea Faulds wrote: > > One other approach I thought of is to use constant scalar expressions: > > +('123'.'456'.'789') > > It's not quite the same of native support, but it works. This is what I do on occasions. I have to read var_export()ed PHP cod

[PHP-DEV] WIKI: phpng-upgrading

Hi ZendEngine developers, I'm not sure if the wiki page is maintained, but I noticed few errors. https://wiki.php.net/phpng-upgrading#strings has following example. - ZVAL_STRING(zv, str, 1); + ZVAL_STRING(zv, str); - ZVAL_STRINGL(zv, str, len, 1); + ZVAL_STRINGL(zv, str, len); - ZVAL_STRING(z

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Wed, 20 Jan 2016, Pavel Kouřil wrote: > On Wed, Jan 20, 2016 at 8:04 PM, Derick Rethans > wrote: > > > > I've decided to re-propose the CoC RFC. There are many reasons for it, > > but there are a few points I want to make. > > if you still insists on some CoC, maybe you could at least look i

AW: [PHP-DEV] [RFC] Allow specifying keys in list()

Hi Andrea I am writing you in private since I think this is rather out of scope. -Ursprüngliche Nachricht- > Von: Pierre Joye [mailto:pierre@gmail.com] > Gesendet: Montag, 18. Januar 2016 05:54 > An: Andrea Faulds > Cc: PHP internals > Betreff: Re: [PHP-DEV] [RFC] Allow specifying ke

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Wed, Jan 20, 2016 at 8:04 PM, Derick Rethans wrote: > Hi, > > I've decided to re-propose the CoC RFC. There are many reasons for it, > but there are a few points I want to make. > > > cheers, > Derick > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Wed, Jan 20, 2016 at 8:37 PM, Paul M. Jones wrote: > > > On Jan 20, 2016, at 13:04, Derick Rethans > wrote: > > > > Hi, > > > > I've decided to re-propose the CoC RFC. > > Is it a violation of the RFC rules to skip step 1 ("Email > internals@lists.php.net to measure reaction to your intended

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Wed, 20 Jan 2016, Stanislav Malyshev wrote: > > You can't do it on the /blob/ view, but if you click on the commit > > to get to the /commit/ view, you can comment on that. :) > > Right. That's what I meant by "patches". But that only specific commit, > not the whole result, right? Correct -

[PHP-DEV] RE: [RFC][VOTE] Number Format Separator

Hi internals! > Voting has opened for the inclusion of a digit separator in PHP[1]. Voting > ends in > one week's time on January 20th. Voting has now ended with 20 for and 18 against. This means the RFC has been declined. Thank you to all who participated in the RFC discussion and voting! -To

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi Stas, Stanislav Malyshev wrote: Hi! You can't do it on the /blob/ view, but if you click on the commit to get to the /commit/ view, you can comment on that. :) Right. That's what I meant by "patches". Ah, okay. I took that to mean pull requests. But that only specific commit, not the

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi! > You can't do it on the /blob/ view, but if you click on the commit to > get to the /commit/ view, you can comment on that. :) Right. That's what I meant by "patches". But that only specific commit, not the whole result, right? -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi Paul, Paul M. Jones wrote: On Jan 20, 2016, at 13:04, Derick Rethans wrote: Hi, I've decided to re-propose the CoC RFC. Is it a violation of the RFC rules to skip step 1 ("Email internals@lists.php.net to measure reaction to your intended proposal") and go straight to step 3 ("Create

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi Stas, Stanislav Malyshev wrote: Hi! In order to make suggestions to the wording of the RFCs, and included Contributer Covenant and Guideslines easier, I've imported it into GitHub: https://github.com/derickr/php-code-of-conduct/blob/master/RFC.rst Great idea. Unfortunately, I don't see a

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi! > In order to make suggestions to the wording of the RFCs, and included > Contributer Covenant and Guideslines easier, I've imported it into > GitHub: > > https://github.com/derickr/php-code-of-conduct/blob/master/RFC.rst Great idea. Unfortunately, I don't see any way in Github to comment

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

On Wed, Jan 20, 2016 at 8:37 PM, Paul M. Jones wrote: > > > On Jan 20, 2016, at 13:04, Derick Rethans > wrote: > > > > Hi, > > > > I've decided to re-propose the CoC RFC. > > Is it a violation of the RFC rules to skip step 1 ("Email > internals@lists.php.net to measure reaction to your intended

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi, In order to make suggestions to the wording of the RFCs, and included Contributer Covenant and Guideslines easier, I've imported it into GitHub: https://github.com/derickr/php-code-of-conduct/blob/master/RFC.rst If you have specific suggestions, they're more than welcome there through Pul

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

> On Jan 20, 2016, at 13:04, Derick Rethans wrote: > > Hi, > > I've decided to re-propose the CoC RFC. Is it a violation of the RFC rules to skip step 1 ("Email internals@lists.php.net to measure reaction to your intended proposal") and go straight to step 3 ("Create the RFC") ?

Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Am 20.01.16 um 20:04 schrieb Derick Rethans: > Hi, > > I've decided to re-propose the CoC RFC. There are many reasons for it, > but there are a few points I want to make. > > I strongly believe that a Code of Conduct is required. The amount of > toxic behaviour on this list is in my opinion una

Re: [PHP-DEV] [RFC][VOTE] Number Format Separator

Hi Pascal, Pascal MARTIN, AFUP wrote: Le 13/01/2016 19:48, Thomas Punt a écrit : Voting has opened for the inclusion of a digit separator in PHP[1]. Voting ends in one week's time on January 20th. Hi, At AFUP, we would be on the -1 side (by a huge margin). The "good" thing would be code tha

[PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct

Hi, I've decided to re-propose the CoC RFC. There are many reasons for it, but there are a few points I want to make. I strongly believe that a Code of Conduct is required. The amount of toxic behaviour on this list is in my opinion unacceptable. It drives people away, it certainly did. It is

[PHP-DEV] NEUTRAL Benchmark Results for PHP Master 2016-01-20

Results for project PHP master, build date 2016-01-20 06:29:57+02:00 commit: dcf3db6 previous commit:8e60e0c revision date: 2016-01-19 22:26:32+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

[PHP-DEV] [RFC] [Withdrawn] Adopt Code of Conduct

All, I've decided to withdraw the CoC RFC. There are many reasons for it, but there are a few points I want to make. As to the content of the RFC, when I initially proposed it, I selected the Contributor Covenant due to it being a well adopted standard. Several people raised objections to it, and

[PHP-DEV] [RFC][VOTE] OpenSSL AEAD support

Hi, The vote is now open: https://wiki.php.net/rfc/openssl_aead#voting Cheers Jakub

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

The bottom line is that the only requisite for contributors is professionalism. People should keep non-work related issues to themselves inside the workplace, as well as they should be respectful to each other no matter what. However, if someone is professional and has never posted off-topic opini

Re: [PHP-DEV] [RFC] [VOTE] Class Constant Visibility

On 08/12/15 10:56, Dmitry Stogov wrote: > Hi Sean, > > The PR has been merged into master. > Please update the RFC accordingly. > Thanks to Nikita and Xinchen for code review and suggestions. > This patch seems to cause problems for me with registering constants on internal interfaces; see bug #