+++ -   Thu Nov 10 21:32:08 2005
@@ -536,7 +536,7 @@
 sub _print_and_exit {
     my ($pod, $paged) = @_;

-    if (-t *STDOUT and eval { require POD::Text }) {
+    if (-t *STDOUT and eval { require Pod::Text }) {
         if ($paged) {
             eval { require IO::Page } or eval { require IO::Pager::Page };
         }
@@ -1218,11 +1218,11 @@

 This argument cause the program to print the complete POD documentation
 for the program and exit. If the standard output stream is connected to
-a terminal and the POD::Text module is available, the POD is formatted
+a terminal and the Pod::Text module is available, the POD is formatted
 before printing. If the IO::Page or IO::Pager::Page module is available,
 the formatted documentation is then paged.

-If standard output is not connected to a terminal or POD::Text is not
+If standard output is not connected to a terminal or Pod::Text is not
 available, the POD is not formatted.

 =item --version

</c>

<p>Welcome, ladies and gentlemen, to The Perl Gallery.</p>

<p>This evening we take look at the unholy mix of [doc://map] and [doc://return].</p>

<p>Let's begin with the argument-less form of <tt>return</tt>.  How often have we seen a routine that ends in a plain <tt>return;</tt>?  "Oh, that just returns <tt>undef</tt>."  Really?  Consider this:
<c>
sub nasty {
  if ( $_[ 0 ] % 3 ) {
    return $_[ 0 ];
  }
  else {
    return;
  }
}

my @x = map nasty( $_ ), 1..10;
</c>
Quick, how many elements in <tt>@x</tt>?  7 or 10?
</c>


<blockquote><em><p>
</p></em></blockquote>

<code>