diff options
Diffstat (limited to 'Master/tlpkg/tlperl/lib/Storable.pm')
| -rw-r--r-- | Master/tlpkg/tlperl/lib/Storable.pm | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/Master/tlpkg/tlperl/lib/Storable.pm b/Master/tlpkg/tlperl/lib/Storable.pm index bb1083d3fd6..7d8a01198d5 100644 --- a/Master/tlpkg/tlperl/lib/Storable.pm +++ b/Master/tlpkg/tlperl/lib/Storable.pm @@ -1,5 +1,6 @@ # -# Copyright (c) 1995-2000, Raphael Manfredi +# Copyright (c) 1995-2001, Raphael Manfredi +# Copyright (c) 2002-2013 by the Perl 5 Porters # # You may redistribute only under the same terms as Perl 5, as specified # in the README file that comes with the distribution. @@ -21,7 +22,7 @@ package Storable; @ISA = qw(Exporter); use vars qw($canonical $forgive_me $VERSION); -$VERSION = '2.41'; +$VERSION = '2.49_01'; BEGIN { if (eval { local $SIG{__DIE__}; require Log::Agent; 1 }) { @@ -31,13 +32,13 @@ BEGIN { # Use of Log::Agent is optional. If it hasn't imported these subs then # provide a fallback implementation. # - if (!exists &logcroak) { + unless ($Storable::{logcroak} && *{$Storable::{logcroak}}{CODE}) { require Carp; *logcroak = sub { Carp::croak(@_); }; } - if (!exists &logcarp) { + unless ($Storable::{logcarp} && *{$Storable::{logcarp}}{CODE}) { require Carp; *logcarp = sub { Carp::carp(@_); @@ -311,7 +312,7 @@ sub _store_fd { # # freeze # -# Store oject and its hierarchy in memory and return a scalar +# Store object and its hierarchy in memory and return a scalar # containing the result. # sub freeze { @@ -1048,7 +1049,7 @@ untrusted sources!> If your application requires accepting data from untrusted sources, you are best off with a less powerful and more-likely safe serialization format -and implementation. If your data is sufficently simple, JSON is a good +and implementation. If your data is sufficiently simple, JSON is a good choice and offers maximum interoperability. =head1 WARNING @@ -1085,8 +1086,8 @@ deal with them. The store functions will C<croak> if they run into such references unless you set C<$Storable::forgive_me> to some C<TRUE> value. In that -case, the fatal message is turned in a warning and some -meaningless string is stored instead. +case, the fatal message is converted to a warning and some meaningless +string is stored instead. Setting C<$Storable::canonical> may not yield frozen strings that compare equal due to possible stringification of numbers. When the @@ -1162,7 +1163,7 @@ correct behaviour. 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 -I<Byte order is not compatible>. If you have such data then you you +I<Byte order is not compatible>. If you have such data then you should set C<$Storable::interwork_56_64bit> 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 @@ -1192,7 +1193,8 @@ Thank you to (in chronological order): Salvador Ortiz Garcia <sog@msg.com.mx> Dominic Dunlop <domo@computer.org> Erik Haugan <erik@solbors.no> - Benjamin A. Holzman <ben.holzman@grantstreet.com> + Benjamin A. Holzman <ben.holzman@grantstreet.com> + Reini Urban <rurban@cpanel.net> for their bug reports, suggestions and contributions. |