ogd - ordered global destruction
perl -mogd yourscript.pl # recommended export PERL5OPT=-mogd perl yourscript.pl use ogd; ogd->register( @object ); # for objects from XSUBs only
This documentation describes version 0.03.
This module adds ordered destruction of objects stored in global variables in LIFO order during global destruction.
Ordered global destruction is only applicable to objects stored in non-lexical variables (even if they are in file scope). Apparently Perl destroys all objects stored file-level lexicals before the first END block is called.
If you store objects in global variables, and those objects contain references to other objects stored in global variabkes, then you cannot be sure of the order in which these objects are destroyed when executing of Perl is stopped (by reaching the end of the script, or by an
To get the proper behaviour, it is better to use file lexical variables. But sometimes this is not possible, e.g. when you're using AutoLoader.
The random way these objects are destroyed, can sometimes be a problem. This pragma is intended to replace this random behaviour by a deterministic behaviour.
ogd pragma install its own version of the
bless() system function. This version keeps a list of weakened references to each and every object created during the execution of Perl. A cleanup run is done every 1024 objects that have been created, to reduce memory usage of this list of weakened references.
When execution of Perl stops and
END code blocks are starting to get called, an internal subroutine is added as the very last END code block to be executed. This is when the B module is loaded to achieve this feat.
Once all other END code blocks have been executed, the internal subroutine loops through all still valid weakened references in LIFO (Last In, First Out) order and executes the
DESTROY method on them. In case the DESTROY method would like to differentiate between a "real" object destruction, or a forced one, the parameter "1" is given to the DESTROY method. While looping through the list of objects, a list of packages in which still valid objects were available, is built.
When DESTROY has been called on all objects, the internal sub loops through all the packages it has seen and installs an empty DESTROY subroutine in those packages.
The internal sub then relinquishes control back to Perl, which will then call DESTROY on all the objects it still thinks are valid (in more or less random order). Since the DESTROY methods have all been replaced by empty stubs, this is effectively a noop.
ogd->register( @object ); # only for blessed objects created in XSUBs
Not all blessed objects in Perl are necessarily created with "bless": they can also be created in XSUBs and thereby bypass the registration mechanism that ogd installs for "bless". For those cases, it is possible to register objects created in such a manner by calling the "register" class function. Any object passed to it will be registered.
B (any) Scalar::Util (any)
ogd pragma installs its own version of the
bless() system function and it can not work without that special version of bless (unless you wish to register your objects yourself). This means that the
ogd pragma needs to be loaded before any modules that you want the special functionality of
ogd to be applied to.
This can be achieved by loading the module from the command line (with the
-M option), or by adding loading of the
ogd pragma in the
PERL5OPT environment variable.
In order to facilitate debugging and testing of
OGD_DEBUG environment variable can be set to a numeric value before loading the
ogd pragma for the first time. Currently, only the value 1 is supported. If set, the following messages will be sent to STDERR:
As soon as one or more objects are registered, a line starting with "+", followed by the number of objects registered, followed by a newline, will be sent to STDERR. Since this usually happens when the
bless() function is executed, you will usually see this as:
If a list cleanup is done (by default, every 1024 object registrations), and destroyed objects have been removed, a line starting with "-", followed by the original number of elements in the list, followed by "->", the number of objects left after cleanup, and a newline. You would e.g. see this as:
As soon as the END block of
ogd itself is executed, a "*" followed by a newline is sent to STDERR:
As soon as all of the valid objects registered have been called with the DESTROY method, a "!" followed by the number of objects handled, will be sent to STDERR. E.g.:
All of the packages of which the DESTROY method has been replaced by an empty stub, followed by the number of objects forcibly destroyed of that class between parentheses, will be sent to STDERR prefixed with "x". For instance:
*Foo(123) Bar(234) Baz(13)
In order to reduce the memory requirements of
ogd, a regular cleanup is performed on the list of registered objects (which may contain reference to already destroyed objects). By default, this happens every 1024 object registrations, but this can be changed by setting the environment variable
OGD_CLEANUP to a numeric value before loading
ogd the first time. The value represents the power of 2 at which a cleanup will be performed: by default this is 10 (as 2**10 = 1024), but any other positive integer value is allowed (allowing for more or lesser aggressive cleanup checks).
before class method should be added to manipulate the order in which objects will be destroyed at global destruction?
Examples should be added.
Elizabeth Mattijsen, <email@example.com>.
Please report bugs to <firstname.lastname@example.org>.
Mark Jason Dominus for the initial impetus. Yitzchak Scott-Thoennes for the suggestion of using the B module. Inspired by similar work on Thread::Bless.
Copyright (c) 2004, 2012 Elizabeth Mattijsen <email@example.com>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.