Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Clone::clone in 5.10 borken? 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Just for giggles, using Storable::dclone works just dandily, but I didn't use it in 5.8 because for one line of code, it's a pain in the ass as a prereq, esp on windows sometimes.

    This would be the Storable that has been in core as of 5.8.0? And built and installed by default? So what's the problem with making it a prerequisite?

    • Can't speak for Chris, but for me it is horribly broken if at any time you upgrade. Anything made with a specific version of Storable will ONLY work with that version of Storable. The data file also breaks between different OSs even with the same version. In a previous project I ended up moving to XML because it actually was persistent!

      It may have changed since, but these days I avoid it wherever possible.

      • The data file also breaks between different OSs even with the same version.

        The default file format is architecture specific, for speed. If you want to move things between systems (or perl configurations) you want nstore or nfreeze.

        As to between versions - yes, there was a bug in the version checking code, based on the intent. It used to (wrongly) insist that the major and minor versions of the file were identical, and as the minor version had often been bumped, that meant problems. Some time ago (I forget w

    • This is also the same Storable that constantly dies of gets wrong cloning with "Can't store CODE items" errors. Another problem Clone::clone never has.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.