The glob was stopped because an error was encountered.
<P></P></DL>
<P>In the case where <A HREF="../../lib/Pod/perlfunc.html#item_glob"><CODE>glob()</CODE></A> has found some matching paths, but is
interrupted by an error, <A HREF="../../lib/Pod/perlfunc.html#item_glob"><CODE>glob()</CODE></A> will return a list of filenames <STRONG>and</STRONG>
set &File::Glob::ERROR.</P>
<P>Note that <A HREF="../../lib/Pod/perlfunc.html#item_glob"><CODE>glob()</CODE></A> deviates from POSIX and FreeBSD <A HREF="../../lib/Pod/perlfunc.html#item_glob"><CODE>glob(3)</CODE></A> behaviour by
not considering <CODE>ENOENT</CODE> and <CODE>ENOTDIR</CODE> as errors - <A HREF="../../lib/Pod/perlfunc.html#item_glob"><CODE>glob()</CODE></A> will
continue processing despite those errors, unless the <A HREF="#item_GLOB_ERR"><CODE>GLOB_ERR</CODE></A> flag is
set.</P>
<P>Be aware that all filenames returned from File::Glob are tainted.</P>
<P>
<HR>
<H1><A NAME="notes">NOTES</A></H1>
<UL>
<LI>
If you want to use multiple patterns, e.g. <CODE>glob "a* b*"</CODE>, you should
probably throw them in a set as in <CODE>glob "{a*,b*}</CODE>. This is because
the argument to glob isn't subjected to parsing by the C shell. Remember
that you can use a backslash to escape things.
<P></P>
<LI>
On DOSISH systems, backslash is a valid directory separator character.
In this case, use of backslash as a quoting character (via GLOB_QUOTE)
interferes with the use of backslash as a directory separator. The
best (simplest, most portable) solution is to use forward slashes for
directory separators, and backslashes for quoting. However, this does
not match ``normal practice'' on these systems. As a concession to user
expectation, therefore, backslashes (under GLOB_QUOTE) only quote the
