RE: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

Ferenc, all, The RFC has provisions for making the 3rd and 4th milestones move as needed: “It's worth noting that the 3rd and 4th milestones will be quality dependent. If we have evidence that suggests that PHP 7 isn't sufficiently mature to go into the RC stage in June, or GA in October - we

RE: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

> -Original Message- > From: morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] On > Behalf Of Levi Morrison > Sent: Friday, November 21, 2014 6:48 PM > To: Zeev Suraski > Cc: PHP internals > Subject: Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline > > The timeline for "Line up any remain

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, Nov 21, 2014 at 7:10 AM, Zeev Suraski wrote: > Kris, > > This existed in the RFC since the get go and I don't believe anybody > raised any concerns about it. There was plenty of time for discussion. > Either way approval of this RFC won't have any effect on the approval or > rejection of

[PHP-DEV] Alternative RFC for 7 roadmap and 5.7

hi, This RFC is not about compete aganst Zeev's RFC but to get all issues related to PHP 7 and a possible 5.7 release solved in one go. Many here think that the timeline proposed (one year, less now) is not realistic. It is not correct to simply ignore us and push yet again another RFC, using the

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Sat, Nov 22, 2014 at 2:18 AM, Zeev Suraski wrote: > >> On 21 בנוב׳ 2014, at 13:06, Ferenc Kovacs wrote: >> >> >> >>> On Fri, Nov 21, 2014 at 9:07 AM, Zeev Suraski wrote: >>> After some Twitter hints that I should get my act together and finally move >>> this to a vote, it’s finally happening:

Re: [PHP-DEV] PHP SAPI module help

On Fri, 2014-11-21 at 23:06 +0400, Tigran Bayburtsyan wrote: > > And based on that now my main problem is that in PHP C++ sources there > are a lot of static, global variables which is not useful for me, to > clean that all for every request So I'm wondering to build > something which will he

Re: [PHP-DEV] PHP SAPI module help

Thanks for your responses. I saw pconn-sapi it's very similar threaded example that I want to implement. I've crated non blocking Event loop in my C++ application ( it's high load binary API server ) , and now I'm trying to integrate PHP SAPI for writing some customisable scripts using PHP functio

[PHP-DEV] Re: fgetcsv incompatible with fputcsv

Am 21.11.2014 um 02:53 schrieb Tjerk Meesters: >> On 21 Nov 2014, at 02:14, Christoph Becker wrote: >> >> Apparently, there is a somewhat hidden bug, see >> for a simplified test script. The expected result is >> >> string(14) ""a""b","a\""b"" >> >> or maybe >> >> strin

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

> BTW, old constructor has problem with traits (is this mentioned already?) > > http://3v4l.org/KZKXo > > I suppose nobody is using this side effect in production code, but > there would be number of users who are confused by this behavior. If I remember the source code correctly, this should be c

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On 21 November 2014 07:36, Ferenc Kovacs wrote: > In this case the 3 month period will be too short imo. > We release RCs/betas every two weeks, so 3 months would be about 6 release. > 5.6.0 had 3 alpha, 4 beta and 4 rc before release. > 5.5.0 had 6 alpha, 4 beta and 3 rc before release. > 5.4.0 h

Re: [PHP-DEV] Re: [OFFTOPIC] conditional compilation, WAS [RFC] Remove PHP 4 Constructors

On Fri, Nov 21, 2014 at 5:55 PM, Alain Williams wrote: > On Wed, Nov 19, 2014 at 07:17:48PM +0100, Julien Pauli wrote: > >> [Off Topic] >> >> It's been a long time I've been thinking about having a compile-time >> preprocessor integrated into our parser/compiler stack. >> I would design it just to

[PHP-DEV] Re: [OFFTOPIC] conditional compilation, WAS [RFC] Remove PHP 4 Constructors

On Wed, Nov 19, 2014 at 07:17:48PM +0100, Julien Pauli wrote: > [Off Topic] > > It's been a long time I've been thinking about having a compile-time > preprocessor integrated into our parser/compiler stack. > I would design it just to support #migration tokens, and nothing more. > This would real

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, Nov 21, 2014 at 1:07 AM, Zeev Suraski wrote: > After some Twitter hints that I should get my act together and finally move > this to a vote, it’s finally happening: Given how long it has been since there was any activity on this topic, I wish that you had issued a pre-vote email to the li

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Nikita Popov wrote on 21/11/2014 16:22: I'm also pretty confident that we can provide robust tooling for automatically porting code to new constructors - including updating parent:: call references if need be. Don't see how that would be a particular issue here. Given the contents of your githu

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Johannes Schlüter wrote on 21/11/2014 16:13: Hi, On Fri, 2014-11-21 at 16:48 +0900, Yasuo Ohgaki wrote: How about use INI until PHP8? No. php.ini needs less settings not more. Especially not for language things. This makes a mess for creating portable code. ze1 compat mode was a fault as we

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

On Wed, Nov 19, 2014 at 12:11 AM, Levi Morrison wrote: > Dear Internals, > > I am proposing an RFC[1] to remove PHP 4 constructors in PHP 7. If > accepted, methods with the same name as their defining class will no > longer be recognized as constructors. As noted in the RFC, there are > already m

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Hi, On Fri, 2014-11-21 at 16:48 +0900, Yasuo Ohgaki wrote: > How about use INI until PHP8? No. php.ini needs less settings not more. Especially not for language things. This makes a mess for creating portable code. ze1 compat mode was a fault as were other ini settings we had. Let's not go the

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, Nov 21, 2014 at 4:18 PM, Zeev Suraski wrote: > > On 21 בנוב׳ 2014, at 13:06, Ferenc Kovacs wrote: > > > > On Fri, Nov 21, 2014 at 9:07 AM, Zeev Suraski wrote: > >> After some Twitter hints that I should get my act together and finally >> move >> this to a vote, it’s finally happening: >

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

> On 21 בנוב׳ 2014, at 13:06, Ferenc Kovacs wrote: > > > >> On Fri, Nov 21, 2014 at 9:07 AM, Zeev Suraski wrote: >> After some Twitter hints that I should get my act together and finally move >> this to a vote, it’s finally happening: >> >> >> >> https://wiki.php.net/rfc/php7timeline#vote

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

Kris, This existed in the RFC since the get go and I don't believe anybody raised any concerns about it. There was plenty of time for discussion. Either way approval of this RFC won't have any effect on the approval or rejection of other RFCs. Kris, All - I'm now on a 7th day straight of a p

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

On 21/11/14 14:15, Rowan Collins wrote: > Lester Caine wrote on 21/11/2014 13:27: >> No - There have been several threads on deprecating things that are >> currently 'hidden' by e_strict. The confusion is created by having two >> incompatible styles of coding, and unless one brings the 'non-e_stric

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Lester Caine wrote on 21/11/2014 13:27: No - There have been several threads on deprecating things that are currently 'hidden' by e_strict. The confusion is created by having two incompatible styles of coding, and unless one brings the 'non-e_strict' code in to line with current practices it crea

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

On 21/11/14 12:36, Jan Schneider wrote: > > Zitat von Lester Caine : > >> On 21/11/14 11:31, Rowan Collins wrote: I know I sound like a broken record, but this is EXACTLY the same problem as e_strict! It is all very well saying old code can still run if you hide the the warnings an

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Hi, I still don't get get what problem this RFC is actually going to solve? I don't see a problem. Yes, PHP4 constructors are are old and should no longer be used. But there is no problem still supporting them. Raise an E_DEPRECATED for those, and be done with it. +1 I can accept BC-breaks if

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Zitat von Lester Caine : On 21/11/14 11:31, Rowan Collins wrote: I know I sound like a broken record, but this is EXACTLY the same problem as e_strict! It is all very well saying old code can still run if you hide the the warnings and ERRORS, but you have to spend the time fixing each and ever

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

On 21/11/14 11:31, Rowan Collins wrote: >> I know I sound like a broken record, but this is EXACTLY the same >> problem as e_strict! It is all very well saying old code can still run >> if you hide the the warnings and ERRORS, but you have to spend the time >> fixing each and every warning simply t

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

Lester Caine wrote on 21/11/2014 09:49: I know I sound like a broken record, but this is EXACTLY the same problem as e_strict! It is all very well saying old code can still run if you hide the the warnings and ERRORS, but you have to spend the time fixing each and every warning simply to ensure t

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, Nov 21, 2014 at 9:07 AM, Zeev Suraski wrote: > After some Twitter hints that I should get my act together and finally move > this to a vote, it’s finally happening: > > > > https://wiki.php.net/rfc/php7timeline#vote > > > > Cast your vote! > > > > Zeev > Hi, could you update the timelin

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

Specifically, this is the sentence that just seems completely out of place: "Arguably, while we should definitely take the opportunity to implement compatibility-breaking changes in 7.0, we also shouldn't turn it into a compatibility-breaking festival, as the more we break, the more likely it is u

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, Nov 21, 2014 at 12:18 AM, Joe Watkins wrote: > On Fri, 2014-11-21 at 10:07 +0200, Zeev Suraski wrote: > > After some Twitter hints that I should get my act together and finally > move > > this to a vote, it’s finally happening: > > > > > > > > https://wiki.php.net/rfc/php7timeline#vote >

Re: [PHP-DEV] [VOTE][RFC] Safe Casting Functions

On 21/11/14 02:10, Yasuo Ohgaki wrote: > To be honest, I have mixed feeling for this FRC. > Stricter type check is good. However, it requires runtime cost. One of the area where it is being held up as good practice is filtering data which is then passed to a database. With best practice on handlin

Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors

On 20/11/14 21:29, Rowan Collins wrote: > The problem is that the constructor is part of the public API (for > inheritance purposes) so the required refactoring is not necessarily isolated > to one project, or even doable by one developer. The maintainer of the > library must first release a ver

Re: [PHP-DEV] [VOTE][RFC] Safe Casting Functions

> On 21 Nov 2014, at 03:02, Adam Harvey wrote: > >> The problem is that it’s the least bad of the available options. > > I disagree. To my mind, the best option right now (barring the status > quo, which realistically I'd prefer) would be the try_* functions > only. They line up with how ext/st

Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

On Fri, 2014-11-21 at 10:07 +0200, Zeev Suraski wrote: > After some Twitter hints that I should get my act together and finally move > this to a vote, it’s finally happening: > > > > https://wiki.php.net/rfc/php7timeline#vote > > > > Cast your vote! > > > > Zeev Morning Zeev, Pro

[PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline

After some Twitter hints that I should get my act together and finally move this to a vote, it’s finally happening: https://wiki.php.net/rfc/php7timeline#vote Cast your vote! Zeev