Oops. I replied to this on the RT site, but it looks like I neglected to tell it to copy the list (or you). I'll cutpaste my response below.
On Tue, 21 Aug 2007 21:02:39 -0400 James E Keenan <[EMAIL PROTECTED]> wrote: > I do have some qualms. > > (1) I know that there have been issues with incompatibility among > different versions of Storable. I myself have been bit by these > issues with different versions of Storable distributed with different > versions of Perl 5.8 (not to mention 5.6). Some of these issues are > alluded to in the POD > (http://search.cpan.org/dist/Storable/Storable.pm#FORWARD_COMPATIBILITY). > I have never heard such compatibility issues with respect to > Data::Dumper. This is not a killer objection, but it should be > considered. > > (2) Not that I'm opposed to Storable entirely. Hey, I use it in > Parrot::Configure::Trace! But there, as in other places I've used > it, I've always found I got better mileage by using 'nstore' instead > of 'store'. Hi! I agree, nstore is more useful for stuff that's kept around for a while, exchanged between machines and so forth. But, keeping in mind these files are built by pmc2c.pl as part of the parrot build process, rebuilt whenever the pmc file changes, and removed whenever you do a "make clean", does forwards compatibility (or even endian-portability) actually matter? Correct me if I'm wrong, but I don't think we keep any of these files around. Mark
