Lines Matching refs:data
94 # To recognize the data files of the Perl module Storable,
98 0 string perl-store perl Storable(v0.6) data
104 0 string pst0 perl Storable(v0.7) data
374 Storable - persistence for Perl data structures
409 The Storable package brings persistence to your Perl data structures
420 To retrieve data stored to disk, use C<retrieve> with a file name.
427 to objects that share a lot of common data into a single array or hash
441 You can also store data in network order to allow easy sharing across
444 as in C<nstore> and C<nstore_fd>. At retrieval time, your data will be
446 from native or network ordered data. Double values are stored stringified
463 The Storable engine can also store data into a Perl scalar instead, to
513 compare data structures by comparing their frozen representations (or
527 Storable file contains malicious data. You can set C<$Storable::Eval>
539 serialize data which is not supported by earlier Perls. By default,
541 encounters data that it cannot deserialize. However, the defaults
546 =item utf8 data
556 data loss, because with C<$drop_utf8> true, it becomes impossible to tell
557 whether the original data was the Unicode string, or a series of bytes
575 knew about. Internal version numbers are increased each time new data
579 data types.
581 This version of Storable will defer croaking until it encounters a data
656 serialization of the underlying Perl data. The hook will again be normally
774 there's a utility called C<file>, which recognizes data files based on
777 of the data. Where that configuration file lives depends on the UNIX
836 to be disappointed when retrieving your data. Indeed, Perl stringifies
852 Storing data canonically that contains large hashes can be
853 significantly slower than storing the same data normally, as
857 your data. There is no slowdown on retrieval.
874 operations on the same data structures, you will get different
888 floating-point data, even with nstore().
892 data back to 8 bit and C<croak()> if the conversion fails.
902 =head2 64 bit data in perl 5.6.0 and 5.6.1
904 This section only applies to you if you have existing data written out
928 that Storable was storing some data differently in the file. Hence Storable
930 written by a 32 bit perl, not realise that the data is actually in a subtly
941 What this means is that if you have data written by Storable 1.x running
944 I<Byte order is not compatible>. If you have such data then you you
947 migrate your data, or any older perl you are communicating with, to this
950 If you don't have data written with specific configuration of perl described