note 58355 added to language.types.boolean

The === and !== are not fully documented in either the Comparison Operator or Booleans type sections. They are talked about a bit more in the sections on strpos() and array_search() but they 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. This refers only to the use of === and !== with functions like strpos() and array_search() which may a needle at character 0 in a string or element 0 in an array. Because the 0 returned by the function evaluates to == 'false' === and !== are used. You can say <?php if ( strpos($needle,$haystack) !== false ) { print "found it\n"; } ?> and you can say <?php if ( strpos($needle,$haystack) === false ) { print "didn't find it\n"; } ?> but you cannot say <?php if ( strpos($needle,$haystack) === true ) { print "found it \n"; } ?> nor can you say <?php if ( strpos($needle,$haystack) !== true ) { print "didn't find it\n"; } ?> This is because strpos() and array_search do not return 'true' when successful and the numbers they return do not evaluate to === true. So you cannot use 'true' in any way with these functions. I frequently find myself adding string elements to an array as I find them and using the growing array as my record of what has already been done such as <?php if ( array_search($needle,$haystack) !== false ) { print "done one of those already\n"; } ?> or <?php if ( array_search($needle,$haystack) === false ) { print "got a new one\n"; array_push($haystack,$needle) } ?> The more natural way to say this would have been the other way around: <?php if ( array_search($needle,$haystack) === true ) { print "done one of those already\n"; } ?> or <?php if ( array_search($needle,$haystack) !== true ) { print "got a new one\n"; array_push($haystack,$needle) } ?> because you don't go around saying, "if this is not false", you say "if this is true". But that won't work. Now I've had it explained to me it makes sense that the function doesn't return 'true' because it returns a number value instead. And given that === checks the type you can't have the number evaluate to '=== true'. But the result for the user of PHP is counter-intuitive and so deserves specific documenting. ---- Manual Page -- http://www.php.net/manual/en/language.types.boolean.php Edit -- http://master.php.net/manage/user-notes.php?action=edit+58355 Delete: added to the manual -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=added+to+the+manual Delete: bad code -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=bad+code Delete: spam -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=spam Delete: useless -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=useless Delete: non-english -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=non-english Delete: already in docs -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes&reason=already+in+docs Delete: other reasons -- http://master.php.net/manage/user-notes.php?action=delete+58355&report=yes Reject -- http://master.php.net/manage/user-notes.php?action=reject+58355&report=yes Search -- http://master.php.net/manage/user-notes.php