Re: [PHP-DEV] PHP 5.3.29 is available, PHP 5.3 reaching end of life

We've rebuilt 5.3.29 using OpenSSL0.9.8zb and retested and released it. Thanks for the suggestion -M On Fri, Aug 15, 2014 at 1:35 AM, Jan Ehrhardt wrote: > Matt Ficken in php.internals (Fri, 15 Aug 2014 00:59:19 -0700): > >I have tested 5.3.29 on Windows thoroughly as its the last 5.3 release.

Re: [PHP-DEV] Let's make a 5.7 release

On Aug 16, 2014 1:57 AM, "Jonathan Wage" wrote: > > I agree with Derick, Zeev and Sebastian. > > It seems more economical at this point for everyone to join together and > focus our efforts on PHP 7. Short term? Maybe, if we forget that the period will be more 6-7 months. Long term? An economical

Re: [PHP-DEV] Let's make a 5.7 release

On Aug 16, 2014 4:11 AM, "Jan Ehrhardt" wrote: > > Christoph Becker in php.internals (Sat, 16 Aug 2014 01:33:28 +0200): > >Wim Godden wrote: > > > >> On 16/08/2014 0:43, Pierre Joye wrote: > >>> Here we have two issues, whether or not we need a 5.x to prepare 7 and if > >>> one year Dev time is en

Re: [PHP-DEV] Let's make a 5.7 release

Christoph Becker in php.internals (Sat, 16 Aug 2014 01:33:28 +0200): >Wim Godden wrote: > >> On 16/08/2014 0:43, Pierre Joye wrote: >>> Here we have two issues, whether or not we need a 5.x to prepare 7 and if >>> one year Dev time is enough. >> >> IMHO, that'll depend on which feature will be add

Re: [PHP-DEV] Let's make a 5.7 release

I agree with Derick, Zeev and Sebastian. It seems more economical at this point for everyone to join together and focus our efforts on PHP 7. I also think we should be bold and target the PHP 7 release for one year from now. If everyone gets on board and works towards the same goal it is possible

Re: [PHP-DEV] Let's make a 5.7 release

Hi all, On Fri, Aug 15, 2014 at 9:48 AM, Andrea Faulds wrote: > I’ve kept putting this off, but given the current “move phpng to master” > vote, I really can’t delay this any longer. > > It looks like PHP 7 is going to happen and phpng will be the base of that. > While we could move straight to

Re: [PHP-DEV] Let's make a 5.7 release

Wim Godden wrote: > On 16/08/2014 0:43, Pierre Joye wrote: >> Here we have two issues, whether or not we need a 5.x to prepare 7 and if >> one year Dev time is enough. > > IMHO, that'll depend on which feature will be added/changed/refactored > for 7. I might have missed that discussion, but so f

Re: [PHP-DEV] Let's make a 5.7 release

On 16/08/2014 0:43, Pierre Joye wrote: Here we have two issues, whether or not we need a 5.x to prepare 7 and if one year Dev time is enough. IMHO, that'll depend on which feature will be added/changed/refactored for 7. I might have missed that discussion, but so far I haven't seen a wishlist

Re: [PHP-DEV] Let's make a 5.7 release

On Sat, Aug 16, 2014 at 12:49 AM, David Soria Parra wrote: > On 2014-08-15, Pierre Joye wrote: >> --001a1133979e094b370500b2c0a9 >> Content-Type: text/plain; charset=UTF-8 >> >> On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote: >> (didn't >>> we learn anything from PHP 6?). >> >> I did. And w

Re: [PHP-DEV] Let's make a 5.7 release

On 2014-08-15, Pierre Joye wrote: > --001a1133979e094b370500b2c0a9 > Content-Type: text/plain; charset=UTF-8 > > On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote: > (didn't >> we learn anything from PHP 6?). > > I did. And with opcache. Both with hypothetical deadlines based on > arbitrary ran

Re: [PHP-DEV] Let's make a 5.7 release

On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote: (didn't > we learn anything from PHP 6?). I did. And with opcache. Both with hypothetical deadlines based on arbitrary random facts about the status or stability. Here we have two issues, whether or not we need a 5.x to prepare 7 and if one ye

Re: [PHP-DEV] Let's make a 5.7 release

On 2014-08-15, Ferenc Kovacs wrote: > --001a11c1258a38c82a0500a8b070 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > we don't have a single instance where we were able to deliver a minor > release under a year, and I'm fairly sure that 7.0 will see more pr

Re: [PHP-DEV] Improved logarithm of base 2|10 of standard math function

On 15 Aug 2014, at 19:57, Marc Bennewitz wrote: > Sara, > > shouldn't it be merged into the branches PHP-5.4, PHP-5.5 as well as > PHP-5.6 and shouldn't there an info in the NEWS file? It's currently > only merged to master. > > Marc There might be an argument against adding to 5.4 and 5.5 in

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

Nikita Popov wrote: > Yes, anything containing simple variables (like $i) will often deviate from > the usual evaluation order due to the CV optimization. I don't touch that. > What I've changed now is that ${a()}[b()] = c() will continue to call a, b, > c, rather than calling c, b, a (which was w

Re: [PHP-DEV] Re: glob() bug 47358

Hi, On Fri, Aug 15, 2014 at 7:59 PM, Stas Malyshev wrote: > Hi! > > > The source of the problem is that the open_basedir will always leek > > information about dirs that the user is not suppose to see (out of the > > open_basedir restriction). The reason is that false value can indicate > > that

Re: [PHP-DEV] Re: glob() bug 47358

Hi! > The source of the problem is that the open_basedir will always leek > information about dirs that the user is not suppose to see (out of the > open_basedir restriction). The reason is that false value can indicate > that (more info in the PR or https://bugs.php.net/bug.php?id=65489 ). > Howe

Re: [PHP-DEV] Improved logarithm of base 2|10 of standard math function

Sara, shouldn't it be merged into the branches PHP-5.4, PHP-5.5 as well as PHP-5.6 and shouldn't there an info in the NEWS file? It's currently only merged to master. Marc On 14.08.2014 17:29, Sara Golemon wrote: > On Thu, Aug 14, 2014 at 2:44 AM, Marc Bennewitz wrote: >> forgotten the link: >>

Re: [PHP-DEV] Re: glob() bug 47358

Hi, On Fri, Aug 15, 2014 at 2:19 AM, Stas Malyshev wrote: > Hi! > > > Sorry, I missed that one. I suspect it was the time where I > > misconfigured git and branches did not get merged. Feel free to merge > > it back/backport as I won't be able to do it before Monday. > > OK, I have backported it

Re: [PHP-DEV] Status of PHP 5.4

Hi! > the release process rfc (https://wiki.php.net/rfc/releaseprocess) governs > the releases since 5.4: 2+1 year of support after the initial X.Y.0 release. > as pointed out, 5.4 is already past the 2 years of bugfix support, so we > should announce it that it is on security fixes only. 5.4.32

[PHP-DEV] Unexpected dead loop

Hi, It looks like you can't call zend_eval_stringl with unserialize() If you do so it causes a segfault in zend_set_compiled_filename() Is it the right way to eval() something in a module? -- Best Regards, Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/ Finger Print: 9F67 391B B770 8FF6 9

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

On Fri, Aug 15, 2014 at 6:58 PM, Christoph Becker wrote: > Andrey Andreev: > >> I'd personally find it horrible if $foo[$i] = $bar[$i++]; is executed >> right-to-left, but given that your examples are a bit weird, I'm not sure >> if mine is affected. Is it? > > Isn't that evaluated from right to l

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

On Fri, Aug 15, 2014 at 5:58 PM, Christoph Becker wrote: > Andrey Andreev: > > > I'd personally find it horrible if $foo[$i] = $bar[$i++]; is executed > > right-to-left, but given that your examples are a bit weird, I'm not sure > > if mine is affected. Is it? > > Isn't that evaluated from right

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

Andrey Andreev: > I'd personally find it horrible if $foo[$i] = $bar[$i++]; is executed > right-to-left, but given that your examples are a bit weird, I'm not sure > if mine is affected. Is it? Isn't that evaluated from right to left already since PHP 5.1.0? See . --

[PHP-DEV] Re: [PHP-CVS] com php-src: Fixed version check: ext/mysqli/mysqli.c

Hey: sorry for top reply: for people who didn't know the context: we were talking about remove all #if PHP_MAJOR_VERSION >= ?? in exts which means, remove all old version supports in master.. what do you think? thanks On Fri, Aug 15, 2014 at 11:28 PM, Pierre Joye wrote: > add

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

On Wed, Aug 13, 2014 at 9:25 PM, Andrey Andreev wrote: > Hi, > > I'd personally find it horrible if $foo[$i] = $bar[$i++]; is executed > right-to-left, but given that your examples are a bit weird, I'm not sure > if mine is affected. Is it? > > Cheers, > Andrey. > I've decided that I'd rather avo

[PHP-DEV] Re: [PHP-CVS] com php-src: Fixed version check: ext/mysqli/mysqli.c

adding mysql@ to the list and move to internals, we should do that for other parts as well but extensions being actively maintained in pecl too (while they will most likely have a separate branche for 7+ anyway. On Fri, Aug 15, 2014 at 5:05 PM, Laruence wrote: > Hey: > > > On Fri, Aug 15, 2014 at

Re: [PHP-DEV] Let's make a 5.7 release

On 15 Aug 2014, at 15:51, Sebastian Bergmann wrote: > With regard to the scope of PHP 7, I think it would be great to limit > ourselves to "infrastructure" improvements (new executor from PHPNG, > AST-based compiler (plus userland extension that provides access to > the AST) from Nikita) and cle

Re: [PHP-DEV] Let's make a 5.7 release

Am 15.08.2014 um 02:48 schrieb Andrea Faulds: > As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add > deprecation warnings and such to help people prepare for 7. If the only changes that PHP 5.7 introduces (as compared to PHP 5.6) are deprecation warnings for features remov

Re: [PHP-DEV] Let's make a 5.7 release

> proposed in the multiple default arguments RFC. Sorry, multiple default blocks in a switch statement RFC. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Let's make a 5.7 release

On 15 Aug 2014, at 11:43, Ferenc Kovacs wrote: > On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote: > >> Basically, you're wanting to give up hope on PHP 7 in one year *at the >> moment it is started*... I think that's a pretty big mistake to do this >> already. The momentum is here now,

Re: [PHP-DEV] Let's make a 5.7 release

I'm not completely sure about others in this thread, but my personal view is that PHP 5.7 should be released at around the same time as PHP 7. It should contain E_DEPRECATED warnings where applicable, such as proposed in the multiple default arguments RFC. I've also heard talk of removing some feat

Re: [PHP-DEV] Let's make a 5.7 release

Derick Rethans wrote (on 15/08/2014): On Fri, 15 Aug 2014, Andrea Faulds wrote: I’ve kept putting this off, but given the current “move phpng to master” vote, I really can’t delay this any longer. It looks like PHP 7 is going to happen and phpng will be the base of that. While we could move st

Re: [PHP-DEV] Let's make a 5.7 release

On Aug 15, 2014 12:43 PM, "Ferenc Kovacs" wrote: > > On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote: > > > On Fri, 15 Aug 2014, Andrea Faulds wrote: > > > > > I’ve kept putting this off, but given the current “move phpng to > > > master” vote, I really can’t delay this any longer. > > > >

Re: [PHP-DEV] Let's make a 5.7 release

On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote: > On Fri, 15 Aug 2014, Andrea Faulds wrote: > > > I’ve kept putting this off, but given the current “move phpng to > > master” vote, I really can’t delay this any longer. > > > > It looks like PHP 7 is going to happen and phpng will be the b

Re: [PHP-DEV] Status of PHP 5.4

On Fri, Aug 15, 2014 at 10:53 AM, Pierre Joye wrote: > On Fri, Aug 15, 2014 at 10:10 AM, Jan Ehrhardt wrote: > > Stas Malyshev in php.internals (Thu, 14 Aug 2014 18:18:12 -0700): > >>> PHP 5.3 has reached the real end of life. Will the effect be that from > >>> now on PHP 5.4 will only get secur

Re: [PHP-DEV] Let's make a 5.7 release

Am 15.08.2014 um 11:25 schrieb Derick Rethans: > Basically, you're wanting to give up hope on PHP 7 in one year *at the > moment it is started*... I think that's a pretty big mistake to do this > already. The momentum is here now, let's use it to get PHP 7 > ready—instead of bogging ourselves do

[PHP-DEV] Re: [PHP-CVS] com php-src: Parameters with duplicate names are not allowed anymore in PHP7.: Zend/tests/bug54013.phpt Zend/tests/bug64515.phpt

On Fri, 15 Aug 2014, Dmitry Stogov wrote: > Log: > Parameters with duplicate names are not allowed anymore in PHP7. > -Bug #54013 (ReflectionParam for duplicate parameter contains garbage) > +Bug #54013 (ReflectionParam for duplicate parameter contains garbage) (PHP7) Just to nitpick - it woul

[PHP-DEV] Fixing the tags

Hi, I'm removing all the tags that Dmitry added by mistake. Please take care by not putting them back! This might require you to delete those tags locally as well. There is a handy script: for i in `git tag -l | grep PHP-`; do git tag -d $i; done cheers, Derick -- PHP Internals - PHP Runtime

RE: [PHP-DEV] Let's make a 5.7 release

> -Original Message- > From: Derick Rethans [mailto:der...@php.net] > Sent: Friday, August 15, 2014 12:25 PM > To: Andrea Faulds > Cc: PHP internals > Subject: Re: [PHP-DEV] Let's make a 5.7 release > > On Fri, 15 Aug 2014, Andrea Faulds wrote: > > > I’ve kept putting this off, but given th

Re: [PHP-DEV] Status of PHP 5.4

On Thu, Aug 14, 2014 at 11:34 PM, Jan Ehrhardt wrote: > PHP 5.3 has reached the real end of life. Will the effect be that from > now on PHP 5.4 will only get security fixes? > > Jan > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Let's make a 5.7 release

On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote: > On Fri, 15 Aug 2014, Andrea Faulds wrote: > >> I’ve kept putting this off, but given the current “move phpng to >> master” vote, I really can’t delay this any longer. >> >> It looks like PHP 7 is going to happen and phpng will be the base o

Re: [PHP-DEV] Let's make a 5.7 release

On Fri, 15 Aug 2014, Andrea Faulds wrote: > I’ve kept putting this off, but given the current “move phpng to > master” vote, I really can’t delay this any longer. > > It looks like PHP 7 is going to happen and phpng will be the base of > that. While we could move straight to PHP 7 after the rel

Re: [PHP-DEV] Status of PHP 5.4

On Fri, Aug 15, 2014 at 10:10 AM, Jan Ehrhardt wrote: > Stas Malyshev in php.internals (Thu, 14 Aug 2014 18:18:12 -0700): >>> PHP 5.3 has reached the real end of life. Will the effect be that from >>> now on PHP 5.4 will only get security fixes? >> >>There's no dependency between the two in the re

Re: [PHP-DEV] PHP 5.3.29 is available, PHP 5.3 reaching end of life

Matt Ficken in php.internals (Fri, 15 Aug 2014 00:59:19 -0700): >I have tested 5.3.29 on Windows thoroughly as its the last 5.3 release. > >I find no regressions. > >All the security and bug fixes didn't break anything from 5.3.28. > >Windows users at least, that want to stay with 5.3 can now upgra

Re: [PHP-DEV] Status of PHP 5.4

Stas Malyshev in php.internals (Thu, 14 Aug 2014 18:18:12 -0700): >> PHP 5.3 has reached the real end of life. Will the effect be that from >> now on PHP 5.4 will only get security fixes? > >There's no dependency between the two in the release RFC, but it would >probably make sense to move 5.4 into

Re: [PHP-DEV] [VOTE] Move the phpng branch to master

Hi, According to voting result, phpng was merged into master and the version number was bumped to 7.0.0-dev. Thanks to contributors, testers, bloggers, voters and everyone evolved :) Thanks. Dmitry. On Wed, Aug 6, 2014 at 4:36 PM, Zeev Suraski wrote: > I opened the voting on the phpng RFC: >

Re: [PHP-DEV] PHP 5.3.29 is available, PHP 5.3 reaching end of life

I have tested 5.3.29 on Windows thoroughly as its the last 5.3 release. I find no regressions. All the security and bug fixes didn't break anything from 5.3.28. Windows users at least, that want to stay with 5.3 can now upgrade to 5.3.29. See: http://qa.php.net/build.php?branch=PHP_5_3&revision

Re: [PHP-DEV] [RFC] Introduce Abstract Syntax Tree

On 14/08/14 13:30, Christoph Becker wrote: > Michael Wallner wrote: > >> On 14 08 2014, at 11:33, Alain Williams wrote: >>> Some code is just broken. >> >> Wat? No. This is totally different to two in/decrements on one line. This >> has to be executed in order. Ignore that. > > The current sp