Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <06F175EB-D44A-445F-8015-8421C7C12F39@ajf.me>
References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me>
	<BCFDECB6-8FBC-4EA1-A081-21BDCC79C1C2@ajf.me>
	<B9B67D82-CB4E-4CA6-AFAB-25A22EC386B4@ajf.me>
	<54D00C40.8060907@lsces.co.uk>
	<54C5DC93-9600-4EE2-BF06-7BF10FC6AD5C@ajf.me>
	<54D08D50.5050407@lsces.co.uk>
	<1C2ED70C-72A0-4513-A134-5DAE4CCA5B3D@ajf.me>
	<54D0DFE5.9030602@lsces.co.uk>
	<06F175EB-D44A-445F-8015-8421C7C12F39@ajf.me>
Date: Tue, 3 Feb 2015 14:29:55 -0600
Message-ID: <CALrkBjbKA19qdQ0fF6AMRVc8QuXUvF1j9DVGrvWoJZ7VM73thQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Lester Caine <lester@lsces.co.uk>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30363fdb0e0d6b050e34efe7
Subject: Re: [PHP-DEV] [RFC] Big Integer Support
From: pencap@gmail.com (Mike Willbanks)

--20cf30363fdb0e0d6b050e34efe7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 3, 2015 at 10:44 AM, Andrea Faulds <ajf@ajf.me> wrote:

>
> > On 3 Feb 2015, at 14:49, Lester Caine <lester@lsces.co.uk> wrote:
> >
> > On 03/02/15 14:03, Andrea Faulds wrote:
> >> But I don=E2=80=99t consider 0.25MB extra to be such a problem in prac=
tice. The
> PHP binary is already huge, and every system running PHP will have ample
> memory.
> >
> > Yes one approach is 'computers are getting faster with lots of memory'
> > ... and for servers this is not a problem ...    they will more than
> > likely be 64bit anyway! But for smaller embedded devices php *IS*
> > becoming an option so I don't have to program in C or something else,
> > and then we look to strip everything that does not need to be present.
>
> Sure, but I don=E2=80=99t think we shouldn=E2=80=99t cripple the language=
 merely for the
> sake of really low-end embedded devices. Also, I=E2=80=99m not convinced =
that the
> overhead, at least in terms of file size, is really that big of an issue.
>
> Just for you, I=E2=80=99ve gone and compiled the bigint branch (with LibT=
omMath)
> and master on my machine:
>
> $ ls -l php7-*
> -rwxr-xr-x  1 ajf  staff  6400408  3 Feb 16:39 php7-bigint
> -rwxr-xr-x  1 ajf  staff  6248920  3 Feb 16:42 php7-master
>
> The difference is a mere 151488 B, or 151 KB.
>
> Is that really so bad?
>

I would take 1MB if I had to so that I could have this in core.  I work
with them everyday and the pain of having to deal with them as strings is a
royal pain.  It would only become worse if this does not get into core and
type hints do as the mess would be drastic for any systems that must handle
64bit integers across the board.  It's not useful to have to always go to
gmp to handle numbers of this type.  It is simply not realistic.

On top of that, we use embedded systems everyday.  I have 6 devices sitting
in front of me right now.  Think of a GUID whereas they have large integer
internal representations and a hex representation for human readable.  On
top of this, we also have beaglebones and raspberry pi's that have internal
memory capacities where this easily fits and flash storage.  There is no
reason that this feature should be held back for embedded systems or even
system on a chip.

Regards,

Mike

--20cf30363fdb0e0d6b050e34efe7--