|
|
|
perlipc(1) -- Perl interprocess communication (signals, fifos, pipes, safe subprocesses, sockets, and semaphores)
|
|
Perl uses a simple signal handling model: the %SIG hash contains names or references of user-installed signal handlers. These handlers will be called with an argument which is the name of the signal that triggered it. A signal may be generated intentionally from a particular keyboard sequence like control-C or control-Z, sent to you from another process, or triggered automatically by the kernel when special events transpire, like a child process exiting, your process running out of stack space, ... |
|
perllocale(1) -- Perl locale handling (internationalization and localization)
|
|
If Perl applications are to be able to understand and present your data correctly according a locale of your choice, all of the following must be true: o Your operating system must support the locale system. If it does, you should find that the setlocale() function is a documented part of its C library. o Definitions for the locales which you use must be installed. You, or your system administrator, must make sure that this is the case. The available locales, the location in which they are kept,... |
|
|
perllol(1) -- Manipulating Lists of Lists in Perl
|
|
Now it's time to print your data structure out. How are you going to do that? Well, if you want only one of the elements, it's trivial: print $LoL[0][0]; If you want to print the whole thing, though, you can't say print @LoL; # WRONG because you'll get just references listed, and perl will never automatically dereference things for you. Instead, you have to roll yourself a loop or two. This prints the whole structure, using the shell-style for() construct to loop across the outer set of subs... |
|
perlmod(1) -- Perl modules (packages and symbol tables)
|
|
See the perlmodlib manpage for general style issues related to building Perl modules and classes as well as descriptions of the standard library and CPAN, the Exporter manpage for how Perl's standard import/export mechanism works, the perltoot manpage for an in-depth tutorial on creating classes, the perlobj manpage for a hard-core reference document on objects, and the perlsub manpage for an explanation of functions and scoping. PPPPaaaaggggeeee 8888... |
|
perlmodlib(1) -- constructing new Perl modules and finding existing ones
|
|
CPAN stands for the Comprehensive Perl Archive Network. This is a globally replicated collection of all known Perl materials, including hundreds of unbundled modules. Here are the major categories of modules: o Language Extensions and Documentation Tools o Development Support o Operating System Interfaces o Networking, Device Control (modems) and InterProcess Communication o Data Types and Data Type Utilities o Database Interfaces o User Interfaces o Interfaces to / Emulations of Other Programmi... |
|
perlobj(1) -- Perl objects
|
|
A kinder, gentler tutorial on object-oriented programming in Perl can be found in the perltoot manpage. You should also check out the perlbot manpage for other object tricks, traps, and tips, as well as the perlmodlib manpage for some style guides on constructing both modules and classes. Page 9 PERLOBJ(1) PERLOBJ(1) PPPPaaaaggggeeee 11110000 |
|
perlop(1) -- Perl operators and precedence
|
|
Terms and List Operators (Leftward) A TERM has the highest precedence in Perl. They includes variables, quote and quote-like operators, any expression in parentheses, and any function whose arguments are parenthesized. Actually, there aren't really functions in this sense, just list operators and unary operators behaving as functions because you put parentheses around the arguments. These are all documented in the perlfunc manpage. If any list operator (print(), etc.) or any unary operator (chd... |
|
perlpod(1) -- plain old documentation
|
|
You can embed pod documentation in your Perl scripts. Start your documentation with a "=head1" command at the beginning, and end it with a "=cut" command. Perl will ignore the pod text. See any of the supplied library modules for examples. If you're going to put your pods at the end of the file, and you're using an __END__ or __DATA__ cut mark, make sure to put an empty line there before the first pod directive. __END__ =head1 NAME modern - I am a modern module If you had not had that empt... |
|
perlre(1) -- Perl regular expressions
|
|
|
|
perlref(1) -- Perl references and nested data structures
|
|
You may not (usefully) use a reference as the key to a hash. It will be converted into a string: $x{ \$a } = $a; If you try to dereference the key, it won't do a hard dereference, and you won't accomplish what you're attempting. You might want to do something more like $r = \@a; $x{ $r } = $r; And then at least you can use the values(), which will be real refs, instead of the keys(), which won't.... |
|
perlrun(1) -- how to execute the Perl interpreter
|
|
Upon startup, Perl looks for your script in one of the following places: 1. Specified line by line via -e switches on the command line. 2. Contained in the file specified by the first filename on the command line. (Note that systems supporting the #! notation invoke interpreters this way.) 3. Passed in implicitly via standard input. This works only if there are no filename arguments--to pass arguments to a STDIN script you must explicitly specify a "-" for the script name. With methods 2 and 3... |
|
perlsec(1) -- Perl security
|
|
|
|
perlstyle(1) -- Perl style guide
|
|
|
|
perlsub(1) -- Perl subroutines
|
|
Like many languages, Perl provides for user-defined subroutines. These may be located anywhere in the main program, loaded in from other files via the do, require, or use keywords, or even generated on the fly using eval or anonymous subroutines (closures). You can even call a function indirectly using a variable containing its name or a CODE reference to it, as in $var = \&function. The Perl model for function call and return values is simple: all functions are passed as parameters one single ... |
|
perlsyn(1) -- Perl syntax
|
|
|
