Re: bug #47358 -- unexpected behaviour

hi, Thanks for the headup! I added a comment and attached a patch (against 5.4) to fix this problem, let me know how it works. I will apply to all branches later. On Sun, Oct 9, 2011 at 5:40 PM, Harald Lapp <harald.lapp@gmail.com> wrote: > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org