| … | |
… | |
| 117 | innermost call to EV::loop return. |
117 | innermost call to EV::loop return. |
| 118 | |
118 | |
| 119 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
119 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
| 120 | fast as possible. |
120 | fast as possible. |
| 121 | |
121 | |
|
|
122 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($events) |
|
|
123 | |
|
|
124 | This function rolls together an I/O and a timer watcher for a single |
|
|
125 | one-shot event without the need for managing a watcher object. |
|
|
126 | |
|
|
127 | If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events> |
|
|
128 | must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ |
|
|
129 | | EV::WRITE>, indicating the type of I/O event you want to wait for. If |
|
|
130 | you do not want to wait for some I/O event, specify C<undef> for |
|
|
131 | C<$fh_or_undef> and C<0> for C<$events>). |
|
|
132 | |
|
|
133 | If timeout is C<undef> or negative, then there will be no |
|
|
134 | timeout. Otherwise a EV::timer with this value will be started. |
|
|
135 | |
|
|
136 | When an error occurs or either the timeout or I/O watcher triggers, then |
|
|
137 | the callback will be called with the received event set (in general |
|
|
138 | you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>, |
|
|
139 | C<EV::WRITE> and C<EV::TIMEOUT>). |
|
|
140 | |
|
|
141 | EV::once doesn't return anything: the watchers stay active till either |
|
|
142 | of them triggers, then they will be stopped and freed, and the callback |
|
|
143 | invoked. |
|
|
144 | |
| 122 | =back |
145 | =back |
| 123 | |
146 | |
| 124 | =head2 WATCHER |
147 | =head2 WATCHER |
| 125 | |
148 | |
| 126 | A watcher is an object that gets created to record your interest in some |
149 | A watcher is an object that gets created to record your interest in some |
| … | |
… | |
| 530 | =back |
553 | =back |
| 531 | |
554 | |
| 532 | =head1 THREADS |
555 | =head1 THREADS |
| 533 | |
556 | |
| 534 | Threads are not supported by this module in any way. Perl pseudo-threads |
557 | Threads are not supported by this module in any way. Perl pseudo-threads |
| 535 | is evil stuff and must die. |
558 | is evil stuff and must die. As soon as Perl gains real threads I will work |
|
|
559 | on thread support for it. |
|
|
560 | |
|
|
561 | =head1 FORK |
|
|
562 | |
|
|
563 | Most of the "improved" event delivering mechanisms of modern operating |
|
|
564 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
|
|
565 | not supported and usually destructive). Libev makes it possible to work |
|
|
566 | around this by having a function that recreates the kernel state after |
|
|
567 | fork in the child. |
|
|
568 | |
|
|
569 | On non-win32 platforms, this module requires the pthread_atfork |
|
|
570 | functionality to do this automatically for you. This function is quite |
|
|
571 | buggy on most BSDs, though, so YMMV. The overhead for this is quite |
|
|
572 | negligible, because everything the function currently does is set a flag |
|
|
573 | that is checked only when the event loop gets used the next time, so when |
|
|
574 | you do fork but not use EV, the overhead is minimal. |
|
|
575 | |
|
|
576 | On win32, there is no notion of fork so all this doesn't apply, of course. |
| 536 | |
577 | |
| 537 | =cut |
578 | =cut |
| 538 | |
579 | |
| 539 | our $DIED = sub { |
580 | our $DIED = sub { |
| 540 | warn "EV: error in callback (ignoring): $@"; |
581 | warn "EV: error in callback (ignoring): $@"; |
