Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105450
To: PHP internals <internals@lists.php.net>
Thread-Topic: Revive Number Format Separator RFC
Thread-Index: AQHU+7D7OGXgdVHJp0Ci/FG71ATk0w==
Date: Thu, 25 Apr 2019 22:07:26 +0000
Message-ID: <DM5PR06MB28578FFCD3349CF7F41F33FDDE3D0@DM5PR06MB2857.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: fb502718-c83f-4915-9fc1-08d6c9ca6720
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2019 22:07:26.9140
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT169
Subject: Revive Number Format Separator RFC
From: theodorejb@outlook.com (Theodore Brown)

Is there any chance the Number Format Separator RFC [1] could be revived fo=
r PHP 7.4? I looked at the discussion from a few years ago and it's not cle=
ar why many people originally voted against it.=0A=
=0A=
JavaScript and Python have both gotten this feature recently and it's somet=
hing I really miss in PHP when declaring/reading large numbers.=0A=
=0A=
Maybe it would help to simplify how the restrictions are described in the R=
FC. As I understand it, the only restriction is that each underscore in a n=
umeric literal must be between two digits. Perhaps the way the RFC describe=
d this syntax made it seem more complex than it is.=0A=
=0A=
Best regards,=0A=
=0A=
Theodore Brown=0A=
=0A=
[1]: https://wiki.php.net/rfc/number_format_separator=