… | |
… | |
402 | correctly. |
402 | correctly. |
403 | |
403 | |
404 | Example: exit on SIGINT |
404 | Example: exit on SIGINT |
405 | |
405 | |
406 | my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); |
406 | my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); |
|
|
407 | |
|
|
408 | =head3 Restart Behaviour |
|
|
409 | |
|
|
410 | While restart behaviour is up to the event loop implementation, most will |
|
|
411 | not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's |
|
|
412 | pure perl implementation). |
|
|
413 | |
|
|
414 | =head3 Safe/Unsafe Signals |
|
|
415 | |
|
|
416 | Perl signals can be either "safe" (synchronous to opcode handling) or |
|
|
417 | "unsafe" (asynchronous) - the former might get delayed indefinitely, the |
|
|
418 | latter might corrupt your memory. |
|
|
419 | |
|
|
420 | AnyEvent signal handlers are, in addition, synchronous to the event loop, |
|
|
421 | i.e. they will not interrupt your running perl program but will only be |
|
|
422 | called as part of the normal event handling (just like timer, I/O etc. |
|
|
423 | callbacks, too). |
407 | |
424 | |
408 | =head3 Signal Races, Delays and Workarounds |
425 | =head3 Signal Races, Delays and Workarounds |
409 | |
426 | |
410 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
427 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
411 | callbacks to signals in a generic way, which is a pity, as you cannot |
428 | callbacks to signals in a generic way, which is a pity, as you cannot |