E
Eric Pozharski
Context: An object forks multiple childs (with help of IO:
ipe, if
that matters). If an object is B<DESTROY>ed then everything is just
fine (there's B<DESTROY> and it works OK). However if filehandles are
closed first then an application get $SIG{CHLD}, obviously. The problem
is that that order (what is B<DESTROY>ed first) is likely out of my
control.
Thus the question. Is there any way (except writing, obviously global,
$SIG{CHLD} handler that would selectively C<IGNORE> or C<DEFAULT> just
got signal) to handle that? Look, I don't understand that as an *easy*
way. I think, that's least intrusive in the outer app environment.
Any comments? I think, the answer is negative.
ipe, ifthat matters). If an object is B<DESTROY>ed then everything is just
fine (there's B<DESTROY> and it works OK). However if filehandles are
closed first then an application get $SIG{CHLD}, obviously. The problem
is that that order (what is B<DESTROY>ed first) is likely out of my
control.
Thus the question. Is there any way (except writing, obviously global,
$SIG{CHLD} handler that would selectively C<IGNORE> or C<DEFAULT> just
got signal) to handle that? Look, I don't understand that as an *easy*
way. I think, that's least intrusive in the outer app environment.
Any comments? I think, the answer is negative.