X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperl.pod;h=f90696e8a8b037694d52fb5d2c590c9dbcf3ee14;hb=9f1b1f2d9ab55954ee07a14c4ab04bd3dd1f99d5;hp=2c1dde20399915fbac46536401ea35ac71020482;hpb=68dc074516a6859e3424b48d1647bcb08b1a1a7d;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perl.pod b/pod/perl.pod index 2c1dde2..f90696e 100644 --- a/pod/perl.pod +++ b/pod/perl.pod @@ -4,75 +4,116 @@ perl - Practical Extraction and Report Language =head1 SYNOPSIS -B S<[ B<-sTuU> ]> - S<[ B<-hv> ] [ B<-V>[:I] ]> - S<[ B<-cw> ] [ B<-d>[:I] ] [ B<-D>[I] ]> - S<[ B<-pna> ] [ B<-F>I ] [ B<-l>[I] ] [ B<-0>[I] ]> - S<[ B<-I>I ] [ B<-m>[B<->]I ] [ B<-M>[B<->]I<'module...'> ]> - S<[ B<-P> ]> - S<[ B<-S> ]> - S<[ B<-x>[I] ]> - S<[ B<-i>[I] ]> - S<[ B<-e> I<'command'> ] [ B<--> ] [ I ] [ I ]...> - -For ease of access, the Perl manual has been split up into a number -of sections: - - perl Perl overview (this section) - perldelta Perl changes since previous version - perlfaq Perl frequently asked questions - - perldata Perl data structures - perlsyn Perl syntax - perlop Perl operators and precedence - perlre Perl regular expressions - perlrun Perl execution and options - perlfunc Perl builtin functions - perlvar Perl predefined variables - perlsub Perl subroutines - perlmod Perl modules - perlform Perl formats - perllocale Perl locale support - - perlref Perl references - perldsc Perl data structures intro - perllol Perl data structures: lists of lists - perltoot Perl OO tutorial - perlobj Perl objects - perltie Perl objects hidden behind simple variables - perlbot Perl OO tricks and examples - perlipc Perl interprocess communication - - perldebug Perl debugging - perldiag Perl diagnostic messages - perlsec Perl security - perltrap Perl traps for the unwary - perlstyle Perl style guide - - perlpod Perl plain old documentation - perlbook Perl book information - - perlembed Perl how to embed perl in your C or C++ app - perlapio Perl internal IO abstraction interface - perlxs Perl XS application programming interface - perlxstut Perl XS tutorial - perlguts Perl internal functions for those doing extensions - perlcall Perl calling conventions from C +B S<[ B<-sTuU> ]> S<[ B<-hv> ] [ B<-V>[:I] ]> + S<[ B<-cw> ] [ B<-d>[:I] ] [ B<-D>[I] ]> + S<[ B<-pna> ] [ B<-F>I ] [ B<-l>[I] ] [ B<-0>[I] ]> + S<[ B<-I>I ] [ B<-m>[B<->]I ] [ B<-M>[B<->]I<'module...'> ]> + S<[ B<-P> ]> S<[ B<-S> ]> S<[ B<-x>[I] ]> + S<[ B<-i>[I] ]> S<[ B<-e> I<'command'> ] + [ B<--> ] [ I ] [ I ]...> + +For ease of access, the Perl manual has been split up into several +sections: + + perl Perl overview (this section) + perldelta Perl changes since previous version + perl5005delta Perl changes in version 5.005 + perl5004delta Perl changes in version 5.004 + perlfaq Perl frequently asked questions + perltoc Perl documentation table of contents + + perldata Perl data structures + perlsyn Perl syntax + perlop Perl operators and precedence + perlre Perl regular expressions + perlrun Perl execution and options + perlfunc Perl builtin functions + perlopentut Perl open() tutorial + perlvar Perl predefined variables + perlsub Perl subroutines + perlmod Perl modules: how they work + perlmodlib Perl modules: how to write and use + perlmodinstall Perl modules: how to install from CPAN + perlform Perl formats + perlunicode Perl unicode support + perllocale Perl locale support + + perlreftut Perl references short introduction + perlref Perl references, the rest of the story + perldsc Perl data structures intro + perllol Perl data structures: arrays of arrays + perlboot Perl OO tutorial for beginners + perltoot Perl OO tutorial, part 1 + perltootc Perl OO tutorial, part 2 + perlobj Perl objects + perltie Perl objects hidden behind simple variables + perlbot Perl OO tricks and examples + perlipc Perl interprocess communication + perlfork Perl fork() information + perlthrtut Perl threads tutorial + perllexwarn Perl warnings and their control + perlfilter Perl source filters + perldbmfilter Perl DBM filters + + perlcompile Perl compiler suite intro + perldebug Perl debugging + perldiag Perl diagnostic messages + perlnumber Perl number semantics + perlsec Perl security + perltrap Perl traps for the unwary + perlport Perl portability guide + perlstyle Perl style guide + + perlpod Perl plain old documentation + perlbook Perl book information + + perlembed Perl ways to embed perl in your C or C++ application + perlapio Perl internal IO abstraction interface + perlxs Perl XS application programming interface + perlxstut Perl XS tutorial + perlguts Perl internal functions for those doing extensions + perlcall Perl calling conventions from C + perlapi Perl API listing (autogenerated) + perlintern Perl internal functions (autogenerated) + + perltodo Perl things to do + perlhack Perl hackers guide + perlhist Perl history records + + perlamiga Perl notes for Amiga + perlcygwin Perl notes for Cygwin + perldos Perl notes for DOS + perlhpux Perl notes for HP-UX + perlos2 Perl notes for OS/2 + perlos390 Perl notes for OS/390 + perlvms Perl notes for VMS + perlwin32 Perl notes for Windows (If you're intending to read these straight through for the first time, the suggested order will tend to reduce the number of forward references.) -Additional documentation for Perl modules is available in the -F directory. Some of this is distributed standard with -Perl, but you'll also find third-party modules there. You should be able -to view this with your man(1) program by including the proper directories -in the appropriate start-up files. To find out where these are, type: +By default, the manpages listed above are installed in the +F directory. + +Extensive additional documentation for Perl modules is available. The +default configuration for perl will place this additional documentation +in the F directory (or else in the F +subdirectory of the Perl library directory). Some of this additional +documentation is distributed standard with Perl, but you'll also find +documentation for third-party modules there. + +You should be able to view Perl's documentation with your man(1) +program by including the proper directories in the appropriate start-up +files, or in the MANPATH environment variable. To find out where the +configuration has installed the manpages, type: perl -V:man.dir -If the directories were F and F, -you would need to add only F to your MANPATH. If -they are different, you'll have to add both stems. +If the directories have a common stem, such as F +and F, you need only to add that stem +(F) to your man(1) configuration files or your MANPATH +environment variable. If they do not share a stem, you'll have to add +both stems. If that doesn't work for some reason, you can still use the supplied F script to view module information. You might @@ -95,17 +136,17 @@ Perl combines (in the author's opinion, anyway) some of the best features of C, B, B, and B, so people familiar with those languages should have little difficulty with it. (Language historians will also note some vestiges of B, Pascal, and even -BASIC-PLUS.) Expression syntax corresponds quite closely to C +BASIC-PLUS.) Expression syntax corresponds closely to C expression syntax. Unlike most Unix utilities, Perl does not arbitrarily limit the size of your data--if you've got the memory, Perl can slurp in your whole file as a single string. Recursion is of -unlimited depth. And the tables used by hashes (previously called +unlimited depth. And the tables used by hashes (sometimes called "associative arrays") grow as necessary to prevent degraded -performance. Perl uses sophisticated pattern matching techniques to -scan large amounts of data very quickly. Although optimized for +performance. Perl can use sophisticated pattern matching techniques to +scan large amounts of data quickly. Although optimized for scanning text, Perl can also deal with binary data, and can make dbm files look like hashes. Setuid Perl scripts are safer than C programs -through a dataflow tracing mechanism which prevents many stupid +through a dataflow tracing mechanism that prevents many stupid security holes. If you have a problem that would ordinarily use B or B or @@ -116,140 +157,251 @@ scripts into Perl scripts. But wait, there's more... -Perl version 5 is nearly a complete rewrite, and provides -the following additional benefits: - -=over 5 - -=item * Many usability enhancements +Begun in 1993 (see L), Perl version 5 is nearly a complete +rewrite that provides the following additional benefits: -It is now possible to write much more readable Perl code (even within -regular expressions). Formerly cryptic variable names can be replaced -by mnemonic identifiers. Error messages are more informative, and the -optional warnings will catch many of the mistakes a novice might make. -This cannot be stressed enough. Whenever you get mysterious behavior, -try the B<-w> switch!!! Whenever you don't get mysterious behavior, -try using B<-w> anyway. +=over -=item * Simplified grammar +=item * modularity and reusability using innumerable modules -The new yacc grammar is one half the size of the old one. Many of the -arbitrary grammar rules have been regularized. The number of reserved -words has been cut by 2/3. Despite this, nearly all old Perl scripts -will continue to work unchanged. +Described in L, L, and L. -=item * Lexical scoping +=item * embeddable and extensible -Perl variables may now be declared within a lexical scope, like "auto" -variables in C. Not only is this more efficient, but it contributes -to better privacy for "programming in the large". Anonymous -subroutines exhibit deep binding of lexical variables (closures). +Described in L, L, L, L, +L, and L. -=item * Arbitrarily nested data structures +=item * roll-your-own magic variables (including multiple simultaneous DBM implementations) -Any scalar value, including any array element, may now contain a -reference to any other variable or subroutine. You can easily create -anonymous variables and subroutines. Perl manages your reference -counts for you. +Described in L and L. -=item * Modularity and reusability +=item * subroutines can now be overridden, autoloaded, and prototyped -The Perl library is now defined in terms of modules which can be easily -shared among various packages. A package may choose to import all or a -portion of a module's published interface. Pragmas (that is, compiler -directives) are defined and used by the same mechanism. +Described in L. -=item * Object-oriented programming +=item * arbitrarily nested data structures and anonymous functions -A package can function as a class. Dynamic multiple inheritance and -virtual methods are supported in a straightforward manner and with very -little new syntax. Filehandles may now be treated as objects. +Described in L, L, L, and L. -=item * Embeddable and Extensible +=item * object-oriented programming -Perl may now be embedded easily in your C or C++ application, and can -either call or be called by your routines through a documented -interface. The XS preprocessor is provided to make it easy to glue -your C or C++ routines into Perl. Dynamic loading of modules is -supported, and Perl itself can be made into a dynamic library. +Described in L, L, and L. -=item * POSIX compliant +=item * compilability into C code or Perl bytecode -A major new module is the POSIX module, which provides access to all -available POSIX routines and definitions, via object classes where -appropriate. +Described in L and L. -=item * Package constructors and destructors +=item * support for light-weight processes (threads) -The new BEGIN and END blocks provide means to capture control as -a package is being compiled, and after the program exits. As a -degenerate case they work just like awk's BEGIN and END when you -use the B<-p> or B<-n> switches. +Described in L and L. -=item * Multiple simultaneous DBM implementations +=item * support for internationalization, localization, and Unicode -A Perl program may now access DBM, NDBM, SDBM, GDBM, and Berkeley DB -files from the same script simultaneously. In fact, the old dbmopen -interface has been generalized to allow any variable to be tied -to an object class which defines its access methods. +Described in L and L. -=item * Subroutine definitions may now be autoloaded +=item * lexical scoping -In fact, the AUTOLOAD mechanism also allows you to define any arbitrary -semantics for undefined subroutine calls. It's not for just autoloading. +Described in L. -=item * Regular expression enhancements +=item * regular expression enhancements -You can now specify non-greedy quantifiers. You can now do grouping -without creating a backreference. You can now write regular expressions -with embedded whitespace and comments for readability. A consistent -extensibility mechanism has been added that is upwardly compatible with -all old regular expressions. +Described in L, with additional examples in L. -=item * Innumerable Unbundled Modules +=item * enhanced debugger and interactive Perl environment, with integrated editor support -The Comprehensive Perl Archive Network described in L -contains hundreds of plug-and-play modules full of reusable -code. See F for a site near you. +Described in L. -=item * Compilability +=item * POSIX 1003.1 compliant library -While not yet in full production mode, a working perl-to-C compiler -does exist. It can generate portable bytecode, simple C, or -optimized C code. +Described in L. =back Okay, that's I enough hype. +=head1 AVAILABILITY + +Perl is available for most operating systems, including virtually +all Unix-like platforms. + +As of early March 2000 (the Perl release 5.6.0), the following +platforms are able to build Perl from the standard source code +distribution available at http://www.perl.com/CPAN/src/index.html + + AIX + DOS DJGPP 1) + FreeBSD + HP-UX + IRIX + Linux + LynxOS + MachTen + MPE/iX + NetBSD + OpenBSD + OS/2 + Rhapsody/Darwin 2) + Solaris + Tru64 UNIX 3) + UNICOS + UNICOS/mk + VMS + VOS + Windows 3.1 1) + Windows 95 1) 4) + Windows 98 1) 4) + Windows NT 1) 4) + + 1) in DOS mode either the DOS or OS/2 ports can be used + 2) new in 5.6.0: the BSD/NeXT-based UNIX of Mac OS X + 3) formerly known as Digital UNIX and before that DEC OSF/1 + 4) compilers: Borland, Cygwin, Mingw32 EGCS/GCC, VC++ + +The following platforms worked for the previous major release +(5.005_03 being the latest maintenance release of that, as of early +March 2000), but be did not manage to test these in time for the 5.6.0 +release of Perl. There is a very good chance that these will work +just fine with 5.6.0. + + A/UX + BeOS + BSD/OS + DG/UX + DYNIX/ptx + DomainOS + Hurd + NextSTEP + OpenSTEP + PowerMAX + QNX + SCO ODT/OSR + SunOS + SVR4 + Ultrix + +The following platform worked for the previous major release (5.005_03 +being the latest maintenance release of that, as of early March 2000). +However, standardization on UTF-8 as the internal string representation +in 5.6.0 has introduced incompatibilities in this EBCDIC platform. +Support for this platform may be enabled in a future release: + + OS390 1) + + 1) Previously known as MVS, or OpenEdition MVS. + +Strongly related to the OS390 platform by also being EBCDIC-based +mainframe platforms are the following platforms: + + BS2000 + VM/ESA + +These are also not expected to work under 5.6.0 for the same reasons +as OS390. Contact the mailing list perl-mvs@perl.org for more details. + +MacOS (Classic, pre-X) is almost 5.6.0-ready; building from the source +does work with 5.6.0, but additional MacOS specific source code is needed +for a complete port. Contact the mailing list macperl-porters@macperl.org +for more more information. + +The following platforms have been known to build Perl from source in +the past, but we haven't been able to verify their status for the +current release, either because the hardware/software platforms are +rare or because we don't have an active champion on these +platforms--or both: + + 3b1 + AmigaOS + ConvexOS + CX/UX + DC/OSx + DDE SMES + DOS EMX + Dynix + EP/IX + ESIX + FPS + GENIX + Greenhills + ISC + MachTen 68k + MiNT + MPC + NEWS-OS + Opus + Plan 9 + PowerUX + RISC/os + Stellar + SVR2 + TI1500 + TitanOS + Unisys Dynix + Unixware + +Support for the following platform is planned for a future Perl release: + + Netware + +The following platforms have their own source code distributions and +binaries available via http://www.perl.com/CPAN/ports/index.html: + + Perl release + + AS/400 5.003 + Netware 5.003_07 + Tandem Guardian 5.004 + +The following platforms have only binaries available via +http://www.perl.com/CPAN/ports/index.html: + + Perl release + + Acorn RISCOS 5.005_02 + AOS 5.002 + LynxOS 5.004_02 + +Although we do suggest that you always build your own Perl from +the source code, both for maximal configurability and for security, +in case you are in a hurry you can check +http://www.perl.com/CPAN/ports/index.html for binary distributions. + =head1 ENVIRONMENT See L. =head1 AUTHOR -Larry Wall >, with the help of oodles of other folks. +Larry Wall , with the help of oodles of other folks. + +If your Perl success stories and testimonials may be of help to others +who wish to advocate the use of Perl in their applications, +or if you wish to simply express your gratitude to Larry and the +Perl developers, please write to perl-thanks@perl.org . =head1 FILES - "/tmp/perl-e$$" temporary file for -e commands "@INC" locations of perl libraries =head1 SEE ALSO a2p awk to perl translator - s2p sed to perl translator + http://www.perl.com/ the Perl Home Page + http://www.perl.com/CPAN the Comprehensive Perl Archive + =head1 DIAGNOSTICS -The B<-w> switch produces some lovely diagnostics. +The C pragma (and the B<-w> switch) produces some +lovely diagnostics. -See L for explanations of all Perl's diagnostics. +See L for explanations of all Perl's diagnostics. The C pragma automatically turns Perl's normally terse warnings +and errors into these longer forms. Compilation errors will tell you the line number of the error, with an indication of the next token or token type that was to be examined. -(In the case of a script passed to Perl via B<-e> switches, each +(In a script passed to Perl via B<-e> switches, each B<-e> is counted as one line.) Setuid scripts have additional constraints that can produce error @@ -263,8 +415,8 @@ switch? The B<-w> switch is not mandatory. Perl is at the mercy of your machine's definitions of various -operations such as type casting, atof(), and sprintf(). The latter -can even trigger a core dump when passed ludicrous input values. +operations such as type casting, atof(), and floating-point +output with sprintf(). If your stdio requires a seek or eof between reads and writes on a particular stream, so does Perl. (This doesn't apply to sysread() @@ -272,15 +424,16 @@ and syswrite().) While none of the built-in data types have any arbitrary size limits (apart from memory size), there are still a few arbitrary limits: a -given variable name may not be longer than 255 characters, and no -component of your PATH may be longer than 255 if you use B<-S>. A regular -expression may not compile to more than 32767 bytes internally. +given variable name may not be longer than 251 characters. Line numbers +displayed by diagnostics are internally stored as short integers, +so they are limited to a maximum of 65535 (higher numbers usually being +affected by wraparound). You may mail your bug reports (be sure to include full configuration -information as output by the myconfig program in the perl source tree, -or by C) to >. -If you've succeeded in compiling perl, the perlbug script in the utils/ -subdirectory can be used to help mail in a bug report. +information as output by the myconfig program in the perl source +tree, or by C) to perlbug@perl.com . If you've succeeded +in compiling perl, the perlbug script in the utils/ subdirectory +can be used to help mail in a bug report. Perl actually stands for Pathologically Eclectic Rubbish Lister, but don't tell anyone I said that.