file::glob.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

.el .IP "\f(CWGLOB_ERR\fR" 4
.IX Item "GLOB_ERR"
Force \fIbsd_glob()\fR to return an error when it encounters a directory it
cannot open or read.  Ordinarily \fIbsd_glob()\fR continues to find matches.
.ie n .IP """GLOB_LIMIT""" 4
.el .IP "\f(CWGLOB_LIMIT\fR" 4
.IX Item "GLOB_LIMIT"
Make \fIbsd_glob()\fR return an error (\s-1GLOB_NOSPACE\s0) when the pattern expands
to a size bigger than the system constant \f(CW\*(C`ARG_MAX\*(C'\fR (usually found in
limits.h).  If your system does not define this constant, \fIbsd_glob()\fR uses
\&\f(CW\*(C`sysconf(_SC_ARG_MAX)\*(C'\fR or \f(CW\*(C`_POSIX_ARG_MAX\*(C'\fR where available (in that
order).  You can inspect these values using the standard \f(CW\*(C`POSIX\*(C'\fR
extension.
.ie n .IP """GLOB_MARK""" 4
.el .IP "\f(CWGLOB_MARK\fR" 4
.IX Item "GLOB_MARK"
Each pathname that is a directory that matches the pattern has a slash
appended.
.ie n .IP """GLOB_NOCASE""" 4
.el .IP "\f(CWGLOB_NOCASE\fR" 4
.IX Item "GLOB_NOCASE"
By default, file names are assumed to be case sensitive; this flag
makes \fIbsd_glob()\fR treat case differences as not significant.
.ie n .IP """GLOB_NOCHECK""" 4
.el .IP "\f(CWGLOB_NOCHECK\fR" 4
.IX Item "GLOB_NOCHECK"
If the pattern does not match any pathname, then \fIbsd_glob()\fR returns a list
consisting of only the pattern.  If \f(CW\*(C`GLOB_QUOTE\*(C'\fR is set, its effect
is present in the pattern returned.
.ie n .IP """GLOB_NOSORT""" 4
.el .IP "\f(CWGLOB_NOSORT\fR" 4
.IX Item "GLOB_NOSORT"
By default, the pathnames are sorted in ascending \s-1ASCII\s0 order; this
flag prevents that sorting (speeding up \fIbsd_glob()\fR).
.PP
The FreeBSD extensions to the \s-1POSIX\s0 standard are the following flags:
.ie n .IP """GLOB_BRACE""" 4
.el .IP "\f(CWGLOB_BRACE\fR" 4
.IX Item "GLOB_BRACE"
Pre-process the string to expand \f(CW\*(C`{pat,pat,...}\*(C'\fR strings like \fIcsh\fR\|(1).
The pattern '{}' is left unexpanded for historical reasons (and \fIcsh\fR\|(1)
does the same thing to ease typing of \fIfind\fR\|(1) patterns).
.ie n .IP """GLOB_NOMAGIC""" 4
.el .IP "\f(CWGLOB_NOMAGIC\fR" 4
.IX Item "GLOB_NOMAGIC"
Same as \f(CW\*(C`GLOB_NOCHECK\*(C'\fR but it only returns the pattern if it does not
contain any of the special characters \*(L"*\*(R", \*(L"?\*(R" or \*(L"[\*(R".  \f(CW\*(C`NOMAGIC\*(C'\fR is
provided to simplify implementing the historic \fIcsh\fR\|(1) globbing
behaviour and should probably not be used anywhere else.
.ie n .IP """GLOB_QUOTE""" 4
.el .IP "\f(CWGLOB_QUOTE\fR" 4
.IX Item "GLOB_QUOTE"
Use the backslash ('\e') character for quoting: every occurrence of a
backslash followed by a character in the pattern is replaced by that
character, avoiding any special interpretation of the character.
(But see below for exceptions on \s-1DOSISH\s0 systems).
.ie n .IP """GLOB_TILDE""" 4
.el .IP "\f(CWGLOB_TILDE\fR" 4
.IX Item "GLOB_TILDE"
Expand patterns that start with '~' to user name home directories.
.ie n .IP """GLOB_CSH""" 4
.el .IP "\f(CWGLOB_CSH\fR" 4
.IX Item "GLOB_CSH"
For convenience, \f(CW\*(C`GLOB_CSH\*(C'\fR is a synonym for
\&\f(CW\*(C`GLOB_BRACE | GLOB_NOMAGIC | GLOB_QUOTE | GLOB_TILDE | GLOB_ALPHASORT\*(C'\fR.
.PP
The \s-1POSIX\s0 provided \f(CW\*(C`GLOB_APPEND\*(C'\fR, \f(CW\*(C`GLOB_DOOFFS\*(C'\fR, and the FreeBSD
extensions \f(CW\*(C`GLOB_ALTDIRFUNC\*(C'\fR, and \f(CW\*(C`GLOB_MAGCHAR\*(C'\fR flags have not been
implemented in the Perl version because they involve more complex
interaction with the underlying C structures.
.PP
The following flag has been added in the Perl implementation for
csh compatibility:
.ie n .IP """GLOB_ALPHASORT""" 4
.el .IP "\f(CWGLOB_ALPHASORT\fR" 4
.IX Item "GLOB_ALPHASORT"
If \f(CW\*(C`GLOB_NOSORT\*(C'\fR is not in effect, sort filenames is alphabetical
order (case does not matter) rather than in \s-1ASCII\s0 order.
.SH "DIAGNOSTICS"
.IX Header "DIAGNOSTICS"
\&\fIbsd_glob()\fR returns a list of matching paths, possibly zero length.  If an
error occurred, &File::Glob::GLOB_ERROR will be non-zero and \f(CW$!\fR will be
set.  &File::Glob::GLOB_ERROR is guaranteed to be zero if no error occurred,
or one of the following values otherwise:
.ie n .IP """GLOB_NOSPACE""" 4
.el .IP "\f(CWGLOB_NOSPACE\fR" 4
.IX Item "GLOB_NOSPACE"
An attempt to allocate memory failed.
.ie n .IP """GLOB_ABEND""" 4
.el .IP "\f(CWGLOB_ABEND\fR" 4
.IX Item "GLOB_ABEND"
The glob was stopped because an error was encountered.
.PP
In the case where \fIbsd_glob()\fR has found some matching paths, but is
interrupted by an error, it will return a list of filenames \fBand\fR
set &File::Glob::ERROR.
.PP
Note that \fIbsd_glob()\fR deviates from \s-1POSIX\s0 and FreeBSD \fIglob\fR\|(3) behaviour
by not considering \f(CW\*(C`ENOENT\*(C'\fR and \f(CW\*(C`ENOTDIR\*(C'\fR as errors \- \fIbsd_glob()\fR will
continue processing despite those errors, unless the \f(CW\*(C`GLOB_ERR\*(C'\fR flag is
set.
.PP
Be aware that all filenames returned from File::Glob are tainted.
.SH "NOTES"
.IX Header "NOTES"
.IP "\(bu" 4
If you want to use multiple patterns, e.g. \f(CW\*(C`bsd_glob("a* b*")\*(C'\fR, you should
probably throw them in a set as in \f(CW\*(C`bsd_glob("{a*,b*}")\*(C'\fR.  This is because
the argument to \fIbsd_glob()\fR isn't subjected to parsing by the C shell.
Remember that you can use a backslash to escape things.
.IP "\(bu" 4
On \s-1DOSISH\s0 systems, backslash is a valid directory separator character.
In this case, use of backslash as a quoting character (via \s-1GLOB_QUOTE\s0)
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 \*(L"normal practice\*(R" on these systems. As a concession to user
expectation, therefore, backslashes (under \s-1GLOB_QUOTE\s0) only quote the
glob metacharacters '[', ']', '{', '}', '\-', '~', and backslash itself.
All other backslashes are passed through unchanged.
.IP "\(bu" 4
Win32 users should use the real slash.  If you really want to use
backslashes, consider using Sarathy's File::DosGlob, which comes with
the standard Perl distribution.
.IP "\(bu" 4
Mac \s-1OS\s0 (Classic) users should note a few differences. Since
Mac \s-1OS\s0 is not Unix, when the glob code encounters a tilde glob (e.g.
~user) and the \f(CW\*(C`GLOB_TILDE\*(C'\fR flag is used, it simply returns that
pattern without doing any expansion.
.Sp
Glob on Mac \s-1OS\s0 is case-insensitive by default (if you don't use any
flags). If you specify any flags at all and still want glob
to be case-insensitive, you must include \f(CW\*(C`GLOB_NOCASE\*(C'\fR in the flags.
.Sp
The path separator is ':' (aka colon), not '/' (aka slash). Mac \s-1OS\s0 users
should be careful about specifying relative pathnames. While a full path
always begins with a volume name, a relative pathname should always
begin with a ':'.  If specifying a volume name only, a trailing ':' is
required.
.Sp
The specification of pathnames in glob patterns adheres to the usual Mac
\&\s-1OS\s0 conventions: The path separator is a colon ':', not a slash '/'. A
full path always begins with a volume name. A relative pathname on Mac
\&\s-1OS\s0 must always begin with a ':', except when specifying a file or
directory name in the current working directory, where the leading colon
is optional. If specifying a volume name only, a trailing ':' is
required. Due to these rules, a glob like <*:> will find all
mounted volumes, while a glob like <*> or <:*> will find
all files and directories in the current directory.
.Sp
Note that updirs in the glob pattern are resolved before the matching begins,
i.e. a pattern like \*(L"*HD:t?p::a*\*(R" will be matched as \*(L"*HD:a*\*(R". Note also,
that a single trailing ':' in the pattern is ignored (unless it's a volume
name pattern like \*(L"*HD:\*(R"), i.e. a glob like <:*:> will find both
directories \fIand\fR files (and not, as one might expect, only directories).
You can, however, use the \f(CW\*(C`GLOB_MARK\*(C'\fR flag to distinguish (without a file
test) directory names from file names.
.Sp
If the \f(CW\*(C`GLOB_MARK\*(C'\fR flag is set, all directory paths will have a ':' appended.
Since a directory like 'lib:' is \fInot\fR a valid \fIrelative\fR path on Mac \s-1OS\s0,
both a leading and a trailing colon will be added, when the directory name in
question doesn't contain any colons (e.g. 'lib' becomes ':lib:').
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\*(L"glob\*(R" in perlfunc, \fIglob\fR\|(3)
.SH "AUTHOR"
.IX Header "AUTHOR"
The Perl interface was written by Nathan Torkington <[e-mail]>,
and is released under the artistic license.  Further modifications were
made by Greg Bacon <[e-mail]>, Gurusamy Sarathy
<[e-mail]>, and Thomas Wegner
<[e-mail]>.  The C glob code has the
following copyright:
.PP
.Vb 2
\&    Copyright (c) 1989, 1993 The Regents of the University of California.
\&    All rights reserved.
\&
\&    This code is derived from software contributed to Berkeley by
\&    Guido van Rossum.
\&
\&    Redistribution and use in source and binary forms, with or without
\&    modification, are permitted provided that the following conditions
\&    are met:
\&
\&    1. Redistributions of source code must retain the above copyright
\&       notice, this list of conditions and the following disclaimer.
\&    2. Redistributions in binary form must reproduce the above copyright
\&       notice, this list of conditions and the following disclaimer in the
\&       documentation and/or other materials provided with the distribution.
\&    3. Neither the name of the University nor the names of its contributors
\&       may be used to endorse or promote products derived from this software
\&       without specific prior written permission.
\&
\&    THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS \`\`AS IS\*(Aq\*(Aq AND
\&    ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
\&    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
\&    ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
\&    FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
\&    DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
\&    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
\&    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
\&    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
\&    OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
\&    SUCH DAMAGE.
.Ve