package autovivification;
-use 5.008003;
+use 5.008_003;
use strict;
use warnings;
=head1 VERSION
-Version 0.10
+Version 0.12
=cut
our $VERSION;
BEGIN {
- $VERSION = '0.10';
+ $VERSION = '0.12';
}
=head1 SYNOPSIS
=head1 DESCRIPTION
When an undefined variable is dereferenced, it gets silently upgraded to an array or hash reference (depending of the type of the dereferencing).
-This behaviour is called I<autovivification> and usually does what you mean (e.g. when you store a value) but it's sometimes unnatural or surprising because your variables gets populated behind your back.
+This behaviour is called I<autovivification> and usually does what you mean (e.g. when you store a value) but it may be unnatural or surprising because your variables gets populated behind your back.
This is especially true when several levels of dereferencing are involved, in which case all levels are vivified up to the last, or when it happens in intuitively read-only constructs like C<exists>.
This pragma lets you disable autovivification for some constructs and optionally throws a warning or an error when it would have happened.
=head1 METHODS
-=head2 C<unimport @opts>
+=head2 C<unimport>
+
+ no autovivification; # defaults to qw<fetch exists delete>
+ no autovivification qw<fetch store exists delete>;
+ no autovivification 'warn';
+ no autovivification 'strict';
Magically called when C<no autovivification @opts> is encountered.
Enables the features given in C<@opts>, which can be :
function($arrayref->[$idx])
function($hashref->{$key})
-An exception is thrown if vivification is needed to store the value, which means that effectively you can only assign to levels that are already defined
+An exception is thrown if vivification is needed to store the value, which means that effectively you can only assign to levels that are already defined.
In the example, this would require C<$arrayref> (resp. C<$hashref>) to already be an array (resp. hash) reference.
=item *
=back
-Each call to C<unimport> adds the specified features to the ones already in use in the current lexical scope.
+Each call to C<unimport> B<adds> the specified features to the ones already in use in the current lexical scope.
When C<@opts> is empty, it defaults to C<< qw<fetch exists delete> >>.
();
}
-=head2 C<import @opts>
+=head2 C<import>
+
+ use autovivification; # default Perl behaviour
+ use autovivification qw<fetch store exists delete>;
Magically called when C<use autovivification @opts> is encountered.
Disables the features given in C<@opts>, which can be the same as for L</unimport>.
-Each call to C<import> removes the specified features to the ones already in use in the current lexical scope.
+Each call to C<import> B<removes> the specified features to the ones already in use in the current lexical scope.
When C<@opts> is empty, it defaults to restoring the original Perl autovivification behaviour.
=head2 C<A_THREADSAFE>
-True iff the module could have been built with thread-safety features enabled.
-This constant only has a meaning with your perl is threaded ; otherwise, it'll always be false.
+True if and only if the module could have been built with thread-safety features enabled.
+This constant only has a meaning when your perl is threaded, otherwise it will always be false.
=head2 C<A_FORKSAFE>
-True iff this module could have been built with fork-safety features enabled.
-This will always be true except on Windows where it's false for perl 5.10.0 and below .
+True if and only if this module could have been built with fork-safety features enabled.
+This constant will always be true, except on Windows where it is false for perl 5.10.0 and below.
=head1 CAVEATS
The pragma doesn't apply when one dereferences the returned value of an array or hash slice, as in C<< @array[$id]->{member} >> or C<< @hash{$key}->{member} >>.
-This syntax is valid Perl, yet it's discouraged as the slice is here useless since the dereferencing enforces scalar context.
+This syntax is valid Perl, yet it is discouraged as the slice is here useless since the dereferencing enforces scalar context.
If warnings are turned on, Perl will complain about one-element slices.
+Autovivifications that happen in code C<eval>'d during the global destruction phase of a spawned thread or pseudo-fork (the processes used internally for the C<fork> emulation on Windows) are not reported.
+
=head1 DEPENDENCIES
L<perl> 5.8.3.
A C compiler.
This module may happen to build with a C++ compiler as well, but don't rely on it, as no guarantee is made in this regard.
-L<XSLoader> (standard since perl 5.006).
+L<XSLoader> (standard since perl 5.6.0).
=head1 SEE ALSO
=head1 COPYRIGHT & LICENSE
-Copyright 2009,2010,2011 Vincent Pit, all rights reserved.
+Copyright 2009,2010,2011,2012,2013 Vincent Pit, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
projects / perl / modules / autovivification.git / blobdiff