Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128032
Date: Mon, 14 Jul 2025 11:54:57 +0000
To: PHP internals <internals@lists.php.net>
Subject: [PHP-DEV] Introduce PHP_INT_MAX_SAFE constant similar to JS's Number.MAX_SAFE_INTEGER constant
Message-ID: <JmibpRsqea2SclQTanbLT9XZn_QjJHHsPQP4-_5AjRByYa6SAQPQqKRYrZQz5UR_GTIEpKZn-NmT-GEx892EO1Xb6LjpurBQjxvGw9wJzdA=@gpb.moe>
Feedback-ID: 96993444:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

Hello internals,

I'm mailing the list for the bike shed of the naming of a new constant I th=
ink we should introduce in PHP which I'm currently calling PHP_INT_MAX_SAFE=
.
The purpose of this integer is to indicate what is the maximal integer valu=
e that can be correctly represented by a float.
On 32 bits this is equal to PHP_INT_MAX, but on 64 bits it is 9007199254740=
991 (which is 2^(53) =E2=80=93 1) as the mantissa of a floating point numbe=
r is 52 bits.

For more information, please see the MDN documentation about Number.MAX_SAF=
E_INTEGER. [1]

The implementation is very simple and the PR is https://github.com/php/php-=
src/pull/19126

Best regards,

Gina P. Banyard

[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Globa=
l_Objects/Number/MAX_SAFE_INTEGER