Update CPANPLUS to 0.79_01

[p5sagit/p5-mst-13.2.git] / lib / Memoize / Expire.pm

diff --git a/lib/Memoize/Expire.pm b/lib/Memoize/Expire.pm
index 8bd5999..97e1aa4 100644 (file)
--- a/lib/Memoize/Expire.pm
+++ b/lib/Memoize/Expire.pm
@@ -3,7 +3,7 @@ package Memoize::Expire;
 # require 5.00556;
 use Carp;
 $DEBUG = 0;
-$VERSION = '0.66';
+$VERSION = '1.00';
 
 # This package will implement expiration by prepending a fixed-length header
 # to the font of the cached data.  The format of the header will be:
@@ -311,15 +311,10 @@ the underlying cache so that the user can specify that the cache is
 also persistent or that it has some other interesting semantics.  The
 example above demonstrates how to do this, as does C<Memoize::Expire>.
 
-Another sample module, C<Memoize::Saves>, is included with this
-package.  It implements a policy that allows you to specify that
-certain function values whould always be looked up afresh.  See the
-documentation for details.
-
 =head1 ALTERNATIVES
 
 Brent Powers has a C<Memoize::ExpireLRU> module that was designed to
-wotk with Memoize and provides expiration of least-recently-used data.
+work with Memoize and provides expiration of least-recently-used data.
 The cache is held at a fixed number of entries, and when new data
 comes in, the least-recently used data is expired.  See
 L<http://search.cpan.org/search?mode=module&query=ExpireLRU>.
@@ -344,7 +339,7 @@ with a lifetime of ten seconds, and you store it at 12:00:00.998 on a
 certain day.  Memoize will look at the clock and see 12:00:00.  Then
 9.01 seconds later, at 12:00:10.008 you try to read it back.  Memoize
 will look at the clock and see 12:00:10 and conclude that the value
-has expired.  This will probably not occur if if you have
+has expired.  This will probably not occur if you have
 C<Time::HiRes> installed.
 
 =head1 AUTHOR