… | |
… | |
233 | use common::sense; |
233 | use common::sense; |
234 | |
234 | |
235 | BEGIN { |
235 | BEGIN { |
236 | # the next line forces initialisation of internal |
236 | # the next line forces initialisation of internal |
237 | # signal handling variables, otherwise, PL_sig_pending |
237 | # signal handling variables, otherwise, PL_sig_pending |
238 | # etc. will be null pointers. |
238 | # etc. might be null pointers. |
239 | $SIG{KILL} = sub { }; |
239 | $SIG{KILL} = sub { }; |
240 | |
240 | |
241 | our $VERSION = '1.0'; |
241 | our $VERSION = '1.05'; |
242 | |
242 | |
243 | require XSLoader; |
243 | require XSLoader; |
244 | XSLoader::load ("Async::Interrupt", $VERSION); |
244 | XSLoader::load ("Async::Interrupt", $VERSION); |
245 | } |
245 | } |
246 | |
246 | |
… | |
… | |
432 | When you expect a lot of signals (e.g. when using SIGIO), then enabling |
432 | When you expect a lot of signals (e.g. when using SIGIO), then enabling |
433 | signal hysteresis can reduce the number of handler invocations |
433 | signal hysteresis can reduce the number of handler invocations |
434 | considerably, at the cost of two extra syscalls. |
434 | considerably, at the cost of two extra syscalls. |
435 | |
435 | |
436 | Note that setting the signal to C<SIG_IGN> can have unintended side |
436 | Note that setting the signal to C<SIG_IGN> can have unintended side |
437 | effects when you fork and exec other programs, as often they do nto expect |
437 | effects when you fork and exec other programs, as often they do not expect |
438 | signals to be ignored by default. |
438 | signals to be ignored by default. |
439 | |
439 | |
440 | =item $async->block |
440 | =item $async->block |
441 | |
441 | |
442 | =item $async->unblock |
442 | =item $async->unblock |
… | |
… | |
536 | |
536 | |
537 | =back |
537 | =back |
538 | |
538 | |
539 | =head1 THE Async::Interrupt::EventPipe CLASS |
539 | =head1 THE Async::Interrupt::EventPipe CLASS |
540 | |
540 | |
541 | Pipes are the predominent utility to make asynchronous signals |
541 | Pipes are the predominant utility to make asynchronous signals |
542 | synchronous. However, pipes are hard to come by: they don't exist on the |
542 | synchronous. However, pipes are hard to come by: they don't exist on the |
543 | broken windows platform, and on GNU/Linux systems, you might want to use |
543 | broken windows platform, and on GNU/Linux systems, you might want to use |
544 | an C<eventfd> instead. |
544 | an C<eventfd> instead. |
545 | |
545 | |
546 | This class creates selectable event pipes in a portable fashion: on |
546 | This class creates selectable event pipes in a portable fashion: on |
… | |
… | |
576 | |
576 | |
577 | =item $epipe->drain |
577 | =item $epipe->drain |
578 | |
578 | |
579 | Drain (empty) the pipe. |
579 | Drain (empty) the pipe. |
580 | |
580 | |
|
|
581 | =item ($c_func, $c_arg) = $epipe->signal_func |
|
|
582 | |
|
|
583 | =item ($c_func, $c_arg) = $epipe->drain_func |
|
|
584 | |
|
|
585 | These two methods returns a function pointer and C<void *> argument |
|
|
586 | that can be called to have the effect of C<< $epipe->signal >> or C<< |
|
|
587 | $epipe->drain >>, respectively, on the XS level. |
|
|
588 | |
|
|
589 | They both have the following prototype and need to be passed their |
|
|
590 | C<$c_arg>, which is a C<void *> cast to an C<IV>: |
|
|
591 | |
|
|
592 | void (*c_func) (void *c_arg) |
|
|
593 | |
|
|
594 | An example call would look like: |
|
|
595 | |
|
|
596 | c_func (c_arg); |
|
|
597 | |
581 | =item $epipe->renew |
598 | =item $epipe->renew |
582 | |
599 | |
583 | Recreates the pipe (useful after a fork). The reading side will not change |
600 | Recreates the pipe (useful after a fork). The reading side will not change |
584 | it's file descriptor number, but the writing side might. |
601 | it's file descriptor number, but the writing side might. |
585 | |
602 | |
|
|
603 | =item $epipe->wait |
|
|
604 | |
|
|
605 | This method blocks the process until there are events on the pipe. This is |
|
|
606 | not a very event-based or ncie way of usign an event pipe, but it can be |
|
|
607 | occasionally useful. |
|
|
608 | |
586 | =back |
609 | =back |
587 | |
610 | |
588 | =cut |
611 | =cut |
589 | |
612 | |
590 | 1; |
613 | 1; |
591 | |
|
|
592 | =head1 EXAMPLE |
|
|
593 | |
|
|
594 | There really should be a complete C/XS example. Bug me about it. Better |
|
|
595 | yet, create one. |
|
|
596 | |
614 | |
597 | =head1 IMPLEMENTATION DETAILS AND LIMITATIONS |
615 | =head1 IMPLEMENTATION DETAILS AND LIMITATIONS |
598 | |
616 | |
599 | This module works by "hijacking" SIGKILL, which is guaranteed to always |
617 | This module works by "hijacking" SIGKILL, which is guaranteed to always |
600 | exist, but also cannot be caught, so is always available. |
618 | exist, but also cannot be caught, so is always available. |