in reply to Storable.pm - corrupt when saving to non-truncated file

I used to like Storable.

I don’t, anymore.

What has been remarkably satisfactory for me is ... YAML.   (There are several flavors of it, including some modules that are “Pure Perl.”)   One very nice advantage of it is that ... it is readable by humans.   You can plainly see what it says.   If storage space happens to be a genuine issue, it is also easily compressible by Zip/deflate and the like...

With Storable, I was fairly awash with “stored” things that I couldn’t actually retrieve.   When I started using YAML, the problems vanished and never returned.   (Of course, all of the things that I actually need to store, are things that YAML can represent.   Your Mileage May Vary.™)

Replies are listed 'Best First'.
Re^2: Storable.pm - corrupt when saving to non-truncated file
by andreas1234567 (Vicar) on Nov 25, 2010 at 14:17 UTC
    I used to like Storable. I don’t, anymore.
    Same story here.
    With Storable, I was fairly awash with “stored” things that I couldn’t actually retrieve.
    Same here. Migration between 32-bit and 64-bit architectures, or between little-endian and big-endian architectures was a nightmare with Storable. Yes, I know there nfreeze supposedly solved (some of) this, but not when one didn't use Storable this way right from the start.

    Now with JSON or YAML there are few good reasons to use Storable IMHO.

    --
    No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]
[reply]
[d/l]

In Section Seekers of Perl Wisdom