Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124378
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] [Discussion] Allow int type argument to BCMath function 
Date: Thu, 11 Jul 2024 10:49:27 +0900
Message-ID: <1655D14E-019E-42D9-B046-028C2405ABAA@sakiot.com>
References: <cbeb88f3-4d1b-41aa-8d63-66c54af0d146@bastelstu.be>
Cc: Jordan LeDoux <jordan.ledoux@gmail.com>,
 Juliette Reinders Folmer <php-internals_nospam@adviesenzo.nl>,
 internals@lists.php.net
In-Reply-To: <cbeb88f3-4d1b-41aa-8d63-66c54af0d146@bastelstu.be>
To: =?utf-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
From: saki@sakiot.com (Saki Takamachi)

Hi Tim,

> That's fair enough.
>=20
> I do still consider accepting 'int' to be less unsafe than accepting 'floa=
t', because the behavior of ints can be reasoned about more easily and becau=
se they to not experience implicit rounding.
>=20
> I do not particularly care whether or not 'int' is accepted or not for tha=
t reason, but I care about 'float' not being accepted. So perhaps it's best t=
o accept neither as you suggested.

Yes, I had completely forgotten about casting priorities.

So, at least I don't plan on including it in 8.4, and may even retract the c=
hange altogether.

Regards,

Saki=