2015-05-18 14:10 GMT+02:00 Julien Pauli jpa...@php.net:
I just voted :-)
OK, so let's wait a little bit more before branching.
Let's at least wait until 5.4 is EOL before branching, or around that
time so we don't end up with: 5 active branches, 4 is more than enough
to work with, even though
On Mon, May 18, 2015 at 12:40 PM, Ferenc Kovacs tyr...@gmail.com wrote:
On Wed, May 13, 2015 at 4:50 PM, Ferenc Kovacs tyr...@gmail.com wrote:
On Wed, May 13, 2015 at 2:56 PM, Julien Pauli jpa...@php.net wrote:
Hello people.
Time is going, and summer is coming.
I think we must have
Dan Ackroyd wrote on 18/05/2015 18:38:
On 18 May 2015 at 15:39, Levi Morrison le...@php.net wrote:
I wouldn't group
TypeException in the same subtree as ParseException, for instance. One
happens at compile time and the other at run time, which means the
intent in what you catch is probably
On Sun, May 17, 2015 at 11:44 AM, Rowan Collins rowan.coll...@gmail.com wrote:
On 17 May 2015 16:02:40 BST, Levi Morrison le...@php.net wrote:
In this specific case we have broken all code out there.
Yes, in the very specific case of people who both caught all exceptions and
handled all
Dan Ackroyd wrote:
On 15 May 2015 at 23:14, Christoph Becker cmbecke...@gmx.de wrote:
I wonder why the GC is not triggered when the memory limit is exhausted,
To hopefully point you in the right direction, I believe the problem I
ran into, and the issue that stops it being a trivial thing
On 19/05/2015 00:07, Christoph Becker wrote:
As Rasmus suggested[1], in an issue linked through #60982, a simple
way to solve this would be to have both a soft and hard limit for
memory, and to allow the soft-limit to be a user callback, which could
call gc_collect_cycles, or not as the user
On Wed, May 13, 2015 at 4:50 PM, Ferenc Kovacs tyr...@gmail.com wrote:
On Wed, May 13, 2015 at 2:56 PM, Julien Pauli jpa...@php.net wrote:
Hello people.
Time is going, and summer is coming.
I think we must have branched 7.0 until end of May, and have our 2 RMs
elected.
Don't forget we
