From: Rafael Garcia-Suarez Date: Thu, 22 Nov 2001 12:54:16 +0000 (+0000) Subject: Re: [DOC PATCHES] pod cleanups X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=076988851d1cdb6cc455615593d7b9380b21955a;p=p5sagit%2Fp5-mst-13.2.git Re: [DOC PATCHES] pod cleanups Message-Id: p4raw-id: //depot/perl@13206 --- diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index be2ab64..b6e6312 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -2437,9 +2437,7 @@ strings, set up your locale environment variables appropriately Note that the C<%a> and C<%b>, the short forms of the day of the week and the month of the year, may not necessarily be three characters wide. -=item lock - - lock I +=item lock THING This function places an advisory lock on a variable, subroutine, or referenced object contained in I until the lock goes out @@ -4787,7 +4785,7 @@ There are also two Perl-specific flags: v interpret string as a vector of integers, output as numbers separated either by dots, or by an arbitrary string received from the argument list when the flag - is preceded by C<*> + is preceded by "*" Where a number would appear in the flags, an asterisk (C<*>) may be used instead, in which case Perl uses the next item in the parameter diff --git a/pod/perlmodinstall.pod b/pod/perlmodinstall.pod index 8da93db..dd0e279 100644 --- a/pod/perlmodinstall.pod +++ b/pod/perlmodinstall.pod @@ -350,10 +350,10 @@ ASCII to EBCDIC. A. DECOMPRESS - Decompress the file with C +Decompress the file with C - You can get gzip from - http://www.s390.ibm.com/products/oe/bpxqp1.html. +You can get gzip from +http://www.s390.ibm.com/products/oe/bpxqp1.html B. UNPACK diff --git a/pod/perlre.pod b/pod/perlre.pod index 5c7e76b..900a01d 100644 --- a/pod/perlre.pod +++ b/pod/perlre.pod @@ -183,9 +183,9 @@ In addition, Perl defines the following: \pP Match P, named property. Use \p{Prop} for longer names. \PP Match non-P \X Match eXtended Unicode "combining character sequence", - equivalent to C<(?:\PM\pM*)> + equivalent to (?:\PM\pM*) \C Match a single C char (octet) even under Unicode. - B breaks up characters into their UTF-8 bytes, + NOTE: breaks up characters into their UTF-8 bytes, so you may end up with malformed pieces of UTF-8. A C<\w> matches a single alphanumeric character or C<_>, not a whole word. @@ -219,10 +219,22 @@ equivalents (if available) are as follows: word \w [3] xdigit - [1] A GNU extension equivalent to C<[ \t]>, `all horizontal whitespace'. - [2] Not I to C<\s> since the C<[[:space:]]> includes - also the (very rare) `vertical tabulator', "\ck", chr(11). - [3] A Perl extension. +=over + +=item [1] + +A GNU extension equivalent to C<[ \t]>, `all horizontal whitespace'. + +=item [2] + +Not exactly equivalent to C<\s> since the C<[[:space:]]> includes +also the (very rare) `vertical tabulator', \ck", chr(11). + +=item [3] + +A Perl extension. + +=back For example use C<[:upper:]> to match all the uppercase characters. Note that the C<[]> are part of the C<[::]> construct, not part of the diff --git a/pod/perlretut.pod b/pod/perlretut.pod index bb2423b..8f7c8cd 100644 --- a/pod/perlretut.pod +++ b/pod/perlretut.pod @@ -2059,7 +2059,7 @@ the first alternative C<[^()]+> matching a substring with no parentheses and the second alternative C<\([^()]*\)> matching a substring delimited by parentheses. The problem with this regexp is that it is pathological: it has nested indeterminate quantifiers - of the form C<(a+|b)+>. We discussed in Part 1 how nested quantifiers +of the form C<(a+|b)+>. We discussed in Part 1 how nested quantifiers like this could take an exponentially long time to execute if there was no match possible. To prevent the exponential blowup, we need to prevent useless backtracking at some point. This can be done by diff --git a/pod/perluniintro.pod b/pod/perluniintro.pod index cd978d0..55f8d56 100644 --- a/pod/perluniintro.pod +++ b/pod/perluniintro.pod @@ -387,8 +387,8 @@ String Equivalence The question of string equivalence turns somewhat complicated in Unicode: what do you mean by equal? - Is C equal to - C? +(Is C equal to +C?) The short answer is that by default Perl compares equivalence (C, C) based only on code points of the characters. @@ -413,8 +413,8 @@ String Collation People like to see their strings nicely sorted, or as Unicode parlance goes, collated. But again, what do you mean by collate? - Does C come before or after - C? +(Does C come before or after +C?) The short answer is that by default Perl compares strings (C, C, C, C, C) based only on the code points of the diff --git a/vms/perlvms.pod b/vms/perlvms.pod index c09e047..35776a4 100644 --- a/vms/perlvms.pod +++ b/vms/perlvms.pod @@ -194,7 +194,7 @@ so we can try to work around them. =head2 Wildcard expansion File specifications containing wildcards are allowed both on -the command line and within Perl globs (e.g. *.cE>). If +the command line and within Perl globs (e.g. C*.cE>). If the wildcard filespec uses VMS syntax, the resultant filespecs will follow VMS syntax; if a Unix-style filespec is passed in, Unix-style filespecs will be returned. @@ -244,11 +244,29 @@ directory specifications may use either VMS or Unix syntax. Perl for VMS supports redirection of input and output on the command line, using a subset of Bourne shell syntax: - reads stdin from F, - >F writes stdout to F, - >>F appends stdout to F, - 2>F writes stderr to F, and - 2>>F appends stderr to F. +=over + +=item * + +Cfile> reads stdin from C, + +=item * + +Cfile> writes stdout to C, + +=item * + +CEfile> appends stdout to C, + +=item * + +C<2Efile> writes stderr to C, and + +=item * + +C<2EEfile> appends stderr to C. + +=back In addition, output may be piped to a subprocess, using the character '|'. Anything after this character on the command