[PATCH] long C<=item>s in pod/perlunicode.pod

Date: Tue, 1 Jul 2003 18:21:34 +0100
Message-ID: <533D273D4014D411AB1D00062938C4D9040465A9@hotel.npl.co.uk>

Subject:  [PATCH] long C<=item>s in lib/CGI.pm
From: Robin Barker <Robin.Barker@npl.co.uk>
Message-ID: <533D273D4014D411AB1D00062938C4D9040465AA@hotel.npl.co.uk>
Date: Tue, 1 Jul 2003 18:25:17 +0100

Subject: [PATCH] long <=item>s  in lib/ExtUtils/MakeMaker/FAQ.pod
From: Robin Barker <Robin.Barker@npl.co.uk>
Date: Tue, 1 Jul 2003 18:29:09 +0100
Message-ID: <533D273D4014D411AB1D00062938C4D9040465AB@hotel.npl.co.uk>

p4raw-id: //depot/perl@19917

diff --git a/lib/CGI.pm b/lib/CGI.pm
index c123cea..ecdb164 100644 (file)
--- a/lib/CGI.pm
+++ b/lib/CGI.pm
@@ -6595,6 +6595,7 @@ Returns either the remote host name or IP address.
 if the former is unavailable.
 
 =item B<script_name()>
+
 Return the script name as a partial URL, for self-refering
 scripts.
 

diff --git a/lib/ExtUtils/MakeMaker/FAQ.pod b/lib/ExtUtils/MakeMaker/FAQ.pod
index ca9d53f..4572da1 100644 (file)
--- a/lib/ExtUtils/MakeMaker/FAQ.pod
+++ b/lib/ExtUtils/MakeMaker/FAQ.pod
@@ -61,7 +61,9 @@ MakeMaker.
 
 =over 4
 
-=item How do I keep my $VERSION up to date without resetting it manually?
+=item
+
+How do I keep my $VERSION up to date without resetting it manually?
 
 Often you want to manually set the $VERSION in the main module
 distribution because this is the version that everybody sees on CPAN
@@ -95,7 +97,9 @@ complicated.
     # must be all on one line or MakeMaker will get confused.
     $VERSION = do { my @r = (q$Revision$ =~ /\d+/g); sprintf "%d."."%03d" x $#r, @r };
 
-=item What's this F<META.yml> thing and how did it get in my F<MANIFEST>?!
+=item
+
+What's this F<META.yml> thing and how did it get in my F<MANIFEST>?!
 
 F<META.yml> is a module meta-data file pioneered by Module::Build and
 automatically generated as part of the 'distdir' target (and thus
@@ -109,7 +113,10 @@ To shut off its generation, pass the C<NO_META> flag to C<WriteMakefile()>.
 
 =over 4
 
-=item How to I prevent "object version X.XX does not match bootstrap parameter Y.YY" errors?
+=item
+
+How to I prevent "object version X.XX does not match bootstrap parameter Y.YY"
+errors?
 
 XS code is very sensitive to the module version number and will
 complain if the version number in your Perl module doesn't match.  If
@@ -124,7 +131,9 @@ WriteMakefile() arguments.
     depend => { '$(FIRST_MAKEFILE)' => '$(VERSION_FROM)' }
 
 
-=item How do I make two or more XS files coexist in the same directory?
+=item
+
+How do I make two or more XS files coexist in the same directory?
 
 Sometimes you need to have two and more XS files in the same package.
 One way to go is to put them into separate directories, but sometimes

diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 91bb0f8..230c105 100644 (file)
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -1079,17 +1079,30 @@ portable concept.  Similarly for the qx and system: how well will the
 
 =over 4
 
-=item chmod, chmod, chown, chroot, exec, link, mkdir, rename, rmdir, stat, symlink, truncate, unlink, utime
+=item *
+
+chmod, chmod, chown, chroot, exec, link, mkdir
+rename, rmdir stat, symlink, truncate, unlink, utime
+
+=item *
+
+%ENV
+
+=item *
+
+glob (aka the <*>)
+
+=item *
 
-=item %ENV
+open, opendir, sysopen
 
-=item glob (aka the <*>)
+=item *
 
-=item open, opendir, sysopen
+qx (aka the backtick operator), system
 
-=item qx (aka the backtick operator), system
+=item *
 
-=item readdir, readlink
+readdir, readlink
 
 =back