Bug 468642 - Review Request: perl-Devel-GlobalDestruction - Expose PL_dirty
Review Request: perl-Devel-GlobalDestruction - Expose PL_dirty
Status: CLOSED NOTABUG
Product: Bugzilla
Classification: Community
Component: Test (Show other bugs)
devel
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
http://search.cpan.org/dist/Devel-Glo...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-26 21:57 EDT by Chris Weyl
Modified: 2013-06-23 22:17 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-26 21:58:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Weyl 2008-10-26 21:57:41 EDT
SRPM URL: http://fedora.biggerontheinside.net/review/perl-Devel-GlobalDestruction-0.02-1.fc9.src.rpm
SPEC URL: http://fedora.biggerontheinside.net/review/perl-Devel-GlobalDestruction.spec

Description:
Perl's global destruction is a little tricky to deal with WRT finalizers
because its 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.

Note You need to log in before you can comment on or make changes to this bug.