Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

PHP in_array() / array_search() odd behaviour

I have found some odd behaviour while I was using the PHP function in_array(). I have an array like this:

$arr = [TRUE, "some string", "something else"];

Now if I want to check if "test" is in the array it is clearly not, but in_array() still returns TRUE, why is that?

$result = in_array("test", $arr);
var_dump($result);  //Output: bool(true)

The same thing happens when using array_search():

$result = array_search("test", $arr);
var_dump($result);  //Output: int(0)

I thought maybe that the value TRUE in the array was automatically causing the function to return TRUE for every result without checking the rest of the array, but I couldn't find any documentation that would suggest that very odd functionality.

like image 959
animuson Avatar asked Apr 29 '10 17:04

animuson


People also ask

What is the difference between in_array and Array_search?

The main difference between both the functions is that array_search() usually returns either key or index whereas in_array() returns TRUE or FALSE according to match found in search. Value: It specifies the value that needs to be searched in an array.

What is the use of in_array () function?

The in_array() function is an inbuilt function in PHP that is used to check whether a given value exists in an array or not. It returns TRUE if the given value is found in the given array, and FALSE otherwise.

Does in_array work for associative array?

in_array() function is utilized to determine if specific value exists in an array. It works fine for one dimensional numeric and associative arrays.


2 Answers

This behaviour of the function in_array() and array_search() is not a bug, but instead well documented behaviour.

Both functions have a 3rd optional parameter called $strict which by default is FALSE:

bool in_array ( mixed $needle , array $haystack [, bool $strict = FALSE ] )

mixed array_search ( mixed $needle , array $haystack [, bool $strict = false ] )

Now what that means is that by default both functions use loosely(==) comparison to compare the values. So they only check if the values are the same after PHP type juggling and without checking the type. Because of that in your example TRUE == "any none emtpy string" evaluates to TRUE.

So by setting the 3rd parameter to TRUE while calling the function you say that PHP should use strict(===) comparison and it should check value AND type of the values while comparing.

See this as a reference: How do the PHP equality (== double equals) and identity (=== triple equals) comparison operators differ?

like image 79
Fletcher Moore Avatar answered Sep 27 '22 20:09

Fletcher Moore


You are right, the boolean can indeed cause this. Set the strict flag in the in_array function, this way also the type of the element is checked (basically the same as using ===):

if (in_array("username", $results, true)) // do something
if (in_array("password", $results, true)) // do something
if (in_array("birthday", $results, true)) // do something
like image 36
Felix Kling Avatar answered Sep 27 '22 20:09

Felix Kling