UCD 5.1.0

[p5sagit/p5-mst-13.2.git] / pod / perlmodlib.PL

diff --git a/pod/perlmodlib.PL b/pod/perlmodlib.PL
index 969dde9..b7e5bf3 100644 (file)
--- a/pod/perlmodlib.PL
+++ b/pod/perlmodlib.PL
@@ -10,6 +10,8 @@ open (MANIFEST, "../MANIFEST") or die $!;
 push @MANIFEST, 'lib/Config.pod', 'lib/Errno.pm', 'lib/lib.pm',
     'lib/DynaLoader.pm', 'lib/XSLoader.pm';
 
+-f "../lib/DynaLoader.pm" or die "Must be run from a source tree where perl has been built\n";
+
 for (@MANIFEST) {
      my $filename;
      next unless s|^lib/|| or m|^ext/|;
@@ -49,6 +51,9 @@ for (@MANIFEST) {
      $perlname =~ s!\b(\w+)/\1\b!$1!;
      $perlname =~ s!/!::!g;
 
+     # modules with non standard locations
+     $perlname =~ s{Base64::QuotedPrint}{QuotedPrint};
+
      ($name, $thing) = split / --? /, $title, 2;
 
      unless ($name and $thing) {
@@ -1070,8 +1075,8 @@ the module after __END__ either using AutoSplit or by saying:
 Does your module pass the 'empty subclass' test? If you say
 C<@SUBCLASS::ISA = qw(YOURCLASS);> your applications should be able
 to use SUBCLASS in exactly the same way as YOURCLASS.  For example,
-does your application still work if you change:  C<$obj = new YOURCLASS;>
-into: C<$obj = new SUBCLASS;> ?
+does your application still work if you change:  C<< $obj = YOURCLASS->new(); >>
+into: C<< $obj = SUBCLASS->new(); >> ?
 
 Avoid keeping any state information in your packages. It makes it
 difficult for multiple other packages to use yours. Keep state