But the second file fails with "Corrupted storable string (binary v2.7)" *unless* I add this, in which case it works fineuse Storable qw/thaw/; use Data::Dump qw/dump/; use Encode qw/decode decode_utf8/; my $file = shift; open (my $fh, "<:raw", $file) || die $!; my $contents = join '', <$fh>; dump thaw $contents;
$contents = decode_utf8($contents);
Though with that code the *first* file fails with "Frozen string corrupt - contains characters outside 0-255", and actually doing "decode('utf-8-strict', $contents, 1)" on the first file throws utf8 "\xDD" does not map to Unicode", though it works ok on the second file.
I'm unable to even imagine why Storable::thaw would expect to be working with logical Perl characters instead of bytes, and came here looking for some clue as to what might be going on.
AFAICT there aren't any non-ascii characters in either data structure.
Versions:
No, I can't post the original data here, it's quite large.$ perl -v This is perl, v5.10.1 (*) built for x86_64-linux-gnu-thread-multi (with 61 registered patches, see perl -V for more detail) ... $ perl -MStorable -le 'print Storable->VERSION' 2.20
In reply to storable and utf8 by kgoess
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |