Add a note in perltodo about a potential extension of readpipe()

[p5sagit/p5-mst-13.2.git] / pod / perldbmfilter.pod

diff --git a/pod/perldbmfilter.pod b/pod/perldbmfilter.pod
index faed2d2..d62e496 100644 (file)
--- a/pod/perldbmfilter.pod
+++ b/pod/perldbmfilter.pod
@@ -86,11 +86,12 @@ sure you have already guessed, this is a problem that DBM Filters can
 fix very easily.
 
     use strict ;
+    use warnings ;
     use SDBM_File ;
     use Fcntl ;
 
     my %hash ;
-    my $filename = "/tmp/filt" ;
+    my $filename = "filt" ;
     unlink $filename ;
 
     my $db = tie(%hash, 'SDBM_File', $filename, O_RDWR|O_CREAT, 0640)
@@ -99,7 +100,8 @@ fix very easily.
     # Install DBM Filters
     $db->filter_fetch_key  ( sub { s/\0$//    } ) ;
     $db->filter_store_key  ( sub { $_ .= "\0" } ) ;
-    $db->filter_fetch_value( sub { s/\0$//    } ) ;
+    $db->filter_fetch_value( 
+        sub { no warnings 'uninitialized' ;s/\0$// } ) ;
     $db->filter_store_value( sub { $_ .= "\0" } ) ;
 
     $hash{"abc"} = "def" ;
@@ -122,7 +124,7 @@ Here is another real-life example. By default, whenever Perl writes to
 a DBM database it always writes the key and value as strings. So when
 you use this:
 
-    $hash{12345} = "soemthing" ;
+    $hash{12345} = "something" ;
 
 the key 12345 will get stored in the DBM database as the 5 byte string
 "12345". If you actually want the key to be stored in the DBM database
@@ -132,9 +134,10 @@ when reading.
 Here is a DBM Filter that does it:
 
     use strict ;
+    use warnings ;
     use DB_File ;
     my %hash ;
-    my $filename = "/tmp/filt" ;
+    my $filename = "filt" ;
     unlink $filename ;