Softpedia
 


LINUX CATEGORIES:



GLOBAL PAGES >>
NEWS ARCHIVE >>
SOFTPEDIA REVIEWS >>
MEET THE EDITORS >>
WEEK'S BEST
  • Linux Kernel 3.9.3 / 3....
  • LibreOffice 3.6.6 / 4.0.3
  • MPlayer 1.1.1
  • systemd 204
  • Arch Linux 2013.05.01
  • Blender 2.67a
  • KDE Software Compilatio...
  • CrunchBang Linux Stable...
  • Elementary OS 0.1 / 0.2...
  • SystemRescueCd 3.6.0
  • Home > Linux > Programming > Libraries

    AtExit 2.01

    Download button

    No screenshots available
    Downloads: 379  View global page NEW!  Tell us about an update
    User Rating:
    Rated by:
    NOT RATED
    0 user(s)
    Developer:

    License / Price:

    Last Updated:

    Category:
    Andrew Langmead, Brad Appleton and Michael A. Chase | More programs
    Perl Artistic License / FREE
    May 23rd, 2007, 22:05 GMT
    ROOT / Programming / Libraries

     Read user reviews (0)  Refer to a friend  Subscribe

    AtExit description

    AtExit is a Perl module that can perform exit processing for a program or object.

    AtExit is a Perl module that can perform exit processing for a program or object.

    SYNOPSIS

    use AtExit;

    sub cleanup {
    my @args = @_;
    print "cleanup() executing: args = @argsn";
    }

    ## Register subroutines to be called when this program exits

    $_ = atexit(&cleanup, "This call was registered first");
    print "first call to atexit() returned $_n";

    $_ = atexit("cleanup", "This call was registered second");
    print "second call to atexit() returned $_n";

    $_ = atexit("cleanup", "This call should've been unregistered by rmexit");
    rmexit($_) or warn "couldnt' unregister exit-sub $_!";

    if (@ARGV == 0) {
    ## Register subroutines to be called when this lexical scope is exited
    my $scope1 = AtExit->new( &cleanup, "Scope 1, Callback 1" );
    {
    ## Do the same for this nested scope
    my $scope2 = AtExit->new;
    $_ = $scope2->atexit( &cleanup, "Scope 2, Callback 1" );
    $scope1->atexit( &cleanup, "Scope 1, Callback 2");
    $scope2->atexit( &cleanup, "Scope 2, Callback 2" );
    $scope2->rmexit($_) or warn "couldn't unregister exit-sub $_!";

    print "*** Leaving Scope 2 ***n";
    }
    print "*** Finished Scope 2 ***n";
    print "*** Leaving Scope 1 ***n";
    }
    print "*** Finished Scope 1 ***n" if (@ARGV == 0);

    END {
    print "*** Now performing program-exit processing ***n";
    }

    The AtExit module provides ANSI-C style exit processing modeled after the atexit function in the standard C library (see atexit(3C)). Various exit processing routines may be registered by calling atexit and passing it the desired subroutine along with any desired arguments. Then, at program-exit time, the subroutines registered with atexit are invoked with their given arguments in the reverse order of registration (last one registered is invoked first). Registering the same subroutine more than once will cause that subroutine to be invoked once for each registration.

    An AtExit object can be created in any scope. When invoked as a function, atexit registers callbacks to be executed at program-exit time. But when invoked as an object-method (using the $object->method_name syntax), callbacks registered with an AtExit object are executed at object-destruction time! The rules for order of execution of the registered subroutines are the same for objects during object-destruction, as for the program during program-termination.

    The atexit function/method should be passed a subroutine name or reference, optionally followed by the list of arguments with which to invoke it at program/object exit time. Anonymous subroutine references passed to atexit act as "closures" (which are described in perlref). If a subroutine name is specified (as opposed to a subroutine reference) then, unless the subroutine name has an explicit package prefix, it is assumed to be the name of a subroutine in the caller's current package. A reference to the specified subroutine is obtained, and, if invocation arguments were specified, it is "wrapped up" in a closure which invokes the subroutine with the specified arguments. The resulting subroutine reference is added to the front of the list of exit-handling subroutines for the program (atexit) or the AtExit object ($exitObject->atexit) and the reference is then returned to the caller (just in case you might want to unregister it later using rmexit. If the given subroutine could not be registered, then the value zero is returned.

    The rmexit function/method should be passed one or more subroutine references, each of which was returned by a previous call to atexit. For each argument given, rmexit will look in the list of exit-handling subroutines for the program (rmexit) or the AtExit object ($exitObject->rmexit) and remove the first matching entry from the list. If no arguments are given, then all program or object exit-handlers are unregistered! The value returned will be the number of subroutines that were successfully unregistered.

    At object destruction time, the DESTROY{} subroutine in the AtExit module iterates over the subroutine references in the AtExit object and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). At program-exit time, the END{} block in the AtExit module iterates over the subroutines in the array returned by the exit_subs method and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). Note that in both cases (program-exit, and object-destruction) the subroutines in this queue are invoked in first-to-last order (the reverse order in which they were registered with atexit).

    Product's homepage

    Requirements:

    · Perl

      


    TAGS:

    program exit processing | object exit processing | Perl module | AtExit | exit | processing

    Go to top

    WindowsGamesDriversMacLinuxScriptsMobileHandheldNews

    SUBMIT PROGRAM   |   ADVERTISE   |   GET HELP   |   SEND US FEEDBACK   |   RSS FEEDS   |   UPDATE YOUR SOFTWARE   |   ROMANIAN FORUM