Good point (about the signal being per-process). But with a little more work, you could make your signal handler
"intelligent" to call the handlers for all the objects that
have registered. Using your sample code as a base:
package Obj;
# Class variable
%handlers=();
sub new {
my $class = shift;
my $self = { @_ };
bless $self, $class;
$self->set_signal_handlers;
$self;
}
sub name {
shift->{'name'};
}
sub set_signal_handlers {
my $self = shift;
if (!%handlers) {
# Class signal handler, only set the first time
$SIG{USR1} = \&class_handle_USR1;
}
# You could index by $self->name, or by any other identifier
$handlers{$self} = sub { $self->handle_USR1() };
}
sub handle_USR1 {
my $self = shift;
print "handling USR1 for ", $self->name, "\n";
}
sub class_handle_USR1 {
foreach (keys %handlers) {
&{$handlers{$_}}();
}
}
package main;
my $obj1 = new Obj(name => 'obj1');
my $obj2 = new Obj(name => 'obj2');
while (1) { }
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|