Comment 3 for bug 1067724

I was unable to replicate the error in 1.5_STABLE. From looking at the glob() documentation ( http://php.net/glob ) I note that the glob function is meant to just return an empty array if it can't find anything, or false on error. So, it's possible that some environments may be causing glob to error out, and the code isn't handling that properly.

There's also this: "Note: On some systems it is impossible to distinguish between empty match and an error. "

It's unclear whether that means that an empty match returns false, or whether it means that an error returns an empty array. But the return value that Jan noted (nearly 1 year ago today) is what you get when you cast boolean false as an array:

var_dump((array) false);

 array(1) {
   [0]=>
   bool(false)
 }