Revision history for autovivification
+0.18 2017-11-04 15:30 UTC
+ + Fix : [RT #123411] : Compatibility with CV-in-stash optimisation
+ Thanks Father Chrysostomos for reporting and contributing a
+ patch.
+ + Fix : [RT #122956] : strict/warn flags seem to simply do nothing
+ The documentation has been amended to clarify how these two
+ options are supposed to be used.
+ Thanks Christian Walde for reporting.
+
0.17 2017-07-31 17:15 UTC
+ Chg : A large chunk of boilerplate XS code, which is also used in
other XS modules, has been factored out of the main .xs file
homepage: http://search.cpan.org/dist/autovivification/
license: http://dev.perl.org/licenses/
repository: http://git.profvince.com/?p=perl%2Fmodules%2Fautovivification.git
-version: '0.17'
+version: '0.18'
x_serialization_backend: 'CPAN::Meta::YAML version 0.018'
autovivification - Lexically disable autovivification.
VERSION
- Version 0.17
+ Version 0.18
SYNOPSIS
no autovivification;
"unimport"
no autovivification; # defaults to qw<fetch exists delete>
no autovivification qw<fetch store exists delete>;
- no autovivification 'warn';
- no autovivification 'strict';
+ no autovivification warn => @categories;
+ no autovivification strict => @categories;
Magically called when "no autovivification @opts" is encountered.
Enables the features given in @opts, which can be :
* 'warn'
- Emits a warning when an autovivification is avoided.
+ Emits a warning when an autovivification is avoided for the
+ categories specified in @opts.
+
+ Note that "no autovivification 'warn'" currently does nothing by
+ itself, in particular it does not make the default categories warn.
+ This behaviour may change in a future version of this pragma.
* 'strict'
- Throws an exception when an autovivification is avoided.
+ Throws an exception when an autovivification is avoided for the
+ categories specified in @opts.
+
+ Note that "no autovivification 'strict'" currently does nothing by
+ itself, in particular it does not make the default categories die.
+ This behaviour may change in a future version of this pragma.
Each call to "unimport" adds the specified features to the ones already
in use in the current lexical scope.