[PHP-DEV] PHP 7 and json

2014-10-11 Thread Remi Collet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Bug 63520 is still not fixed. We have 2 alternative extensions - - jsonc the older one, probably not perfect, but used in a lot of downstream distributions - - jsond the recent one I think it is time to switch ext/json to another implementat

[PHP-DEV] PHP 7 and readline

2014-10-11 Thread Remi Collet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, For a lot of time, PHP can use readline (default) or libedit (prefered choice in all downstream) distribution. Readline is GPLv3 so is not compatible with PHP License I think is time to drop readline support (or, at least switch libedit as the

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Rowan Collins
On 11/10/2014 10:13, Lester Caine wrote: BIGINT is the SQL99-compliant 64-bit signed integer type It's a matter of context. In C, and therefore in related discussions (which includes the internals of PHP), integers are referred to as "short" (for 16-bit), "long" (for 32-bit) and "long long"

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Rowan Collins
On 11/10/2014 20:39, Lester Caine wrote: it will not fix the problem that was ORIGINALLY being discussed Your assuming that Andrea's RFC is a response to that particular discussion, rather than simply assuming that it's a valid discussion in its own right. It's perfectly possible to have tw

Re: [PHP-DEV] [RFC] Remove deprecated functionality in PHP 7

2014-10-11 Thread Rasmus Lerdorf
> On Oct 11, 2014, at 16:47, Kris Craig wrote: > >> On Oct 11, 2014 1:52 PM, "Nikita Popov" wrote: >> >> Hi internals! >> >> We currently have a number of deprecated features, which we likely want to >> remove in PHP 7. I've created a tracking RFC listing deprecated >> functionality (if I miss

Re: [PHP-DEV] [RFC] Remove deprecated functionality in PHP 7

2014-10-11 Thread Kris Craig
On Oct 11, 2014 1:52 PM, "Nikita Popov" wrote: > > Hi internals! > > We currently have a number of deprecated features, which we likely want to > remove in PHP 7. I've created a tracking RFC listing deprecated > functionality (if I missed something, please tell): > > https://wiki.php.net/rfc/r

Re: [PHP-DEV] Deprecation of func_get_args(), call_user_func_array() and related API

2014-10-11 Thread Andrea Faulds
On 11 Oct 2014, at 23:42, Rowan Collins wrote: > func_get_args() and func_num_args(), OTOH, existed solely to support > variadics, and anything taking advantage of them being functions rather than > a language structure would have to be quite exotic and arcane, so in > principle they could, e

Re: [PHP-DEV] Deprecation of func_get_args(), call_user_func_array() and related API

2014-10-11 Thread Rowan Collins
On 11/10/2014 04:10, Marco Pivetta wrote: That would actually be worse, as it wouldn't be possible to pass them to methods with a `callable` hint or similars such as `array_map`. That sounds like a good counter to your own argument that there is no use-case for these functions. Indeed, there

[PHP-DEV] [RFC] Remove deprecated functionality in PHP 7

2014-10-11 Thread Nikita Popov
Hi internals! We currently have a number of deprecated features, which we likely want to remove in PHP 7. I've created a tracking RFC listing deprecated functionality (if I missed something, please tell): https://wiki.php.net/rfc/remove_deprecated_functionality_in_php7 I expect many of these

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Lester Caine
On 11/10/14 19:22, Johannes Schlüter wrote: > But that's bikesheding, if we like we can call it also > yellow-blue-striped birds with red dots. Please discuss the contents not > the painting. Thanks. I AM discussing the content ... it will not fix the problem that was ORIGINALLY being discussed it

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Johannes Schlüter
On Sat, 2014-10-11 at 17:05 +0100, Lester Caine wrote: > BIGINT is a cleanly defined concept and something we have had to cope > with for some time since PHP does not support 64 bit integers cleanly. > Now that 64 bit builds support a clean 64 bit integer, the problem > arises that 32 bit builds wi

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Lester Caine
On 11/10/14 14:36, Pierre Joye wrote: > > On Oct 11, 2014 4:14 PM, "Lester Caine" > wrote: >> >> On 11/10/14 01:18, Andrea Faulds wrote: >> >>> >> What you want is 64-bit data handling. This is arbitrary-bit > data handling. It’s not a “wrong approach”. >> >> > >> >> >

Re: [PHP-DEV] Deprecation of func_get_args(), call_user_func_array() and related API

2014-10-11 Thread Pierre Joye
On Oct 11, 2014 3:34 AM, "Andrea Faulds" wrote: > > I would vote against any such proposal, and I hope others on the list would join me in doing so. I fully agree with you here.

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Pierre Joye
On Oct 11, 2014 4:14 PM, "Lester Caine" wrote: > > On 11/10/14 01:18, Andrea Faulds wrote: > >>> >> What you want is 64-bit data handling. This is arbitrary-bit data handling. It’s not a “wrong approach”. > >> > > >> > So BIGINT on 32 bit platforms will be different to BIGINT on 64 bit > >> > plat

Re: [PHP-DEV] [RFC] Big Integer Support

2014-10-11 Thread Lester Caine
On 11/10/14 01:18, Andrea Faulds wrote: >>> >> What you want is 64-bit data handling. This is arbitrary-bit data >>> >> handling. It’s not a “wrong approach”. >> > >> > So BIGINT on 32 bit platforms will be different to BIGINT on 64 bit >> > platforms? BIGINT is a fix length number not a variable

Re: [PHP-DEV] GMP memory allocator, various issues

2014-10-11 Thread Remi Collet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 11/10/2014 08:17, Remi Collet a écrit : > Le 11/10/2014 07:37, Remi Collet a écrit : > >> I will try to create a patch, for test, as we really need to fix >> this problem, especially it gmp going to go into core (bigint >> patch). > > See > htt