Lines Matching defs:bsd_glob
16 bsd_glob
55 bsd_glob
119 sub bsd_glob {
126 # CORE::glob() (use bsd_glob() instead)
129 goto &bsd_glob;
198 @list = bsd_glob('*.[ch]');
199 $homedir = bsd_glob('~gnat', GLOB_TILDE | GLOB_ERR);
219 File::Glob::bsd_glob() implements the FreeBSD glob(3) routine, which is
221 bsd_glob() takes a mandatory C<pattern> argument, and an optional
226 Since v5.6.0, Perl's CORE::glob() is implemented in terms of bsd_glob().
230 whereas bsd_glob() considers them as one pattern.
232 The POSIX defined flags for bsd_glob() are:
238 Force bsd_glob() to return an error when it encounters a directory it
239 cannot open or read. Ordinarily bsd_glob() continues to find matches.
243 Make bsd_glob() return an error (GLOB_NOSPACE) when the pattern expands
245 limits.h). If your system does not define this constant, bsd_glob() uses
258 makes bsd_glob() treat case differences as not significant.
262 If the pattern does not match any pathname, then bsd_glob() returns a list
269 flag prevents that sorting (speeding up bsd_glob()).
327 bsd_glob() returns a list of matching paths, possibly zero length. If an
344 In the case where bsd_glob() has found some matching paths, but is
348 Note that bsd_glob() deviates from POSIX and FreeBSD glob(3) behaviour
349 by not considering C<ENOENT> and C<ENOTDIR> as errors - bsd_glob() will
361 If you want to use multiple patterns, e.g. C<bsd_glob "a* b*">, you should
362 probably throw them in a set as in C<bsd_glob "{a*,b*}">. This is because
363 the argument to bsd_glob() isn't subjected to parsing by the C shell.