Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80527
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <CA+9eiLuOcd-u_kzu+MZM71Ns_-9vsSbifFF5x9Q1b4k0NV12Wg@mail.gmail.com> <F41D165E-A2FB-4423-BF8F-6F6B5F4E201E@ajf.me> <68229C26-4EEC-49DC-BA05-D5AC9728D1E8@ajf.me> <CA+9eiLvh9RFVmYD1_y0AU0NVkkxYTfjv_C6H4tN8RH-w7X7M1g@mail.gmail.com> <EBBCF759-F622-4903-9821-DE3C63CD142A@ajf.me> <CA+9eiLv6MQjvqe2XXQjpUF1PjaNgPMYOoUmVDR3qZLkcjTd+SA@mail.gmail.com> <93376D88-A704-4F89-AB90-82EEDAE82081@ajf.me> <CA+9eiLtU6NEeXsN3c05qN_=8Bs5_arf6eVs-rrwzHKK1wZ8o7Q@mail.gmail.com> <CA+9eiLt6VyfQ+3WfYcVmYwnCcVgP4wwnA8rsbpDEN1ccf=g2Hg@mail.gmail.com> <B4C261EA-309F-463C-B7D8-0511D635DDA4@ajf.me> <CA+9eiLvKXzcvxuR37mBVYWmtfgeJY600363qc3Hn1THMojeCTg@mail.gmail.com> <CAEZPtU6vUsy6CjHCnLJu9nr1EV1i97kbkZD6SSZ-652Vf9iXLg@mail.gmail.com> <CA+9eiLtYGXLY2xN411oczkWVuKDnhM9fq6+c89A27STp4AQfSQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CA+9eiLtYGXLY2xN411oczkWVuKDnhM9fq6+c89A27STp4AQfSQ@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-CC3D14C8-CB11-4606-A6FB-985A427396F8
Content-Transfer-Encoding: 7bit
Message-ID: <1E8DD8EB-D82C-42F4-9A55-4387078EF74A@ajf.me>
Cc: Pierre Joye <pierre.php@gmail.com>,
 PHP Internals <internals@lists.php.net>
Date: Thu, 15 Jan 2015 11:01:10 +0000
To: Dmitry Stogov <dmitry@zend.com>
Subject: Re: [PHP-DEV] [RFC] Big Integer Support
From: ajf@ajf.me (Andrea Faulds)

--Apple-Mail-CC3D14C8-CB11-4606-A6FB-985A427396F8
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hey Dmitry,

> On 15 Jan 2015, at 07:56, Dmitry Stogov <dmitry@zend.com> wrote:
>=20
> ext/session and ext/json are required by most apps.
> Actually I stopped attempts to build it when I saw compilation errors in e=
xt/session.
>=20
> Thanks. Dmitry.

Oh dear, does ext/session not build? :/

So far I've only built the branch with --disable-all.

In the case of most extensions, the main source of compilation errors will b=
e changes to certain Zend Engine functions. In particular, is_numeric_string=
_ex needs to support bigints now and has an extra parameter. I don't think I=
 changed very many other functions.

Porting extensions should for the most part be relatively simple. Most exten=
sions are just sets of functions and use zpp. If they're using the 'l' speci=
fier (Z_PARAM_LONG) they'll continue to work. In most cases there is no need=
 to update an 'l' parameter to support bigints. The length of a string can't=
 exceed PHP's max integer size, for example. Of course, there are some funct=
ions where it would have a clear benefit to add bigint support.

The main problem with extensions is 'z'=20


>=20
>> On Thu, Jan 15, 2015 at 10:44 AM, Pierre Joye <pierre.php@gmail.com> wrot=
e:
>> On Thu, Jan 15, 2015 at 8:05 AM, Dmitry Stogov <dmitry@zend.com> wrote:
>> > Oh, it's still in draft state.
>> > Too may extensions are missing ext/seesion, ext/json, ext/pdo.
>> > Only very simple tests may be done now, and they can't predict impact o=
n
>> > real-life applications.
>>=20
>> We may as well try to help here.
>>=20
>> This patch is anything we want but simple. I really do not want to see
>> Andrea going down the pain we had with the 64bit patch. So let
>> organize ourselves to avoid that.
>>=20
>> Step 1:
>>=20
>> Which extensions do we consider as critical to actually get a clue
>> about the impact?
>>=20
>> I see session, standard ( ;) ), json on top of my head. Which other?
>>=20
>> Let help Andrea to port these exts and do the other once we know if
>> the RFC is accepted or not.
>>=20
>> Cheers,
>> Pierre
>=20

--Apple-Mail-CC3D14C8-CB11-4606-A6FB-985A427396F8--