Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111044
MIME-Version: 1.0
References: <CAFPFaM+MVVOd2ATWkEZQ_TVv2DwdbUP3zNkG_qh5f652CFkLZA@mail.gmail.com>
In-Reply-To: <CAFPFaM+MVVOd2ATWkEZQ_TVv2DwdbUP3zNkG_qh5f652CFkLZA@mail.gmail.com>
Date: Thu, 16 Jul 2020 15:39:21 +0200
Message-ID: <CADyq6sJrreJu3jyKdk75CFekWsCJLyf54hdK27bONLMk4t-r9g@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000aca52405aa8f2b96"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Saner numeric strings
From: ocramius@gmail.com (Marco Pivetta)

--000000000000aca52405aa8f2b96
Content-Type: text/plain; charset="UTF-8"

Hey George,

I really like this specific bit of the proposal:

 > And the various cases which currently emit an E_WARNING will be promoted
to TypeErrors.

I really do not like these particular horrible behaviors of the language
(huge "yikes" for PHP being so broken):

 * `"123" == "123 "` - do not want - already bad enough that leading
whitespace is ignored here, and already caused some security issues on my
end some years ago
 * `is_numeric("123   ") === true` - `is_numeric()` should probably be
soft-deprecated and replaced with something stricter, instead of expanding
this too...

I don't really care about `declare(strict_types=0), since I don't use it
anymore, nor plan to use it anymore in any foreseeable future, but the two
points above really feel wrong, and I'm conflicted about what to vote.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Thu, Jul 16, 2020 at 3:21 PM G. P. B. <george.banyard@gmail.com> wrote:

> Hello internals,
>
> I've opened voting for the Saner Numeric strings RFC:
> https://wiki.php.net/rfc/saner-numeric-strings
>
> This will last 2 weeks until the 30th of July
>
> Best regards
>
> George P. Banyard
>

--000000000000aca52405aa8f2b96--