Expose PL_dirty, the flag which marks global
http://search.cpan.org/dist/Devel-GlobalDestruction/
Perl's global destruction is a little tricky to deal with WRT finalizers
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
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if
global destruction is in effect.
- Developed at devel:languages:perl
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:RISCV/perl-Devel-GlobalDestruction && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| Devel-GlobalDestruction-0.04.tar.gz | 0000046820 45.7 KB | |
| perl-Devel-GlobalDestruction.changes | 0000001016 1016 Bytes | |
| perl-Devel-GlobalDestruction.spec | 0000002239 2.19 KB |
Revision 7 (latest revision is 16)
Stephan Kulow (coolo)
accepted
request 94390
from
Stephan Kulow (coolo)
(revision 7)
- update to 0.04
* To detect a perl with ${^GLOBAL_PHASE}, check for the feature
itself instead of a specific perl version (doy).
* Stop depending on Scope::Guard for the tests (doy).
* Upgrade ppport.h from version 3.13 to 3.19.
Comments 0