Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count

Hi 2015-03-11 1:49 GMT-03:00 Stanislav Malyshev : > Hi! > > > related to the proposed RFC. *But* after some heuristics it was > > noticeable that most warnings had a common cause. I parsed the output > > It doesn't matter if it has common cause or not. If I have a system of > Wordpress-like size,

Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count

Hi! > related to the proposed RFC. *But* after some heuristics it was > noticeable that most warnings had a common cause. I parsed the output It doesn't matter if it has common cause or not. If I have a system of Wordpress-like size, I'm bound to get a lot of failures, that's what it is telling m

Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count

Hi, 2015-03-10 21:31 GMT-03:00 Stanislav Malyshev : > Hi! > > >- Even if you already read the RFC in the past, read it again now. > >- Don't claim **possible** massive BC breaks before read the > >measurements already done. No matter how seasoned you are with PHP, > real > >number

Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count

Hi! >- Even if you already read the RFC in the past, read it again now. >- Don't claim **possible** massive BC breaks before read the >measurements already done. No matter how seasoned you are with PHP, real >numbers matter most than assumptions. Your measurements are welcome too.

Re: [PHP-DEV] Consistent function names

On 10/03/15 20:44, Yasuo Ohgaki wrote: >> > YES there is room to create a more consistent procedural interface, but >> > my original question still applies "consistent with what rules?" > > It's possible choice. > I agree that names without "_" looks more consistent. > Personally, I don't care muc

Re: [PHP-DEV] Request Feedback for Instance Variable Sugar RFC

Hi, okay indeed the dynamic properties are a problem I didn't think about on my suggestion. Without the wish to hijack this thread for another typesafety discussion, I must say again that PHP needs a less dynamic and more declaratively properties concept in my opinion. So I would suggest for now

Re: [PHP-DEV] Consistent function names

Hi Lester, On Tue, Mar 10, 2015 at 6:27 PM, Lester Caine wrote: > On 10/03/15 01:59, Yasuo Ohgaki wrote: > > The same argument applies to fresh new OO APIs. It's just a matter of > > targeted PHP version to be supported. There are many things to be > > considered to decide targeted PHP version o

Re: [PHP-DEV] [Discussion] Deprecate function sizeof()

Hi Pierre, On Tue, Mar 10, 2015 at 3:54 PM, Pierre Joye wrote: > I do not think it has anything to do with OO or procedural but the actual > gains. > > I see none here. > Why not? PHP is distributed with set of APIs. i.e. Libraries. Tight binding with libraries and language make library update d

Re: [PHP-DEV] Re: Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

On 3/10/15 1:29 PM, Marcio Almada wrote: I think we should do some effort to discuss and discard as much options as possible so we can have max 2 options or maybe eliminate the secondary voting at all (which is the perfect scenario IMMO), but this requires a good absolute number of opinions. I

Re: [PHP-DEV] [VOTE] [RFC] continue output buffering

Hi Mike, On Mon, Mar 9, 2015 at 7:45 AM, Michael Wallner wrote: > Hi, I’d like to start vote on RFC:continue_ob — any objections? > > https://wiki.php.net/rfc/continue_ob > > > I think it would be good to put an example of why this is immensely useful in t

[PHP-DEV] Re: Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

Hi, 2015-03-10 11:39 GMT-03:00 Patrick ALLAERT : > Hello, > > Le ven. 6 mars 2015 à 00:44, Marcio Almada a > écrit : >> >> You are right about this. I'll setup a yes/no vote + a vote to decide >> between E_WARNING (for consistency), E_DEPRECATED or E_STRICT. For me this >> is just a detail but m

Re: [PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

Hi, 2015-03-10 12:45 GMT-03:00 Dan Ackroyd : > On 10 March 2015 at 15:02, Anthony Ferrara wrote: > > > > Can we please come down to a single RFC, with a single vote yes/no? > > It's easier to understand, easier to manage and has less possibility > > of gaming. > > > While I generally agree, in t

Re: [PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

2015-03-10 13:52 GMT-03:00 Anthony Ferrara : > Dan, > > On Tue, Mar 10, 2015 at 11:45 AM, Dan Ackroyd > wrote: > > On 10 March 2015 at 15:02, Anthony Ferrara wrote: > >> > >> Can we please come down to a single RFC, with a single vote yes/no? > >> It's easier to understand, easier to manage and

Re: [PHP-DEV] Introduce DerOetzi

Hello Anthony, as I already told to Sebastian Bergmann, who although asked for my thesis, I'm not allowed to share in public, because of some internals of my former company inside. But I am open for discussion about the things I have done for the thesis and especially based on it afterwards on a p

Re: [PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

Patrick, My viewpoint is that options in an RFC are dangerous. I would much rather have a single RFC, with a single vote (yes/no). I think we should be discouraging the options as much as possible. The reason is simple: an RFC should be an encapsulated idea, not a menu of options. The author shou

Re: [PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

Dan, On Tue, Mar 10, 2015 at 11:45 AM, Dan Ackroyd wrote: > On 10 March 2015 at 15:02, Anthony Ferrara wrote: >> >> Can we please come down to a single RFC, with a single vote yes/no? >> It's easier to understand, easier to manage and has less possibility >> of gaming. > > > While I generally ag

Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count

Hello, Le lun. 2 mars 2015 à 00:03, Marcio Almada a écrit : Hi, internals > > I'm moving the "Strict Argument Count" RFC into discussion phase: > > RFC: https://wiki.php.net/rfc/strict_argcount > PR: https://github.com/php/php-src/pull/1108 > > Many different opinions were collected during resea

Re: [PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

2015-03-10 16:02 GMT+01:00 Anthony Ferrara : > Patrick, > > My viewpoint is that options in an RFC are dangerous. I would much > rather have a single RFC, with a single vote (yes/no). I think we > should be discouraging the options as much as possible. > > The reason is simple: an RFC should be an

[PHP-DEV] Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count")

Hello, Le ven. 6 mars 2015 à 00:44, Marcio Almada a écrit : > > You are right about this. I'll setup a yes/no vote + a vote to decide > between E_WARNING (for consistency), E_DEPRECATED or E_STRICT. For me this > is just a detail but maybe it's very important to others, so better to let > each vo

[PHP-DEV] Introduce DerOetzi

Hi, sorry I did the wrong order, starting to discuss already without introducing me first: My name is Johannes Ott. I am 31 years old. I'm developing with PHP since 2004, I have written my thesis about "Testdriven development of a PHP- Framework with namespaces and 'typesafety' as implemented i

[PHP-DEV] Hello PHP-World

Hello, my name is Mike Pretzlaw, I am a (senior) developer, (junior) project manager and work with PHP for a decade now. About time to contribute to the PHP-Core and give something back to it. Unfortunately the registration (https://wiki.php.net/rfc/engine_exceptions_for_php7?do=register) doe

Re: [PHP-DEV] Consistent function names

On 10/03/15 01:59, Yasuo Ohgaki wrote: > The same argument applies to fresh new OO APIs. It's just a matter of > targeted PHP version to be supported. There are many things to be > considered to decide targeted PHP version other than this RFC. We have many > new features/behaviors in newer PHP vers

[PHP-DEV] SAPI apache2handler + pipelined HTTP request core dumps

Dear internals, can somebody knowledgeable about the apache2handler code, please have a look at the following bug report? https://bugs.php.net/bug.php?id=68486 I just added a comment with a hotfix that appears to work at first glance, but I'm completely unsure whether that will result in memor