perldata.1

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

.PP
A list value may also be subscripted like a normal array.  You must
put the list in parentheses to avoid ambiguity.  For example:
.PP
.Vb 2
\&    # Stat returns list value.
\&    $time = (stat($file))[8];
\&
\&    # SYNTAX ERROR HERE.
\&    $time = stat($file)[8];  # OOPS, FORGOT PARENTHESES
\&
\&    # Find a hex digit.
\&    $hexdigit = (\*(Aqa\*(Aq,\*(Aqb\*(Aq,\*(Aqc\*(Aq,\*(Aqd\*(Aq,\*(Aqe\*(Aq,\*(Aqf\*(Aq)[$digit\-10];
\&
\&    # A "reverse comma operator".
\&    return (pop(@foo),pop(@foo))[0];
.Ve
.PP
Lists may be assigned to only when each element of the list
is itself legal to assign to:
.PP
.Vb 1
\&    ($a, $b, $c) = (1, 2, 3);
\&
\&    ($map{\*(Aqred\*(Aq}, $map{\*(Aqblue\*(Aq}, $map{\*(Aqgreen\*(Aq}) = (0x00f, 0x0f0, 0xf00);
.Ve
.PP
An exception to this is that you may assign to \f(CW\*(C`undef\*(C'\fR in a list.
This is useful for throwing away some of the return values of a
function:
.PP
.Vb 1
\&    ($dev, $ino, undef, undef, $uid, $gid) = stat($file);
.Ve
.PP
List assignment in scalar context returns the number of elements
produced by the expression on the right side of the assignment:
.PP
.Vb 2
\&    $x = (($foo,$bar) = (3,2,1));       # set $x to 3, not 2
\&    $x = (($foo,$bar) = f());           # set $x to f()\*(Aqs return count
.Ve
.PP
This is handy when you want to do a list assignment in a Boolean
context, because most list functions return a null list when finished,
which when assigned produces a 0, which is interpreted as \s-1FALSE\s0.
.PP
It's also the source of a useful idiom for executing a function or
performing an operation in list context and then counting the number of
return values, by assigning to an empty list and then using that
assignment in scalar context. For example, this code:
.PP
.Vb 1
\&    $count = () = $string =~ /\ed+/g;
.Ve
.PP
will place into \f(CW$count\fR the number of digit groups found in \f(CW$string\fR.
This happens because the pattern match is in list context (since it
is being assigned to the empty list), and will therefore return a list
of all matching parts of the string. The list assignment in scalar
context will translate that into the number of elements (here, the
number of times the pattern matched) and assign that to \f(CW$count\fR. Note
that simply using
.PP
.Vb 1
\&    $count = $string =~ /\ed+/g;
.Ve
.PP
would not have worked, since a pattern match in scalar context will
only return true or false, rather than a count of matches.
.PP
The final element of a list assignment may be an array or a hash:
.PP
.Vb 2
\&    ($a, $b, @rest) = split;
\&    my($a, $b, %rest) = @_;
.Ve
.PP
You can actually put an array or hash anywhere in the list, but the first one
in the list will soak up all the values, and anything after it will become
undefined.  This may be useful in a \fImy()\fR or \fIlocal()\fR.
.PP
A hash can be initialized using a literal list holding pairs of
items to be interpreted as a key and a value:
.PP
.Vb 2
\&    # same as map assignment above
\&    %map = (\*(Aqred\*(Aq,0x00f,\*(Aqblue\*(Aq,0x0f0,\*(Aqgreen\*(Aq,0xf00);
.Ve
.PP
While literal lists and named arrays are often interchangeable, that's
not the case for hashes.  Just because you can subscript a list value like
a normal array does not mean that you can subscript a list value as a
hash.  Likewise, hashes included as parts of other lists (including
parameters lists and return lists from functions) always flatten out into
key/value pairs.  That's why it's good to use references sometimes.
.PP
It is often more readable to use the \f(CW\*(C`=>\*(C'\fR operator between key/value
pairs.  The \f(CW\*(C`=>\*(C'\fR operator is mostly just a more visually distinctive
synonym for a comma, but it also arranges for its left-hand operand to be
interpreted as a string \*(-- if it's a bareword that would be a legal simple
identifier (\f(CW\*(C`=>\*(C'\fR doesn't quote compound identifiers, that contain
double colons). This makes it nice for initializing hashes:
.PP
.Vb 5
\&    %map = (
\&                 red   => 0x00f,
\&                 blue  => 0x0f0,
\&                 green => 0xf00,
\&   );
.Ve
.PP
or for initializing hash references to be used as records:
.PP
.Vb 5
\&    $rec = {
\&                witch => \*(AqMable the Merciless\*(Aq,
\&                cat   => \*(AqFluffy the Ferocious\*(Aq,
\&                date  => \*(Aq10/31/1776\*(Aq,
\&    };
.Ve
.PP
or for using call-by-named-parameter to complicated functions:
.PP
.Vb 7
\&   $field = $query\->radio_group(
\&               name      => \*(Aqgroup_name\*(Aq,
\&               values    => [\*(Aqeenie\*(Aq,\*(Aqmeenie\*(Aq,\*(Aqminie\*(Aq],
\&               default   => \*(Aqmeenie\*(Aq,
\&               linebreak => \*(Aqtrue\*(Aq,
\&               labels    => \e%labels
\&   );
.Ve
.PP
Note that just because a hash is initialized in that order doesn't
mean that it comes out in that order.  See \*(L"sort\*(R" in perlfunc for examples
of how to arrange for an output ordering.
.Sh "Subscripts"
.IX Subsection "Subscripts"
An array is subscripted by specifying a dollar sign (\f(CW\*(C`$\*(C'\fR), then the
name of the array (without the leading \f(CW\*(C`@\*(C'\fR), then the subscript inside
square brackets.  For example:
.PP
.Vb 2
\&    @myarray = (5, 50, 500, 5000);
\&    print "Element Number 2 is", $myarray[2], "\en";
.Ve
.PP
The array indices start with 0. A negative subscript retrieves its 
value from the end.  In our example, \f(CW$myarray[\-1]\fR would have been 
5000, and \f(CW$myarray[\-2]\fR would have been 500.
.PP
Hash subscripts are similar, only instead of square brackets curly brackets
are used. For example:
.PP
.Vb 7
\&    %scientists = 
\&    (
\&        "Newton" => "Isaac",
\&        "Einstein" => "Albert",
\&        "Darwin" => "Charles",
\&        "Feynman" => "Richard",
\&    );
\&
\&    print "Darwin\*(Aqs First Name is ", $scientists{"Darwin"}, "\en";
.Ve
.Sh "Slices"
.IX Xref "slice array, slice hash, slice"
.IX Subsection "Slices"
A common way to access an array or a hash is one scalar element at a
time.  You can also subscript a list to get a single element from it.
.PP
.Vb 3
\&    $whoami = $ENV{"USER"};             # one element from the hash
\&    $parent = $ISA[0];                  # one element from the array
\&    $dir    = (getpwnam("daemon"))[7];  # likewise, but with list
.Ve
.PP
A slice accesses several elements of a list, an array, or a hash
simultaneously using a list of subscripts.  It's more convenient
than writing out the individual elements as a list of separate
scalar values.
.PP
.Vb 4
\&    ($him, $her)   = @folks[0,\-1];              # array slice
\&    @them          = @folks[0 .. 3];            # array slice
\&    ($who, $home)  = @ENV{"USER", "HOME"};      # hash slice
\&    ($uid, $dir)   = (getpwnam("daemon"))[2,7]; # list slice
.Ve
.PP
Since you can assign to a list of variables, you can also assign to
an array or hash slice.
.PP
.Vb 4
\&    @days[3..5]    = qw/Wed Thu Fri/;
\&    @colors{\*(Aqred\*(Aq,\*(Aqblue\*(Aq,\*(Aqgreen\*(Aq} 
\&                   = (0xff0000, 0x0000ff, 0x00ff00);
\&    @folks[0, \-1]  = @folks[\-1, 0];
.Ve
.PP
The previous assignments are exactly equivalent to
.PP
.Vb 4
\&    ($days[3], $days[4], $days[5]) = qw/Wed Thu Fri/;
\&    ($colors{\*(Aqred\*(Aq}, $colors{\*(Aqblue\*(Aq}, $colors{\*(Aqgreen\*(Aq})
\&                   = (0xff0000, 0x0000ff, 0x00ff00);
\&    ($folks[0], $folks[\-1]) = ($folks[\-1], $folks[0]);
.Ve
.PP
Since changing a slice changes the original array or hash that it's
slicing, a \f(CW\*(C`foreach\*(C'\fR construct will alter some\*(--or even all\*(--of the
values of the array or hash.
.PP
.Vb 1
\&    foreach (@array[ 4 .. 10 ]) { s/peter/paul/ } 
\&
\&    foreach (@hash{qw[key1 key2]}) {
\&        s/^\es+//;           # trim leading whitespace
\&        s/\es+$//;           # trim trailing whitespace
\&        s/(\ew+)/\eu\eL$1/g;   # "titlecase" words
\&    }
.Ve
.PP
A slice of an empty list is still an empty list.  Thus:
.PP
.Vb 3
\&    @a = ()[1,0];           # @a has no elements
\&    @b = (@a)[0,1];         # @b has no elements
\&    @c = (0,1)[2,3];        # @c has no elements
.Ve
.PP
But:
.PP
.Vb 2
\&    @a = (1)[1,0];          # @a has two elements
\&    @b = (1,undef)[1,0,2];  # @b has three elements
.Ve
.PP
This makes it easy to write loops that terminate when a null list
is returned:
.PP
.Vb 3
\&    while ( ($home, $user) = (getpwent)[7,0]) {
\&        printf "%\-8s %s\en", $user, $home;
\&    }
.Ve
.PP
As noted earlier in this document, the scalar sense of list assignment
is the number of elements on the right-hand side of the assignment.
The null list contains no elements, so when the password file is
exhausted, the result is 0, not 2.
.PP
If you're confused about why you use an '@' there on a hash slice
instead of a '%', think of it like this.  The type of bracket (square
or curly) governs whether it's an array or a hash being looked at.
On the other hand, the leading symbol ('$' or '@') on the array or
hash indicates whether you are getting back a singular value (a
scalar) or a plural one (a list).
.Sh "Typeglobs and Filehandles"
.IX Xref "typeglob filehandle *"
.IX Subsection "Typeglobs and Filehandles"
Perl uses an internal type called a \fItypeglob\fR to hold an entire
symbol table entry.  The type prefix of a typeglob is a \f(CW\*(C`*\*(C'\fR, because
it represents all types.  This used to be the preferred way to
pass arrays and hashes by reference into a function, but now that
we have real references, this is seldom needed.
.PP
The main use of typeglobs in modern Perl is create symbol table aliases.
This assignment:
.PP
.Vb 1
\&    *this = *that;
.Ve
.PP
makes \f(CW$this\fR an alias for \f(CW$that\fR, \f(CW@this\fR an alias for \f(CW@that\fR, \f(CW%this\fR an alias
for \f(CW%that\fR, &this an alias for &that, etc.  Much safer is to use a reference.
This:
.PP
.Vb 1
\&    local *Here::blue = \e$There::green;
.Ve
.PP
temporarily makes \f(CW$Here::blue\fR an alias for \f(CW$There::green\fR, but doesn't
make \f(CW@Here::blue\fR an alias for \f(CW@There::green\fR, or \f(CW%Here::blue\fR an alias for
\&\f(CW%There::green\fR, etc.  See \*(L"Symbol Tables\*(R" in perlmod for more examples
of this.  Strange though this may seem, this is the basis for the whole
module import/export system.
.PP
Another use for typeglobs is to pass filehandles into a function or
to create new filehandles.  If you need to use a typeglob to save away
a filehandle, do it this way:
.PP
.Vb 1
\&    $fh = *STDOUT;
.Ve
.PP
or perhaps as a real reference, like this:
.PP
.Vb 1
\&    $fh = \e*STDOUT;
.Ve
.PP
See perlsub for examples of using these as indirect filehandles
in functions.
.PP
Typeglobs are also a way to create a local filehandle using the \fIlocal()\fR
operator.  These last until their block is exited, but may be passed back.
For example:
.PP
.Vb 7
\&    sub newopen {
\&        my $path = shift;
\&        local  *FH;  # not my!
\&        open   (FH, $path)          or  return undef;
\&        return *FH;
\&    }
\&    $fh = newopen(\*(Aq/etc/passwd\*(Aq);
.Ve
.PP
Now that we have the \f(CW*foo{THING}\fR notation, typeglobs aren't used as much
for filehandle manipulations, although they're still needed to pass brand
new file and directory handles into or out of functions. That's because
\&\f(CW*HANDLE{IO}\fR only works if \s-1HANDLE\s0 has already been used as a handle.
In other words, \f(CW*FH\fR must be used to create new symbol table entries;
\&\f(CW*foo{THING}\fR cannot.  When in doubt, use \f(CW*FH\fR.
.PP
All functions that are capable of creating filehandles (\fIopen()\fR,
\&\fIopendir()\fR, \fIpipe()\fR, \fIsocketpair()\fR, \fIsysopen()\fR, \fIsocket()\fR, and \fIaccept()\fR)
automatically create an anonymous filehandle if the handle passed to
them is an uninitialized scalar variable. This allows the constructs
such as \f(CW\*(C`open(my $fh, ...)\*(C'\fR and \f(CW\*(C`open(local $fh,...)\*(C'\fR to be used to
create filehandles that will conveniently be closed automatically when
the scope ends, provided there are no other references to them. This
largely eliminates the need for typeglobs when opening filehandles
that must be passed around, as in the following example:
.PP
.Vb 5
\&    sub myopen {
\&        open my $fh, "@_"
\&             or die "Can\*(Aqt open \*(Aq@_\*(Aq: $!";
\&        return $fh;
\&    }
\&
\&    {
\&        my $f = myopen("</etc/motd");
\&        print <$f>;
\&        # $f implicitly closed here
\&    }
.Ve
.PP
Note that if an initialized scalar variable is used instead the
result is different: \f(CW\*(C`my $fh=\*(Aqzzz\*(Aq; open($fh, ...)\*(C'\fR is equivalent
to \f(CW\*(C`open( *{\*(Aqzzz\*(Aq}, ...)\*(C'\fR.
\&\f(CW\*(C`use strict \*(Aqrefs\*(Aq\*(C'\fR forbids such practice.
.PP
Another way to create anonymous filehandles is with the Symbol
module or with the IO::Handle module and its ilk.  These modules
have the advantage of not hiding different types of the same name
during the \fIlocal()\fR.  See the bottom of \*(L"\fIopen()\fR\*(R" in perlfunc for an
example.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
See perlvar for a description of Perl's built-in variables and
a discussion of legal variable names.  See perlref, perlsub,
and \*(L"Symbol Tables\*(R" in perlmod for more discussion on typeglobs and
the \f(CW*foo{THING}\fR syntax.