Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82722
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <6FD9B9A4-E831-4D4F-AD66-BD04D8C37991@ajf.me>
References: <6FD9B9A4-E831-4D4F-AD66-BD04D8C37991@ajf.me>
Date: Sun, 15 Feb 2015 20:39:46 +0800
Message-ID: <CABBJUpcpUiXTX4hv=Lj6JMWhxRriV8c+8kD50gUk7Cq-hhqM+A@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [VOTE] Big Integer Support
From: laruence@php.net (Xinchen Hui)

Hey:


On Sun, Feb 15, 2015 at 10:46 AM, Andrea Faulds <ajf@ajf.me> wrote:
> Hi everyone,
>
> I should=E2=80=99ve done this a long time ago, but I=E2=80=99m going to h=
old a vote on this RFC. The implementation isn=E2=80=99t finished, but the =
remaining work isn=E2=80=99t impossible to surmount (though help would cert=
ainly be appreciated). RFCs can be put to vote without implementations (or =
so says https://wiki.php.net/rfc/howto), so the fact the implementation is =
unfinished isn=E2=80=99t necessarily a blocker.
for such a big change, the implementation self is also important,
there was some RFC accepted with "not good" implementation, which
cause lots of troubles for us to maintaining .
>
> Putting it to a vote, finally, means I can stimulate further discussion (=
let=E2=80=99s face it, most discussion on a given RFC happens during voting=
), and importantly, see how much support the RFC has in order motivate myse=
lf to finish the implementation.
>
> I think this would be a useful feature for PHP. It brings PHP into line w=
ith other modern dynamic languages in having integers of arbitrary size. It=
 makes integer behaviour both more intuitive and more consistent across pla=
tforms. It (finally) adds a means for handling of 64-bit (and larger) integ=
ers in 32-bit environments. I think allowing integers to grow as needed and=
 not having to worry about platform-specific details is very =E2=80=9CPHP=
=E2=80=9D, as well.
>
from your RFC:
"
but obviously the implementations of anything dealing with integers
may need to be changed."

this sounds too much compare to the benefits it brings.. (User can use
bcmath or other similar thing to deal with big int).

and actually, I'd prefer this to be a extension instead of get it into core=
..

too much changes for little gains..

Thus, I voted -1 on this.

thanks
> So, anyway, here=E2=80=99s the RFC, including the voting widget:
>
> https://wiki.php.net/rfc/bigint
>
> Voting starts today (2015-02-15) and ends in 10 days (2015-02-25).
>
> If you have any queries, please ask.
>
> Thanks!
>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



--=20
Xinchen Hui
@Laruence
http://www.laruence.com/