Bundle vivify_ref()

[perl/modules/autovivification.git] / Changes

diff --git a/Changes b/Changes
index 7489b0faf7c15ab7c0466434f186cf3920a343b2..633707a69b82eefb14683b501f1f2671a9c8e865 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,5 +1,35 @@
 Revision history for autovivification
 
+0.15    2015-05-14 20:35 UTC
+        + Chg : The new environment variable to enable thread tests on older
+                perls is PERL_FORCE_TEST_THREADS. Note that this variable
+                should only be turned on by authors.
+        + Fix : The module has been taught about the new multideref
+                optimization, and will function properly on perl 5.21.11 and
+                above.
+        + Fix : The module will no longer crash or behave erratically when it
+                is loaded by several threads (or Windows emulated processes)
+                ran in parallel.
+        + Fix : Update the Windows ActivePerl + gcc 3.4 workaround for
+                ExtUtils::MakeMaker 7.04. Thanks Christian Walde for reporting
+                and feedback on this issue.
+        + Fix : Be really compatible with the optional OP_PARENT feature.
+        + Tst : $ENV{$Config{ldlibpthname}} is now preserved on all platforms,
+                which will address failures of t/43-peep.t and
+                t/51-threads-teardown.t with unusual compilers (like icc) that
+                link all their compiled objects to their own libraries.
+
+0.14    2014-11-01 22:25 UTC
+        + Fix : [RT #99458] : AnyEvent::Loop hangs if autovivification 0.13 is
+                loaded
+                [RT #99904] : 'no autovivification' breaks Lingua::EN::Inflect
+                from a distance
+                This was a regression in 0.13 which caused the peephole
+                optimizer to loop infinitely on "... while 1" constructs.
+                However, the Lingua::EN::Inflect problem only occured in perl
+                5.20 and above.
+                Thanks Toshio Ito and Kent Fredric for reporting.
+
 0.13    2014-10-04 16:55 UTC
         This release contains a change that, while being very likely to be safe,
         can potentially cause freezes during code compilation. Every release