Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123044
Precedence: bulk
MIME-Version: 1.0
References: <40553F28-2EC2-475A-BD8E-1D6517AA2A51@rwec.co.uk>
 <2B518F62-B774-45C9-82A2-EF6653AAE34E@sakiot.com> <A703D145-1A10-4C7E-9E0C-1F0BEF94CF99@rwec.co.uk>
 <F36A5C9B-7F3E-4EB7-A254-2ADB47AB6AE0@sakiot.com> <CAL0xaBEQdWX735rE-EoxEr=44VTX5ud=XOvxn_g1Y28V2fugFg@mail.gmail.com>
 <57c268e9be57edad86155c461b0fd181@gliadin.co.uk> <CAL0xaBHW8wdPu4qsnoXwzmensO5Yj=0HQS0VLknFcSonYcci=g@mail.gmail.com>
 <b41a5f80-5663-439b-942a-1d362116fe6e@app.fastmail.com>
In-Reply-To: <b41a5f80-5663-439b-942a-1d362116fe6e@app.fastmail.com>
Date: Mon, 8 Apr 2024 17:49:48 +0300
Message-ID: <CAL0xaBETd6e0G0A_G_VL_Wciiur9JC-ffb41mNsH4gndbxuefA@mail.gmail.com>
Subject: Re: [PHP-DEV] Native decimal scalar support and object types in
 BcMath - do we want both?
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007631a8061596eb52"
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--0000000000007631a8061596eb52
Content-Type: text/plain; charset="UTF-8"

On Mon, Apr 8, 2024, 16:40 Rowan Tommins [IMSoP] <imsop.php@rwec.co.uk>
wrote:

> On Mon, 8 Apr 2024, at 13:42, Arvids Godjuks wrote:
>
> The ini setting I was considering would function similarly to what it does
> for floats right now - I assume it changes the exponent, thereby increasing
> their precision but reducing the integer range they can cover.
>
>
> If you're thinking of the "precision" setting, it doesn't do anything
> nearly that clever; it's purely about how many decimal digits should be
> *displayed* when converting a binary float value to a decimal string. In
> recent versions og PHP, it has a "-1" setting that automatically does the
> right thing in most cases.
> https://www.php.net/manual/en/ini.core.php#ini.precision
>
> The other way around - parsing a string to a float, including when
> compiling source code - has a lot of different compile-time options,
> presumably to optimise on different platforms; but no user options at all:
> https://github.com/php/php-src/blob/master/Zend/zend_strtod.c
>
> Regards,
> --
> Rowan Tommins
> [IMSoP]
>

Thanks for the info. Then we just specify the value range for the decimal
the same way it's done for integer and float and let developers decide if
it fits their needs or they need to use BCMath/Decimal/GMP extensions.

Develop for the common use case for the core, let extensions take the
burden of the rest.

>

--0000000000007631a8061596eb52
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Mon, Apr 8, 2024, 16:40 Rowan Tommins [IMSoP] &lt;<=
a href=3D"mailto:imsop.php@rwec.co.uk">imsop.php@rwec.co.uk</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><u></u><div><div>On Mon, 8 Apr 2024=
, at 13:42, Arvids Godjuks wrote:<br></div><blockquote type=3D"cite" id=3D"=
m_-4489821713558585876qt"><div dir=3D"ltr"><div dir=3D"ltr">The ini setting=
 I was considering would function similarly to what it does for floats righ=
t now - I assume it changes the exponent, thereby increasing their precisio=
n but reducing the integer range they can cover.<br></div></div></blockquot=
e><div><br></div><div>If you&#39;re thinking of the &quot;precision&quot; s=
etting, it doesn&#39;t do anything nearly that clever; it&#39;s purely abou=
t how many decimal digits should be *displayed* when converting a binary fl=
oat value to a decimal string. In recent versions og PHP, it has a &quot;-1=
&quot; setting that automatically does the right thing in most cases. <a hr=
ef=3D"https://www.php.net/manual/en/ini.core.php#ini.precision" target=3D"_=
blank" rel=3D"noreferrer">https://www.php.net/manual/en/ini.core.php#ini.pr=
ecision</a><br></div><div><br></div><div>The other way around - parsing a s=
tring to a float, including when compiling source code - has a lot of diffe=
rent compile-time options, presumably to optimise on different platforms; b=
ut no user options at all: <a href=3D"https://github.com/php/php-src/blob/m=
aster/Zend/zend_strtod.c" target=3D"_blank" rel=3D"noreferrer">https://gith=
ub.com/php/php-src/blob/master/Zend/zend_strtod.c</a><br></div><div><br></d=
iv><div>Regards,<br></div><div>-- <br>Rowan Tommins</div><div>[IMSoP]<br></=
div></div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Thanks for the info. Then we just specify the value range for the dec=
imal the same way it&#39;s done for integer and float and let developers de=
cide if it fits their needs or they need to use BCMath/Decimal/GMP extensio=
ns.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Develop for the comm=
on use case for the core, let extensions take the burden of the rest.</div>=
<div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div><div></div></div></blockquote></div></div></div>

--0000000000007631a8061596eb52--