Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113356
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Wed, 3 Mar 2021 20:30:38 +0100
References: <CAF+90c-93pAMM3XYrj=G_Z+uaTRTgzdEOULYwKUj7Hp64FBp6w@mail.gmail.com>
 <c79fe1ef-433a-72d7-9b89-ae279b39a1f5@gmail.com>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <c79fe1ef-433a-72d7-9b89-ae279b39a1f5@gmail.com>
Message-ID: <E0DF66AE-A0DC-4715-8771-5D9EC81A6BFB@cschneid.com>
Subject: Re: [PHP-DEV] Don't compare zero exponentials in strings as equal
From: cschneid@cschneid.com (Christian Schneider)

Am 03.03.2021 um 19:21 schrieb Stanislav Malyshev <smalyshev@gmail.com>:
> Nobody who applies =3D=3D to strings and expects it to work out as =
stri g comparison is doing the right thing. If you apply =3D=3D to =
hex-encoded hashes, that code is fubar, and fixing one particular corner =
case won't rescue it. So I wonder if fixing one particular corner case =
while leaving many others in would do much.


Just brainstorming, but following that logic, if we would like to remedy =
this in the long run:
a) Should =3D=3D with two strings where one (or both?) of them is =
numeric cause an E_NOTICE or E_WARNING that =3D=3D=3D should be used?
b) Should =3D=3D with two strings leave them as string? Possibly after a =
period of notice/warning as described in a)?

I haven't really thought this through but I still wanted to throw it out =
there.
I'm sure you'll tell me how foolish I am and why this is a very bad idea =
;-)

- Chris