| … | |
… | |
| 38 | |
38 | |
| 39 | You can use this module to bind a signal to a callback while at the same |
39 | You can use this module to bind a signal to a callback while at the same |
| 40 | time activating an event pipe that you can C<select> on, fixing the race |
40 | time activating an event pipe that you can C<select> on, fixing the race |
| 41 | completely. |
41 | completely. |
| 42 | |
42 | |
| 43 | This can be used to implement the signal hadling in event loops, |
43 | This can be used to implement the signal handling in event loops, |
| 44 | e.g. L<AnyEvent>, L<POE>, L<IO::Async::Loop> and so on. |
44 | e.g. L<AnyEvent>, L<POE>, L<IO::Async::Loop> and so on. |
| 45 | |
45 | |
| 46 | =item Background threads want speedy reporting |
46 | =item Background threads want speedy reporting |
| 47 | |
47 | |
| 48 | Assume you want very exact timing, and you can spare an extra cpu core |
48 | Assume you want very exact timing, and you can spare an extra cpu core |
| … | |
… | |
| 158 | _attach $self, $asy->signal_func; |
158 | _attach $self, $asy->signal_func; |
| 159 | |
159 | |
| 160 | So to repeat: first the XS object is created, then it is queried for the |
160 | So to repeat: first the XS object is created, then it is queried for the |
| 161 | callback that should be called when the Interrupt object gets signalled. |
161 | callback that should be called when the Interrupt object gets signalled. |
| 162 | |
162 | |
| 163 | Then the interrupt object is queried for the callback fucntion that the |
163 | Then the interrupt object is queried for the callback function that the |
| 164 | thread should call to signal the Interrupt object, and this callback is |
164 | thread should call to signal the Interrupt object, and this callback is |
| 165 | then attached to the thread. |
165 | then attached to the thread. |
| 166 | |
166 | |
| 167 | You have to be careful that your new thread is not signalling before the |
167 | You have to be careful that your new thread is not signalling before the |
| 168 | signal function was configured, for example by starting the background |
168 | signal function was configured, for example by starting the background |
| … | |
… | |
| 638 | =head1 IMPLEMENTATION DETAILS AND LIMITATIONS |
638 | =head1 IMPLEMENTATION DETAILS AND LIMITATIONS |
| 639 | |
639 | |
| 640 | This module works by "hijacking" SIGKILL, which is guaranteed to always |
640 | This module works by "hijacking" SIGKILL, which is guaranteed to always |
| 641 | exist, but also cannot be caught, so is always available. |
641 | exist, but also cannot be caught, so is always available. |
| 642 | |
642 | |
| 643 | Basically, this module fakes the occurance of a SIGKILL signal and |
643 | Basically, this module fakes the occurence of a SIGKILL signal and |
| 644 | then intercepts the interpreter handling it. This makes normal signal |
644 | then intercepts the interpreter handling it. This makes normal signal |
| 645 | handling slower (probably unmeasurably, though), but has the advantage |
645 | handling slower (probably unmeasurably, though), but has the advantage |
| 646 | of not requiring a special runops function, nor slowing down normal perl |
646 | of not requiring a special runops function, nor slowing down normal perl |
| 647 | execution a bit. |
647 | execution a bit. |
| 648 | |
648 | |
