diff options
| -rw-r--r-- | lib/Pod/Html.pm | 2 | ||||
| -rw-r--r-- | pod/perlfaq4.pod | 2 | ||||
| -rwxr-xr-x | pod/roffitall | 8 | ||||
| -rw-r--r-- | vms/ext/DCLsym/DCLsym.pm | 2 | ||||
| -rw-r--r-- | vms/ext/Stdio/Stdio.pm | 6 | ||||
| -rw-r--r-- | vms/perlvms.pod | 2 |
6 files changed, 17 insertions, 5 deletions
diff --git a/lib/Pod/Html.pm b/lib/Pod/Html.pm index aaefc3cdac..6efaf1ffa2 100644 --- a/lib/Pod/Html.pm +++ b/lib/Pod/Html.pm @@ -916,7 +916,7 @@ sub process_over { # process_back - process a pod back tag and convert it to HTML format. # sub process_back { - warn "$0: $podfile: unexpected =back directive in paragraph $paragraph. ignorning.\n" + warn "$0: $podfile: unexpected =back directive in paragraph $paragraph. ignoring.\n" unless $listlevel; return unless $listlevel; diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod index bcf03990bc..a5b505c4a7 100644 --- a/pod/perlfaq4.pod +++ b/pod/perlfaq4.pod @@ -371,7 +371,7 @@ suggests (assuming your string is contained in $text): If you want to represent quotation marks inside a quotation-mark-delimited field, escape them with backslashes (eg, -C<"like \"this\""). Unescaping them is a task addressed earlier in +C<"like \"this\"">. Unescaping them is a task addressed earlier in this section. Alternatively, the Text::ParseWords module (part of the standard perl diff --git a/pod/roffitall b/pod/roffitall index d69054f41b..cbd19af4fe 100755 --- a/pod/roffitall +++ b/pod/roffitall @@ -180,14 +180,22 @@ fi #psroff -t -man -rC1 -rD1 -rF1 > $tmp/PerlDoc.ps 2>$tmp/PerlTOC.raw #nroff -man -rC1 -rD1 -rF1 > $tmp/PerlDoc.txt 2>$tmp/PerlTOC.nr.raw +# First, create the raw data run="$cmd -rC1 -rD1 -rF1 >$tmp/PerlDoc.$ext 2>$tmp/PerlTOC.$ext.raw" echo "$me: running $run" eval $run $toroff + +#Now create the TOC echo "$me: parsing TOC" ./rofftoc $tmp/PerlTOC.$ext.raw > $tmp/PerlTOC.tmp.man run="$cmd $tmp/PerlTOC.tmp.man >$tmp/PerlTOC.$ext" echo "$me: running $run" eval $run + +# Finally, recreate the Doc, without the blank page 0 +run="$cmd -rC1 -rD1 >$tmp/PerlDoc.$ext 2>$tmp/PerlTOC.$ext.raw" +echo "$me: running $run" +eval $run $toroff rm -f $tmp/PerlTOC.tmp.man $tmp/PerlTOC.$ext.raw echo "$me: leaving you with $tmp/PerlDoc.$ext and $tmp/PerlTOC.$ext" diff --git a/vms/ext/DCLsym/DCLsym.pm b/vms/ext/DCLsym/DCLsym.pm index 057951dd99..44c4b84a65 100644 --- a/vms/ext/DCLsym/DCLsym.pm +++ b/vms/ext/DCLsym/DCLsym.pm @@ -201,6 +201,8 @@ can also call methods directly to manipulate individual symbols. In some cases, this allows you finer control than using a tied hash aggregate. The following methods are supported: +=over + =item new This creates a C<VMS::DCLsym> object which can be used as a handle for later diff --git a/vms/ext/Stdio/Stdio.pm b/vms/ext/Stdio/Stdio.pm index 516e678e2c..218c406fa4 100644 --- a/vms/ext/Stdio/Stdio.pm +++ b/vms/ext/Stdio/Stdio.pm @@ -76,7 +76,7 @@ __END__ =head1 NAME -VMS::Stdio +VMS::Stdio - standard I/O functions via VMS extensions =head1 SYNOPSIS @@ -99,7 +99,7 @@ remove("another.file"); =head1 DESCRIPTION -This package gives Perl scripts access to VMS extensions to several +This package gives Perl scripts access via VMS extensions to several C stdio operations not available through Perl's CORE I/O functions. The specific routines are described below. These functions are prototyped as unary operators, with the exception of C<vmsopen> @@ -141,6 +141,8 @@ VMS::Stdio function. This compatibility interface will be removed in a future release of this extension, so please update your code to use the new routines. +=over + =item flush This function causes the contents of stdio buffers for the specified diff --git a/vms/perlvms.pod b/vms/perlvms.pod index 5f9e91f635..c599e5834c 100644 --- a/vms/perlvms.pod +++ b/vms/perlvms.pod @@ -58,7 +58,7 @@ define a foreign command to invoke this image. Perl extensions are packages which provide both XS and Perl code to add new functionality to perl. (XS is a meta-language which simplifies writing C code which interacts with Perl, see -L<perlapi> for more details.) The Perl code for an +L<perlxs> for more details.) The Perl code for an extension is treated like any other library module - it's made available in your script through the appropriate C<use> or C<require> statement, and usually defines a Perl |