Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122671
Precedence: bulk
MIME-Version: 1.0
References: <a1f10f65-2d44-45bf-8692-51398c168bbe@redmagic.org.uk> <09F87F91-6538-48D2-9E34-0296E02CCC1A@sakiot.com>
In-Reply-To: <09F87F91-6538-48D2-9E34-0296E02CCC1A@sakiot.com>
Date: Sun, 17 Mar 2024 16:52:04 -0700
Message-ID: <CAMrTa2E=-QWHrJG2biPYmDtSJBvx5Er0r44AaOHqk2FRRkzs_g@mail.gmail.com>
Subject: Re: [PHP-DEV] Supporting object types in BCMath
To: Saki Takamachi <saki@sakiot.com>
Cc: Barney Laurance <barney@redmagic.org.uk>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000003d14880613e3ee35"
From: jordan.ledoux@gmail.com (Jordan LeDoux)

--0000000000003d14880613e3ee35
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 16, 2024 at 8:39=E2=80=AFAM Saki Takamachi <saki@sakiot.com> wr=
ote:

> Hi Barney,
>
> Thanks, that's what I was starting to worry about too. It seems like a
> good idea to support only immutability, as you say earlier in your propos=
al.
>
> Regards.
>
> Saki


Using a BCNum inside a loop is the use case, where every loop would result
in memory allocation for a new object, as well as the overhead of the
constructor, etc.

Granted, only people who REALLY know what they are doing should be doing
this. Though my library which essentially IS a wrapped for BCMath that is
upgradeable if you install other extensions (like ext-decimal) does support
both, I suggest using primarily immutables in my docs.

That said, the C library itself for BCMath is insanely inefficient as far
as arbitrary precision math goes, so I would suggest that people don't get
their hopes up too much on the performance front.

Jordan

--0000000000003d14880613e3ee35
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Mar 16, 2024 at 8:39=E2=80=AF=
AM Saki Takamachi &lt;<a href=3D"mailto:saki@sakiot.com">saki@sakiot.com</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi =
Barney,<br>
<br>
Thanks, that&#39;s what I was starting to worry about too. It seems like a =
good idea to support only immutability, as you say earlier in your proposal=
.<br>
<br>
Regards.<br>
<br>
Saki</blockquote><div><br></div><div>Using a BCNum inside a loop is the use=
 case, where every loop would result in memory allocation for a new object,=
 as well as the overhead of the constructor, etc.</div><div><br></div><div>=
Granted, only people who REALLY know what they are doing should be doing th=
is. Though my library which essentially IS a wrapped for BCMath that is upg=
radeable if you install other extensions (like ext-decimal) does support bo=
th, I suggest using primarily immutables in my docs.</div><div><br></div><d=
iv>That said, the C library itself for BCMath is insanely inefficient as fa=
r as arbitrary precision math goes, so I would suggest that people don&#39;=
t get their hopes up too much on the performance front.</div><div><br></div=
><div>Jordan<br></div></div></div>

--0000000000003d14880613e3ee35--