Anybody who has been coding Perl since "1995", and has been here on PM longer than I have should know that the first thing to do when a bug is discovered in a module is to report it via the official bug tracker for the software. On Storable's (and all other's) CPAN page, this link is located at the right side of the page. On its (or any) listing on metacpan, click on "Issues", on the left hand side.

I feel it very irresponsible and disrespectful to blatantly state that a module is not fit for use as you have. As SuicideJunkie pointed out, Storable has been in core since pre-5.8.0. You should know as well as I that the perl5-porters maintain core modules (with over/insight by the original author, per perlpolicy), and that for core issues, one would email the perl5-porters list with their complaints before recommending against the use of a module.

Personally, I can't say one way or another that I'm a good coder or not, but I'd be pretty disturbed if someone was recommending against the use of one of my modules, if the person doing so didn't even take the time to inform me through one of many channels about the problems that bring one to such outright contempt.

In reply to Re^2: Writing indexed arrays in to an file and then retrieved by stevieb
in thread Writing indexed arrays in to an file and then retrieved by perlmuser

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.