Re: [PHP-DEV] [RFC] Generalize support of negative string offsets

On Wed, Feb 10, 2016 at 3:51 PM, Yasuo Ohgaki wrote: > Behavior regarding array. (a bit off topic, but error level should > match with new string '{}' errors.) > > php > error_reporting(-1); > php > $v=array(); > php > $v .= 'abc'; > > Notice: Array to string conversion in php shell code on line 1

Re: [PHP-DEV] [RFC] Generalize support of negative string offsets

Hi Francois, On Tue, Feb 9, 2016 at 12:09 AM, François Laupretre wrote: > Slightly off-topic but, as I was looking for the way to add support for > '$str[]=' assignments, I found something strange. > > Just for curiosity, does someone know a reason for this : > > $str = "abc"; > $str[1]="z"; > va

Re: [PHP-DEV] Implementing Generics, and none scalar default properties.

Den 2016-01-08 kl. 02:24, skrev Ben Scholzen 'DASPRiD': By the way, Rasmus updated the RFC quite a bit, you guys may want to take a look at it again. On 26.09.2015 12:23, Dominic Grostate wrote: An alternative that rfc might be to add a modifier to ctor, something like. required public funct

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Matt Prelude wrote on 09/02/2016 17:56: Rowan On 09/02/16 17:42, Rowan Collins wrote: Without going into point by point discussion, I think you're conflating several things here: 1) the right of the accused to know *what* they are accused of, which I agree is fundamental 2) the right of the

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Matt Prelude wrote on 09/02/2016 15:51: Without the right to face the accuser, the accusation, or a guarantee that all supporting AND contradictory evidence and testimony will be published, this is a 'secret court' proposal. Without going into point by point discussion, I think you're conflat

Re: [PHP-DEV] Re: Karma?

On Tue, Feb 9, 2016 at 4:52 PM, Matt Prelude wrote: > > > On 09/02/16 15:31, Christoph Becker wrote: > >> On 09.02.2016 at 15:50 Matt Prelude wrote: >> >> Where can I find out how voting karma works? >>> >>> I've searched but there appears to be little in the way of a clear guide. >>> >>> Keen to

[PHP-DEV] NEUTRAL Benchmark Results for PHP Master 2016-02-09

Results for project PHP master, build date 2016-02-09 11:18:11+02:00 commit: 4fcc3f7 previous commit:bd497f4 revision date: 2016-02-09 12:20:33+08: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] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Pierre Joye wrote on 09/02/2016 16:00: Also one problem we have now with the RFCs is feedback not being taken into account because it does not match the author ideas. In a previous discussion, I backed the idea of encouraging all RFCs to have multiple authorship. The idea that an RFC "belongs"

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi, So, rather than putting words in your mouth, I will ask the question directly: you say above that you do not agree that there is a need for a *new* enforcement process, but do you agree that there is a need for the *old* enforcement process to be recognised as such? Yes, have no issue wit

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Matt Prelude wrote on 09/02/2016 15:51: On 09/02/16 15:24, Rowan Collins wrote: That said, I am not convinced either a) that the current process has any guarantee of transparency - who exactly has the right to block people from the list, or revoke other karma? what transparent process are the

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

hi Zeev, On Tue, Feb 9, 2016 at 8:08 PM, Zeev Suraski wrote: >> Feel free to reply here with suggestions, comments, etc. > > I think this is a pretty good start and I can stand behind most of this text. > I do have a number of issues/suggestions with it though (apologies for not > doing this s

Re: [PHP-DEV] Re: Karma?

On 09/02/16 15:31, Christoph Becker wrote: On 09.02.2016 at 15:50 Matt Prelude wrote: Where can I find out how voting karma works? I've searched but there appears to be little in the way of a clear guide. Keen to get involved, but not sure where to start. Who can vote is described in

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi Rowan, On 09/02/16 15:24, Rowan Collins wrote: That said, I am not convinced either a) that the current process has any guarantee of transparency - who exactly has the right to block people from the list, or revoke other karma? what transparent process are they obliged to follow when doing

Re: [PHP-DEV] Proposal for a new array function

guilhermebla...@gmail.com wrote on 09/02/2016 15:41: My personal take on this: Let's add just more 1 function over a 9 function's array API, because I want to optimize 3 lines in my PHP code, and language lack of Generics while we still refuse to carefully think about a proper OO Collection

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Lester Caine wrote on 09/02/2016 15:31: In the context of policing CoC 'infringements' then a threat of some action should be enough to defuse the situation. Agreed. There is no need to 'settle out of court', but my point was more one of the feeling these days that "out of court settlement"

Re: [PHP-DEV] Proposal for a new array function

My personal take on this: Let's add just more 1 function over a 9 function's array API, because I want to optimize 3 lines in my PHP code, and language lack of Generics while we still refuse to carefully think about a proper OO Collection API. Regards, On Tue, Feb 9, 2016 at 6:19 AM, Matthew

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

Here is my reasons for no: 1- Non-intuitive behavior 2- Hard to read code, takes more time to understand underlying logic/flow 3- YAANPI => Yet Another Alternate Named Parameters Implementation (when I look at future scope) 4- Most common usage form (first example) still forces you to type almost

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi, On 09/02/16 15:23, David Zuelke wrote: I agree with Zeev here. It would be good to simplify this, and adding an explicit note about the inverse as well. Something like: "Debate issues and ideas, not the person holding them. Regardless of what side of a discussion you're on, realize that cr

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On 09/02/16 15:01, Rowan Collins wrote: > Lester Caine wrote on 09/02/2016 14:55: >> On 09/02/16 14:32, Rowan Collins wrote: >>> nobody would agree to an "out of court settlement" if there was no court >>> case to be avoided. >> That one is probably a bad example. How many cases are settled simply

[PHP-DEV] Re: Karma?

On 09.02.2016 at 15:50 Matt Prelude wrote: > Where can I find out how voting karma works? > > I've searched but there appears to be little in the way of a clear guide. > > Keen to get involved, but not sure where to start. Who can vote is described in

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On 09.02.2016, at 15:33, Derick Rethans wrote: > > On Tue, 9 Feb 2016, Zeev Suraski wrote: > >> 1. "Debate the technical issues, and never attack a person's opinion. >> People will disagree, so be it." >> >> I think this sentence is problematic. Not that I'm pro-attacks, but >> opinions - a

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Matt Prelude wrote on 09/02/2016 15:11: Taking your nuclear weapons analogy a little further, we are now (as a world) very concerned about making sure that the wrong people do not get access to nuclear weapons. Whilst we cannot go back and un-invent the nuclear weapon, we can avoid creating a pun

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Thanks for the work, Derick. Looks good! (aaand I just top-replied :p) > On 09.02.2016, at 13:33, Derick Rethans wrote: > > Hello! > > Things have quieted down around the Code of Conduct and Contributor > Guidelines process, but I have not been sitting still. In the last week, > the followi

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi, On 09/02/16 14:32, Rowan Collins wrote: Having procedures for violation and not using them could still have value. The most famous example of this is surely nuclear weapons, which are frequently cited as a deterrent, not intended for actual use. A less violent example in the UK would be t

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Lester Caine wrote on 09/02/2016 14:55: On 09/02/16 14:32, Rowan Collins wrote: nobody would agree to an "out of court settlement" if there was no court case to be avoided. That one is probably a bad example. How many cases are settled simply to avoid exorbitant legal costs? Being right has not

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On 09/02/16 14:32, Rowan Collins wrote: > nobody would agree to an "out of court settlement" if there was no court > case to be avoided. That one is probably a bad example. How many cases are settled simply to avoid exorbitant legal costs? Being right has nothing to do with the results, or 'no admi

[PHP-DEV] Karma?

Hi, Where can I find out how voting karma works? I've searched but there appears to be little in the way of a clear guide. Keen to get involved, but not sure where to start. - Matt. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On 09/02/16 14:33, Derick Rethans wrote: >> 5. I think the 'max 2 lines email signature' requirement is a bit >> > archaic. Who cares? Do we expect people to change their signature >> > especially for internals? Not important, but if we're nitpicking :) > Heh - it's always been in there ! :þ

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On Tue, 9 Feb 2016, Levi Morrison wrote: > > Voting is non-binding, and will end at Friday February 12th, at noon > > UTC. > > What does this mean in this context? We're voting but nothing will > actually change? Just want to see how close this text is to being done, so that we can move over to

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi, > I feel that the "Contributor Guidelines" are now in a reasonable shape > to do a quick poll to gauge acceptability. As this is not a formal RFC > vote, it's simply done through an online poll: note - the voting thing is now on the WIKI at: https://wiki.php.net/adopt-code-of-conduct/guid

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Matt Prelude wrote on 09/02/2016 13:56: If the Drupal CWG have not needed to impose punishments as a result of their CoC, and in the history of Internals you could count the bans on one hand, then I really don't see why we need to go to the lengths of establishing committees and punishment proc

RE: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On Tue, 9 Feb 2016, Zeev Suraski wrote: > 1. "Debate the technical issues, and never attack a person's opinion. > People will disagree, so be it." > > I think this sentence is problematic. Not that I'm pro-attacks, but > opinions - as ideas - should absolutely be up for scrutiny and debate.

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

> Voting is non-binding, and will end at Friday February 12th, at noon > UTC. What does this mean in this context? We're voting but nothing will actually change? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

On Tue, 9 Feb 2016, Joe Watkins wrote: > Morning Derick, > > I know you're asking about another document right now, but I still find > the language of the CoC jarring. > > This: "Coercing other members to vote for a particular option on an > RFC, or to change or withdraw an RFC". These

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hi, On 09/02/16 12:33, Derick Rethans wrote: [snip] - Texts should be void from ambiguity. I couldn't agree more. Ambiguity has a chilling effect on speech, and will damage the quality of discourse on internals. Having said that, I think that the CoC being proposed is too wordy, and still

RE: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

> Feel free to reply here with suggestions, comments, etc. I think this is a pretty good start and I can stand behind most of this text. I do have a number of issues/suggestions with it though (apologies for not doing this sooner - I was swamped in the last 3 weeks with travel & out of town vi

Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Morning Derick, I know you're asking about another document right now, but I still find the language of the CoC jarring. This: "Coercing other members to vote for a particular option on an RFC, or to change or withdraw an RFC". That's too vague: https://twitter.com/krakjoe/status/685

[PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress

Hello! Things have quieted down around the Code of Conduct and Contributor Guidelines process, but I have not been sitting still. In the last week, the following things happened: - I had a call with the Drupal Community Working Group - as suggested by Larry Garfield. Stanislav was on the cal

Re: [PHP-DEV] Proposal for a new array function

Thanks kindly for the rapid and very helpful feedback. I'm going over it today and will collate it and think over it further. Given that the feedback's been so constructive and positive, I'll be getting started on an RFC over the next day or so. Matt -- Kind regards, *Matthew Setter* *Freelanc

Re: [PHP-DEV] Proposal for a new array function

Yasuo Ohgaki wrote on 09/02/2016 02:52: bool is_array(mixed $var [, long $type_of_array]); where $type_of_array is bit flags such as PHP_ARRAY_REAL, PHP_ARRAY_HASH, PHP_ARRAY, PHP_ARRAY_RECLUSIVE, etc. I like this variant (although I don't like the term "real"). Unlike returning the type, it'

[PHP-DEV] Re: Proposal for a new array function

On 08/02/16 15:32, Matthew Setter wrote: > I want to propose a new PHP array method, called has_numeric_keys (or > something similar/better), that would have the following method signature: > > bool has_numeric_keys(array $array) > > The reason for it is to check if the array passed to it only ha

Re: [PHP-DEV] Proposal for a new array function

On 09/02/16 02:52, Yasuo Ohgaki wrote: > Hi, > > On Tue, Feb 9, 2016 at 1:03 AM, Kinn Julião wrote: >> And what's wrong with doing: >> https://gist.github.com/kinncj/566bbc019be5707b01f2 ? > > Perfectly ok to me while it would be slower. > > BTW, it's easy and quick to detect array is real arra