From 96090e4f0acf1d24051c680595b4740bd24cb69a Mon Sep 17 00:00:00 2001 From: Apocalypse Date: Tue, 15 Feb 2011 18:38:04 -0700 Subject: [PATCH] Fix bad pod links found by Test::Pod::LinkCheck --- pod/perldata.pod | 4 ++-- pod/perldebguts.pod | 2 +- pod/perldebug.pod | 2 +- pod/perldiag.pod | 2 +- pod/perlembed.pod | 4 ++-- pod/perlfaq7.pod | 3 +-- pod/perlfaq8.pod | 2 +- pod/perlform.pod | 2 +- pod/perlfunc.pod | 21 ++++++++++++--------- pod/perlglossary.pod | 11 +++++------ pod/perlinterp.pod | 2 +- pod/perllocale.pod | 2 +- pod/perlmod.pod | 2 +- pod/perlobj.pod | 2 +- pod/perlperf.pod | 4 ++-- pod/perlport.pod | 2 +- pod/perlre.pod | 4 ++-- pod/perlreapi.pod | 2 +- pod/perlrun.pod | 4 ++-- pod/perlsub.pod | 2 +- pod/perltodo.pod | 2 +- pod/perlvar.pod | 2 +- pod/perlvms.pod | 6 +++--- 23 files changed, 45 insertions(+), 44 deletions(-) diff --git a/pod/perldata.pod b/pod/perldata.pod index 03191b5..1b1cbf4 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -862,8 +862,8 @@ C forbids such practice. 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 local(). See the bottom of L for an -example. +during the local(). See the bottom of L +for an example. =head1 SEE ALSO diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod index d6bffb1..e5970a3 100644 --- a/pod/perldebguts.pod +++ b/pod/perldebguts.pod @@ -151,7 +151,7 @@ after the debugger completes its own initialization.) After the rc file is read, the debugger reads the PERLDB_OPTS environment variable and uses it to set debugger options. The contents of this variable are treated as if they were the argument -of an C debugger command (q.v. in L). +of an C debugger command (q.v. in L). =head3 Debugger Internal Variables diff --git a/pod/perldebug.pod b/pod/perldebug.pod index 07aa302..8fbb231 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -654,7 +654,7 @@ X Level of verbosity. By default, the debugger leaves your exceptions and warnings alone, because altering them can break correctly running programs. It will attempt to print a message when uncaught INT, BUS, or -SEGV signals arrive. (But see the mention of signals in L below.) +SEGV signals arrive. (But see the mention of signals in L below.) To disable this default safe mode, set these values to something higher than 0. At a level of 1, you get backtraces upon receiving any kind diff --git a/pod/perldiag.pod b/pod/perldiag.pod index 7a3b962..087f906 100644 --- a/pod/perldiag.pod +++ b/pod/perldiag.pod @@ -2413,7 +2413,7 @@ an undefined value for the length. See L. =item Lexing code attempted to stuff non-Latin-1 character into Latin-1 input (F) An extension is attempting to insert text into the current parse -(using L or similar), but tried to insert a character +(using L or similar), but tried to insert a character that couldn't be part of the current input. This is an inherent pitfall of the stuffing mechanism, and one of the reasons to avoid it. Where it is necessary to stuff, stuffing only plain ASCII is recommended. diff --git a/pod/perlembed.pod b/pod/perlembed.pod index 1144e43..8edff17 100644 --- a/pod/perlembed.pod +++ b/pod/perlembed.pod @@ -1109,8 +1109,8 @@ you will have to write the explicit full form Perl_warn(aTHX_ "%d bottles of beer on the wall", bottlecount); -(See L.> ) Hiding the short forms is very useful for avoiding +(See L for the explanation +of the C. ) Hiding the short forms is very useful for avoiding all sorts of nasty (C preprocessor or otherwise) conflicts with other software packages (Perl defines about 2400 APIs with these short names, take or leave few hundred, so there certainly is room for conflict.) diff --git a/pod/perlfaq7.pod b/pod/perlfaq7.pod index 983825b..5d7a1e8 100644 --- a/pod/perlfaq7.pod +++ b/pod/perlfaq7.pod @@ -633,8 +633,7 @@ Why do you want to do that? :-) If you want to override a predefined function, such as open(), then you'll have to import the new definition from a different -module. See L. There's -also an example in L. +module. See L. If you want to overload a Perl operator, such as C<+> or C<**>, then you'll want to use the C pragma, documented diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod index 99af392..0e9fcc5 100644 --- a/pod/perlfaq8.pod +++ b/pod/perlfaq8.pod @@ -933,7 +933,7 @@ approach will suffice: =head2 How can I write expect in Perl? -Once upon a time, there was a library called L (part of the +Once upon a time, there was a library called F (part of the standard perl distribution), which never really got finished. If you find it somewhere, I. These days, your best bet is to look at the Expect module available from CPAN, which also requires two diff --git a/pod/perlform.pod b/pod/perlform.pod index df0f0a1..6a6a83a 100644 --- a/pod/perlform.pod +++ b/pod/perlform.pod @@ -393,7 +393,7 @@ by checking $FORMAT_LINES_LEFT before each write() and print the footer yourself if necessary. Here's another strategy: Open a pipe to yourself, using C -(see L) and always write() to MYSELF instead of STDOUT. +(see L) and always write() to MYSELF instead of STDOUT. Have your child process massage its STDIN to rearrange headers and footers however you like. Not very convenient, but doable. diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 2047dd6..3ed689e 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1271,7 +1271,7 @@ C raises an exception. Inside an C the error message is stuffed into C<$@> and the C is terminated with the undefined value. If the exception is outside of all enclosing Cs, then the uncaught exception prints LIST to C and exits with a non-zero value. If you -need to exit the process with a specific exit code, see L. +need to exit the process with a specific exit code, see L. Equivalent examples: @@ -1355,7 +1355,7 @@ You can arrange for a callback to be run just before the C does its deed, by setting the C<$SIG{__DIE__}> hook. The associated handler is called with the error text and can change the error message, if it sees fit, by calling C again. See -L for details on setting C<%SIG> entries, and +L for details on setting C<%SIG> entries, and L<"eval BLOCK"> for some examples. Although this feature was to be run only right before your program was to exit, this is not currently so: the C<$SIG{__DIE__}> hook is currently called @@ -1401,9 +1401,9 @@ is just like eval `cat stat.pl`; except that it's more efficient and concise, keeps track of the current -filename for error messages, searches the @INC directories, and updates -C<%INC> if the file is found. See L for these -variables. It also differs in that code evaluated with C +filename for error messages, searches the C<@INC> directories, and updates +C<%INC> if the file is found. See L and L for +these variables. It also differs in that code evaluated with C cannot see lexicals in the enclosing scope; C does. It's the same, however, in that it does reparse the file every time you call it, so you probably don't want to do this inside a loop. @@ -2775,7 +2775,8 @@ respectively. =item Otherwise, If EXPR has the UTF8 flag set If the current package has a subroutine named C, it will be used to -change the case (See L.) +change the case +(See L.) Otherwise Unicode semantics are used for the case change. =item Otherwise, if C is in effect @@ -3302,7 +3303,8 @@ replace dash (C<'-'>) with the command. See L for more examples of this. (You are not allowed to C to a command that pipes both in I out, but see L, L, and -L for alternatives.) +L for +alternatives.) In the form of pipe opens taking three or more arguments, if LIST is specified (extra arguments after the command name) then LIST becomes arguments @@ -4342,7 +4344,8 @@ unless you are very careful. In addition, note that Perl's pipes use IO buffering, so you may need to set C<$|> to flush your WRITEHANDLE after each command, depending on the application. -See L, L, and L +See L, L, and +L for examples of such things. On systems that support a close-on-exec flag on files, that flag is set @@ -7030,7 +7033,7 @@ The behavior is undefined if LENGTH is greater than the length of the file. The position in the file of FILEHANDLE is left unchanged. You may want to -call L before writing to the file. +call L before writing to the file. =item uc EXPR X X X diff --git a/pod/perlglossary.pod b/pod/perlglossary.pod index c4fb406..3a573c3 100644 --- a/pod/perlglossary.pod +++ b/pod/perlglossary.pod @@ -241,7 +241,7 @@ the numbered variables (C<$1>, C<$2>, etc.) continue to refer to these same values, as long as the pattern was the last successful match of the current dynamic scope. C<\g{-1}> can be used to refer to a group by relative rather than absolute position; and groups can be also be named, and -referred to later by name rather than number. See L. +referred to later by name rather than number. See L. =item backtracking @@ -894,7 +894,7 @@ will be called a "binary-only" distribution. =item (to be) dropped modules -When Perl 5 was first released (see L), several modules were +When Perl 5 was first released (see L), several modules were included, which have now fallen out of common use. It has been suggested that these modules should be removed, since the distribution became rather large, and the common criterion for new module additions is now limited to @@ -2985,9 +2985,8 @@ L must be the last switch in a cluster. A program technique that lets you evaluate an L and then, based on the value of the expression, do a multiway branch to the appropriate piece of code for that value. Also called a "case -structure", named after the similar Pascal construct. Most switch -statements in Perl are spelled C. See L. +structure", named after the similar Pascal construct. See +L. =item symbol @@ -3155,7 +3154,7 @@ to build special tools. Perl is sort of a machine shop. To turn one string representation into another by mapping each character of the source string to its corresponding character in the result string. See -LSEARCHLISTEREPLACEMENTLISTEcds>. +LSEARCHLISTEREPLACEMENTLISTEcdsr>. =item trigger diff --git a/pod/perlinterp.pod b/pod/perlinterp.pod index 5d16e8b..74a5e4e 100644 --- a/pod/perlinterp.pod +++ b/pod/perlinterp.pod @@ -696,7 +696,7 @@ stack implements the C equivalent of, for example: ... } -See L for how to use the save stack. +See L for how to use the save stack. =head1 MILLIONS OF MACROS diff --git a/pod/perllocale.pod b/pod/perllocale.pod index 0bec423..45385e8 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -866,7 +866,7 @@ using GNU libc and you can ignore C. However, in the case you are using C: it affects the language of informational, warning, and error messages output by commands (in other words, it's like C) but it has higher -priority than L. Moreover, it's not a single value but +priority than C. Moreover, it's not a single value but instead a "path" (":"-separated list) of I (not locales). See the GNU C library documentation for more information. diff --git a/pod/perlmod.pod b/pod/perlmod.pod index 1a166a8..5266f19 100644 --- a/pod/perlmod.pod +++ b/pod/perlmod.pod @@ -66,7 +66,7 @@ main, but we decided it was more useful for package writers to be able to use leading underscore to indicate private variables and method names. However, variables and functions named with a single C<_>, such as $_ and C, are still forced into the package C
. See also -L. +L. Ced strings are compiled in the package in which the eval() was compiled. (Assignments to C<$SIG{}>, however, assume the signal diff --git a/pod/perlobj.pod b/pod/perlobj.pod index fdecd84..850225f 100644 --- a/pod/perlobj.pod +++ b/pod/perlobj.pod @@ -576,7 +576,7 @@ destructed. Plain refs are only garbage-collected if the destruct level is greater than 0. You can test the higher levels of global destruction by setting the PERL_DESTRUCT_LEVEL environment variable, presuming C<-DDEBUGGING> was enabled during perl build time. -See L for more information. +See L for more information. A more complete garbage collection strategy will be implemented at a future date. diff --git a/pod/perlperf.pod b/pod/perlperf.pod index a934271..cac6eee 100644 --- a/pod/perlperf.pod +++ b/pod/perlperf.pod @@ -567,7 +567,7 @@ to execute, C and C, for example. The differences in the actual times recorded might be in the algorithm used internally, or it could be due to system resource limitations or contention. -See also the L which will profile database queries running +See also the L which will profile database queries running under the C namespace. =head2 Devel::NYTProf @@ -1137,7 +1137,7 @@ deserve further attention. Apache::DProf Apache::SmallProf Benchmark - DBIx::Profiler + DBIx::Profile Devel::AutoProfiler Devel::DProf Devel::DProfLB diff --git a/pod/perlport.pod b/pod/perlport.pod index 97a2a2d..9b34ef2 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -1145,7 +1145,7 @@ Also see: =item * -F (installed as L), L +F (installed as F), L =item * diff --git a/pod/perlre.pod b/pod/perlre.pod index 0175fbe..56e42f8 100644 --- a/pod/perlre.pod +++ b/pod/perlre.pod @@ -1840,12 +1840,12 @@ match takes a long time to finish. A powerful tool for optimizing such beasts is what is known as an "independent group", -which does not backtrack (see Lpattern) >>>). Note also that +which does not backtrack (see Lpattern) >>>). Note also that zero-length look-ahead/look-behind assertions will not backtrack to make the tail match, since they are in "logical" context: only whether they match is considered relevant. For an example where side-effects of look-ahead I have influenced the -following match, see Lpattern) >>>. +following match, see Lpattern) >>>. =head2 Version 8 Regular Expressions X X X diff --git a/pod/perlreapi.pod b/pod/perlreapi.pod index dfe7af5..7028650 100644 --- a/pod/perlreapi.pod +++ b/pod/perlreapi.pod @@ -131,7 +131,7 @@ Additional flags: Set if C is in effect. If present in C<< rx->extflags >> C will use the locale dependent definition of whitespace under when RXf_SKIPWHITE or RXf_WHITE are in effect. Under ASCII whitespace -is defined as per L, and by the internal +is defined as per L, and by the internal macros C under UTF-8 and C under C. diff --git a/pod/perlrun.pod b/pod/perlrun.pod index 473205a..9165dca 100644 --- a/pod/perlrun.pod +++ b/pod/perlrun.pod @@ -927,7 +927,7 @@ will treat the #! line as the first line. Thus a warning on the 2nd line of the program (which is on the 100th line in the file) will be reported as line 2, and not as line 100. This can be overridden by using the #line directive. -(See L) +(See L) If a directory name is specified, Perl will switch to that directory before running the program. The B<-x> switch controls only the @@ -1211,7 +1211,7 @@ X Relevant only if your perl executable was built with B<-DDEBUGGING>, this controls the behavior of global destruction of objects and other -references. See L for more information. +references. See L for more information. =item PERL_DL_NONLAZY X diff --git a/pod/perlsub.pod b/pod/perlsub.pod index cfa4ad4..ece4f15 100644 --- a/pod/perlsub.pod +++ b/pod/perlsub.pod @@ -351,7 +351,7 @@ it. Similarly, in the conditional the scope of $answer extends from its declaration through the rest of that conditional, including any C and C clauses, -but not beyond it. See L for information +but not beyond it. See L for information on the scope of variables in statements with modifiers. The C loop defaults to scoping its index variable dynamically diff --git a/pod/perltodo.pod b/pod/perltodo.pod index ba10a48..de0e373 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -28,7 +28,7 @@ programming languages offer you 1 line of immortality? =head2 Migrate t/ from custom TAP generation Many tests below F still generate TAP by "hand", rather than using library -functions. As explained in L, tests in F are +functions. As explained in L, tests in F are written in a particular way to test that more complex constructions actually work before using them routinely. Hence they don't use C, but instead there is an intentionally simpler library, F. However, diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 53295f0..39bab24 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -1691,7 +1691,7 @@ A format contains C calls that put their result into C<$^A>. After calling its format, C prints out the contents of C<$^A> and empties. So you never really see the contents of C<$^A> unless you call C yourself and then look at it. See -L and L. +L and L. =item HANDLE->format_formfeed(EXPR) diff --git a/pod/perlvms.pod b/pod/perlvms.pod index fe2b5d8..7e96c06 100644 --- a/pod/perlvms.pod +++ b/pod/perlvms.pod @@ -848,10 +848,10 @@ Therefore, the "system time" elements will always be 0, since there is no difference between "user time" and "system" time under VMS, and the time accumulated by a subprocess may or may not appear separately in the "child time" field, depending on -whether L keeps track of subprocesses separately. Note +whether C keeps track of subprocesses separately. Note especially that the VAXCRTL (at least) keeps track only of -subprocesses spawned using L and L; it will not -accumulate the times of subprocesses spawned via pipes, L, +subprocesses spawned using C and C; it will not +accumulate the times of subprocesses spawned via pipes, C, or backticks. =item unlink LIST -- 2.7.4