Re: [PHP-DEV] RFC: Deprecate mb_ereg_replace eval option

Hi Rouven, On 4 January 2016 at 16:46, Rouven Weßling wrote: > I’d like to propose the following RFC to you > https://wiki.php.net/rfc/deprecate_mb_ereg_replace_eval_option > > The mandatory discussion period will end January 19th. Are the wrong functions are listed

Re: [PHP-DEV] Re: [RFC] array_key_(first|last|index) functions proposal

On 04/01/2016 17:05, Andrea Faulds wrote: How often would such functions be useful? Perhaps they fill a gap, but I'm not sure if it's one that needs filling. array_key_first and array_key_last can already be accomplished in two or so lines of code (four if you make a function), and

Re: [PHP-DEV] Re: RFC Operator Overloading in Userspace

On 04/01/2016 16:34, Andrea Faulds wrote: In Haskell, a purely-functional programming language, certain operators (and also certain math functions like abs()) are defined as part of "typeclasses", somewhat akin to interfaces in classical object-oriented languages like Java or PHP. These

Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

On 1 January 2016 at 12:12, Bishop Bettini wrote: > On Fri, Jan 1, 2016 at 2:53 PM, John Bafford wrote: >> I think when I brought this up before, the major open discussion point >> before the thread died was what period of time constituted long enough for >>

Re: [PHP-DEV] Re: Testing HTTP/2 support in PHP

Hi Andrea On Mon, Jan 4, 2016 at 5:16 PM, Andrea Faulds wrote: > Hi Davey, > > Davey Shafik wrote [snip] We could also add a flag (e.g. --[no-]http2) on the CLI for >> enabling/disabling it — this would be helpful for testing HTTP/2 client >> fallback when it's not supported. >>

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

Hey all, I have created a new RFC for the PHP Project to adopt the Contributor Covenant as the official Code of Conduct for the project https://wiki.php.net/rfc/adopt-code-of-conduct Let me know what you think or if there are any concerns Thanks Anthony -- PHP Internals - PHP Runtime

Re: [PHP-DEV] RFC Operator Overloading in Userspace

On Sat, 2016-01-02 at 18:14 -0800, Sara Golemon wrote: > https://wiki.php.net/rfc/operator-overloading Back in the days when I created the first implementation of operator overloading in the engine[1] I didn't see it fit for the language. Meanwhile we have more type hints and stuff making it a

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

On Fri, Jan 1, 2016 at 9:20 PM, Johannes Schlüter wrote: > On Fri, 2016-01-01 at 13:28 -0500, Bishop Bettini wrote: >> Hi, and happy New Year! >> >> Now that the big push for PHP 7 is done, I'd like to revive earlier >> discussions >>

Re: [PHP-DEV] RFC Operator Overloading in Userspace

On Sat, 2 Jan 2016, Sara Golemon wrote: > Patricio Tarantino has asked me to help him propose Operator > Overloading in PHP 7.1 (based in part on my operator extension in > PECL). I think we can expose this to usespace as magic methods with > very little overhead (the runtime check and dispatch

Re: [PHP-DEV] Simple project started segfaulting on 7.1-dev - where to report that?

On Mon, 4 Jan 2016, Julien Pauli wrote: > On Fri, Jan 1, 2016 at 8:13 PM, Grzegorz Zdanowski > wrote: > > Hi! > > > > Couple minutes ago I came across segfault in nightly builds of PHP. > > Normally I will report it at bugs.php.net but environment is little > >

Re: [PHP-DEV] Simple project started segfaulting on 7.1-dev - where to report that?

On Fri, 1 Jan 2016, Grzegorz Zdanowski wrote: > Couple minutes ago I came across segfault in nightly builds of PHP. > Normally I will report it at bugs.php.net but environment is little > complicated here. > > - Segfault is only present on TravisCI -> so maybe bug should be > reported to

Re: [PHP-DEV] Simple project started segfaulting on 7.1-dev - where to report that?

On Fri, Jan 1, 2016 at 8:13 PM, Grzegorz Zdanowski wrote: > Hi! > > Couple minutes ago I came across segfault in nightly builds of PHP. Normally > I will report it at bugs.php.net but environment is little complicated here. > > - Segfault is only present on TravisCI -> so

Re: [PHP-DEV] [RFC] Differentiate op from assign-op in operator overloading

On Mon, Jan 4, 2016 at 1:37 AM, Sara Golemon wrote: > This is a separate proposal from the userspace operator overloading I > put up for Patricio yesterday and aims to fix what I see as a bug in > our operator overloading implementation (though some may disagree). > > It

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

On Mon, Jan 4, 2016 at 4:41 PM, Adam Harvey wrote: > On 4 January 2016 at 13:06, Anthony Ferrara wrote: >> I have created a new RFC for the PHP Project to adopt the Contributor >> Covenant as the official Code of Conduct for the project >> >>

Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

Hi! > Warn at 2 weeks, close at 4? There's no real harm in closing it unmerged: > the submitter can always resubmit. That sounds way too short. I mean if we did process all worthy pulls in matter of days, then fine (but see below) but we are very far from that. And when we take a long time to

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

On Mon, Jan 4, 2016 at 10:45 PM, Stanislav Malyshev wrote: > Hi! > > > I have created a new RFC for the PHP Project to adopt the Contributor > > Covenant as the official Code of Conduct for the project > > > > https://wiki.php.net/rfc/adopt-code-of-conduct > > > > Let me

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

On 4 January 2016 at 13:06, Anthony Ferrara wrote: > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct I am definitely pro-this. Good thinking!

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

Adam, On Mon, Jan 4, 2016 at 4:41 PM, Adam Harvey wrote: > On 4 January 2016 at 13:06, Anthony Ferrara wrote: >> I have created a new RFC for the PHP Project to adopt the Contributor >> Covenant as the official Code of Conduct for the project >> >>

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

On 1/4/16 4:45 PM, Stanislav Malyshev wrote: > Looks to me like solution in search of a problem. I'm with PHP project > since 90s, and maybe it is my biased view As someone who originally was hesitant to do something similar with his conferences. I can speak that the reason for such a proposal

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

On Tue, Jan 5, 2016 at 7:21 AM, Eli wrote: > On 1/4/16 4:45 PM, Stanislav Malyshev wrote: >> Looks to me like solution in search of a problem. I'm with PHP project >> since 90s, and maybe it is my biased view > > As someone who originally was hesitant to do something similar with

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

On Mon, Jan 4, 2016 at 4:06 PM, Anthony Ferrara wrote: > Hey all, > > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct > > Let me know what you

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

Hi! > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct > > Let me know what you think or if there are any concerns Looks to me like solution in search of a

Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

On Mon, Jan 4, 2016 at 3:26 PM, Adam Harvey wrote: > On 1 January 2016 at 12:12, Bishop Bettini wrote: > > On Fri, Jan 1, 2016 at 2:53 PM, John Bafford wrote: > >> I think when I brought this up before, the major open discussion point > >>

Re: [PHP-DEV] Re: RFC Operator Overloading in Userspace

Hi Rowan, Rowan Collins wrote: On 04/01/2016 16:34, Andrea Faulds wrote: In Haskell, a purely-functional programming language, certain operators (and also certain math functions like abs()) are defined as part of "typeclasses", somewhat akin to interfaces in classical object-oriented languages

Re: [PHP-DEV] Re: RFC Operator Overloading in Userspace

Hi! > constraint on function parameters and return types. I think it would be > more worth pursuing a Haskell-style approach in PHP, most likely with a > hierarchy of magic interfaces. I agree that interface approach looks better than Python/C++ approach for PHP. One thing it also allows is

[PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

I swear, 2016 isn't going to be "An RFC per day" year, but... https://wiki.php.net/rfc/token-get-always-tokens This should be pretty non-controversial. I hope? -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

Hi! > https://wiki.php.net/rfc/token-get-always-tokens > > This should be pretty non-controversial. I hope? No way! Just kidding :) I think it's a great idea, token_get_all() is annoying to deal with. We'd have to fix token_name though so that this would still work: foreach ($tokens as

Re: [PHP-DEV] Re: RFC Operator Overloading in Userspace

Hi Stas, Stanislav Malyshev wrote: Hi! constraint on function parameters and return types. I think it would be more worth pursuing a Haskell-style approach in PHP, most likely with a hierarchy of magic interfaces. I agree that interface approach looks better than Python/C++ approach for

Re: [PHP-DEV] Re: Testing HTTP/2 support in PHP

Hi Andrea, On Jan 5, 2016 12:16 AM, "Andrea Faulds" wrote: > > Hi Davey, > > > Davey Shafik wrote: >> >> However, Rasmus raised the possibility of adding HTTP/2 support to the >> cli-server [2], and (someone? @php-pulls) suggested we pull in a third >> party lib to do the heavy

Re: [PHP-DEV] RFC Operator Overloading in Userspace

> Am 4.1.2016 um 20:39 schrieb Johannes Schlüter : > > On Sat, 2016-01-02 at 18:14 -0800, Sara Golemon wrote: >> https://wiki.php.net/rfc/operator-overloading > > Back in the days when I created the first implementation of operator > overloading in the engine[1] I didn't

Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

On Mon, Jan 4, 2016 at 4:21 PM, Stanislav Malyshev wrote: > I think it's a great idea, token_get_all() is annoying > to deal with. We'd have to fix token_name though so that this would > still work: > Ah, excellent point! > We could, of course, do something like >

Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

Hi! >> We could, of course, do something like >> $token[0]<=255?$token[0]:token_name($token[0]) - but that looks hacky. >> > Do you mean have users of the API do that? Or have the implementation > of token_name() do that? Because the latter doesn't seem unreasonable > at all. I meant for

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

> On Jan 4, 2016, at 21:48, Michael Cullum wrote: > > I do apologise for saying offender, it was the wrong word to use there, but I > think the context of the rest of my post made it clear the meaning was not > meant to say that they were automatically guilty (although

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

> On Jan 4, 2016, at 22:31, Sara Golemon wrote: > > On Mon, Jan 4, 2016 at 8:26 PM, Paul M. Jones wrote: >> This RFC is not about "respect." It is about a cabal being able to ban at >> will, without supervision or oversight, based on their own whims. The

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

On Mon, Jan 4, 2016 at 8:40 PM, Paul M. Jones wrote: >> No definitions, no oversight, just straight up "the will of the star >> chamber." It's naked power masquerading as care-and-respect. > Please, offer definitions. Offer paths to oversight you deem sufficient. An RFC is

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

On Tue, Jan 5, 2016 at 1:37 AM, Stanislav Malyshev wrote: > Hi! > > > The effort to create and adopt a CoC is minimal and the benefits are > > huge. It creates, confirms or ensure that the context of the php.net > > remains a safe for anyone to contribute. > > It also

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

Hi! > for that to happen you need a corrupt CoC team, a fairly unknown N Define "corrupt". They may believe they are doing the world a huge favor by getting us rid of horrible, terrible, no good N. The problem is that they'd be doing it without needing any consensus and will have a good chance

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

Huge +1 to this for the reasons stated both by Eli about why it should exist, and the reasons mentioned by Ferenc in that it's not giving out new powers, but adding accountability to the use of those powers. I do think however there is some fine tuning that could be done. 1) When a summary report

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

> On Jan 4, 2016, at 20:31, Michael Cullum wrote: > > Huge +1 to this for the reasons stated both by Eli about why it should > exist, and the reasons mentioned by Ferenc in that it's not giving out new > powers, but adding accountability to the use of those powers. I do

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

> On Jan 4, 2016, at 22:10, Pierre Joye wrote: > > What you define in a > very disrespectful way as "poor little hurt" is matter of mutual > respects. This RFC is not about "respect." It is about a cabal being able to ban at will, without supervision or oversight, based

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

> On Jan 4, 2016, at 22:00, Pierre Joye wrote: > > I think many > already explained why it is not about free speech but protection and > about confirm and ensure a safe context, given you understand what > "safe" means here. Protection *from what* exactly? Clearly I don't

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

Really, the core portion of this RFC that reveals how it will be used, is this: > Project maintainers have the right and responsibility to to ban temporarily or > permanently any contributor for other behaviors that they deem inappropriate, > threatening, offensive, or harmful. No definitions,

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

> On Jan 4, 2016, at 22:46, Sara Golemon wrote: > > On Mon, Jan 4, 2016 at 8:40 PM, Paul M. Jones wrote: >>> No definitions, no oversight, just straight up "the will of the star >>> chamber." It's naked power masquerading as care-and-respect. >> >

Re: [PHP-DEV] Re: Additional Rounding modes for the round() function

On 04/01/2016 17:12, Andrea Faulds wrote: Hi Mark, Mark Baker wrote: I'd like to suggest a couple of additional options for the round() function, two new flags for PHP_ROUND_UP and PHP_ROUND_DOWN; which are similar to the existing ceil() and floor() functions, but allow a precision argument as

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

On Tue, Jan 5, 2016 at 1:55 AM, Stanislav Malyshev wrote: > Hi! > > > currently I (and a bunch of other people) could revoke anybody's karma, > > how is this any different(ofc. it would be reverted and I would get a > > scolding)? > > The difference is that those 5(3) people

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

On Mon, 4 Jan 2016 at 21:07 Anthony Ferrara wrote: > Hey all, > > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct > > Let me know what you

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

Hi! > Right, that's one of the parts that need more work and thoughts. My > comment was mainly about the usefulness of a CoC. If we're talking about having a declaration of principles, I am not sure we need elaborate text to say "don't be an ass" but I don't mind having one in case somebody ever

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

On Mon, Jan 4, 2016 at 4:37 PM, Stanislav Malyshev wrote: > It also provides a way for 5 (or, since CoC mechanisms are not specified > at all, even 3 assuming CoC decides by majority) people to accuse any > member of the community of some pretty dark things (without even

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

I do apologise for saying offender, it was the wrong word to use there, but I think the context of the rest of my post made it clear the meaning was not meant to say that they were automatically guilty (although at the point in proceedings I was referring to was where their name had been released

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

> On Jan 4, 2016, at 21:22, Bishop Bettini wrote: > > Every long standing collaborative system adopts, uses, and sheds rules of > conduct to suit its real and perceived challenges. Including the one headed by Linus Torvalds, right? (/me rolls eyes) I don't know which is

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

On Tue, Jan 5, 2016 at 10:47 AM, Paul M. Jones wrote: > >> On Jan 4, 2016, at 21:22, Bishop Bettini wrote: >> >> Every long standing collaborative system adopts, uses, and sheds rules of >> conduct to suit its real and perceived challenges. > > Including the

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

> On Jan 4, 2016, at 22:42, Sara Golemon wrote: > > Formalized rules and due process are terrible for a free and open society? This proposal is neither formalized, nor due process. You're great at C, Sara, but you're horrible at law. OMG WAS THAT OFFENSIVE? BAN BAN BAN!

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

Hi! > The effort to create and adopt a CoC is minimal and the benefits are > huge. It creates, confirms or ensure that the context of the php.net > remains a safe for anyone to contribute. It also provides a way for 5 (or, since CoC mechanisms are not specified at all, even 3 assuming CoC

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

On Tue, Jan 5, 2016 at 7:37 AM, Stanislav Malyshev wrote: > Hi! > >> The effort to create and adopt a CoC is minimal and the benefits are >> huge. It creates, confirms or ensure that the context of the php.net >> remains a safe for anyone to contribute. > > It also provides a

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

Hi! > be rarely needed, I could only remember/find two instances when we had > to ban somebody from the list: > http://marc.info/?l=php-general=102852881828032=2 (which was a > controversial action as it turned out later) > and > https://www.mail-archive.com/internals@lists.php.net/msg57482.html

[PHP-DEV] Re: [RFC Discussion] Precise Session Management

Hi all, On Sat, Dec 19, 2015 at 7:33 AM, Yasuo Ohgaki wrote: > I would like to restart better session management for PHP 7.1. > > https://wiki.php.net/rfc/precise_session_management > > Although this RFC targets PHP 7.1, new session management > could be applied to older

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

Hi! > It's really not much more than Wheaton's Law in a form that > (hopefully) is just detailed enough to stop someone from being able to > say "but you didn't explicitly say I couldn't abuse someone because > $X". That assumes we told somebody that anything goes unless it's explicitly

Re: [PHP-DEV] Re: Testing HTTP/2 support in PHP

Hi Pierre, Pierre Joye wrote: Hi Andrea, On Jan 5, 2016 12:16 AM, "Andrea Faulds" wrote: Hmm, this would mean a new dependency, and more potential complexity. I'm not sure if HTTP/2 justifies it. Also, don't all the major client implementations of HTTP/2 require TLS? Or is

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

On Mon, 2016-01-04 at 17:34 -0800, Stanislav Malyshev wrote: > My main issue is with procedures which can have real impact on people > and the atmosphere in the project and have IMHO way too little > safeguards for that as proposed. Of course, as I said, there's not much > need for that procedure

Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

On Mon, Jan 4, 2016 at 7:38 PM, Stanislav Malyshev wrote: >> Do you mean have users of the API do that? Or have the implementation >> of token_name() do that? Because the latter doesn't seem unreasonable >> at all. > > I meant for token_name() to do that internally, so that

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

> On Jan 4, 2016, at 22:32, Paul M. Jones wrote: > > Really, the core portion of this RFC that reveals how it will be used, is > this: > >> Project maintainers have the right and responsibility to to ban temporarily >> or >> permanently any contributor for other

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

On Tue, Jan 5, 2016 at 7:53 AM, Paul M. Jones wrote: > >> On Jan 4, 2016, at 18:21, Eli wrote: >> >> On 1/4/16 4:45 PM, Stanislav Malyshev wrote: >>> Looks to me like solution in search of a problem. I'm with PHP project >>> since 90s, and maybe it is my

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

Hi Bishop, Bishop Bettini wrote: I am -1 on removing @ for 7.x series. But, I would be in favor of all changes that remove unnecessary error messages or add functionality to better work with error messages. In my mind, those are requisite steps before removing @. I agree here. It'd be nice

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

On Thu, Dec 31, 2015 at 1:10 PM, Stanislav Malyshev wrote: > I don't think it is a good idea, currently, for the following reasons: > [::snip::] It terrifies me to say this, but I completely agree with Stas. ;) I can't personally remember the last time I used @ in any

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

On Jan 4, 2016 10:00 PM, "Paul M. Jones" wrote: > > > > On Jan 4, 2016, at 20:31, Michael Cullum wrote: > > > > Huge +1 to this for the reasons stated both by Eli about why it should > > exist, and the reasons mentioned by Ferenc in that it's not

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

On Tue, Jan 5, 2016 at 11:00 AM, Pierre Joye wrote: > On Tue, Jan 5, 2016 at 10:47 AM, Paul M. Jones wrote: >> >>> On Jan 4, 2016, at 21:22, Bishop Bettini wrote: >>> >>> Every long standing collaborative system adopts, uses, and sheds

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

On Mon, Jan 4, 2016 at 8:34 PM, Paul M. Jones wrote: >> There is supervision, there is oversight. >> The oversight is this list. Any council issuing temp-bans without >> justification will be sanctioned. >> I'm quite certain that you, among others, will see to that. > > If

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

> On Jan 4, 2016, at 18:21, Eli wrote: > > On 1/4/16 4:45 PM, Stanislav Malyshev wrote: >> Looks to me like solution in search of a problem. I'm with PHP project >> since 90s, and maybe it is my biased view > > As someone who originally was hesitant to do something similar with

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

Hi! > currently I (and a bunch of other people) could revoke anybody's karma, > how is this any different(ofc. it would be reverted and I would get a > scolding)? The difference is that those 5(3) people get a special stand, while right now everybody is equal (well, there are RMs but that is

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

On 4 January 2016 at 17:34, Stanislav Malyshev wrote: > If we're talking about having a declaration of principles, I am not sure > we need elaborate text to say "don't be an ass" but I don't mind having > one in case somebody ever need explicit instructions on how exactly not

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

Hi Bishop, > On Dec 31, 2015, at 3:48 PM, Bishop Bettini wrote: > > I am -1 on removing @ for 7.x series. But, I would be in favor of all > changes that remove unnecessary error messages or add functionality to > better work with error messages. In my mind, those are requisite

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

On Mon, Jan 4, 2016 at 8:26 PM, Paul M. Jones wrote: > This RFC is not about "respect." It is about a cabal being able to ban at > will, without supervision or oversight, based on their own whims. The > "respect" bit is a velvet glove on an iron fist. > There is

Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)

Total +1. I wanted to propose that, without the flag, but it got too late for the PHP7 BC breaking season. Adding a flag seems to be a better idea :P 2016-01-04 18:56 GMT-04:00 Sara Golemon : > I swear, 2016 isn't going to be "An RFC per day" year, but... > >

Re: [PHP-DEV] RFC Operator Overloading in Userspace

Hi, I did consider that as an alternate option. function overload_register($op, $lhtype, $rhtype, $callback); overload_type(ZEND_ADD, 'Complex', 'any', 'Complex::add'); This would get pretty expensive in terms of large lookup tables though, so I'm hesitant there. This is much better, IMO, as

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

> On Jan 4, 2016, at 23:19, Félix Gagnon wrote: > > @Paul can you really be flaming all this stuff? Most of your messages seem to > be virulent hateful speeches, and you wonder why people support this? What "hate" is being propounded? This is exactly what I mean:

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

Hi! > 2) To the claim that "we're all equal now", that's hogwash. :-) PHP > Internals may not have a formal structure or hierarchy beyond Release > Managers, but because it's a group of more than 2 people there is of > course an implicit, informal power structure. The best writeup on that >

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

Hi! > difficult as it would be unlikely that 5 people would all be 'corrupt' in > the same fashion compared to one where lots of individuals hold that power > and can exercise it on their own. Here's that "corrupt" again - but the point here is that no corruption is necessary. Human perception

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

On 01/04/2016 07:22 PM, Sara Golemon wrote: > On Thu, Dec 31, 2015 at 1:10 PM, Stanislav Malyshev > wrote: >> I don't think it is a good idea, currently, for the following reasons: >> > [::snip::] > > It terrifies me to say this, but I completely agree with Stas. ;) > > I

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

On Mon, Jan 4, 2016 at 9:45 PM, Sara Golemon wrote: > On Thu, Dec 31, 2015 at 6:52 AM, Junade Ali wrote: >> I am looking to submit an RFC in order to remove the error suppression >> operator in PHP, namely the @ symbol. >> > Forwarding a suggestion

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

Hi, chiming in from the side, On Tue, Jan 5, 2016 at 12:45 AM, Sara Golemon wrote: > Forwarding a suggestion twitter/@Beryllium9: > > How about a global "disable error suppression" setting? That way a > project lead could enforce it for their codebase (and guarantee that > devs

Re: [PHP-DEV] Re: RFC Operator Overloading in Userspace

On 01/04/2016 05:04 PM, Andrea Faulds wrote: I agree that we could do something with interfaces. I would like to point out that we actually already have an example of this, in the form of the \ArrayAccess interface, which requires you to implement all the different indexing operations at once.

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

I'm not exactly sure how far down the rabbit hole I'm going with this but... @Paul can you really be flaming all this stuff? Most of your messages seem to be virulent hateful speeches, and you wonder why people support this? 2016-01-04 23:50 GMT-05:00 Paul M. Jones : > > >

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

On 01/04/2016 03:06 PM, Anthony Ferrara wrote: Hey all, I have created a new RFC for the PHP Project to adopt the Contributor Covenant as the official Code of Conduct for the project https://wiki.php.net/rfc/adopt-code-of-conduct Let me know what you think or if there are any concerns Thanks

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

On 5 January 2016 at 05:49, Paul M. Jones wrote: > > > On Jan 4, 2016, at 22:42, Sara Golemon wrote: > > > > Formalized rules and due process are terrible for a free and open > society? > > This proposal is neither formalized, nor due process. You're great

Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)

On Thu, Dec 31, 2015 at 6:52 AM, Junade Ali wrote: > I am looking to submit an RFC in order to remove the error suppression > operator in PHP, namely the @ symbol. > Forwarding a suggestion twitter/@Beryllium9: How about a global "disable error suppression" setting? That way a

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

Hi, PHP friends. Following on from Larry’s comments, here’s a thing I wrote one time: https://gist.github.com/nateabele/8d156730dc428322fca5 Someone proposed adding the Contributor Covenant to one of my OS projects. I read it, and some of the language made me a little uncomfortable, so I

[PHP-DEV] RFC: Deprecate mb_ereg_replace eval option

Dear internals, I’d like to propose the following RFC to you https://wiki.php.net/rfc/deprecate_mb_ereg_replace_eval_option The mandatory discussion period will end January 19th. Best regards Rouven -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

[PHP-DEV] Re: Additional Rounding modes for the round() function

Hi Mark, Mark Baker wrote: I'd like to suggest a couple of additional options for the round() function, two new flags for PHP_ROUND_UP and PHP_ROUND_DOWN; which are similar to the existing ceil() and floor() functions, but allow a precision argument as well. The PR is at

[PHP-DEV] Re: Testing HTTP/2 support in PHP

Hi Davey, Davey Shafik wrote: However, Rasmus raised the possibility of adding HTTP/2 support to the cli-server [2], and (someone? @php-pulls) suggested we pull in a third party lib to do the heavy lifting [3]. My recommendation would be to use libnghttp2 [4] which curl also uses — however, as

[PHP-DEV] Re: RFC Operator Overloading in Userspace

Hi Sara, Sara Golemon wrote: Patricio Tarantino has asked me to help him propose Operator Overloading in PHP 7.1 (based in part on my operator extension in PECL). I think we can expose this to usespace as magic methods with very little overhead (the runtime check and dispatch is already there,

[PHP-DEV] Re: [RFC] array_key_(first|last|index) functions proposal

Hi John, John Bafford wrote: Happy New Year, everyone! I’d like to present the first new PHP RFC for this year, a proposal to add functions to easily get the first, last, or an arbitrary key (and value) by index from an array, taking advantage of PHP’s property that arrays are ordered maps.

Re: [PHP-DEV] [RFC] On-Demand Name Mangling

On Sat, Jan 2, 2016 at 11:45 AM, Rowan Collins wrote: > On 02/01/2016 03:09, Bishop Bettini wrote: > >> But, even without a setting, there's an escape hatch: userland can >> polyfill >> the mangling behavior using extract. The updated RFC demonstrates an >> algorithm.

[PHP-DEV] Wiki RFC karma request: duncan3dc

Hi, I'd like to create an RFC to change the behaviour of counting objects, as discussed in the following pull request: https://github.com/php/php-src/pull/1672 Please can I be granted rfc karma so I can create this? My wiki username is duncan3dc Thanks, Craig

Re: [PHP-DEV] Re: [RFC] array_key_(first|last|index) functions proposal

Hi Andrea, > On Jan 4, 2016, at 12:05, Andrea Faulds wrote: > > Hi John, > > John Bafford wrote: >> Happy New Year, everyone! >> >> I’d like to present the first new PHP RFC for this year, a proposal to add >> functions to easily get the first, last, or an arbitrary key (and