… | |
… | |
47 | my ($w, $revents) = @_; |
47 | my ($w, $revents) = @_; |
48 | warn $w->path, " has changed somehow.\n"; |
48 | warn $w->path, " has changed somehow.\n"; |
49 | }; |
49 | }; |
50 | |
50 | |
51 | # MAINLOOP |
51 | # MAINLOOP |
52 | EV::loop; # loop until EV::unloop is called or all watchers stop |
52 | EV::run; # loop until EV::unloop is called or all watchers stop |
53 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
53 | EV::run EV::RUN_ONCE; # block until at least one event could be handled |
54 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
54 | EV::run EV::RUN_NOWAIT; # try to handle same events, but do not block |
|
|
55 | |
|
|
56 | =head1 BEFORE YOU START USING THIS MODULE |
|
|
57 | |
|
|
58 | If you only need timer, I/O, signal, child and idle watchers and not the |
|
|
59 | advanced functionality of this module, consider using L<AnyEvent> instead, |
|
|
60 | specifically the simplified API described in L<AE>. |
|
|
61 | |
|
|
62 | When used with EV as backend, the L<AE> API is as fast as the native L<EV> |
|
|
63 | API, but your programs/modules will still run with many other event loops. |
55 | |
64 | |
56 | =head1 DESCRIPTION |
65 | =head1 DESCRIPTION |
57 | |
66 | |
58 | This module provides an interface to libev |
67 | This module provides an interface to libev |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
68 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
… | |
… | |
68 | can use it through the L<AnyEvent> module, stay portable to other event |
77 | can use it through the L<AnyEvent> module, stay portable to other event |
69 | loops (if you don't rely on any watcher types not available through it) |
78 | loops (if you don't rely on any watcher types not available through it) |
70 | and still be faster than with any other event loop currently supported in |
79 | and still be faster than with any other event loop currently supported in |
71 | Perl. |
80 | Perl. |
72 | |
81 | |
|
|
82 | =head2 PORTING FROM EV 3.X to 4.X |
|
|
83 | |
|
|
84 | EV version 4 introduces a number of incompatible changes summarised |
|
|
85 | here. According to the depreciation strategy used by libev, there is a |
|
|
86 | compatibility layer in place so programs should continue to run unchanged |
|
|
87 | (the XS interface lacks this layer, so programs using that one need to be |
|
|
88 | updated). |
|
|
89 | |
|
|
90 | This compatibility layer will be switched off in some future release. |
|
|
91 | |
|
|
92 | All changes relevant to Perl are renames of symbols, functions and |
|
|
93 | methods: |
|
|
94 | |
|
|
95 | EV::loop => EV::run |
|
|
96 | EV::LOOP_NONBLOCK => EV::RUN_NOWAIT |
|
|
97 | EV::LOOP_ONESHOT => EV::RUN_ONCE |
|
|
98 | |
|
|
99 | EV::unloop => EV::break |
|
|
100 | EV::UNLOOP_CANCEL => EV::BREAK_CANCEL |
|
|
101 | EV::UNLOOP_ONE => EV::BREAK_ONE |
|
|
102 | EV::UNLOOP_ALL => EV::BREAK_ALL |
|
|
103 | |
|
|
104 | EV::TIMEOUT => EV::TIMER |
|
|
105 | |
|
|
106 | EV::loop_count => EV::iteration |
|
|
107 | EV::loop_depth => EV::depth |
|
|
108 | EV::loop_verify => EV::verify |
|
|
109 | |
|
|
110 | The loop object methods corresponding to the functions above have been |
|
|
111 | similarly renamed. |
|
|
112 | |
73 | =head2 MODULE EXPORTS |
113 | =head2 MODULE EXPORTS |
74 | |
114 | |
75 | This module does not export any symbols. |
115 | This module does not export any symbols. |
76 | |
116 | |
77 | =cut |
117 | =cut |
78 | |
118 | |
79 | package EV; |
119 | package EV; |
80 | |
120 | |
81 | no warnings; |
121 | use common::sense; |
82 | use strict; |
|
|
83 | |
122 | |
84 | BEGIN { |
123 | BEGIN { |
85 | our $VERSION = '3.52'; |
124 | our $VERSION = '4.11'; |
86 | use XSLoader; |
125 | use XSLoader; |
87 | XSLoader::load "EV", $VERSION; |
126 | XSLoader::load "EV", $VERSION; |
88 | } |
127 | } |
89 | |
128 | |
90 | @EV::IO::ISA = |
129 | @EV::IO::ISA = |
… | |
… | |
125 | will then also service the kqueue loop to some extent. See the example in |
164 | will then also service the kqueue loop to some extent. See the example in |
126 | the section about embed watchers for an example on how to achieve that. |
165 | the section about embed watchers for an example on how to achieve that. |
127 | |
166 | |
128 | =over 4 |
167 | =over 4 |
129 | |
168 | |
130 | =item $loop = new EV::loop [$flags] |
169 | =item $loop = new EV::Loop [$flags] |
131 | |
170 | |
132 | Create a new event loop as per the specified flags. Please refer to |
171 | Create a new event loop as per the specified flags. Please refer to |
133 | the C<ev_loop_new ()> function description in the libev documentation |
172 | the C<ev_loop_new ()> function description in the libev documentation |
134 | (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>, |
173 | (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>, |
135 | or locally-installed as F<EV::libev> manpage) for more info. |
174 | or locally-installed as F<EV::libev> manpage) for more info. |
… | |
… | |
147 | Must be called after a fork in the child, before entering or continuing |
186 | Must be called after a fork in the child, before entering or continuing |
148 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
187 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
149 | this function automatically, at some performance loss (refer to the libev |
188 | this function automatically, at some performance loss (refer to the libev |
150 | documentation). |
189 | documentation). |
151 | |
190 | |
152 | =item $loop->loop_verify |
191 | =item $loop->verify |
153 | |
192 | |
154 | Calls C<ev_verify> to make internal consistency checks (for debugging |
193 | Calls C<ev_verify> to make internal consistency checks (for debugging |
155 | libev) and abort the program if any data structures were found to be |
194 | libev) and abort the program if any data structures were found to be |
156 | corrupted. |
195 | corrupted. |
157 | |
196 | |
… | |
… | |
202 | |
241 | |
203 | Returns the time the last event loop iteration has been started. This |
242 | Returns the time the last event loop iteration has been started. This |
204 | is the time that (relative) timers are based on, and referring to it is |
243 | is the time that (relative) timers are based on, and referring to it is |
205 | usually faster then calling EV::time. |
244 | usually faster then calling EV::time. |
206 | |
245 | |
|
|
246 | =item EV::now_update |
|
|
247 | |
|
|
248 | =item $loop->now_update |
|
|
249 | |
|
|
250 | Establishes the current time by querying the kernel, updating the time |
|
|
251 | returned by C<EV::now> in the progress. This is a costly operation and |
|
|
252 | is usually done automatically within C<EV::loop>. |
|
|
253 | |
|
|
254 | This function is rarely useful, but when some event callback runs for a |
|
|
255 | very long time without entering the event loop, updating libev's idea of |
|
|
256 | the current time is a good idea. |
|
|
257 | |
|
|
258 | =item EV::suspend |
|
|
259 | |
|
|
260 | =item $loop->suspend |
|
|
261 | |
|
|
262 | =item EV::resume |
|
|
263 | |
|
|
264 | =item $loop->resume |
|
|
265 | |
|
|
266 | These two functions suspend and resume a loop, for use when the loop is |
|
|
267 | not used for a while and timeouts should not be processed. |
|
|
268 | |
|
|
269 | A typical use case would be an interactive program such as a game: When |
|
|
270 | the user presses C<^Z> to suspend the game and resumes it an hour later it |
|
|
271 | would be best to handle timeouts as if no time had actually passed while |
|
|
272 | the program was suspended. This can be achieved by calling C<suspend> |
|
|
273 | in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling |
|
|
274 | C<resume> directly afterwards to resume timer processing. |
|
|
275 | |
|
|
276 | Effectively, all C<timer> watchers will be delayed by the time spend |
|
|
277 | between C<suspend> and C<resume>, and all C<periodic> watchers |
|
|
278 | will be rescheduled (that is, they will lose any events that would have |
|
|
279 | occured while suspended). |
|
|
280 | |
|
|
281 | After calling C<suspend> you B<must not> call I<any> function on the given |
|
|
282 | loop other than C<resume>, and you B<must not> call C<resume> |
|
|
283 | without a previous call to C<suspend>. |
|
|
284 | |
|
|
285 | Calling C<suspend>/C<resume> has the side effect of updating the event |
|
|
286 | loop time (see C<now_update>). |
|
|
287 | |
207 | =item $backend = EV::backend |
288 | =item $backend = EV::backend |
208 | |
289 | |
209 | =item $backend = $loop->backend |
290 | =item $backend = $loop->backend |
210 | |
291 | |
211 | Returns an integer describing the backend used by libev (EV::BACKEND_SELECT |
292 | Returns an integer describing the backend used by libev (EV::BACKEND_SELECT |
212 | or EV::BACKEND_EPOLL). |
293 | or EV::BACKEND_EPOLL). |
213 | |
294 | |
214 | =item EV::loop [$flags] |
295 | =item $active = EV::run [$flags] |
215 | |
296 | |
216 | =item $loop->loop ([$flags]) |
297 | =item $active = $loop->run ([$flags]) |
217 | |
298 | |
218 | Begin checking for events and calling callbacks. It returns when a |
299 | Begin checking for events and calling callbacks. It returns when a |
219 | callback calls EV::unloop. |
300 | callback calls EV::unloop or the flasg are nonzero (in which case the |
|
|
301 | return value is true) or when there are no active watchers which reference |
|
|
302 | the loop (keepalive is true), in which case the return value will be |
|
|
303 | false. The returnv alue can generally be interpreted as "if true, there is |
|
|
304 | more work left to do". |
220 | |
305 | |
221 | The $flags argument can be one of the following: |
306 | The $flags argument can be one of the following: |
222 | |
307 | |
223 | 0 as above |
308 | 0 as above |
224 | EV::LOOP_ONESHOT block at most once (wait, but do not loop) |
309 | EV::RUN_ONCE block at most once (wait, but do not loop) |
225 | EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait) |
310 | EV::RUN_NOWAIT do not block at all (fetch/handle events but do not wait) |
226 | |
311 | |
227 | =item EV::unloop [$how] |
312 | =item EV::break [$how] |
228 | |
313 | |
229 | =item $loop->unloop ([$how]) |
314 | =item $loop->break ([$how]) |
230 | |
315 | |
231 | When called with no arguments or an argument of EV::UNLOOP_ONE, makes the |
316 | When called with no arguments or an argument of EV::BREAK_ONE, makes the |
232 | innermost call to EV::loop return. |
317 | innermost call to EV::loop return. |
233 | |
318 | |
234 | When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as |
319 | When called with an argument of EV::BREAK_ALL, all calls to EV::loop will |
235 | fast as possible. |
320 | return as fast as possible. |
236 | |
321 | |
237 | =item $count = EV::loop_count |
322 | When called with an argument of EV::BREAK_CANCEL, any pending break will |
|
|
323 | be cancelled. |
238 | |
324 | |
|
|
325 | =item $count = EV::iteration |
|
|
326 | |
239 | =item $count = $loop->loop_count |
327 | =item $count = $loop->iteration |
240 | |
328 | |
241 | Return the number of times the event loop has polled for new |
329 | Return the number of times the event loop has polled for new |
242 | events. Sometimes useful as a generation counter. |
330 | events. Sometimes useful as a generation counter. |
243 | |
331 | |
244 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
332 | =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) |
… | |
… | |
258 | timeout. Otherwise a EV::timer with this value will be started. |
346 | timeout. Otherwise a EV::timer with this value will be started. |
259 | |
347 | |
260 | When an error occurs or either the timeout or I/O watcher triggers, then |
348 | When an error occurs or either the timeout or I/O watcher triggers, then |
261 | the callback will be called with the received event set (in general |
349 | the callback will be called with the received event set (in general |
262 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
350 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
263 | C<EV::WRITE> and C<EV::TIMEOUT>). |
351 | C<EV::WRITE> and C<EV::TIMER>). |
264 | |
352 | |
265 | EV::once doesn't return anything: the watchers stay active till either |
353 | EV::once doesn't return anything: the watchers stay active till either |
266 | of them triggers, then they will be stopped and freed, and the callback |
354 | of them triggers, then they will be stopped and freed, and the callback |
267 | invoked. |
355 | invoked. |
268 | |
356 | |
269 | =item EV::feed_fd_event ($fd, $revents) |
357 | =item EV::feed_fd_event $fd, $revents |
270 | |
358 | |
271 | =item $loop->feed_fd_event ($fd, $revents) |
359 | =item $loop->feed_fd_event ($fd, $revents) |
272 | |
360 | |
273 | Feed an event on a file descriptor into EV. EV will react to this call as |
361 | Feed an event on a file descriptor into EV. EV will react to this call as |
274 | if the readyness notifications specified by C<$revents> (a combination of |
362 | if the readyness notifications specified by C<$revents> (a combination of |
275 | C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>. |
363 | C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>. |
276 | |
364 | |
277 | =item EV::feed_signal_event ($signal) |
365 | =item EV::feed_signal_event $signal |
278 | |
366 | |
279 | Feed a signal event into EV. EV will react to this call as if the signal |
367 | Feed a signal event into the default loop. EV will react to this call as |
280 | specified by C<$signal> had occured. |
368 | if the signal specified by C<$signal> had occured. |
|
|
369 | |
|
|
370 | =item EV::feed_signal $signal |
|
|
371 | |
|
|
372 | Feed a signal event into EV - unlike C<EV::feed_signal_event>, this works |
|
|
373 | regardless of which loop has registered the signal, and is mainly useful |
|
|
374 | fro custom signal implementations. |
281 | |
375 | |
282 | =item EV::set_io_collect_interval $time |
376 | =item EV::set_io_collect_interval $time |
283 | |
377 | |
284 | =item $loop->set_io_collect_interval ($time) |
378 | =item $loop->set_io_collect_interval ($time) |
285 | |
379 | |
… | |
… | |
290 | These advanced functions set the minimum block interval when polling for I/O events and the minimum |
384 | These advanced functions set the minimum block interval when polling for I/O events and the minimum |
291 | wait interval for timer events. See the libev documentation at |
385 | wait interval for timer events. See the libev documentation at |
292 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> |
386 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> |
293 | (locally installed as F<EV::libev>) for a more detailed discussion. |
387 | (locally installed as F<EV::libev>) for a more detailed discussion. |
294 | |
388 | |
|
|
389 | =item $count = EV::pending_count |
|
|
390 | |
|
|
391 | =item $count = $loop->pending_count |
|
|
392 | |
|
|
393 | Returns the number of currently pending watchers. |
|
|
394 | |
|
|
395 | =item EV::invoke_pending |
|
|
396 | |
|
|
397 | =item $loop->invoke_pending |
|
|
398 | |
|
|
399 | Invoke all currently pending watchers. |
|
|
400 | |
295 | =back |
401 | =back |
296 | |
402 | |
297 | |
403 | |
298 | =head1 WATCHER OBJECTS |
404 | =head1 WATCHER OBJECTS |
299 | |
405 | |
… | |
… | |
313 | |
419 | |
314 | Each watcher type has its associated bit in revents, so you can use the |
420 | Each watcher type has its associated bit in revents, so you can use the |
315 | same callback for multiple watchers. The event mask is named after the |
421 | same callback for multiple watchers. The event mask is named after the |
316 | type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
422 | type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
317 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
423 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
318 | (which can set both EV::READ and EV::WRITE bits), and EV::timer (which |
424 | (which can set both EV::READ and EV::WRITE bits). |
319 | uses EV::TIMEOUT). |
|
|
320 | |
425 | |
321 | In the rare case where one wants to create a watcher but not start it at |
426 | In the rare case where one wants to create a watcher but not start it at |
322 | the same time, each constructor has a variant with a trailing C<_ns> in |
427 | the same time, each constructor has a variant with a trailing C<_ns> in |
323 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
428 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
324 | |
429 | |
… | |
… | |
403 | |
508 | |
404 | =item $previous_state = $w->keepalive ($bool) |
509 | =item $previous_state = $w->keepalive ($bool) |
405 | |
510 | |
406 | Normally, C<EV::loop> will return when there are no active watchers |
511 | Normally, C<EV::loop> will return when there are no active watchers |
407 | (which is a "deadlock" because no progress can be made anymore). This is |
512 | (which is a "deadlock" because no progress can be made anymore). This is |
408 | convinient because it allows you to start your watchers (and your jobs), |
513 | convenient because it allows you to start your watchers (and your jobs), |
409 | call C<EV::loop> once and when it returns you know that all your jobs are |
514 | call C<EV::loop> once and when it returns you know that all your jobs are |
410 | finished (or they forgot to register some watchers for their task :). |
515 | finished (or they forgot to register some watchers for their task :). |
411 | |
516 | |
412 | Sometimes, however, this gets in your way, for example when the module |
517 | Sometimes, however, this gets in your way, for example when the module |
413 | that calls C<EV::loop> (usually the main program) is not the same module |
518 | that calls C<EV::loop> (usually the main program) is not the same module |
… | |
… | |
645 | |
750 | |
646 | =item $w = EV::signal $signal, $callback |
751 | =item $w = EV::signal $signal, $callback |
647 | |
752 | |
648 | =item $w = EV::signal_ns $signal, $callback |
753 | =item $w = EV::signal_ns $signal, $callback |
649 | |
754 | |
|
|
755 | =item $w = $loop->signal ($signal, $callback) |
|
|
756 | |
|
|
757 | =item $w = $loop->signal_ns ($signal, $callback) |
|
|
758 | |
650 | Call the callback when $signal is received (the signal can be specified by |
759 | Call the callback when $signal is received (the signal can be specified by |
651 | number or by name, just as with C<kill> or C<%SIG>). |
760 | number or by name, just as with C<kill> or C<%SIG>). |
|
|
761 | |
|
|
762 | Only one event loop can grab a given signal - attempting to grab the same |
|
|
763 | signal from two EV loops will crash the program immediately or cause data |
|
|
764 | corruption. |
652 | |
765 | |
653 | EV will grab the signal for the process (the kernel only allows one |
766 | EV will grab the signal for the process (the kernel only allows one |
654 | component to receive a signal at a time) when you start a signal watcher, |
767 | component to receive a signal at a time) when you start a signal watcher, |
655 | and removes it again when you stop it. Perl does the same when you |
768 | and removes it again when you stop it. Perl does the same when you |
656 | add/remove callbacks to C<%SIG>, so watch out. |
769 | add/remove callbacks to C<%SIG>, so watch out. |
… | |
… | |
881 | =item $w = $loop->check_ns ($callback) |
994 | =item $w = $loop->check_ns ($callback) |
882 | |
995 | |
883 | Call the callback just after the process wakes up again (after it has |
996 | Call the callback just after the process wakes up again (after it has |
884 | gathered events), but before any other callbacks have been invoked. |
997 | gathered events), but before any other callbacks have been invoked. |
885 | |
998 | |
886 | This is used to integrate other event-based software into the EV |
999 | This can be used to integrate other event-based software into the EV |
887 | mainloop: You register a prepare callback and in there, you create io and |
1000 | mainloop: You register a prepare callback and in there, you create io and |
888 | timer watchers as required by the other software. Here is a real-world |
1001 | timer watchers as required by the other software. Here is a real-world |
889 | example of integrating Net::SNMP (with some details left out): |
1002 | example of integrating Net::SNMP (with some details left out): |
890 | |
1003 | |
891 | our @snmp_watcher; |
1004 | our @snmp_watcher; |
… | |
… | |
925 | The callbacks of the created watchers will not be called as the watchers |
1038 | The callbacks of the created watchers will not be called as the watchers |
926 | are destroyed before this can happen (remember EV::check gets called |
1039 | are destroyed before this can happen (remember EV::check gets called |
927 | first). |
1040 | first). |
928 | |
1041 | |
929 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
1042 | The C<check_ns> variant doesn't start (activate) the newly created watcher. |
|
|
1043 | |
|
|
1044 | =item EV::CHECK constant issues |
|
|
1045 | |
|
|
1046 | Like all other watcher types, there is a bitmask constant for use in |
|
|
1047 | C<$revents> and other places. The C<EV::CHECK> is special as it has |
|
|
1048 | the same name as the C<CHECK> sub called by Perl. This doesn't cause |
|
|
1049 | big issues on newer perls (beginning with 5.8.9), but it means thatthe |
|
|
1050 | constant must be I<inlined>, i.e. runtime calls will not work. That means |
|
|
1051 | that as long as you always C<use EV> and then C<EV::CHECK> you are on the |
|
|
1052 | safe side. |
930 | |
1053 | |
931 | =back |
1054 | =back |
932 | |
1055 | |
933 | |
1056 | |
934 | =head3 FORK WATCHERS - the audacity to resume the event loop after a fork |
1057 | =head3 FORK WATCHERS - the audacity to resume the event loop after a fork |
… | |
… | |
1002 | |
1125 | |
1003 | =back |
1126 | =back |
1004 | |
1127 | |
1005 | =head3 ASYNC WATCHERS - how to wake up another event loop |
1128 | =head3 ASYNC WATCHERS - how to wake up another event loop |
1006 | |
1129 | |
1007 | Async watchers are provided by EV, but have little use in perl directly, as perl |
1130 | Async watchers are provided by EV, but have little use in perl directly, |
1008 | neither supports threads nor direct access to signal handlers or other |
1131 | as perl neither supports threads running in parallel nor direct access to |
1009 | contexts where they could be of value. |
1132 | signal handlers or other contexts where they could be of value. |
1010 | |
1133 | |
1011 | It is, however, possible to use them from the XS level. |
1134 | It is, however, possible to use them from the XS level. |
1012 | |
1135 | |
1013 | Please see the libev documentation for further details. |
1136 | Please see the libev documentation for further details. |
1014 | |
1137 | |
… | |
… | |
1016 | |
1139 | |
1017 | =item $w = EV::async $callback |
1140 | =item $w = EV::async $callback |
1018 | |
1141 | |
1019 | =item $w = EV::async_ns $callback |
1142 | =item $w = EV::async_ns $callback |
1020 | |
1143 | |
|
|
1144 | =item $w = $loop->async ($callback) |
|
|
1145 | |
|
|
1146 | =item $w = $loop->async_ns ($callback) |
|
|
1147 | |
1021 | =item $w->send |
1148 | =item $w->send |
1022 | |
1149 | |
1023 | =item $bool = $w->async_pending |
1150 | =item $bool = $w->async_pending |
1024 | |
1151 | |
1025 | =back |
1152 | =back |
|
|
1153 | |
|
|
1154 | =head3 CLEANUP WATCHERS - how to clean up when the event loop goes away |
|
|
1155 | |
|
|
1156 | Cleanup watchers are not supported on the Perl level, they can only be |
|
|
1157 | used via XS currently. |
1026 | |
1158 | |
1027 | |
1159 | |
1028 | =head1 PERL SIGNALS |
1160 | =head1 PERL SIGNALS |
1029 | |
1161 | |
1030 | While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour |
1162 | While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour |
… | |
… | |
1042 | my $async_check = EV::check sub { }; |
1174 | my $async_check = EV::check sub { }; |
1043 | |
1175 | |
1044 | This ensures that perl gets into control for a short time to handle any |
1176 | This ensures that perl gets into control for a short time to handle any |
1045 | pending signals, and also ensures (slightly) slower overall operation. |
1177 | pending signals, and also ensures (slightly) slower overall operation. |
1046 | |
1178 | |
1047 | =head1 THREADS |
1179 | =head1 ITHREADS |
1048 | |
1180 | |
1049 | Threads are not supported by this module in any way. Perl pseudo-threads |
1181 | Ithreads are not supported by this module in any way. Perl pseudo-threads |
1050 | is evil stuff and must die. As soon as Perl gains real threads I will work |
1182 | is evil stuff and must die. Real threads as provided by Coro are fully |
1051 | on thread support for it. |
1183 | supported (and enhanced support is available via L<Coro::EV>). |
1052 | |
1184 | |
1053 | =head1 FORK |
1185 | =head1 FORK |
1054 | |
1186 | |
1055 | Most of the "improved" event delivering mechanisms of modern operating |
1187 | Most of the "improved" event delivering mechanisms of modern operating |
1056 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
1188 | systems have quite a few problems with fork(2) (to put it bluntly: it is |
… | |
… | |
1078 | |
1210 | |
1079 | 1; |
1211 | 1; |
1080 | |
1212 | |
1081 | =head1 SEE ALSO |
1213 | =head1 SEE ALSO |
1082 | |
1214 | |
|
|
1215 | L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS> |
1083 | L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as |
1216 | (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as event |
1084 | event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient |
1217 | loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient thread |
1085 | coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for |
1218 | integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for |
1086 | event-loop agnostic and portable event driven programming. |
1219 | event-loop agnostic and portable event driven programming. |
1087 | |
1220 | |
1088 | =head1 AUTHOR |
1221 | =head1 AUTHOR |
1089 | |
1222 | |
1090 | Marc Lehmann <schmorp@schmorp.de> |
1223 | Marc Lehmann <schmorp@schmorp.de> |