use strict;
use warnings;
-our $VERSION = '0.11';
+our $VERSION = '0.12';
use Sub::Exporter::Progressive -setup => {
exports => [ qw(in_global_destruction) ],
# the eval already installed everything, nothing to do
}
else {
- # internally, PL_main_start is nulled immediately before entering global destruction
- # and we can use B to detect that. It will also be null before the main runloop starts,
- # so we check install a CHECK if needed to detect that.
+ # internally, PL_main_cv is set to Nullcv immediately before entering
+ # global destruction and we can use B to detect that. B::main_cv will
+ # only ever be a B::CV or a B::SPECIAL that is a reference to 0
require B;
- my $started = !B::main_start()->isa(q[B::NULL]);
- unless ($started) {
- # work around 5.6 eval bug
- eval '0 && $started; CHECK { $started = 1 }; 1'
- or die $@;
- }
- eval '0 && $started; sub in_global_destruction () { $started && B::main_start()->isa(q[B::NULL]) }; 1'
+ eval 'sub in_global_destruction () { ${B::main_cv()} == 0 }; 1'
or die $@;
}
because it's not ordered and objects can sometimes disappear.
Writing defensive destructors is hard and annoying, and usually if global
-destruction is happenning you only need the destructors that free up non
+destruction is happening you only need the destructors that free up non
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if global
Returns true if the interpreter is in global destruction. In perl 5.14+, this
returns C<${^GLOBAL_PHASE} eq 'DESTRUCT'>, and on earlier perls, detects it using
-the value of C<PL_main_start> or C<PL_dirty>.
+the value of C<PL_main_cv> or C<PL_dirty>.
=back