|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #23110 Ugly behaviour of == (and ===)
Submitted: 2003-04-08 06:43 UTC Modified: 2004-08-06 21:13 UTC
Avg. Score:4.9 ± 0.3
Reproduced:5 of 6 (83.3%)
Same Version:2 (40.0%)
Same OS:4 (80.0%)
From: kyrael at web dot de Assigned:
Status: Closed Package: Documentation problem
PHP Version: 4.3.1 OS: Linux
Private report: No CVE-ID: None
 [2003-04-08 06:43 UTC] kyrael at web dot de
string(3) "1e1"
string(2) "10"

This behaviour is ugly - both operands are strings, and they are clearly not equal. '1e0' and '1.0' and '1' are "equal" too. Same with '3.20' and '3.2'. Does PHP think i am stupid and unable to type numbers when i want them?
According to the manual, == returns true if the two operands are equal, and === returns true if the operands are equal and of the same type. == says they are equal, and according to var_dump they are both strings - why doesn't === return true then? So this behaviour is neither logical nor documented. String comparison, even with == when both operands are strings, should return 'equal' if and only if the strings are really equal. Wouldn't be PHP5 a chance to change this?


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2003-04-08 06:57 UTC] kyrael at web dot de
Btw, in switch you can't use strcmp or ===, because switch seems to use ==.
 [2003-05-02 13:10 UTC]
This will not change, the documentation team needs to be clear on that.

We don't have '===' for nothing.
 [2004-02-04 18:15 UTC] tgrey at supercomputerinc dot com
highly illogical indeed.  if the types differ, how could the values be considered equal?  when working with functions that could have different input types this behaviour is disasterous.  it seems to be counterproductive to loose variable types, since a data type check has to be added.

working around is often possible, but if i wanted to code around my *** to get to my elbow i'd be using perl.  imho this behavior needs some strong reconsideration.

very simple example:
	echo "zero: $in";
	echo "not zero: $in";

or worse yet:
function test($in=0)
	case 0:
		echo "zero: $in";
	case "blah":  // never reached!
		echo "blah: $in";
		echo "default: $in";
 [2004-05-22 11:20 UTC]
See also #20726.
 [2004-08-06 21:13 UTC]
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.

"If you compare integer with the string, the string is converted to number. If you compare two numerical strings, they are compared as integers. These rules are valid also for the switch statement." + example:

var_dump(0 == "a"); // 0 == 0 -> true
var_dump("1" == "01"); // 1 == 1 -> true

switch ("a") {
case 0:
    echo "0";
case "a": // never reached because "a" is already matched with 0
    echo "a";

PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Jul 16 15:01:28 2024 UTC