.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH Storable 3 "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide"
Storable \- persistence for Perl data structures
\& store \e%table, 'file';
\& $hashref = retrieve('file');
\& use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);
\& nstore \e%table, 'file';
\& $hashref = retrieve('file'); # There is NO nretrieve()
\& # Storing to and retrieving from an already opened file
\& store_fd \e@array, \e*STDOUT;
\& nstore_fd \e%table, \e*STDOUT;
\& $aryref = fd_retrieve(\e*SOCKET);
\& $hashref = fd_retrieve(\e*SOCKET);
\& # Serializing to memory
\& $serialized = freeze \e%table;
\& %table_clone = %{ thaw($serialized) };
\& # Deep (recursive) cloning
\& $cloneref = dclone($ref);
\& use Storable qw(lock_store lock_nstore lock_retrieve)
\& lock_store \e%table, 'file';
\& lock_nstore \e%table, 'file';
\& $hashref = lock_retrieve('file');
The Storable package brings persistence to your Perl data structures
containing \s-1SCALAR\s0, \s-1ARRAY\s0, \s-1HASH\s0 or \s-1REF\s0 objects, i.e. anything that can be
conveniently stored to disk and retrieved at a later time.
It can be used in the regular procedural way by calling \f(CW\*(C`store\*(C'\fR with
a reference to the object to be stored, along with the file name where
the image should be written.
The routine returns \f(CW\*(C`undef\*(C'\fR for I/O problems or other internal error,
a true value otherwise. Serious errors are propagated as a \f(CW\*(C`die\*(C'\fR exception.
To retrieve data stored to disk, use \f(CW\*(C`retrieve\*(C'\fR with a file name.
The objects stored into that file are recreated into memory for you,
and a \fIreference\fR to the root object is returned. In case an I/O error
occurs while reading, \f(CW\*(C`undef\*(C'\fR is returned instead. Other serious
errors are propagated via \f(CW\*(C`die\*(C'\fR.
Since storage is performed recursively, you might want to stuff references
to objects that share a lot of common data into a single array or hash
table, and then store that object. That way, when you retrieve back the
whole thing, the objects will continue to share what they originally shared.
At the cost of a slight header overhead, you may store to an already
opened file descriptor using the \f(CW\*(C`store_fd\*(C'\fR routine, and retrieve
from a file via \f(CW\*(C`fd_retrieve\*(C'\fR. Those names aren't imported by default,
so you will have to do that explicitly if you need those routines.
The file descriptor you supply must be already opened, for read
if you're going to retrieve and for write if you wish to store.
\& store_fd(\e%table, *STDOUT) || die "can't store to stdout\en";
\& $hashref = fd_retrieve(*STDIN);
You can also store data in network order to allow easy sharing across
multiple platforms, or when storing on a socket known to be remotely
connected. The routines to call have an initial \f(CW\*(C`n\*(C'\fR prefix for \fInetwork\fR,
as in \f(CW\*(C`nstore\*(C'\fR and \f(CW\*(C`nstore_fd\*(C'\fR. At retrieval time, your data will be
correctly restored so you don't have to know whether you're restoring
from native or network ordered data. Double values are stored stringified
to ensure portability as well, at the slight risk of loosing some precision
When using \f(CW\*(C`fd_retrieve\*(C'\fR, objects are retrieved in sequence, one
object (i.e. one recursive tree) per associated \f(CW\*(C`store_fd\*(C'\fR.
If you're more from the object-oriented camp, you can inherit from
Storable and directly store your objects by invoking \f(CW\*(C`store\*(C'\fR as
a method. The fact that the root of the to-be-stored tree is a
blessed reference (i.e. an object) is special-cased so that the
retrieve does not provide a reference to that object but rather the
blessed object reference itself. (Otherwise, you'd get a reference
.IX Header "MEMORY STORE"
The Storable engine can also store data into a Perl scalar instead, to
later retrieve them. This is mainly used to freeze a complex structure in
some safe compact memory place (where it can possibly be sent to another
process via some \s-1IPC\s0, since freezing the structure also serializes it in
effect). Later on, and maybe somewhere else, you can thaw the Perl scalar
out and recreate the original complex structure in memory.
Surprisingly, the routines to be called are named \f(CW\*(C`freeze\*(C'\fR and \f(CW\*(C`thaw\*(C'\fR.
If you wish to send out the frozen scalar to another machine, use
\&\f(CW\*(C`nfreeze\*(C'\fR instead to get a portable image.
Note that freezing an object structure and immediately thawing it
actually achieves a deep cloning of that structure:
\& dclone(.) = thaw(freeze(.))
Storable provides you with a \f(CW\*(C`dclone\*(C'\fR interface which does not create
that intermediary scalar but instead freezes the structure in some
internal memory space and then immediately thaws it out.
.IX Header "ADVISORY LOCKING"
The \f(CW\*(C`lock_store\*(C'\fR and \f(CW\*(C`lock_nstore\*(C'\fR routine are equivalent to
\&\f(CW\*(C`store\*(C'\fR and \f(CW\*(C`nstore\*(C'\fR, except that they get an exclusive lock on
the file before writing. Likewise, \f(CW\*(C`lock_retrieve\*(C'\fR does the same
as \f(CW\*(C`retrieve\*(C'\fR, but also gets a shared lock on the file before reading.
As with any advisory locking scheme, the protection only works if you
systematically use \f(CW\*(C`lock_store\*(C'\fR and \f(CW\*(C`lock_retrieve\*(C'\fR. If one side of
your application uses \f(CW\*(C`store\*(C'\fR whilst the other uses \f(CW\*(C`lock_retrieve\*(C'\fR,
you will get no protection at all.
The internal advisory locking is implemented using Perl's \fIflock()\fR
routine. If your system does not support any form of \fIflock()\fR, or if
you share your files across \s-1NFS\s0, you might wish to use other forms
of locking by using modules such as LockFile::Simple which lock a
file using a filesystem entry, instead of locking the file descriptor.
The heart of Storable is written in C for decent speed. Extra low-level
optimizations have been made when manipulating perl internals, to
sacrifice encapsulation for the benefit of greater speed.
.SH "CANONICAL REPRESENTATION"
.IX Header "CANONICAL REPRESENTATION"
Normally, Storable stores elements of hashes in the order they are
stored internally by Perl, i.e. pseudo\-randomly. If you set
\&\f(CW$Storable::canonical\fR to some \f(CW\*(C`TRUE\*(C'\fR value, Storable will store
hashes with the elements sorted by their key. This allows you to
compare data structures by comparing their frozen representations (or
even the compressed frozen representations), which can be useful for
creating lookup tables for complicated queries.
Canonical order does not imply network order; those are two orthogonal
.SH "FORWARD COMPATIBILITY"
.IX Header "FORWARD COMPATIBILITY"
This release of Storable can be used on a newer version of Perl to
serialize data which is not supported by earlier Perls. By default,
Storable will attempt to do the right thing, by \f(CW\*(C`croak()\*(C'\fRing if it
encounters data that it cannot deserialize. However, the defaults
can be changed as follows:
Perl 5.6 added support for Unicode characters with code points > 255,
and Perl 5.8 has full support for Unicode characters in hash keys.
Perl internally encodes strings with these characters using utf8, and
Storable serializes them as utf8. By default, if an older version of
Perl encounters a utf8 value it cannot represent, it will \f(CW\*(C`croak()\*(C'\fR.
To change this behaviour so that Storable deserializes utf8 encoded
values as the string of bytes (effectively dropping the \fIis_utf8\fR flag)
set \f(CW$Storable::drop_utf8\fR to some \f(CW\*(C`TRUE\*(C'\fR value. This is a form of
data loss, because with \f(CW$drop_utf8\fR true, it becomes impossible to tell
whether the original data was the Unicode string, or a series of bytes
that happen to be valid utf8.
.IP "restricted hashes" 4
.IX Item "restricted hashes"
Perl 5.8 adds support for restricted hashes, which have keys
restricted to a given set, and can have values locked to be read only.
By default, when Storable encounters a restricted hash on a perl
that doesn't support them, it will deserialize it as a normal hash,
silently discarding any placeholder keys and leaving the keys and
all values unlocked. To make Storable \f(CW\*(C`croak()\*(C'\fR instead, set
\&\f(CW$Storable::downgrade_restricted\fR to a \f(CW\*(C`FALSE\*(C'\fR value. To restore
the default set it back to some \f(CW\*(C`TRUE\*(C'\fR value.
.IP "files from future versions of Storable" 4
.IX Item "files from future versions of Storable"
Earlier versions of Storable would immediately croak if they encountered
a file with a higher internal version number than the reading Storable
knew about. Internal version numbers are increased each time new data
types (such as restricted hashes) are added to the vocabulary of the file
format. This meant that a newer Storable module had no way of writing a
file readable by an older Storable, even if the writer didn't store newer
This version of Storable will defer croaking until it encounters a data
type in the file that it does not recognize. This means that it will
continue to read files generated by newer Storable modules which are careful
in what they write out, making it easier to upgrade Storable modules in a
The old behaviour of immediate croaking can be re-instated by setting
\&\f(CW$Storable::accept_future_minor\fR to some \f(CW\*(C`FALSE\*(C'\fR value.
All these variables have no effect on a newer Perl which supports the
.IX Header "ERROR REPORTING"
Storable uses the \*(L"exception\*(R" paradigm, in that it does not try to workaround
failures: if something bad happens, an exception is generated from the
caller's perspective (see Carp and \f(CW\*(C`croak()\*(C'\fR). Use eval {} to trap
When Storable croaks, it tries to report the error via the \f(CW\*(C`logcroak()\*(C'\fR
routine from the \f(CW\*(C`Log::Agent\*(C'\fR package, if it is available.
Normal errors are reported by having \fIstore()\fR or \fIretrieve()\fR return \f(CW\*(C`undef\*(C'\fR.
Such errors are usually I/O errors (or truncated stream errors at retrieval).
.IX Header "WIZARDS ONLY"
Any class may define hooks that will be called during the serialization
and deserialization process on objects that are instances of that class.
Those hooks can redefine the way serialization is performed (and therefore,
how the symmetrical deserialization should be conducted).
\& dclone(.) = thaw(freeze(.))
everything we say about hooks should also hold for deep cloning. However,
hooks get to know whether the operation is a mere serialization, or a cloning.
Therefore, when serializing hooks are involved,
\& dclone(.) <> thaw(freeze(.))
Well, you could keep them in sync, but there's no guarantee it will always
hold on classes somebody else wrote. Besides, there is little to gain in
doing so: a serializing hook could keep only one attribute of an object,
which is probably not what should happen during a deep cloning of that
Here is the hooking interface:
.ie n .IP """STORABLE_freeze""\fR \fIobj\fR, \fIcloning" 4
.el .IP "\f(CWSTORABLE_freeze\fR \fIobj\fR, \fIcloning\fR" 4
.IX Item "STORABLE_freeze obj, cloning"
The serializing hook, called on the object during serialization. It can be
inherited, or defined in the class itself, like any other method.
Arguments: \fIobj\fR is the object to serialize, \fIcloning\fR is a flag indicating
whether we're in a \fIdclone()\fR or a regular serialization via \fIstore()\fR or \fIfreeze()\fR.
Returned value: A \s-1LIST\s0 \f(CW\*(C`($serialized, $ref1, $ref2, ...)\*(C'\fR where \f(CW$serialized\fR
is the serialized form to be used, and the optional \f(CW$ref1\fR, \f(CW$ref2\fR, etc... are
extra references that you wish to let the Storable engine serialize.
At deserialization time, you will be given back the same \s-1LIST\s0, but all the
extra references will be pointing into the deserialized structure.
The \fBfirst time\fR the hook is hit in a serialization flow, you may have it
return an empty list. That will signal the Storable engine to further
discard that hook for this class and to therefore revert to the default
serialization of the underlying Perl data. The hook will again be normally
processed in the next serialization.
Unless you know better, serializing hook should always say:
\& my ($self, $cloning) = @_;
\& return if $cloning; # Regular default serialization
in order to keep reasonable \fIdclone()\fR semantics.
.ie n .IP """STORABLE_thaw""\fR \fIobj\fR, \fIcloning\fR, \fIserialized, ..." 4
.el .IP "\f(CWSTORABLE_thaw\fR \fIobj\fR, \fIcloning\fR, \fIserialized\fR, ..." 4
.IX Item "STORABLE_thaw obj, cloning, serialized, ..."
The deserializing hook called on the object during deserialization.
But wait: if we're deserializing, there's no object yet... right?
Wrong: the Storable engine creates an empty one for you. If you know Eiffel,
you can view \f(CW\*(C`STORABLE_thaw\*(C'\fR as an alternate creation routine.
This means the hook can be inherited like any other method, and that
\&\fIobj\fR is your blessed reference for this particular instance.
The other arguments should look familiar if you know \f(CW\*(C`STORABLE_freeze\*(C'\fR:
\&\fIcloning\fR is true when we're part of a deep clone operation, \fIserialized\fR
is the serialized string you returned to the engine in \f(CW\*(C`STORABLE_freeze\*(C'\fR,
and there may be an optional list of references, in the same order you gave
them at serialization time, pointing to the deserialized objects (which
have been processed courtesy of the Storable engine).
When the Storable engine does not find any \f(CW\*(C`STORABLE_thaw\*(C'\fR hook routine,
it tries to load the class by requiring the package dynamically (using
the blessed package name), and then re-attempts the lookup. If at that
time the hook cannot be located, the engine croaks. Note that this mechanism
will fail if you define several classes in the same file, but perlmod
It is up to you to use this information to populate \fIobj\fR the way you want.
.IX Subsection "Predicates"
Predicates are not exportable. They must be called by explicitly prefixing
them with the Storable package name.
.ie n .IP """Storable::last_op_in_netorder""" 4
.el .IP "\f(CWStorable::last_op_in_netorder\fR" 4
.IX Item "Storable::last_op_in_netorder"
The \f(CW\*(C`Storable::last_op_in_netorder()\*(C'\fR predicate will tell you whether
network order was used in the last store or retrieve operation. If you
don't know how to use this, just forget about it.
.ie n .IP """Storable::is_storing""" 4
.el .IP "\f(CWStorable::is_storing\fR" 4
.IX Item "Storable::is_storing"
Returns true if within a store operation (via STORABLE_freeze hook).
.ie n .IP """Storable::is_retrieving""" 4
.el .IP "\f(CWStorable::is_retrieving\fR" 4
.IX Item "Storable::is_retrieving"
Returns true if within a retrieve operation (via STORABLE_thaw hook).
.IX Subsection "Recursion"
With hooks comes the ability to recurse back to the Storable engine.
Indeed, hooks are regular Perl code, and Storable is convenient when
it comes to serializing and deserializing things, so why not use it
to handle the serialization string?
There are a few things you need to know, however:
You can create endless loops if the things you serialize via \fIfreeze()\fR
(for instance) point back to the object we're trying to serialize in
Shared references among objects will not stay shared: if we're serializing
the list of object [A, C] where both object A and C refer to the \s-1SAME\s0 object
B, and if there is a serializing hook in A that says freeze(B), then when
deserializing, we'll get [A', C'] where A' refers to B', but C' refers to D,
a deep clone of B'. The topology was not preserved.
That's why \f(CW\*(C`STORABLE_freeze\*(C'\fR lets you provide a list of references
to serialize. The engine guarantees that those will be serialized in the
same context as the other objects, and therefore that shared objects will
In the above [A, C] example, the \f(CW\*(C`STORABLE_freeze\*(C'\fR hook could return:
\& ("something", $self->{B})
and the B part would be serialized by the engine. In \f(CW\*(C`STORABLE_thaw\*(C'\fR, you
would get back the reference to the B' object, deserialized for you.
Therefore, recursion should normally be avoided, but is nonetheless supported.
.IX Subsection "Deep Cloning"
There is a Clone module available on \s-1CPAN\s0 which implements deep cloning
natively, i.e. without freezing to memory and thawing the result. It is
aimed to replace Storable's \fIdclone()\fR some day. However, it does not currently
support Storable hooks to redefine the way deep cloning is performed.
.IX Header "Storable magic"
Yes, there's a lot of that :\-) But more precisely, in \s-1UNIX\s0 systems
there's a utility called \f(CW\*(C`file\*(C'\fR, which recognizes data files based on
their contents (usually their first few bytes). For this to work,
a certain file called \fImagic\fR needs to taught about the \fIsignature\fR
of the data. Where that configuration file lives depends on the \s-1UNIX\s0
flavour; often it's something like \fI/usr/share/misc/magic\fR or
\&\fI/etc/magic\fR. Your system administrator needs to do the updating of
the \fImagic\fR file. The necessary signature information is output to
\&\s-1STDOUT\s0 by invoking \fIStorable::show_file_magic()\fR. Note that the \s-1GNU\s0
implementation of the \f(CW\*(C`file\*(C'\fR utility, version 3.38 or later,
is expected to contain support for recognising Storable files
out\-of\-the\-box, in addition to other kinds of Perl files.
Here are some code samples showing a possible usage of Storable:
\& use Storable qw(store retrieve freeze thaw dclone);
\& %color = ('Blue' => 0.1, 'Red' => 0.8, 'Black' => 0, 'White' => 1);
\& store(\e%color, '/tmp/colors') or die "Can't store %a in /tmp/colors!\en";
\& $colref = retrieve('/tmp/colors');
\& die "Unable to retrieve from /tmp/colors!\en" unless defined $colref;
\& printf "Blue is still %lf\en", $colref->{'Blue'};
\& $colref2 = dclone(\e%color);
\& $str = freeze(\e%color);
\& printf "Serialization of %%color is %d bytes long.\en", length($str);
\& $colref3 = thaw($str);
which prints (on my machine):
\& Blue is still 0.100000
\& Serialization of %color is 102 bytes long.
If you're using references as keys within your hash tables, you're bound
to be disappointed when retrieving your data. Indeed, Perl stringifies
references used as hash table keys. If you later wish to access the
items via another reference stringification (i.e. using the same
reference that was used for the key originally to record the value into
the hash table), it will work because both references stringify to the
It won't work across a sequence of \f(CW\*(C`store\*(C'\fR and \f(CW\*(C`retrieve\*(C'\fR operations,
however, because the addresses in the retrieved objects, which are
part of the stringified references, will probably differ from the
original addresses. The topology of your structure is preserved,
but not hidden semantics like those.
On platforms where it matters, be sure to call \f(CW\*(C`binmode()\*(C'\fR on the
descriptors that you pass to Storable functions.
Storing data canonically that contains large hashes can be
significantly slower than storing the same data normally, as
temporary arrays to hold the keys for each hash have to be allocated,
populated, sorted and freed. Some tests have shown a halving of the
speed of storing \*(-- the exact penalty will depend on the complexity of
your data. There is no slowdown on retrieval.
You can't store \s-1GLOB\s0, \s-1CODE\s0, \s-1FORMLINE\s0, etc.... If you can define
semantics for those operations, feel free to enhance Storable so that
The store functions will \f(CW\*(C`croak\*(C'\fR if they run into such references
unless you set \f(CW$Storable::forgive_me\fR to some \f(CW\*(C`TRUE\*(C'\fR value. In that
case, the fatal message is turned in a warning and some
meaningless string is stored instead.
Setting \f(CW$Storable::canonical\fR may not yield frozen strings that
compare equal due to possible stringification of numbers. When the
string version of a scalar exists, it is the form stored; therefore,
if you happen to use your numbers as strings between two freezing
operations on the same data structures, you will get different
When storing doubles in network order, their value is stored as text.
However, you should also not expect non-numeric floating-point values
such as infinity and \*(L"not a number\*(R" to pass successfully through a
\&\fInstore()\fR/\fIretrieve()\fR pair.
As Storable neither knows nor cares about character sets (although it
does know that characters may be more than eight bits wide), any difference
in the interpretation of character codes between a host and a target
system is your problem. In particular, if host and target use different
code points to represent the characters used in the text representation
of floating-point numbers, you will not be able be able to exchange
floating-point data, even with \fInstore()\fR.
\&\f(CW\*(C`Storable::drop_utf8\*(C'\fR is a blunt tool. There is no facility either to
return \fBall\fR strings as utf8 sequences, or to attempt to convert utf8
data back to 8 bit and \f(CW\*(C`croak()\*(C'\fR if the conversion fails.
Prior to Storable 2.01, no distinction was made between signed and
unsigned integers on storing. By default Storable prefers to store a
scalars string representation (if it has one) so this would only cause
problems when storing large unsigned integers that had never been coverted
to string or floating point. In other words values that had been generated
by integer operations such as logic ops and then not used in any string or
arithmetic context before storing.
.Sh "64 bit data in perl 5.6.0 and 5.6.1"
.IX Subsection "64 bit data in perl 5.6.0 and 5.6.1"
This section only applies to you if you have existing data written out
by Storable 2.02 or earlier on perl 5.6.0 or 5.6.1 on Unix or Linux which
has been configured with 64 bit integer support (not the default)
If you got a precompiled perl, rather than running Configure to build
your own perl from source, then it almost certainly does not affect you,
and you can stop reading now (unless you're curious). If you're using perl
on Windows it does not affect you.
Storable writes a file header which contains the sizes of various C
language types for the C compiler that built Storable (when not writing in
network order), and will refuse to load files written by a Storable not
on the same (or compatible) architecture. This check and a check on
machine byteorder is needed because the size of various fields in the file
are given by the sizes of the C language types, and so files written on
different architectures are incompatible. This is done for increased speed.
(When writing in network order, all fields are written out as standard
lengths, which allows full interworking, but takes longer to read and write)
Perl 5.6.x introduced the ability to optional configure the perl interpreter
to use C's \f(CW\*(C`long long\*(C'\fR type to allow scalars to store 64 bit integers on 32
bit systems. However, due to the way the Perl configuration system
generated the C configuration files on non-Windows platforms, and the way
Storable generates its header, nothing in the Storable file header reflected
whether the perl writing was using 32 or 64 bit integers, despite the fact
that Storable was storing some data differently in the file. Hence Storable
running on perl with 64 bit integers will read the header from a file
written by a 32 bit perl, not realise that the data is actually in a subtly
incompatible format, and then go horribly wrong (possibly crashing) if it
encountered a stored integer. This is a design failure.
Storable has now been changed to write out and read in a file header with
information about the size of integers. It's impossible to detect whether
an old file being read in was written with 32 or 64 bit integers (they have
the same header) so it's impossible to automatically switch to a correct
backwards compatibility mode. Hence this Storable defaults to the new,
What this means is that if you have data written by Storable 1.x running
on perl 5.6.0 or 5.6.1 configured with 64 bit integers on Unix or Linux
then by default this Storable will refuse to read it, giving the error
\&\fIByte order is not compatible\fR. If you have such data then you you
should set \f(CW$Storable::interwork_56_64bit\fR to a true value to make this
Storable read and write files with the old header. You should also
migrate your data, or any older perl you are communicating with, to this
current version of Storable.
If you don't have data written with specific configuration of perl described
above, then you do not and should not do anything. Don't set the flag \-
not only will Storable on an identically configured perl refuse to load them,
but Storable a differently configured perl will load them believing them
to be correct for it, and then may well fail or crash part way through
Thank you to (in chronological order):
\& Jarkko Hietaniemi <jhi@iki.fi>
\& Ulrich Pfeifer <pfeifer@charly.informatik.uni-dortmund.de>
\& Benjamin A. Holzman <bah@ecnvantage.com>
\& Andrew Ford <A.Ford@ford-mason.co.uk>
\& Gisle Aas <gisle@aas.no>
\& Jeff Gresham <gresham_jeffrey@jpmorgan.com>
\& Murray Nesbitt <murray@activestate.com>
\& Marc Lehmann <pcg@opengroup.org>
\& Justin Banks <justinb@wamnet.com>
\& Jarkko Hietaniemi <jhi@iki.fi> (AGAIN, as perl 5.7.0 Pumpkin!)
\& Salvador Ortiz Garcia <sog@msg.com.mx>
\& Dominic Dunlop <domo@computer.org>
\& Erik Haugan <erik@solbors.no>
for their bug reports, suggestions and contributions.
Benjamin Holzman contributed the tied variable support, Andrew Ford
contributed the canonical order for hashes, and Gisle Aas fixed
a few misunderstandings of mine regarding the perl internals,
and optimized the emission of \*(L"tags\*(R" in the output streams by
simply counting the objects instead of tagging them (leading to
a binary incompatibility for the Storable image starting at version
0.6\-\-older images are, of course, still properly understood).
Murray Nesbitt made Storable thread\-safe. Marc Lehmann added overloading
and references to tied items support.
Storable was written by Raphael Manfredi \fI<Raphael_Manfredi@pobox.com>\fR
Maintenance is now done by the perl5\-porters \fI<perl5\-porters@perl.org>\fR
Please e\-mail us with problems, bug fixes, comments and complaints,
although if you have complements you should send them to Raphael.
Please don't e\-mail Raphael with problems, as he no longer works on
Storable, and your message will be delayed while he forwards it to us.
projects / OpenSPARC-T2-DV / blob