Am 03.03.2021 um 19:21 schrieb Stanislav Malyshev <smalys...@gmail.com>: > Nobody who applies == to strings and expects it to work out as stri g > comparison is doing the right thing. If you apply == 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 == with two strings where one (or both?) of them is numeric cause an E_NOTICE or E_WARNING that === should be used? b) Should == 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
