dslinux/user/perl/ext/Thread/Thread Signal.pm Specific.pm

cayenne dslinux_cayenne at user.in-berlin.de
Mon Dec 4 17:59:49 CET 2006


Update of /cvsroot/dslinux/dslinux/user/perl/ext/Thread/Thread
In directory antilope:/tmp/cvs-serv17422/ext/Thread/Thread

Added Files:
	Signal.pm Specific.pm 
Log Message:
Adding fresh perl source to HEAD to branch from

--- NEW FILE: Specific.pm ---
package Thread::Specific;

our $VERSION = '1.00';

=head1 NAME

Thread::Specific - thread-specific keys

=head1 SYNOPSIS

    use Thread::Specific;
    my $k = key_create Thread::Specific;

=head1 DESCRIPTION

C<key_create> returns a unique thread-specific key.

=cut

sub import : locked : method {
    require fields;
    fields::->import(@_);
}	

sub key_create : locked : method {
    our %FIELDS;   # suppress "used only once"
    return ++$FIELDS{__MAX__};
}

1;

--- NEW FILE: Signal.pm ---
package Thread::Signal;
use Thread qw(async);

our $VERSION = '1.00';

=head1 NAME

Thread::Signal - Start a thread which runs signal handlers reliably (for old code)

=head1 CAVEAT

For new code the use of the C<Thread::Signal> module is discouraged and
the direct use of the C<threads> and associated modules is encouraged instead.

However, there is no direct equivalent of the Thread::Signal module in the
new implementation of threads.  On the bright side: signals are now delivered
reliably to Perl programs that do not use threads.  The handling of signals
with the new threading features is up to the underlying thread implementation
that is being used and may therefor be less reliable.

If you want to specify a thread-specific signal, you can alter the %SIG hash
in the thread where you want to handle a signal differently from other threads.
This at least seems to work under Linux.  But there are no guarantees and your
mileage may vary.

For the whole story about the development of threads in Perl, and why you
should B<not> be using this module unless you know what you're doing, see the
CAVEAT of the C<Thread> module.

=head1 SYNOPSIS

    use Thread::Signal;

    $SIG{HUP} = \&some_handler;

=head1 DESCRIPTION

The C<Thread::Signal> module starts up a special signal handler thread.
All signals to the process are delivered to it and it runs the
associated C<$SIG{FOO}> handlers for them. Without this module,
signals arriving at inopportune moments (such as when perl's internals
are in the middle of updating critical structures) cause the perl
code of the handler to be run unsafely which can cause memory corruption
or worse.

=head1 BUGS

This module changes the semantics of signal handling slightly in that
the signal handler is run separately from the main thread (and in
parallel with it). This means that tricks such as calling C<die> from
a signal handler behave differently (and, in particular, can't be
used to exit directly from a system call).

=cut

if (!init_thread_signals()) {
    require Carp;
    Carp::croak("init_thread_signals failed: $!");
}

async {
    my $sig;
    while ($sig = await_signal()) {
	&$sig();
    }
};

END {
    kill_sighandler_thread();
}

1;




More information about the dslinux-commit mailing list