[PHP-DEV] Spurious open_basedir warning

2015-05-19 Thread Christoph Becker
Hello Internals, there are several bug reports related to open_basedir and non-existant files/directories.[1] uramihsayibok's comment on bug #53041 sheds some light on the issue. A few weeks ago I had a closer look at it, and it seems that using expand_filepath_with_mode() instead of

Re: [PHP-DEV] [VOTE] Exceptions in the engine

2015-05-19 Thread Yasuo Ohgaki
Hi all, On Sun, May 17, 2015 at 8:44 AM, Levi Morrison le...@php.net wrote: On Sat, May 16, 2015 at 2:17 PM, Rowan Collins rowan.coll...@gmail.com wrote: On 16/05/2015 20:15, Levi Morrison wrote: The difference is that as time goes on and I've written code for PHP 7 I was hit by this

Re: [PHP-DEV] trigger GC before memory limit is exhausted

2015-05-19 Thread Dan Ackroyd
On 19/05/2015 00:07, Christoph Becker wrote: What happens if the soft limit is exhausted, but the GC can free only a little memory? That might trigger the GC shortly afterwards again and again. The usual way to stop this sort of flapping is to set the point at which the alarm gets reset to be

Re: [PHP-DEV] trigger GC before memory limit is exhausted

2015-05-19 Thread Dan Ackroyd
On 19 May 2015 at 14:28, Rowan Collins rowan.coll...@gmail.com wrote: Dan Ackroyd wrote on 19/05/2015 14:08: * When gc_collect_cycles is called (and potentially other functions), at the end of that function check whether the amount of memory being used is less than reset level for each

Re: [PHP-DEV] trigger GC before memory limit is exhausted

2015-05-19 Thread Rowan Collins
Dan Ackroyd wrote on 19/05/2015 14:08: * When gc_collect_cycles is called (and potentially other functions), at the end of that function check whether the amount of memory being used is less than reset level for each trigger. If so reduce the current memory limit to the lowest trigger level.

[PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Nikita Popov
Hi internals! For PHP 7 we soft-reserved a number of class names [1] like numeric, so that we have the ability to introduce them as typehints in a 7.x release. Soft here means that we only document these names as being reserved and don't throw an error when they're used. I'd like to add void to

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Mariano Iglesias
+1

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Peter Cowburn
On 19 May 2015 at 17:16, Levi Morrison le...@php.net wrote: I strongly disagree with this action. These types required an RFC; why should this be different? Also note that neither of the reserve typename RFC were unanimous. Furthermore, we are past the RFC stage. We are *supposed to already

[PHP-DEV] Throwable Interface RFC

2015-05-19 Thread Aaron Piotrowski
Hi all! I’ve registered on the wiki with username trowski and would like to request write access so I can create an RFC for the PR at https://github.com/php/php-src/pull/1284 Thanks! Aaron Piotrowski -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Julien Pauli
On Tue, May 19, 2015 at 5:28 PM, Nikita Popov nikita@gmail.com wrote: Hi internals! For PHP 7 we soft-reserved a number of class names [1] like numeric, so that we have the ability to introduce them as typehints in a 7.x release. Soft here means that we only document these names as being

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Levi Morrison
On Tue, May 19, 2015 at 10:16 AM, Levi Morrison le...@php.net wrote: I strongly disagree with this action. These types required an RFC; why should this be different? Also note that neither of the reserve typename RFC were unanimous. Furthermore, we are past the RFC stage. We are *supposed to

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Sara Golemon
On Tue, May 19, 2015 at 9:16 AM, Levi Morrison le...@php.net wrote: I strongly disagree with this action. These types required an RFC; why should this be different? Also note that neither of the reserve typename RFC were unanimous. Furthermore, we are past the RFC stage. We are *supposed to

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Levi Morrison
I strongly disagree with this action. These types required an RFC; why should this be different? Also note that neither of the reserve typename RFC were unanimous. Furthermore, we are past the RFC stage. We are *supposed to already have an alpha* by now and we are proposing new changes?. Please

Re: [PHP-DEV] Soft-reserve void class name

2015-05-19 Thread Rowan Collins
On 19 May 2015 17:21:58 BST, Levi Morrison le...@php.net wrote: On a related note it is unclear what BC breaks are exactly allowed in minor releases. Adding new reserved types is a BC break, but it was done in PHP 5.4 with `callable`. We should solidify what we do and do not allow in minor

[PHP-DEV] Re: Soft-reserve void class name

2015-05-19 Thread Benoit Schildknecht
Le Tue, 19 May 2015 17:28:34 +0200, Nikita Popov nikita@gmail.com a écrit: Hi internals! For PHP 7 we soft-reserved a number of class names [1] like numeric, so that we have the ability to introduce them as typehints in a 7.x release. Soft here means that we only document these names as