From: Audrey Tang Date: Sat, 29 Dec 2001 01:59:28 +0000 (+0800) Subject: Module names and other nits X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=fe854a6f990f7776a8ee8bd28f02e1bd36e5bb58;p=p5sagit%2Fp5-mst-13.2.git Module names and other nits Message-ID: <20011229015928.A29712@geb.elixus.org> p4raw-id: //depot/perl@13922 --- diff --git a/lib/Exporter/Heavy.pm b/lib/Exporter/Heavy.pm index b3afe9c..d1c4a10 100644 --- a/lib/Exporter/Heavy.pm +++ b/lib/Exporter/Heavy.pm @@ -12,7 +12,7 @@ our $Verbose; Exporter::Heavy - Exporter guts -=head1 SYNOPIS +=head1 SYNOPSIS (internal use only) diff --git a/pod/perl561delta.pod b/pod/perl561delta.pod index 86235f0..9ac8545 100644 --- a/pod/perl561delta.pod +++ b/pod/perl561delta.pod @@ -1608,7 +1608,7 @@ messages. For example: =head1 NAME - sample - Using GetOpt::Long and Pod::Usage + sample - Using Getopt::Long and Pod::Usage =head1 SYNOPSIS diff --git a/pod/perl56delta.pod b/pod/perl56delta.pod index 75d7728..5262c37 100644 --- a/pod/perl56delta.pod +++ b/pod/perl56delta.pod @@ -1011,7 +1011,7 @@ messages. For example: =head1 NAME - sample - Using GetOpt::Long and Pod::Usage + sample - Using Getopt::Long and Pod::Usage =head1 SYNOPSIS diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod index ff2b074..827bb2f 100644 --- a/pod/perldebguts.pod +++ b/pod/perldebguts.pod @@ -967,4 +967,4 @@ L, L L, and -L. +L. diff --git a/pod/perldebug.pod b/pod/perldebug.pod index bb01bd3..7f58ddf 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -948,7 +948,7 @@ L, L, L, L, -L, +L, L, L, and diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod index 19066f4..d145eb6 100644 --- a/pod/perlfaq4.pod +++ b/pod/perlfaq4.pod @@ -1849,7 +1849,7 @@ in L. =head2 How can I use a reference as a hash key? -You can't do this directly, but you could use the standard Tie::Refhash +You can't do this directly, but you could use the standard Tie::RefHash module distributed with Perl. =head1 Data: Misc @@ -1919,10 +1919,10 @@ respectively. =head2 How do I keep persistent data across program calls? For some specific applications, you can use one of the DBM modules. -See L. More generically, you should consult the FreezeThaw, -Storable, or Class::Eroot modules from CPAN. Starting from Perl 5.8 -Storable is part of the standard distribution. Here's one example using -Storable's C and C functions: +See L. More generically, you should consult the FreezeThaw +or Storable modules from CPAN. Starting from Perl 5.8 Storable is part +of the standard distribution. Here's one example using Storable's C +and C functions: use Storable; store(\%hash, "filename"); diff --git a/pod/perlfaq6.pod b/pod/perlfaq6.pod index 6ddc0be..fe53ea8 100644 --- a/pod/perlfaq6.pod +++ b/pod/perlfaq6.pod @@ -643,7 +643,7 @@ programming language, you insensitive scoundrel! Starting from Perl 5.6 Perl has had some level of multibyte character support. Perl 5.8 or later is recommended. Supported multibyte -character repetoires include Unicode, and legacy encodings +character repertoires include Unicode, and legacy encodings through the Encode module. See L, L, and L. diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 188d800..39a6ea4 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -4236,7 +4236,7 @@ documentation. =item send SOCKET,MSG,FLAGS -Sends a message on a socket. Attemps to send the scalar MSG to the +Sends a message on a socket. Attempts to send the scalar MSG to the SOCKET filehandle. Takes the same flags as the system call of the same name. On unconnected sockets you must specify a destination to send TO, in which case it does a C C. Returns the number of diff --git a/pod/perlguts.pod b/pod/perlguts.pod index 8a1d511..2b8faf0 100644 --- a/pod/perlguts.pod +++ b/pod/perlguts.pod @@ -247,7 +247,7 @@ portion of the string between the "real" and the "fake" beginnings is shown in parentheses, and the values of C and C reflect the fake beginning, not the real one. -Something similar to the offset hack is perfomed on AVs to enable +Something similar to the offset hack is performed on AVs to enable efficient shifting and splicing off the beginning of the array; while C points to the first element in the array that is visible from Perl, C points to the real start of the C array. These are diff --git a/pod/perlpacktut.pod b/pod/perlpacktut.pod index 93ec186..423ab03 100644 --- a/pod/perlpacktut.pod +++ b/pod/perlpacktut.pod @@ -727,7 +727,7 @@ call, creating the items we intend to stuff into the C<$env> buffer: to each key (in C<$_>) it adds the C<=> separator and the hash entry value. Each triplet is packed with the template code sequence C that is multiplied with the number of keys. (Yes, that's what the C -function resturns in scalar context.) To get the very last null byte, +function returns in scalar context.) To get the very last null byte, we add a C<0> at the end of the C list, to be packed with C. (Attentive readers may have noticed that we could have omitted the 0.) diff --git a/pod/perlsub.pod b/pod/perlsub.pod index efadf8f..aa5fd5b 100644 --- a/pod/perlsub.pod +++ b/pod/perlsub.pod @@ -1204,7 +1204,7 @@ Note however that some built-ins can't have their syntax expressed by a prototype (such as C or C). If you override them you won't be able to fully mimic their original syntax. -The built-ins C, C and C can also be overriden, but due +The built-ins C, C and C can also be overridden, but due to special magic, their original syntax is preserved, and you don't have to define a prototype for their replacements. (You can't override the C syntax, though). @@ -1214,9 +1214,9 @@ C replacement as C, it will actually receive the argument C<"Foo/Bar.pm"> in @_. See L. And, as you'll have noticed from the previous example, if you override -C, the C*E> glob operator is overriden as well. +C, the C*E> glob operator is overridden as well. -Finally, some built-ins (e.g. C or C) can't be overriden. +Finally, some built-ins (e.g. C or C) can't be overridden. =head2 Autoloading diff --git a/pod/perltodo.pod b/pod/perltodo.pod index 94c4f9d..1df5fda 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -148,7 +148,7 @@ Reader-writer locks, realtime/asynchronous IO =head2 IPv6 Support -There are non-core modules, such as C, but these will need +There are non-core modules, such as C, but these will need integrating when IPv6 actually starts to really happen. See RFC 2292 and RFC 2553. @@ -223,7 +223,7 @@ C<&>, C, C and C. =head2 Replace pod2html with something using Pod::Parser -The CPAN module C may be a more suitable basis for a +The CPAN module C may be a more suitable basis for a C convertor; the current one duplicates the functionality abstracted in C, which makes updating the POD language difficult. diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 3edc0ca..db5a475 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -730,9 +730,9 @@ As you can see, the continuation bytes all begin with C<10>, and the leading bits of the start byte tells how many bytes the are in the encoded character. -=item UTF-EBDIC +=item UTF-EBCDIC -Like UTF-8, but EBDCIC-safe, as UTF-8 is ASCII-safe. +Like UTF-8, but EBCDIC-safe, as UTF-8 is ASCII-safe. =item UTF-16, UTF-16BE, UTF16-LE, Surrogates, and BOMs (Byte Order Marks) diff --git a/pod/perlutil.pod b/pod/perlutil.pod index 93b9e0b..57eddda 100644 --- a/pod/perlutil.pod +++ b/pod/perlutil.pod @@ -171,9 +171,9 @@ very useful for creating skeletons of pure Perl modules. =item L -Perl comes with a profiler, the F module. The +Perl comes with a profiler, the F module. The F utility analyzes the output of this profiler and tells you -which subroutines are taking up the most run time. See L +which subroutines are taking up the most run time. See L for more information. =item L @@ -190,6 +190,6 @@ L, L, L, L, L, L, L, L, L, L, L, L, L, L, -L, L +L, L =cut diff --git a/pod/perlxs.pod b/pod/perlxs.pod index 5146a1e..0398641 100644 --- a/pod/perlxs.pod +++ b/pod/perlxs.pod @@ -1714,7 +1714,7 @@ have been designed so that they will work with non-threaded Perl as well. It is therefore strongly recommended that these macros be used by all XS modules that make use of static data. -The easiest way to get a template set of macros to use is by specifiying +The easiest way to get a template set of macros to use is by specifying the C<-g> (C<--global>) option with h2xs (see L). Below is an example module that makes use of the macros.