Delicious Bookmark this on Delicious Share on Facebook SlashdotSlashdot It! Digg! Digg

PHP : Language Reference : Operators : Comparison Operators

Comparison Operators

Comparison operators, as their name implies, allow you to compare two values. You may also be interested in viewing the type comparison tables, as they show examples of various type related comparisons.

Table 6.4. Comparison Operators

Example Name Result
$a == $b Equal TRUE if $a is equal to $b.
$a === $b Identical TRUE if $a is equal to $b, and they are of the same type. (introduced in PHP 4)
$a != $b Not equal TRUE if $a is not equal to $b.
$a <> $b Not equal TRUE if $a is not equal to $b.
$a !== $b Not identical TRUE if $a is not equal to $b, or they are not of the same type. (introduced in PHP 4)
$a < $b Less than TRUE if $a is strictly less than $b.
$a > $b Greater than TRUE if $a is strictly greater than $b.
$a <= $b Less than or equal to TRUE if $a is less than or equal to $b.
$a >= $b Greater than or equal to TRUE if $a is greater than or equal to $b.

If you compare an integer with a string, the string is converted to a number. If you compare two numerical strings, they are compared as integers. These rules also apply to the switch statement.

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

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

For various types, comparison is done according to the following table (in order).

Table 6.5. Comparison with Various Types

Type of Operand 1 Type of Operand 2 Result
null or string string Convert NULL to "", numerical or lexical comparison
bool or null anything Convert to bool, FALSE < TRUE
object object Built-in classes can define its own comparison, different classes are uncomparable, same class - compare properties the same way as arrays (PHP 4), PHP 5 has its own explanation
string, resource or number string, resource or number Translate strings and resources to numbers, usual math
array array Array with fewer members is smaller, if key from operand 1 is not found in operand 2 then arrays are uncomparable, otherwise - compare value by value (see following example)
array anything array is always greater
object anything object is always greater

Example 6.2. Transcription of standard array comparison

// Arrays are compared like this with standard comparison operators
function standard_array_compare($op1, $op2)
   if (
count($op1) < count($op2)) {
       return -
1; // $op1 < $op2
} elseif (count($op1) > count($op2)) {
1; // $op1 > $op2
   foreach (
$op1 as $key => $val) {
       if (!
array_key_exists($key, $op2)) {
null; // uncomparable
} elseif ($val < $op2[$key]) {
           return -
       } elseif (
$val > $op2[$key]) {
0; // $op1 == $op2

See also strcasecmp(), strcmp(), Array operators, and the manual section on Types.

Ternary Operator

Another conditional operator is the "?:" (or ternary) operator.

Example 6.3. Assigning a default value

// Example usage for: Ternary Operator
$action = (empty($_POST['action'])) ? 'default' : $_POST['action'];

// The above is identical to this if/else statement
if (empty($_POST['action'])) {
$action = 'default';
} else {
$action = $_POST['action'];


The expression (expr1) ? (expr2) : (expr3) evaluates to expr2 if expr1 evaluates to TRUE, and expr3 if expr1 evaluates to FALSE.


Please note that the ternary operator is a statement, and that it doesn't evaluate to a variable, but to the result of a statement. This is important to know if you want to return a variable by reference. The statement return $var == 42 ? $a : $b; in a return-by-reference function will therefore not work and a warning is issued in later PHP versions.


Is is recommended that you avoid "stacking" ternary expressions. PHP's behaviour when using more than one ternary operator within a single statement is non-obvious:

Example 6.4. Non-obvious Ternary Behaviour

// on first glance, the following appears to output 'true'
echo (true?'true':false?'t':'f');

// however, the actual output of the above is 't'
// this is because ternary expressions are evaluated from left to right

// the following is a more obvious version of the same code as above
echo ((true ? 'true' : 'false') ? 't' : 'f');

// here, you can see that the first expression is evaluated to 'true', which
// in turn evaluates to (bool)true, thus returning the true branch of the
// second ternary expression.

Code Examples / Notes » language.operators.comparison


You should be very careful when using == with an result set returned from a query that can be an empty array, multi-dimensional array or a boolean false value (if the query failed to execute). In PHP, an empty array is equivalent to true.
$myArray = array();
// check if there is any error with the query
if ($myArray == false)
   echo "Yes";
return Yes
Use === instead.


You can't just compare two arrays with the === operator
like you would think to find out if they are equal or not.  This is more complicated when you have multi-dimensional arrays.  Here is a recursive comparison function.
* Compares two arrays to see if they contain the same values.  Returns TRUE or FALSE.
* usefull for determining if a record or block of data was modified (perhaps by user input)
* prior to setting a "date_last_updated" or skipping updating the db in the case of no change.
* @param array $a1
* @param array $a2
* @return boolean
function array_compare_recursive($a1, $a2)
  if (!(is_array($a1) and (is_array($a2)))) { return FALSE;}

  if (!count($a1) == count($a2))
      return FALSE; // arrays don't have same number of entries
  foreach ($a1 as $key => $val)
      if (!array_key_exists($key, $a2))
          {return FALSE; // uncomparable array keys don't match
      elseif (is_array($val) and is_array($a2[$key]))  // if both entries are arrays then compare recursive
          {if (!array_compare_recursive($val,$a2[$key])) return FALSE;
      elseif (!($val === $a2[$key])) // compare entries must be of same type.
          {return FALSE;
  return TRUE; // $a1 === $a2


With Nested ternary Operators you have to set the logical  parentheses to get the correct result.
($test) ? "TEST1 true" :  ($test2) ? "TEST2 true" : "false";
This will output: TEST2 true;
($test) ? "TEST1 true" : (($test2) ? "TEST2 true" : "false");
Anyway don't nest them to much....!!


When you want to know if two arrays contain the same values, regardless of the values' order, you cannot use "==" or "===".  In other words:
(array(1,2) == array(2,1)) === false;
To answer that question, use:
function array_equal($a, $b) {
   return (is_array($a) && is_array($b) && array_diff($a, $b) === array_diff($b, $a));
A related, but more strict problem, is if you need to ensure that two arrays contain the same key=>value pairs, regardless of the order of the pairs.  In that case, use:
function array_identical($a, $b) {
   return (is_array($a) && is_array($b) && array_diff_assoc($a, $b) === array_diff_assoc($b, $a));
$a = array (2, 1);
$b = array (1, 2);
// true === array_equal($a, $b);
// false === array_identical($a, $b);
$a = array ('a' => 2, 'b' => 1);
$b = array ('b' => 1, 'a' => 2);
// true === array_identical($a, $b)
// true === array_equal($a, $b)
(See also the solution "rshawiii at yahoo dot com" posted)


Warning, string comparison may be even stranger than you thought:
$a = "0e2";
$b = "0e3";
if ($a == $b)  print '$a ==  $b'."\n"; // True
if ($a === $b) print '$a === $b'."\n"; // False
if ("000e002073" == "0e2857") print '"000e002073" == "0e2857"'."\n"; // True
$a == $b
"000e002073" == "0e2857"
According to Table 15.4, since $a and $b are of the same type, it might have been expected that == and === gave the same result? Not necessarily.
The clue is in the text below the table:
"If you compare two numerical strings, they are compared as integers."
Since these strings are numerical strings (in fact floats, if you hadn't worked it out yet), they are compared as integers.
This is the behaviour we know and love about php, and I have no problem with it. I do have a problem that == and === give different answers for objects when "they are of the same type."
I think that Table 15.4 gives no inkling of this.
Table 15.5 might have made the situation clearer, but makes no distinction between == and ===.
Of course, to be really safe, we should have been using strcmp() in any case, but it seems to be quite common that people use == for strings, so it should be pointed out.
I am suggesting (by other mechanism) a change to the page, but in the meantime (or if it is rejected) this note may help.
By the way, this was a real problem for me.
If you are comparing a significant number of strings which happen to be hex, it is quite surprising to find that "000" == "0e0" whereas "000" != "0f0".
I think I might start using things like "0e0" for username and password on websites to see what breaks :-)

webmaster __at__ digitalanime __dot__ nl

Let's say, we have this little script:
$username = 'Me';
$guestusername = 'Guest';
echo 'Hello, ' . isset($i) ? 'my friend: ' . $username . ', how are you doing?' : 'my guest, ' . $guestusername . ', please register';
What you want:
If $i is set, display:
Hello, my friend: Me, how are you doing?
If not, display:
Hello, my guest, Guest, please register
BUT, you DON'T get that result!
If $i is set, you get this:
my friend: Me, how are you doing? (so, there's not "Hello, " before it)
If $i is NOT set, you get this:
my friend: Me, how are you doing?
So... That's the same!
You can solve this by using the "(" and ")" to give priority to the ternary operator:
$username = 'Me';
$guestusername = 'Guest';
echo 'Hello, ' . (isset($i) ? 'my friend: ' . $username . ', how are you doing?' : 'my guest, ' . $guestusername . ', please register');
When $i is set, you get this:
Hello, my friend: Me, how are you doing? (expected)
When $i is NOT set, you get this:
Hello, my guest, Guest, please register (expected too)
So.. Please, don't be dumb and ALWAYS use the priority-signs (or.. How do you call them?), ( and ).
By using them, you won't get unneeded trouble and always know for sure your code is doing what you want: The right thing.


Today I notices problem with comparision different data types.
My code is like that:
function checkAndChange( $values)
$core = &Core::_();
$user = &$core->getUser();
switch( $user->changePassword( $values['oldpass'], $values['newpass'], $values['newpass2']))
case( 'old'):
return 'Bad current password';

case( 'user'):
return 'Bad user';
case( 'new'):
return 'Can\'t change';
return true;
return true;
function checkAndChange is called by callback, function changePassword returned string (indicating any error) or bool true (if no error). The problem was that if changePassword returned true it was always taking the first case - so in the example case( 'old'), if I changed order of cases giving case( 'new') as the first one then it was taken.
This code was used to track the value of $res (which was the return from changePassword
function checkAndChange( $values)
$core = &Core::_();
$user = &$core->getUser();
            $res = $user->changePassword( $values['oldpass'], $values['newpass'], $values['newpass2']);
            echo( '<pre>');
            print_r( $res);
switch( $res)
case( 'old'):
return 'Bad current password';

case( 'user'):
return 'Bad user';
case( 'new'):
return 'Can\'t change';
return true;
return true;
Even if constructions matched wrongly and even using $res === 'new'. Maybe that was a bug or something.
How I dealed with this ? I stoped mixing the types and from that time changePassword is returning an empty string for success.
Maybe this would help someone having the same problem as I had.
PHP 4.4.7, Windows XP


This operator is very is usefull and will save you time and lines once you get the hang of it. Try this next time you are looping through rows in a table and want to change the bgColor:
<table border=1 width=100% align=center style="border-collapse: collapse" bgColor="lightblue">
<td>Column 1</td>
<td>Column 2</td>
<td>Column 3</td>
<td>Column 4</td>
while ($i++ < 10)
$rbg = $rbg=="#EEEEEE" ? "#FFFFFF" : "#EEEEEE";
<tr bgColor="<?=$rbg?>">
<td>Cell 1-<?=$i?></td>
<td>Cell 2-<?=$i?></td>
<td>Cell 3-<?=$i?></td>
<td>Cell 4-<?=$i?></td>
<? } ?>

07-sep-2005 09:09

The following contrasts the trinary operator associativity in PHP and Java.  The first test would work as expected in Java (evaluates left-to-right, associates right-to-left, like if stmnt), the second in PHP (evaluates and associates left-to-right)
echo "\n\n######----------- trinary operator associativity\n\n";
function trinaryTest($foo){
$bar = $foo > 20
? "greater than 20"
: $foo > 10
? "greater than 10"
: $foo > 5
? "greater than 5"
: "not worthy of consideration";
echo $foo." =>  ".$bar."\n";
echo "----trinaryTest\n\n";
function trinaryTestParens($foo){

$bar = $foo > 20
? "greater than 20"
: ($foo > 10
? "greater than 10"
: ($foo > 5
? "greater than 5"
: "not worthy of consideration"));
echo $foo." =>  ".$bar."\n";
echo "----trinaryTestParens\n\n";
######----------- trinary operator associativity
21 =>  greater than 5
11 =>  greater than 5
6 =>  greater than 5
4 =>  not worthy of consideration
21 =>  greater than 20
11 =>  greater than 10
6 =>  greater than 5
4 =>  not worthy of consideration


The === and !== are not fully documented in either the Comparison Operator, Booleans type sections. They are talked about a bit more in the sections on strpos() and array_search() but those sections refer you to the section on Booleans for further information.
I am putting my contribution on === and !== in the Booleans section with pointers to it from the comment areas of other sections.

04-jan-2007 03:11

Since php 5.2 the operator == for object vs object is not recursion safe, it will cause a fatal error if one of the objects contains a refernce to it self (indirect refferences also counts here).
If you are just checking if two object pointers points to the same object use === instead and aviod this issue (you might get a minimal speed bost too).


Regarding gamephreak AT removethis gmail DOT com,
I found those results interesting, so I decided to test them on my own dedicated server. I found that actually, the identity and equality operators are almost exactly the same speed when dealing with numbers and/or strings (I did not test arrays, objects, etc). I ran the same tests plus a couple of inequality tests as well, this time over a 100,000 iteration loop (rounded to 7 significant digits using round()). :
'foo' == 'foo': 0.0130451
'foo' === 'foo': 0.0124481
42 == 42: 0.0124421
42 === 42: 0.0124369
'foo' == 'bar': 0.0124562
'foo' === 'bar': 0.012475
42 == 43: 0.012471
42 === 43: 0.0124719
'42' == 42: 0.0124779
'42' === 42: 0.0124731
'42' == 43: 0.0124722
'42' === 43: 0.01248
42 != 43: 0.012444
42 !== 43: 0.0124211
This was just one snapshot, though. If I refreshed the page I was using to test this, sometimes the "winners" would reverse. In other words, no operator was clearly faster, and I think that system "noise" is may usually be more significant than the speed of these operators.
Here is sample code for one of the loops:
$time1 = microtime(true);
for ($i = 0; $i < 100000; $i++){
'42' == 43;
$time2 = microtime(true);
print "'42' == 43: " . round($time2 - $time1, 7) . '
The lesson here is that you should make your coding decisions based on what makes more sense from a logical perspective, and not what is faster. Personally I hate the equality operator since PHP's dynamic typing makes it unpredictable (e.g. two strings compared may both be cast as numbers...).


Please note that the example in some notes before is not 100% correct, because it misses the call of abs().
To compare a float you should use abs($myFloat - 0.3) < EPSILON. This way of comparison is very common in other languages and it's cleaner than converting the values to strings. I suggest using a constant instead of a variable for EPSILON.


note: the behavior below is documented in the appendix K about type comparisons, but since it is somewhat buried i thought i should raise it here for people since it threw me for a loop until i figured it out completely.
just to clarify a tricky point about the == comparison operator when dealing with strings and numbers:
('some string' == 0) returns TRUE
however, ('123' == 0) returns FALSE
also note that ((int) 'some string') returns 0
and ((int) '123') returns 123
the behavior makes senes but you must be careful when comparing strings to numbers, e.g. when you're comparing a request variable which you expect to be numeric. its easy to fall into the trap of:
if ($_GET['myvar']==0) dosomething();
as this will dosomething() even when $_GET['myvar'] is 'some string' and clearly not the value 0
i was getting lazy with my types since php vars are so flexible, so be warned to pay attention to the details...


Note: according to the spec, PHP's comparison
operators are not transitive.  For example,
the following are all true in PHP5:
"11" < "a" < 2 < "11"
As a result, the outcome of sorting an array
depends on the order the elements appear
in the pre-sort array.  The following code will
dump out two arrays with *different* orderings:
$a = array(2,    "a",  "11", 2);
$b = array(2,    "11", "a",  2);
This is not a bug report -- given the spec on
this documentation page, what PHP does is
"correct".  But that may not be what was


Note that typecasting will NOT prevent the default behavior for converting two numeric strings to numbers when comparing them.
if ((string) '0123' == (string) '123')
print 'equals';
print 'doesn\'t equal';
Still prints 'equals'
As far as I can tell the only way to avoid this is to use the identity comparison operators (=== and !==).

hayley watson

Note that the "ternary operator" is better described as the "conditional operator". The former name merely notes that it has three arguments without saying anything about what it does. Needless to say, if PHP picked up any more ternary operators, this will be a problem.
"Conditional Operator" is actually descriptive of the semantics, and is the name historically given to it in, e.g., C.


if you want to use the ?: operator, you should be careful with the precedence.
Here's an example of the priority of operators:
echo 'Hello, ' . isset($i) ? 'my friend: ' . $username . ', how are you doing?' : 'my guest, ' . $guestusername . ', please register';
This make "'Hello, ' . isset($i)" the sentence to evaluate. So, if you think to mix more sentences with the ?: operator, please use always parentheses to force the proper evaluation of the sentence.
echo 'Hello, ' . (isset($i) ? 'my friend: ' . $username . ', how are you doing?' : 'my guest, ' . $guestusername . ', please register');
for general rule, if you mix ?: with other sentences, always close it with parentheses.


If you need nested ifs on I var its important to group the if so it works.
//Dont Works
//Parse error: parse error, unexpected ':'
$var='<option value="1" '.$status == "1" ? 'selected="selected"' :''.'>Value 1</option>';
$var='<option value="1" '.($status == "1" ? 'selected="selected"' :'').'>Value 1</option>';
echo $var;


I think everybody should read carefully what "jeronimo at DELETE_THIS dot transartmedia dot com" wrote. It's a great pitfall even for seasoned programmers and should be looked upon with a great attention.
For example, comparing passwords with == may result in a very large security hole.
I would add some more to it:
The workaround is to use strcmp() or ===.
Note on ===:
While the php documentation says that, basically,
($a===$b)  is the same as  ($a==$b && gettype($a) == gettype($b)),
this is not true.
The difference between == and === is that === never does any type conversion. So, while, according to documentation, ("+0.1" === ".1") should return true (because both are strings and == returns true), === actually returns false (which is good).


I often see questions with == and === perhaps this snippet should do.
   $x="1"; //a _string_ with numeric value 1
   $y=1;    //an _integer_ with value 1
   echo "test == :".($x == $y);        //equates to TRUE
   echo "
test === :".($x === $y); //equates to FALSE


I guess quicker method would be:
$colors = array('#EEEEEE', '#FFFFFF');
while ($i++ < 10) {
   <tr bgColor="<?=$colors[$i%2]?>">
      <td>Cell 1-<?=$i?></td>
      <td>Cell 2-<?=$i?></td>
      <td>Cell 3-<?=$i?></td>
      <td>Cell 4-<?=$i?></td>
<?php } ?>
And you can easily add more colors:
$colors = array('#EEEEEE', '#FFFFFF', '#DDDDDD', '#CCCCCC');
while ($i++ < 10) {
   <tr bgColor="<?=$colors[$i%4]?>">
      <td>Cell 1-<?=$i?></td>
      <td>Cell 2-<?=$i?></td>
      <td>Cell 3-<?=$i?></td>
      <td>Cell 4-<?=$i?></td>
<?php } ?>


I also ran a benchmark of equals versus identical on my own server.  I found the difference to be surprisingly significant (average of 15% across multiple executions of the script).  Just for kicks I had it compare int to float speed as well and that came up to roughly 40% faster in favor of int (in equal/identical comparisons - no idea how they perform otherwise), and had it compare ==/=== to !=/!== and came up to negligible difference (averages out to 0).  Here are the results over 100k iterations - if you want to know exactly what comparisons were done let me know:
           100000 iterations
           total identical 36.142370939255
              total equals 41.991316795349
                  total is 38.998074293137
                 total not 39.135613441467
                 total int 29.253834247589
               total float 48.879853487015
 %gain identical vs equals 13.928941272788
           %gain is vs not 0.35144242350103
        %gain int vs float 40.151550872875
                total time 78.15989112854

sven dot heyll

Hi folks,
to the float comparison problem...
This worked for me:
//! compare two floating point values, return true if they are equal
//! (enough) or false otherwise
function float_equal($f1, $f2)
return ($f1 > $f2) ? (false) : (!($f1 < $f2));
// compare floats
$f1 = 0.037;
$f2 = 1000387.978;
echo "$f1 and $f2 are ".(float_equal($f1,$f2)?("equal"):("not equal"))."<br />";
$f1 = 0.3;
$f2 = 0.3;
echo "$f1 and $f2 are ".(float_equal($f1,$f2)?("equal"):("not equal"))."<br />";


For those of you who need to use === with PHP 3, this should do the trick:
function is_identical( $left, $right )
if( phpversion() >= 4 )
return ( $left === $right );
if( ( $left == $right ) && ( gettype( $left ) == gettype( $right ) ) )
return TRUE;
return FALSE;
1 === '1' is the same as is_identical( 1, '1' ).


For converted Perl programmers: use strict comparison operators (===, !==) in place of string comparison operators (eq, ne). Don't use the simple equality operators (==, !=), because ($a == $b) will return TRUE in many situations where ($a eq $b) would return FALSE.
For instance...
"mary" == "fred" is FALSE, but
"+010" == "10.0" is TRUE (!)
In the following examples, none of the strings being compared are identical, but because PHP *can* evaluate them as numbers, it does so, and therefore finds them equal...
echo ("007" == "7" ? "EQUAL" : "not equal");
// Prints: EQUAL
// Surrounding the strings with single quotes (') instead of double
// quotes (") to ensure the contents aren't evaluated, and forcing
// string types has no effect.
echo ( (string)'0001' == (string)'+1.' ? "EQUAL" : "not equal");
// Prints: EQUAL
// Including non-digit characters (like leading spaces, "e", the plus
// or minus sign, period, ...) can still result in this behavior, if
// a string happens to be valid scientific notation.
echo ('  131e-2' == '001.3100' ? "EQUAL" : "not equal");
// Prints: EQUAL
If you're comparing passwords (or anything else for which "near" precision isn't good enough) this confusion could be detrimental. Stick with strict comparisons...
// Same examples as above, using === instead of ==
echo ("007" === "7" ? "EQUAL" : "not equal");
// Prints: not equal
echo ( (string)'0001' === (string)'+1.' ? "EQUAL" : "not equal");
// Prints: not equal
echo ('  131e-2' === '001.3100' ? "EQUAL" : "not equal");
// Prints: not equal


Float values comparation:
if ( (string) $a == (string) $b) {
 print 'a is equal to b';
} else {
 print 'a is not equal to b';


Don't be deceived into thinking that === compares objects for identity, it does not. It does a recusrive comparison which fails if there are recusrive object references involved, and will report as identical two different object instances that happen to merely have the same value.
You can see the stated problem at:
My workaround is php::CompareObjects($a,$b)
# static class to hold methods to encapsulate php deficiencies in various versions
class php {
 # in === on objects in php4 does a dumb recusrive check instead
 function CompareObject(&$a,&$b) {
   $value='Bah! Stupid===';
   while(isset($a->$key)) $key.=rand(0,9);
   if (isset($b->$key)) return FALSE;
   return $result;

02-dec-2004 11:47

Concerning floats: It is simply pointless to compare a float with the value "0.3". The number 0.3 is not exactly representable in binary. Period. So is the number 0.1, and an infinite number of others numbers. Just like 1/3 is not exactly representable in decimal. How would you code the test for your float to be one third? Maybe $myFloat == 0.33333333333   Hmm: you see: Everyone would agree that this test is not accurate.
The test $myFloat == 0.3 is making exactly the same mistake.
So the float which you think should be 0.3 is really something very close to it; if you print it in decimal, the conversion will end up with the closest decimal representation, which may well be "0.3". But "0.3" is also the "right display decimal" for hundreds of float values.
The correct way to "compare" floats is: ( $myFloat - 0.3 ) < $EPSILON where $EPSILON is something like 1e-10, depending on your application. Approximate algorithms are the only right way to treat floats, which are only approximate by themselves.


be REALLY careful when comparing float values. PHP, like most languages, is vunerable to he problems of floating point precision.
Do NOT compare floats directly, and this also means any decimal value at all.
The headaches finding out if $var = 0.3 caused me are unbelievable. even though the stored variable WAS 0.3 it was still ignoring it - this was to do with the internal float not recognising it as 0.3 even though it *displayed* it as 0.3 when echo'd or printed... basically it was stored imprecisly, but not able to display it as such.
I ended up having to compare after multiplying by 10, rounding, and then dividing by 10... rediculous, but sadly the only way I could find to reliably do it. The round seemed to remove the break in the float...
jesus that took me ages to find...

thomas dot oldbury

Be careful when using the ternary operator!
The following will not evaluate to the expected result:
echo "a string that has a " . (true) ? 'true' : 'false' . " condition in. ";
Will print true.
Instead, use this:
echo "a string that has a " . ((true) ? 'true' : 'false') . " condition in. ";
This will evaluate to the expected result: "a string that has a true condition in. "
I hope this helps.


//attention about this case!
if($a=="some string..."){ /* (...) -> true! */ }
if($a==="some string..."){ /* (...) -> false */ }
if($a=="some string..."){ /*(...) -> false */ }
if($a==="some string..."){ /*(...) -> false */ }


$a = "iowjoiwef";
$b = 0;
print ($a == $b); // is 1
print ("$a" == "$b"); // is 0
Now someone mentions the point that
$y = "123";
print (int) $y; // is 123
Why would anyone want "iowjoiwef" to be 0 when casted to int? Why should int take precedence on operator casting when comparing two values, isn't php a string oriented language.. Is it strongly typed? What about operator overloading? Does it offer it? Really? Can we cover up this problem? No?
If you want people making more bugs, I suggest you stick with this form of self deception..
This is bad interpreter design.. You might as well compile PHP.. Because it can't be a valid interpreter..


"Identical to" is faster compared to "equals to." I ran a test script that compared various combinations of strings and integers over a 10000x loop. Sample results:
'foo' v. 'foo' eq: 0.00274
'foo' v. 'foo' id: 0.001671
42 v. 42 eq: 0.00171
42 v. 42 id: 0.001436
'foo' v. 'bar' eq: 0.002589
'foo' v. 'bar' id: 0.001658
42 v. 43 eq: 0.001719
42 v. 43 id: 0.001419
'42' v. 42 eq: 0.00223
'42' v. 42 id: 0.001392
'42' v. 43 eq: 0.002281
'42' v. 43 id: 0.001389

Change Language

Follow Navioo On Twitter
Operator Precedence
Arithmetic Operators
Assignment Operators
Bitwise Operators
Comparison Operators
Error Control Operators
Execution Operators
Incrementing/Decrementing Operators
Logical Operators
String Operators
Array Operators
Type Operators
eXTReMe Tracker