Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78181
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.214.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me>
References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me>
Date: Tue, 21 Oct 2014 12:35:17 +0400
Message-ID: <CA+9eiLuOcd-u_kzu+MZM71Ns_-9vsSbifFF5x9Q1b4k0NV12Wg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd6ba9a07050a0505eab6f8
Subject: Re: [PHP-DEV] [RFC] Big Integer Support
From: dmitry@zend.com (Dmitry Stogov)

--047d7bd6ba9a07050a0505eab6f8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Andrea,

Why don't you use the ability of operator overloading? (it's in the engine
since 5.6).

BIGINT don't have to be completely transparent. If user would like to work
with BIGINT, let them crate PHP objects explicitly and then use operator
overloading. e.g.

<?php
function print_powers_of_two($bits) {
    $bit =3D BIGINT(1);
    $last =3D BIGINT(2) ** $bits;
    while ($bit < $last) {
        $bit *=3D 2;
        echo "$bit\n";
    }
}
print_powers_of_two(256);
?>

Your solution would allows writing the same without BIGINT, but not for
free.
I expect, it'll make some slowdown for all PHP scripts, independently, if
they use BIGINT or not.
I'll try to take a deeper look into the patch later...

Could you provide some benchmark results, comparing your patch with master?

Thanks. Dmitry.

On Sat, Oct 11, 2014 at 1:33 AM, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening,
>
> Since I don=E2=80=99t want this to languish as a =E2=80=98Draft=E2=80=99 =
forever, despite the
> patch being incomplete, I am finally putting the Big Integer Support RFC
> =E2=80=9CUnder Discussion=E2=80=9D.
>
> The RFC can be found here: https://wiki.php.net/rfc/bigint
>
> The patch is, as I mentioned, incomplete. Additionally, there are quite a
> few matters left to be decided (see Open Questions). However, I think I
> should put this formally under discussion now.
>
> Any help with the patch (largely just updating extensions and the
> mountains of tests these changes break, though later I will need to deal
> with opcache) would be appreciated.
>
> Thanks!
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--047d7bd6ba9a07050a0505eab6f8--