X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=ext%2FStorable%2FChangeLog;h=a182162ba8c10d92ecf6e0e4bacea6db28c1f0ee;hb=e9d185f8391f09209c11be82e97358d853f1ba30;hp=c281ab9ec647dc94d4d87d05d9c04931e6c9a2ad;hpb=25f64a11de689eea2260b6bdee0819ca648746ff;p=p5sagit%2Fp5-mst-13.2.git diff --git a/ext/Storable/ChangeLog b/ext/Storable/ChangeLog index c281ab9..a182162 100644 --- a/ext/Storable/ChangeLog +++ b/ext/Storable/ChangeLog @@ -1,3 +1,165 @@ +Mon May 23 22:48:49 IST 2005 Abhijit Menon-Sen + + Version 2.15 + + Minor changes to address a couple of compile problems. + +Mon Apr 25 07:29:14 IST 2005 Abhijit Menon-Sen + + Version 2.14 + + 1. Store weak references + 2. Add STORABLE_attach hook. + +Thu Jun 17 12:26:43 BST 2004 Nicholas Clark + + Version 2.13 + + 1. Don't change the type of top level overloaded references to RV - + they are perfectly correct as PVMG + 2. Storable needs to cope with incoming frozen data that happens to be + utf8 encoded. + +Wed Mar 17 15:40:29 GMT 2004 Nicholas Clark + + Version 2.12 + + 1. Add regression tests for the auto-require of STORABLE_thaw + 2. Add auto-require of modules to restore overloading (and tests) + 3. Change to no context (should give speedup with ithreads) + +Sat Mar 13 20:11:03 GMT 2004 Nicholas Clark + + Version 2.11 + + 1. Storing restricted hashes in canonical order would SEGV. Fixed. + 2. It was impossible to retrieve references to PL_sv_no and and + PL_sv_undef from STORABLE_thaw hooks. + 3. restrict.t was failing on 5.8.0, due to 5.8.0's unique + implementation of restricted hashes using PL_sv_undef + 4. These changes allow a space optimisation for restricted hashes. + +Sat Jan 24 16:22:32 IST 2004 Abhijit Menon-Sen + + Version 2.10 + + 1. Thread safety: Storable::CLONE/init_perlinterp() now create + a new Perl context for each new ithread. + (From Stas Bekman and Jan Dubois.) + 2. Fix a tag count mismatch with $Storable::Deparse that caused + all back-references after a stored sub to be off-by-N (where + N was the number of code references in between). + (From Sam Vilain.) + 3. Prevent CODE references from turning into SCALAR references. + (From Slaven Rezic.) + +Sat Jan 3 18:49:18 GMT 2004 Nicholas Clark + + Version 2.09 + + Fix minor problems with the CPAN release + 1: Make Storable.xs work on 5.8.2 and later (already in the core) + 2: Ship the linux hints file + 3: Ship Test::More for the benefit of Perls pre 5.6.2 + 4: Correct Makefile.PL to only install in core for 5.8.0 and later + +Sat Sep 6 01:08:20 IST 2003 Abhijit Menon-Sen + + Version 2.08 + + This release works around a 5.8.0 bug which caused hashes to not + be marked as having key flags even though an HEK had HEK_WASUTF8 + set. (Note that the only reasonable solution is to silently drop + the flag from the affected key.) + + Users of RT 3 who were seeing assertion failures should upgrade. + (Perl 5.8.1 will have the bug fixed.) + +Mon May 5 10:24:16 IST 2003 Abhijit Menon-Sen + + Version 2.07 + + Minor bugfixes (self-tied objects are now correctly stored, as + are the results of additions larger than INT_MAX). + +Mon Oct 7 21:56:38 BST 2002 Nicholas Clark + + Version 2.06 + + Remove qr// from t/downgrade.t so that it will run on 5.004 + Mention $File::Spec::VERSION a second time in t/forgive.t so that it + runs without warnings in 5.004 (this may be a 5.00405 bug I'm working + round) + Fix t/integer.t initialisation to actually generate 64 bits of 9c + Fix comparison tests to use eval to get around 64 bit IV conversion + issues on 5.6.x, following my t/integer.t ^ precedence bug found by + Rafael Garcia-Suarez + Alter t/malice.t to work with Test/More.pm in t/, and skip individual + subtests that use $Config{ptrsize}, so that the rest of the test can + now be run with 5.004 + Change t/malice.t and the error message in check_magic in Storable.xs + from "Pointer integer size" to "Pointer size" + Remove prerequisite of Test::More from Makefile.PL + Ship Test::Builder, Test::Simple and Test::More in t + +Thu Oct 3 08:57:22 IST 2002 Abhijit Menon-Sen + + Version 2.05 + + Adds support for CODE references from Slaven Rezic + . + +Fri Jun 7 23:55:41 BST 2002 Nicholas Clark + + Version 2.04 + + Bug fix from Radu Greab (plus regression test) + to fix a recently introduced bug detected by Dave Rolsky. + Bug was that for a non threaded build, the class information was + being lost at freeze time on the first object with a STORABLE_freeze + hook. Consequentially the object was not blessed at all when thawed. + (The presence (or lack) of STORABLE_thaw was irrelevant; this was + a store-time data lost bug, caused by failure to initialize internal + context) + The bug was introduced as development perl change 16442 (on + 2002/05/07), so has been present since 2.00. + Patches to introduce more regression tests to reduce the chance of + a reoccurance of this sort of goof are always welcome. + +Thu May 30 20:31:08 BST 2002 Nicholas Clark + + Version 2.03 Header changes on 5.6.x on Unix where IV is long long + + 5.6.x introduced the ability to have IVs as long long. However, + Configure still defined BYTEORDER based on the size of a long. + Storable uses the BYTEORDER value as part of the header, but + doesn't explicity store sizeof(IV) anywhere in the header. + Hence on 5.6.x built with IV as long long on a platform that + uses Configure (ie most things except VMS and Windows) headers + are identical for the different IV sizes, despite the files + containing some fields based on sizeof(IV) + + 5.8.0 is consistent; all platforms have BYTEORDER in config.h + based on sizeof(IV) rather than sizeof(long). This means that + the value of BYTEORDER will change from (say) 4321 to 87654321 + between 5.6.1 and 5.8.0 built with the same options to Configure + on the same machine. This means that the Storable header will + differ, and the two versions will wrongly thing that they are + incompatible. + + For the benefit of long term consistency, Storable now + implements the 5.8.0 BYTEORDER policy on 5.6.x. This means that + 2.03 onwards default to be incompatible with 2.02 and earlier + (ie the large 1.0.x installed base) on the same 5.6.x perl. + + To allow interworking, a new variable + $Storable::interwork_56_64bit is introduced. It defaults to + false. Set it to true to read and write old format files. Don't + use it unless you have existing stored data written with 5.6.x + that you couldn't otherwise read, or you need to interwork with + a machine running older Storable on a 5.6.x with long long IVs + (i.e., you probably don't need to use it). + Sat May 25 22:38:39 BST 2002 Nicholas Clark Version 2.02