* James E Keenan <[EMAIL PROTECTED]> [2005-12-25 03:05]: > Why was I getting this error message running on one module but > not on another? > > I googled for the error message. The pages I found didn't > exactly clarify the problem for me.
Use the source, Luke. I hit http://search.cpan.org/dist/Storable where I was led to http://search.cpan.org/src/AMS/Storable-2.15/Storable.xs where searching for [binary image] brought up a few debugging and croak messages; the one which corresponds to your error message is found in a conditional block that’s preceded by the following comment: /* * Inter-operability sanity check: we can't retrieve * something stored using a format more recent than ours, * because we have no way to know what has changed, and * letting retrieval go would mean a probable failure * reporting a "corrupted" storable file. */ Devel::Cover is a red herring. What you’re seeing has nothing to do with it and everything to do with Storable – either a problem in your installation or a bug in the module. The ChangeLog for Storable has this illuminating entry: > Fri May 17 22:48:59 BST 2002 Nicholas Clark <[EMAIL PROTECTED]> > > 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 still 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. The whole thing is too long to paste here, read it over there. It seems there is some versioning magic depending on the version of `perl` which sometimes goes wrong. Since Google suggests that this is such a frequent issue, you might want to get in touch with the maintainer to discuss whether there is a bug to be hunted down or a POD amendment to document what users should do when they encounter this. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
