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

Sounds like the xdebug.scream or the Scream PECL extension ( https://pecl.php.net/package/scream) to me. +1 for baking this functionality into core On Tue, Jan 5, 2016 at 5:45 AM, Sara Golemon wrote: > On Thu, Dec 31, 2015 at 6:52 AM, Junade Ali wrote: > > I

[PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline

Hopefully mostly everyone is back from the holidays by now, the vote is now open for the PHP 5 Support Timeline RFC: https://wiki.php.net/rfc/php56timeline#vote Voting ends January 13th 2016 at 10:00am GMT. Thanks! Zeev

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

> -Original Message- > From: a...@adamharvey.name [mailto:a...@adamharvey.name] On > Behalf Of Adam Harvey > Sent: Tuesday, January 05, 2016 3:46 AM > To: Stanislav Malyshev > Cc: PHP internals > Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct > > On 4 January 2016 at 17:34,

Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline

Hi, just bumping this so that there is less chance this gets lost in the CoC thread :-) cheers, Derick On Tue, 5 Jan 2016, Zeev Suraski wrote: > Hopefully mostly everyone is back from the holidays by now, the vote is now > open for the PHP 5 Support Timeline RFC: > > > >

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

Grzegorz Zdanowski wrote on 05/01/2016 12:27: Before deprecating @ operator I think we should make a RFC which cover unified setting to convert all E_* to exceptions (like PhpWarningException). I know it's just a temporary solution, because exception should be more specific, but it's a huge

[PHP-DEV] Proposed change in json_encode+JSON_UNESCAPED_UNICODE behavior

Hi, I'm proposing a small change in the behavior of `json_encode(str, JSON_UNESCAPED_UNICODE)` around the issue of line terminators. The U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR characters are allowed unescaped in JSON strings, but *not* allowed unescaped in Javascript. This is

Re: [PHP-DEV] What's up with gcov.php.net?

On Thu, Dec 31, 2015 at 10:26 AM, Xinchen Hui wrote: > Hey: > > > On Thu, Dec 31, 2015 at 5:19 PM, Michael Wallner wrote: > > > > > > On 30 12 2015, at 22:34, Andrea Faulds wrote: > > > > > > Hi everyone, > > > > > > If any of you have looked at

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

On 5 January 2016 at 16:59, Stanislav Malyshev wrote: > Hi! > > > How exactly would you feel about having all of this made explicit to all > > the other PHP devs? Presumably you look up to some of these people - > > I presume you would feel bad. However your example is

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

> On Jan 5, 2016, at 10:03 AM, Paul M. Jones wrote: > > >> On Jan 5, 2016, at 09:55, Ben Ramsey wrote: >> >> >>> On Jan 4, 2016, at 10:29 PM, Paul M. Jones wrote: >>> >>> If there's an accusation, then *due process* needs to be

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

On 05/01/2016 15:59, François Laupretre wrote: Anyway, I don't say that it cannot happen, I just say that, AFAIK, we never got such concerns in the PHP community. So, maybe we should go the 'politically-correct' way but I'm afraid that's just a waste of time or, as Stas said, a solution for

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

All, 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

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

On Jan 5, 2016 11:13 PM, "Derick Rethans" wrote: > > On Tue, 5 Jan 2016, François Laupretre wrote: > > > Le 05/01/2016 15:31, Peter Lind a écrit : > > > > > A quick question: suppose you're from a minority group, and you've been the > > > target of abuse previously your life. You

[PHP-DEV] Help Design a New Cryptography API for PHP 7.1

TL;DR, make this part of PHP 7.1: $cipher = new Php\Crypto\Symmetric([ 'driver' => 'openssl' ]); $key = $cipher->deriveKey( $someUserProvidedPasswordString, $someHardCodedSalt ); $encrypted = $cipher->encrypt($message, $key); I'm developing a userland

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

On Tue, Jan 5, 2016 at 3:57 AM, Zeev Suraski wrote: >> From: Derick Rethans [mailto:der...@php.net] >> That's going to mean an INI setting.. that hosters could abuse. >> Having an INI setting like this as part of core is IMO not a great idea. > I honestly don't understand why

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

On Tue, 5 Jan 2016, François Laupretre wrote: > Le 05/01/2016 15:31, Peter Lind a écrit : > > > A quick question: suppose you're from a minority group, and you've been the > > target of abuse previously your life. You now join the PHP community and for > > whatever reason, someone takes a dislike

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

Le 05/01/2016 15:31, Peter Lind a écrit : A quick question: suppose you're from a minority group, and you've been the target of abuse previously your life. You now join the PHP community and for whatever reason, someone takes a dislike to you and starts harassing you in private. The abuse

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

On 1/5/16 11:08 AM, Pierre Joye wrote: Anyway, I don't say that it cannot happen, I just say that, AFAIK, we never got such concerns in the PHP community. Sorry - not true. I can name several issues from various PHP related conferences. Although not directly under the "control" of the PHP

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

On Tue, Jan 5, 2016 at 11:08 AM, Mark Baker wrote: > On 05/01/2016 15:59, François Laupretre wrote: >> >> >> Anyway, I don't say that it cannot happen, I just say that, AFAIK, we >> never got such concerns in the PHP community. So, maybe we should go the >>

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

Hi! > Interface is a good way to implement new functionality for classes, but > operator overloading is language feature itself, so from my point of view, > it will be better to put this functionality into the magic method. No contradiction here. Language features can use interfaces, see

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

Hi Sara, 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 twitter/@Beryllium9: How about a global "disable error

Re: [PHP-DEV] Push Litespeed SAPI 6.9 to PHP 7.0.1

On 2015-12-24 12:18, Lior Kaplan wrote: On Thu, Dec 24, 2015 at 1:09 PM, Tom Sommer wrote: On 2015-12-16 14:41, Tom Sommer wrote: Hi I realise 7.0.1 is already out in RC1, but there is a bug in the Litespeed 6.8 sapi which breaks php_flag and php_value. It's causing our

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

> On Jan 4, 2016, at 10:29 PM, Paul M. Jones wrote: > > If there's an accusation, then *due process* needs to be applied. If it rises > to the level of needing *due process* then the police should be involved. > There's no need, *none at all*, for a star chamber *or* a

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

> Am 05.01.2016 um 15:29 schrieb Alexander Lisachenko : > > 2016-01-05 2:04 GMT+03:00 Andrea Faulds : > >> 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

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

Hi! > How exactly would you feel about having all of this made explicit to all > the other PHP devs? Presumably you look up to some of these people - I presume you would feel bad. However your example is purely theoretical and hand-crafted to exactly fit your argument. It is easy to imagine

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

> On Jan 5, 2016, at 09:55, Ben Ramsey wrote: > > >> On Jan 4, 2016, at 10:29 PM, Paul M. Jones wrote: >> >> If there's an accusation, then *due process* needs to be applied. If it >> rises to the level of needing *due process* then the police should

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

2016-01-05 2:04 GMT+03:00 Andrea Faulds : > 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

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

> > +1. The proposed CoC is too vague for a multi-cultural environment like > ours. Reference to ethics, for example, is subjective by nature. But I'm OK > for a more precise text that everybody must explicitely approve before > getting any karma. > > But I am opposed to any form of law

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

On Jan 5, 2016 7:32 AM, "Peter Lind" wrote: > > > > > +1. The proposed CoC is too vague for a multi-cultural environment like > > ours. Reference to ethics, for example, is subjective by nature. But I'm OK > > for a more precise text that everybody must explicitely approve

[PHP-DEV] BAD Benchmark Results for PHP Master 2016-01-05

Results for project PHP master, build date 2016-01-05 06:30:04+02:00 commit: 928d2cb previous commit:65e456f revision date: 2016-01-04 18:14:08+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

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

On Mon, Jan 4, 2016 at 11:56 PM, Sara Golemon wrote: > 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? > > +1 Would be nice if someone could come up with a

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

Paul M. Jones wrote on 05/01/2016 16:03: It's a*political* action designed with a*political* intent Please stop assuming that everybody has a hidden agenda at odds with their public statements, and claiming that you somehow know that the negative possibilities of this policy are

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

Hi! > That is the problem: you cannot discuss how to protect the accused > without having the context of the abused. As you have yourself pointed > out with examples, it is a tradeoff. But that is exactly what I want - to have full(er) context! The secret procedure makes that harder. Of course,

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

On Tue, Jan 5, 2016 at 6:37 PM, Larry Garfield wrote: > On 1/5/16 11:08 AM, Pierre Joye wrote: > >> Anyway, I don't say that it cannot happen, I just say that, AFAIK, we never got such concerns in the PHP community. >>> Sorry - not true. I can name several

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

> On Jan 5, 2016, at 13:20, Anthony Ferrara wrote: > > Paul isn't trolling. He is simply passionate about it. While I do > believe he can be more constructive with how he interacts in this > specific thread, he definitely isn't trolling (trying to cause drama > for drama's

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

On 5 January 2016 at 19:53, Stanislav Malyshev wrote: > Hi! > > > Yes, I thought it up, hence it's theoretical. If you think that means it > > hasn't happened countless times along those lines, you need to learn how > > to google. > > I hope you realize how weak is an

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

On 5 January 2016 at 20:26, Stanislav Malyshev wrote: > Hi! > > > That is the problem: you cannot discuss how to protect the accused > > without having the context of the abused. As you have yourself pointed > > out with examples, it is a tradeoff. > > But that is exactly

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

On Mon, Jan 4, 2016 at 1:39 AM, Nikita Popov wrote: > I'd like to provide some context as to why the current implementation works > as it does. > Thanks for the context, Niki. It makes sense that, with GMP as the flagship target of operator overloading, stripping away the

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

Hi! > It's interesting to note how few people in this thread consider the > perspective of potential harassed or abused people - instead only > focusing on how to protect the accused. We do not discuss it much because it is a) covered in the RFC thus forming context of the discussion and b) most

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

Hi! > Yes, I thought it up, hence it's theoretical. If you think that means it > hasn't happened countless times along those lines, you need to learn how > to google. I hope you realize how weak is an argument along the lines of "I am right, if you don't see it, learn how to google". > Is there

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

On 5 January 2016 at 19:42, Stanislav Malyshev wrote: > Hi! > > > It's interesting to note how few people in this thread consider the > > perspective of potential harassed or abused people - instead only > > focusing on how to protect the accused. > > We do not discuss it

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

On Tue, Jan 5, 2016 at 9:37 AM, Andrea Faulds wrote: >> How about a global "disable error suppression" setting? That way a >> project lead could enforce it for their codebase (and guarantee that >> devs "aren't lazy"), but PHP doesn't lose its pragmatism? > > I don't think that

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

> > > Additionally, given that this CoC has far reaching consequences, I would > suggest opening up voting on it's implementation to a wider segment of the > community eg those currently subscribed to the PHP mailing lists or at > least those who have recently participated on one. > > ~C >

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

On Tue, Jan 5, 2016 at 10:27 AM, Kevin Smith wrote: > Much of the argument in favor of a code of conduct seems to be centered > around the desire to send a message to the wider developer world that we’re a > welcoming community that doesn’t look kindly on poor treatment of

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

On Tue, Jan 5, 2016 at 6:53 PM, Sara Golemon wrote: > On Tue, Jan 5, 2016 at 9:37 AM, Andrea Faulds wrote: > >> 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] [Draft] Adopt Code of Conduct

On 5 January 2016 at 16:15, Anthony Ferrara wrote: > All, > > 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

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

On Tue, Jan 5, 2016 at 10:09 AM, Ferenc Kovacs wrote: >> > I don't think that would work out too well. Remember that many projects >> > have >> > error handles which convert all errors to exceptions: if you disable @ >> > in >> > those projects, wouldn't their code break? >> >

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

Much of the argument in favor of a code of conduct seems to be centered around the desire to send a message to the wider developer world that we’re a welcoming community that doesn’t look kindly on poor treatment of others. If that’s the goal, rather than the goal being to punish or censor

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

On Tue, 5 Jan 2016, 18:20 Ferenc Kovacs wrote: > >> Additionally, given that this CoC has far reaching consequences, I would >> suggest opening up voting on it's implementation to a wider segment of the >> community eg those currently subscribed to the PHP mailing lists or at

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

Rowan, On Tue, Jan 5, 2016 at 2:16 PM, Rowan Collins wrote: > Paul M. Jones wrote on 05/01/2016 16:03: >> >> It's a*political* action designed with a*political* intent > > > Please stop assuming that everybody has a hidden agenda at odds with their > public statements,

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

Anthony Ferrara wrote on 05/01/2016 19:20: Paul isn't trolling. He is simply passionate about it. While I do believe he can be more constructive with how he interacts in this specific thread, he definitely isn't trolling (trying to cause drama for drama's sake). We should be careful about that

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

Hi, Le 05/01/2016 10:32, Zeev Suraski a écrit : One thing I really like about the covenant Anthony is proposing (besides it being the same as the one a bunch of other projects are using) is that it actually is pretty short, considering what it is. The English version fits on one screen on my

[PHP-DEV] VCS Account Request: bof

Help with mirror (infrastructure!) maintenance. Hannes Magnusson indicated I\d need a GIT account for that, Daniel Brown thinks I\ll need web karma. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

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

On Mon, Jan 4, 2016 at 2:56 PM, Sara Golemon wrote: > https://wiki.php.net/rfc/token-get-always-tokens > A suggestion from a co-worker who's worried about seeing patterns like: case ($t['token']) { case T_PAAMAYIM_NEKUDOTAYIM: // do something break; case ord(';'):

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

> On Jan 5, 2016, at 12:22 PM, Sara Golemon wrote: > > On Tue, Jan 5, 2016 at 10:09 AM, Ferenc Kovacs wrote: I don't think that would work out too well. Remember that many projects have error handles which convert all errors to exceptions: if

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

> -Original Message- > From: Anthony Ferrara [mailto:ircmax...@gmail.com] > Sent: Tuesday, January 05, 2016 6:16 PM > To: internals@lists.php.net > Subject: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct > > As to the comments in this thread, I won't reply to every one, but here > are a

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

Hi Michael, Michael Cullum wrote: 4) What voting method would be used to choose the 5 people? Single Transferable Vote is a much better system for this kind of thing, especially considering the nature of ensuring a balance of opinion on the committee. The one issue with this being it's not

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

Hi Sara, Sara Golemon wrote: 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? This is more of a side-note, but maybe it's worth bringing up. Since token_get_all gives an array

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

Hi Chris, Chris Riley wrote: On Tue, 5 Jan 2016, 18:20 Ferenc Kovacs wrote: Additionally, given that this CoC has far reaching consequences, I would suggest opening up voting on it's implementation to a wider segment of the community eg those currently subscribed to the

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

Hi! > In response to significant feedback here and elsewhere, I have > expanded the text of the RFC significantly. It now includes the text > of the Contributor Covenant 1.3.0 as well as including verbage about > updating it requiring an RFC. Thanks for improving the RFC. It is already much

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

Hi Sara, Sara Golemon wrote: On Tue, Jan 5, 2016 at 12:52 PM, Andrea Faulds wrote: This is more of a side-note, but maybe it's worth bringing up. Since token_get_all gives an array with subarrays of a regular structure, might it be worthwhile returning an array of objects

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

Hi! > > own custom one, there are two reasons for this. First, it's a standard > > that's been adopted by a number of significant scale projects. Second, > > I completely disagree that Contributor Covenant's text is any kind of > "standard". I've seen a number of CoCs, and it's not the worst

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

HI Anthony, On Mon, Jan 4, 2016 at 4:37 PM, Bishop Bettini wrote: > On Mon, Jan 4, 2016 at 4:06 PM, 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

[PHP-DEV] Fwd: [PHP Wiki] Your DokuWiki password

Good Day! I'm a new member of the PHP Community Wiki and I'd like to have my account updated so that I might edit my profile and update my password. My username is specified below (and my sig has links to my blog and LinkedIn profile. I'm a multi-decade experienced PHP developer / architect /

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

Morning internalz, I'm going to keep it simple, because I'm sure everybody is getting a bit bored ... I object to the idea that we should try to limit "offence" ... it's not quantifiable, and it doesn't matter whatever, I'm offended by all sorts of things ... so what ... I can see

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

Hi! >> True, but as Larry said, either side is problematic. Too loose of a >> CoC with no enforcement and nothing really was changed from today >> considering we already have the post that Rasmus made 6-7 years ago. That implies we do *need* change from situation today. But so far I didn't see

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

> On Jan 5, 2016, at 15:51, Chase Peeler wrote: > > While overall I tend to agree with Paul on the concept of a CoC, I don't > think that precludes the ability to offer suggestions. It's to everyone's > advantage to make sure that if we do adopt a CoC, we adopt the best

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

Hi Rowan, I don’t presume to speak for Paul, but I don’t think the point is that any particular person involved in this discussion is presumed to have a political intent, rather that CoCs themselves (the Contributor Covenant in particular), and the people typically agitating for them, come

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

On Tue, Jan 5, 2016 at 10:00 PM, Andrea Faulds wrote: > Hi Chris, > > > Chris Riley wrote: > >> On Tue, 5 Jan 2016, 18:20 Ferenc Kovacs wrote: >> >> >>> Additionally, given that this CoC has far reaching consequences, I would suggest opening up voting on it's

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

Hi! >> True, but as Larry said, either side is problematic. Too loose of a >> CoC with no enforcement and nothing really was changed from today >> considering we already have the post that Rasmus made 6-7 years ago. That implies we do *need* change from situation today. But so far I didn't see

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

On Mon, Jan 4, 2016 at 10:47 PM, 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

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

> On Jan 5, 2016, at 16:21, Nate Abele wrote: > > Hi Rowan, > > I don’t presume to speak for Paul, but I don’t think the point is that any > particular person involved in this discussion is presumed to have a political > intent, rather that CoCs themselves (the

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

On Tue, Jan 5, 2016 at 11:13 PM, Stanislav Malyshev wrote: > Hi! > > >> True, but as Larry said, either side is problematic. Too loose of a > >> CoC with no enforcement and nothing really was changed from today > >> considering we already have the post that Rasmus made 6-7

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

On Tue, Jan 5, 2016 at 6:16 AM, Nikita Popov wrote: > Would be nice if someone could come up with a more explicit name for the > flag. TOKEN_FULL is not obvious, at least to me. TOKEN_ALWAYS_ARRAY? > Yeah, I'm not a huge fan of the name either, but I couldn't come up with

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

Ferenc Kovacs wrote on 05/01/2016 18:09: sure and most projects check the error_reporting() level against the $errno like in the manual: if (!(error_reporting() & $errno)) { // This error code is not included in error_reporting return; } @ changes the

[PHP-DEV] Re: Proposed change in json_encode+JSON_UNESCAPED_UNICODE behavior

Hi Eddie, Eddie Kohler wrote: The U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR characters are allowed unescaped in JSON strings, but *not* allowed unescaped in Javascript. This is widely considered a minor wart in the JSON specification.

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

Larry >> I'll chime in on this, since you and I had a quite pleasant and >> productive conversation last night. I believe we agreed that the >> original draft was over-focused on punitive measures and not enough on >> low-impact mediation. >> >> I imagine, because I love all you guys (and gals),

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

On 1/5/16 1:03 PM, Sara Golemon wrote: On Tue, Jan 5, 2016 at 10:27 AM, Kevin Smith wrote: Much of the argument in favor of a code of conduct seems to be centered around the desire to send a message to the wider developer world that we’re a welcoming community that

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

Zeev, On Tue, Jan 5, 2016 at 3:10 PM, Zeev Suraski wrote: >> -Original Message- >> From: Anthony Ferrara [mailto:ircmax...@gmail.com] >> Sent: Tuesday, January 05, 2016 6:16 PM >> To: internals@lists.php.net >> Subject: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct >>

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

Hi Dan, > On 04 Jan 2016, at 20:52, Dan Ackroyd wrote: > > Are the wrong functions are listed in this sentence: "Emit an > E_DEPRECATED error whenever mb_ereg_replace_callback or > mb_eregi_replace_callback is called with the e option." As the RFC is > meant to be about

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

> -Original Message- > From: Rasmus Lerdorf [mailto:ras...@lerdorf.com] > Sent: Tuesday, January 05, 2016 7:28 AM > To: Sara Golemon; Stanislav Malyshev > Cc: Junade Ali; PHP internals > Subject: Re: [PHP-DEV] Deprecation of the Error Control Operator (@ > symbol) > > On 01/04/2016 07:22

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

On Tue, 5 Jan 2016, Michael Heap wrote: > > On Tue, Jan 5, 2016 at 5:45 AM, 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

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

> -Original Message- > From: Derick Rethans [mailto:der...@php.net] > Sent: Tuesday, January 05, 2016 12:57 PM > To: Michael Heap > Cc: Sara Golemon; Junade Ali; PHP internals > Subject: Re: [PHP-DEV] Deprecation of the Error Control Operator (@ > symbol) > > On Tue, 5 Jan 2016, Michael

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

I don't think this is a good idea. the proposed code of conduct (contributor covenant) is extremly open to interpretation, as it is very subjective where harassment starts, what personal attacks are, if something is trolling, and i don't even want to see a discussion if something someone said is

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

On Tue, Jan 5, 2016 at 12:21 PM, Anthony Ferrara wrote: >>> It's been mentioned that we may want to adopt a CoC, but it shouldn't >>> "have teeth". I disagree here, as without an enforcement mechanism it >>> basically is no different from where we are at today. >> >> I think

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

On Tue, 5 Jan 2016, Sara Golemon wrote: > On Tue, Jan 5, 2016 at 3:57 AM, Zeev Suraski wrote: > > >> From: Derick Rethans [mailto:der...@php.net] > >> That's going to mean an INI setting.. that hosters could abuse. > >> Having an INI setting like this as part of core is IMO not a

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

While overall I tend to agree with Paul on the concept of a CoC, I don't think that precludes the ability to offer suggestions. It's to everyone's advantage to make sure that if we do adopt a CoC, we adopt the best one possible. Obviously one of the biggest fears is unjust treatment of the

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

On Tue, Jan 5, 2016 at 12:52 PM, Andrea Faulds wrote: > This is more of a side-note, but maybe it's worth bringing up. Since > token_get_all gives an array with subarrays of a regular structure, might it > be worthwhile returning an array of objects instead? It would probably >

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

Chase, On Tue, Jan 5, 2016 at 4:51 PM, Chase Peeler wrote: > While overall I tend to agree with Paul on the concept of a CoC, I don't > think that precludes the ability to offer suggestions. It's to everyone's > advantage to make sure that if we do adopt a CoC, we adopt

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

> On Jan 5, 2016, at 18:19, Pierre Joye wrote: > > On Jan 6, 2016 1:03 AM, "Ferenc Kovacs" wrote: > >>> Who would like to be connected with the Drupal people in this space, if > I >>> can get their time? I figure Anthony and Stas are good to include

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

On Jan 6, 2016 7:53 AM, "Paul M. Jones" wrote: > > > > On Jan 5, 2016, at 18:19, Pierre Joye wrote: > > > > On Jan 6, 2016 1:03 AM, "Ferenc Kovacs" wrote: > > > >>> Who would like to be connected with the Drupal people in this space,

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

Hi, On 6 January 2016 at 09:20, Paul M. Jones wrote: > > > On Jan 5, 2016, at 17:09, Terry Cullen wrote: > > > > Hi, > > > > > > > > On 5 January 2016 at 07:06, Anthony Ferrara wrote: > > > >> Hey all, > >> > >> I have created a

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

On Jan 6, 2016 1:03 AM, "Ferenc Kovacs" wrote: > > Who would like to be connected with the Drupal people in this space, if I > > can get their time? I figure Anthony and Stas are good to include there > > (proposer and someone with well-reasoned concerned). One or two more

Re: [PHP-DEV] token_get_all(): additional location information, and raw tokens

On Tue, Jan 5, 2016 at 3:57 PM, Fred Emmott wrote: > - T_ELSEIF to T_ELSE T_WHITESPACE T_IF > HHVM only does that when the text of T_ELSEIF is "else\w+if" which happens because of a fugly lexer hack which yeah... let's not talk about that. -Sara -- PHP Internals -

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

On Tue, Jan 5, 2016 at 11:40 AM, Rowan Collins wrote: >> @ changes the error_reporting() level for that particular call, so those >> custom error handler won't throw exceptions for the suppressed errors but >> when you remove/nop @ their code would throwing stuff left and

Re: [PHP-DEV] Re: Proposed change in json_encode+JSON_UNESCAPED_UNICODE behavior

Yes, without the JSON_UNESCAPED_UNICODE flag, all characters with Unicode values >= 0x80 are escaped. That's the default behavior. On Tue, Jan 5, 2016 at 2:45 PM, Andrea Faulds wrote: > Hi Eddie, > > Eddie Kohler wrote: >> >> The U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR

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

On Tue, Jan 5, 2016 at 12:24 PM, Aaron Piotrowski wrote: > Before anything can be done with the @ operator, changes will need to > be made to remove warnings for conditions that the code has no way of > checking prior to calling these functions. > I'd include pragmatism in that

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

Hi, On 5 January 2016 at 07:06, 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

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

> On Jan 4, 2016, at 22:29, Paul M. Jones wrote: > > >> On Jan 4, 2016, at 21:48, Michael Cullum wrote: >> >> I do apologise for saying offender, it was the wrong word to use there For the record: accepted. The COC is a speech-policing code, so

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

Hi! > Exhibit A: > https://github.com/CoralineAda/contributor_covenant/commit/0e927bc01614d6b0de021a314dbe95e7dfcc7bb9#diff-eacf331f0ffc35d4b482f1d15a887d3bL17 > > Exhibit B: https://archive.is/dgilk (the threatening language at the > end is particularly chilling) > I think this kind of

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

On 1/5/16 4:30 PM, Paul M. Jones wrote: On Jan 5, 2016, at 16:21, Nate Abele wrote: Hi Rowan, I don’t presume to speak for Paul, but I don’t think the point is that any particular person involved in this discussion is presumed to have a political intent, rather that

  1   2   >