A couple documentation fixes

diff --git a/Changes b/Changes
index 84aa1b1..d6066b3 100644 (file)
--- a/Changes
+++ b/Changes
@@ -4,11 +4,13 @@ Revision history for DBM::Deep.
     - (This version is compatible with 1.0007)
     - Fixed a number of Win32 issues (Reported by Steven Samelson - thank you!)
         - Much thanks to Nigel Sandever and David Golden for their help
-        debugging the issues, particularly with DBM::Deep's usage of
-        File::Temp which removes a number of warnings.
+          debugging the issues, particularly with DBM::Deep's usage of
+          File::Temp (which removes a number of warnings).
         - Autovivification now works on Win32. It turns out that when a
-        process takes a shared flock on a file, it's not allowed to write to
-        it under Win32, unlike *nix. This is probably a good catch.
+          process takes a shared flock on a file, it's not allowed to write to
+          it under Win32, unlike *nix. This is probably a good catch.
+            - Note: The fix is a hack. All locks are now exclusive until a
+              better fix is found.
 
 1.0007 Jan 10 00:00:00 2008 EDT
     - (This version is compatible with 1.0006)

diff --git a/lib/DBM/Deep.pod b/lib/DBM/Deep.pod
index d7fe1ed..0711b5e 100644 (file)
--- a/lib/DBM/Deep.pod
+++ b/lib/DBM/Deep.pod
@@ -582,6 +582,12 @@ L<Fcntl/> module.
   # something here
   $db->unlock();
 
+=head2 Win32/Cygwin
+
+Due to Win32 actually enforcing the read-only status of a shared lock, all
+locks on Win32 and cygwin are exclusive. This is because of how autovivification
+currently works. Hopefully, this will go away in a future release.
+
 =head1 IMPORTING/EXPORTING
 
 You can import existing complex structures by calling the C<import()> method,