Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110771
MIME-Version: 1.0
Date: Mon, 29 Jun 2020 12:30:35 +0200
Message-ID: <CAFPFaMK2ku+Jicv2znPnOb7RUQRc8iyVxRNOzjxRRmZh04RB2A@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000014509705a9368d61"
Subject: [PHP-DEV][RFC] Saner numeric strings
From: george.banyard@gmail.com ("G. P. B.")

--00000000000014509705a9368d61
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Greetings internal,

While reviving the "Permit trailing whitespace in numeric strings" RFC [1]
I didn't see Nikita's comment on Andrea's original PR which commented on
the fact that we should get rid of the "leading-numeric string" concept.

Therefore, mostly due to time constraints, I've merge the trailing
whitespace RFC with the removal of this concept in the following RFC:
https://wiki.php.net/rfc/saner-numeric-strings

The main gist is to convert all E_NOTICEs  =E2=80=9CA non well formed numer=
ic value
encountered=E2=80=9D to the usual E_WARNING =E2=80=9CA non-numeric value en=
countered=E2=80=9D and
allow trailing whitespaces, which would be most reasonables cases where the
E_NOTICE has been emitted.

This RFC is heavily based on Andrea's original RFC [1] and I would like to
thank her once more for the preliminary work she's done that I could reuse.

Best regards

George P. Banyard

[1] https://wiki.php.net/rfc/trailing_whitespace_numerics

--00000000000014509705a9368d61--