| CC: | "Lincoln A. Baxter" <lab [...] lincolnbaxter.com.make.me.VALID>, "Lincoln A. Baxter" <lab [...] lincolnbaxter.com> |
| Subject: | Sys::SigAction and "safe" attribute. |
| Date: | Fri, 10 Oct 2008 16:44:00 +0400 |
| To: | bug-Sys-SigAction [...] rt.cpan.org |
| From: | "Dmitry V. Krivenok" <krivenok [...] orangesystem.ru> |
Hello!
Doc (http://search.cpan.org/~lbaxter/Sys-SigAction-0.10/lib/Sys/SigAction.pm) says that
it's possible to pass "safe" attribute in set_sig_handler:
my $h = set_sig_handler( 'ALRM' ,\&mysubname ,{ mask=>[ 'ALRM' ] ,safe=>1 } );
However, I found (in SigAction.pm version 0.10) that this attribute is
ignored (it is just checked in _attrs_warning subroutine).
Why not to add
$act->safe( $attrs->{safe} );
after
my $act = POSIX::SigAction->new( $handler ,$mask ,$attrs->{flags} );
if perl >= 5.8.2 is used?
Currently we always use unsafe signals model (despite of safe attribute).
Thank you beforehand!
--
Sincerely yours, Dmitry V. Krivenok
Orange System Company
Saint-Petersburg, Russia
work phone: +7 812 332-32-40
cellular phone: +7 921 576-70-91
e-mail: krivenok@orangesystem.ru
web: http://www.orangesystem.ru
skype: krivenok_dmitry
jabber: krivenok_dmitry@jabber.ru
icq: 242-526-443