What's the fracking point? What purpose does Storable serve if one can't rely on it to recover the data again?

The point is to know the limitations of your tools and to keep your tools current. 

Fri May 17 22:48:59 BST 2002   Nicholas Clark <nick@ccl4.org>

    Version 2.0, binary format 2.5 (but writes format 2.4 on pre 5.7.3
+)

        The perl5 porters have decided to make sure that Storable stil
+l
        builds on pre-5.8 perls, and make the 5.8 version available on
+ CPAN.
        The VERSION is now 2.0, and it passes all tests on 5.005_03, 5
+.6.1
        and 5.6.1 with threads. On 5.6.0 t/downgrade.t fails tests 34 
+and 37,
        due to a bug in 5.6.0 - upgrade to 5.6.1.

        Jarkko and I have collated the list of changes the perl5 porte
+rs have
        from the perl5 Changes file:

        - data features of upcoming perl 5.8.0 are supported: Unicode 
+hash
          keys (Unicode hash values have been supported since Storable
+ 1.0.1)
          and "restricted hashes" (readonly hashes and hash entries)
        - a newer version of perl can now be used to serialize data wh
+ich is
          not supported in earlier perls: Storable will attempt to do 
+the
          right thing for as long as possible, croaking only when safe
+ data
          conversion simply isn't possible. Alternatively earlier perl
+s can
          opt to have a lossy downgrade data instead of croaking
        - when built with perls pre 5.7.3 this Storable writes out fil
+es
          with binary format 2.4, the same format as Storable 1.0.8 on
+wards.
          This should mean that this Storable will inter-operate seaml
+essly
          with any Storable 1.0.8 or newer on perls pre 5.7.3
        - dclone() now works with empty string scalar objects
        - retrieving of large hashes is now more efficient
        - more routines autosplit out of the main module, so Storable 
+should
          load slightly more quickly
        - better documentation
        - the internal context objects are now freed explicitly, rathe
+r than
          relying on thread or process exit
        - bugs fixed in debugging trace code affecting builds made wit
+h 64 bit
          IVs
        - code tidy-ups to allow clean compiles with more warning opti
+ons
          turned on avoid problems with $@ getting corrupted on 5.005_
+03 if
          Carp wasn't already loaded
        - added &show_file_magic, so you can add to /etc/magic and tea
+ch
          Unix's file command about Storable files

        We plan to keep Storable on CPAN in sync with the Perl core, s
+o
        if you encounter bugs or other problems building or using Stor
+able,
        please let us know at perl5-porters@perl.org
        Patches welcome!

[download]

In reply to Re: Burned by Storable by Anonymous Monk
in thread Burned by Storable by ruzam

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.