Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104528
MIME-Version: 1.0
References: <CAF+90c821boRO6YsO0SH0JbDb8E8eTHfEK=e4Y5_z9P7+OOnUg@mail.gmail.com>
In-Reply-To: <CAF+90c821boRO6YsO0SH0JbDb8E8eTHfEK=e4Y5_z9P7+OOnUg@mail.gmail.com>
Date: Wed, 27 Feb 2019 09:06:33 +0100
Message-ID: <CADq_Cxo6g-HLY6JagnA1M5n-Buw=12MBp2ympdq0mVzQuDrC6w@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000095e4cd0582dba7d8"
Subject: Re: [PHP-DEV] [RFC] Saner string to number comparisons
From: robin@kingsquare.nl ("Kingsquare.nl - Robin Speekenbrink")

--00000000000095e4cd0582dba7d8
Content-Type: text/plain; charset="UTF-8"

Op di 26 feb. 2019 om 13:27 schreef Nikita Popov <nikita.ppv@gmail.com>:

> Hi internals,
>
> I think it is well known that == in PHP is a pretty big footgun. It doesn't
> have to be. I think that type juggling comparisons in a language like PHP
> have some merit, it's just that the particular semantics of == in PHP make
> it so dangerous. The biggest WTF factor is probably that 0 == "foobar"
> returns true.
>
> I'd like to bring forward an RFC for PHP 8 to change the semantics of ==
> and other non-strict comparisons, when used between a number and a string:
>
> https://wiki.php.net/rfc/string_to_number_comparison
>
> ...
>
> Regards,
> Nikita
>

Dear All,

From a user-space POV this is a very good way forward and I (personally)
really like the proposal of having a transitional period (7.4 anyone?)

As of the 0 == "" bit: I do think that an empty string is widespread
regarded as falsey-string... Thus 0 == "" sould IMHO return true...

Just my 2 cents, keep up the excellent Nikita!
(and everyone else ofcourse)

Regards,
Robin

--00000000000095e4cd0582dba7d8--