bug #47358 -- unexpected behaviour
| From: | Harald Lapp | Date: | Sun, 09 Oct 2011 15:40:24 +0000 |
| Subject: | bug #47358 -- unexpected behaviour | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-55762@lists.php.net to get a copy of this message | ||
hi,
could someone please enlighten me, why bug #47358
http://bugs.php.net/bug.php?id=47358 was closed
as "bogus"? the bug was
reported for 5.2.9 but applies to 5.3.x and 5.4.x as well. i can't see, why
glob should return 'false' if the search pattern does not match, even
though if the directory being searched in is valid compared to the
open_basedir settings:
php -r "var_dump(glob('/tmp/*.php'));"
array(0) {
}
vs.
php -d "open_basedir=/tmp/" -r "var_dump(glob('/tmp/*.php'));"
bool(false)
i fail to understand, why the second one is expected behaviour.
i stumbled over this when playing with the fat free framework, which uses
quite a lot of glob statements in its autoloader, in a shared hosting
environment.
thanks in advance,
harald