Bug #54547 [Ver]: wrong equality of string numbers

From: Date: Wed, 11 Apr 2012 10:45:46 +0000
Subject: Bug #54547 [Ver]: wrong equality of string numbers
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-169430@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=54547&edit=1

 ID:                 54547
 Updated by:         hholzgra@php.net
 Reported by:        peter dot ritt at gmx dot net
 Summary:            wrong equality of string numbers
 Status:             Verified
 Type:               Bug
 Package:            Unknown/Other Function
 Operating System:   linux
 PHP Version:        5.3.6
 Assigned To:        dmitry
 Block user comment: N
 Private report:     N

 New Comment:

If we indeed want to change the behavior here (and i'm yet undecided to whether i'd want
to do this or not, although slightly biased towards a 'yes):

wouldn't it be easier (although probably slightly less effective performance wise) to do a
string comparison first if both arguments are strings, and only fall back to numeric auto casts if
the string comparison fails?

If the strings really contain different numeric literals i'd expect a string comparison to fail
quickly as there can only be so much digits (ok, in theory you could have up to 300+ digits, but not
all of them significant).

This would take care of all possible edge cases (assuming that there may be others that we
aren't aware of yet, even though i can't think of any right now) and not just the overflow
case at hand, and the required engine changes would probably be a single chunk only, so having
better patch locality ...

Or are there other places where we'd need an extended is_numeric_string check with overflow
control, too?


Previous Comments:
------------------------------------------------------------------------
[2012-04-11 08:44:39] net at janoszen dot hu

Same problem:

php > var_dump('0xff' == '255');
bool(true)

------------------------------------------------------------------------
[2012-04-11 07:47:21] foobla at spambog dot com

I don't think it's about PHP_MAX_INT, rather about the maximum precision of a
double/float. "==" converts both strings to numbers (after spending CPU cycles to detect
whether they look like numbers), as described in http://www.phpsadness.com/sad/47

once converted, the floats seem to actually *be* equal, even with "===":

php -r '
$a = (double)"9223372036854775807";
$b = (double)"9223372036854775808";
var_dump($a, $b, $a == $b, $a === $b);
'
float(9.2233720368548E+18)
float(9.2233720368548E+18)
bool(true)
bool(true)

------------------------------------------------------------------------
[2011-04-18 03:04:14] cataphract@php.net

Maybe this should be Won't Fix to keep it consistent with 9223372036854775807 ==
9223372036854775808 (with number literals).

------------------------------------------------------------------------
[2011-04-17 05:44:03] cataphract@php.net

The following patch has been added/updated:

Patch Name: bug54547-2.diff
Revision:   1303011843
URL:        http://bugs.php.net/patch-display.php?bug=54547&patch=bug54547-2.diff&revision=1303011843

------------------------------------------------------------------------
[2011-04-17 01:59:59] cataphract@php.net

The following patch has been added/updated:

Patch Name: bug54547.diff
Revision:   1302998399
URL:        http://bugs.php.net/patch-display.php?bug=54547&patch=bug54547.diff&revision=1302998399

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=54547


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=54547&edit=1


Thread (44 messages)

« previous php.bugs (#169430) next »