ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/EV.pm
(Generate patch)

Comparing EV/EV.pm (file contents):
Revision 1.18 by root, Thu Nov 1 08:10:03 2007 UTC vs.
Revision 1.141 by root, Tue Oct 22 10:43:05 2013 UTC

1=head1 NAME 1=head1 NAME
2 2
3EV - perl interface to libevent, monkey.org/~provos/libevent/ 3EV - perl interface to libev, a high performance full-featured event loop
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use EV; 7 use EV;
8
9 # TIMERS
10
11 my $w = EV::timer 2, 0, sub {
12 warn "is called after 2s";
13 };
14
15 my $w = EV::timer 2, 2, sub {
16 warn "is called roughly every 2s (repeat = 2)";
17 };
18
19 undef $w; # destroy event watcher again
20
21 my $w = EV::periodic 0, 60, 0, sub {
22 warn "is called every minute, on the minute, exactly";
23 };
24
25 # IO
26
27 my $w = EV::io *STDIN, EV::READ, sub {
28 my ($w, $revents) = @_; # all callbacks receive the watcher and event mask
29 warn "stdin is readable, you entered: ", <STDIN>;
30 };
31
32 # SIGNALS
33
34 my $w = EV::signal 'QUIT', sub {
35 warn "sigquit received\n";
36 };
37
38 # CHILD/PID STATUS CHANGES
8 39
9 # TIMER 40 my $w = EV::child 666, 0, sub {
41 my ($w, $revents) = @_;
42 my $status = $w->rstatus;
43 };
10 44
11 my $w = EV::timer 2, 0, sub { 45 # STAT CHANGES
12 warn "is called after 2s"; 46 my $w = EV::stat "/etc/passwd", 10, sub {
13 };
14
15 my $w = EV::timer 2, 1, sub {
16 warn "is called roughly every 2s (repeat = 1)";
17 };
18
19 undef $w; # destroy event watcher again
20
21 my $w = EV::timer_abs 0, 60, sub {
22 warn "is called every minute, on the minute, exactly";
23 };
24
25 # IO
26
27 my $w = EV::io \*STDIN, EV::READ | EV::PERSIST, sub {
28 my ($w, $revents) = @_; # all callbacks get the watcher object and event mask
29 if ($revents & EV::TIMEOUT) {
30 warn "nothing received on stdin for 10 seconds, retrying";
31 } else {
32 warn "stdin is readable, you entered: ", <STDIN>;
33 }
34 };
35 $w->timeout (10);
36
37 my $w = EV::timed_io \*STDIN, EV::READ, 30, sub {
38 my ($w, $revents) = @_; 47 my ($w, $revents) = @_;
39 if ($revents & EV::TIMEOUT) { 48 warn $w->path, " has changed somehow.\n";
40 warn "nothing entered within 30 seconds, bye bye.\n";
41 $w->stop;
42 } else {
43 my $line = <STDIN>;
44 warn "you entered something, you again have 30 seconds.\n";
45 }
46 }; 49 };
47 50
48 # SIGNALS
49
50 my $w = EV::signal 'QUIT', sub {
51 warn "sigquit received\n";
52 };
53
54 my $w = EV::signal 3, sub {
55 warn "sigquit received (this is GNU/Linux, right?)\n";
56 };
57
58 # CHILD/PID STATUS CHANGES
59
60 my $w = EV::child 666, sub {
61 my ($w, $revents, $status) = @_;
62 };
63
64 # MAINLOOP 51 # MAINLOOP
65 EV::dispatch; # loop as long as watchers are active 52 EV::run; # loop until EV::unloop is called or all watchers stop
66 EV::loop; # the same thing
67 EV::loop EV::LOOP_ONESHOT; # block until some events could be handles 53 EV::run EV::RUN_ONCE; # block until at least one event could be handled
68 EV::loop EV::LOOP_NONBLOCK; # check and handle some events, but do not wait 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
58If you only need timer, I/O, signal, child and idle watchers and not the
59advanced functionality of this module, consider using L<AnyEvent> instead,
60specifically the simplified API described in L<AE>.
61
62When used with EV as backend, the L<AE> API is as fast as the native L<EV>
63API, but your programs/modules will still run with many other event loops.
69 64
70=head1 DESCRIPTION 65=head1 DESCRIPTION
71 66
72This module provides an interface to libev 67This module provides an interface to libev
73(L<http://software.schmorp.de/pkg/libev.html>). You probably should 68(L<http://software.schmorp.de/pkg/libev.html>). While the documentation
74acquaint yourself with its documentation and source code to be able to use 69below is comprehensive, one might also consult the documentation of
75this module fully. 70libev itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod> or
71F<perldoc EV::libev>) for more subtle details on watcher semantics or some
72discussion on the available backends, or how to force a specific backend
73with C<LIBEV_FLAGS>, or just about in any case because it has much more
74detailed information.
75
76This module is very fast and scalable. It is actually so fast that you
77can use it through the L<AnyEvent> module, stay portable to other event
78loops (if you don't rely on any watcher types not available through it)
79and still be faster than with any other event loop currently supported in
80Perl.
81
82=head2 PORTING FROM EV 3.X to 4.X
83
84EV version 4 introduces a number of incompatible changes summarised
85here. According to the depreciation strategy used by libev, there is a
86compatibility 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
88updated).
89
90This compatibility layer will be switched off in some future release.
91
92All changes relevant to Perl are renames of symbols, functions and
93methods:
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
110The loop object methods corresponding to the functions above have been
111similarly renamed.
112
113=head2 MODULE EXPORTS
114
115This module does not export any symbols.
76 116
77=cut 117=cut
78 118
79package EV; 119package EV;
80 120
81use strict; 121use common::sense;
82 122
83BEGIN { 123BEGIN {
84 our $VERSION = '0.03'; 124 our $VERSION = '4.15';
85 use XSLoader; 125 use XSLoader;
126 local $^W = 0; # avoid spurious warning
86 XSLoader::load "EV", $VERSION; 127 XSLoader::load "EV", $VERSION;
87} 128}
88 129
89@EV::Io::ISA = 130@EV::IO::ISA =
90@EV::Timer::ISA = 131@EV::Timer::ISA =
91@EV::Periodic::ISA = 132@EV::Periodic::ISA =
92@EV::Signal::ISA = 133@EV::Signal::ISA =
134@EV::Child::ISA =
135@EV::Stat::ISA =
93@EV::Idle::ISA = 136@EV::Idle::ISA =
94@EV::Prepare::ISA = 137@EV::Prepare::ISA =
95@EV::Check::ISA = 138@EV::Check::ISA =
96@EV::Child::ISA = "EV::Watcher"; 139@EV::Embed::ISA =
140@EV::Fork::ISA =
141@EV::Async::ISA =
142 "EV::Watcher";
143
144@EV::Loop::Default::ISA = "EV::Loop";
145
146=head1 EVENT LOOPS
147
148EV supports multiple event loops: There is a single "default event loop"
149that can handle everything including signals and child watchers, and any
150number of "dynamic event loops" that can use different backends (with
151various limitations), but no child and signal watchers.
152
153You do not have to do anything to create the default event loop: When
154the module is loaded a suitable backend is selected on the premise of
155selecting a working backend (which for example rules out kqueue on most
156BSDs). Modules should, unless they have "special needs" always use the
157default loop as this is fastest (perl-wise), best supported by other
158modules (e.g. AnyEvent or Coro) and most portable event loop.
159
160For specific programs you can create additional event loops dynamically.
161
162If you want to take advantage of kqueue (which often works properly for
163sockets only) even though the default loop doesn't enable it, you can
164I<embed> a kqueue loop into the default loop: running the default loop
165will then also service the kqueue loop to some extent. See the example in
166the section about embed watchers for an example on how to achieve that.
167
168=over 4
169
170=item $loop = new EV::Loop [$flags]
171
172Create a new event loop as per the specified flags. Please refer to
173the C<ev_loop_new ()> function description in the libev documentation
174(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>,
175or locally-installed as F<EV::libev> manpage) for more info.
176
177The loop will automatically be destroyed when it is no longer referenced
178by any watcher and the loop object goes out of scope.
179
180If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK>
181is recommended, as only the default event loop is protected by this
182module. If you I<are> embedding this loop in the default loop, this is not
183necessary, as C<EV::embed> automatically does the right thing on fork.
184
185=item $loop->loop_fork
186
187Must be called after a fork in the child, before entering or continuing
188the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
189this function automatically, at some performance loss (refer to the libev
190documentation).
191
192=item $loop->verify
193
194Calls C<ev_verify> to make internal consistency checks (for debugging
195libev) and abort the program if any data structures were found to be
196corrupted.
197
198=item $loop = EV::default_loop [$flags]
199
200Return the default loop (which is a singleton object). Since this module
201already creates the default loop with default flags, specifying flags here
202will not have any effect unless you destroy the default loop first, which
203isn't supported. So in short: don't do it, and if you break it, you get to
204keep the pieces.
205
206=back
207
97 208
98=head1 BASIC INTERFACE 209=head1 BASIC INTERFACE
99 210
100=over 4 211=over 4
101 212
102=item $EV::NPRI
103
104How many priority levels are available.
105
106=item $EV::DIED 213=item $EV::DIED
107 214
108Must contain a reference to a function that is called when a callback 215Must contain a reference to a function that is called when a callback
109throws an exception (with $@ containing thr error). The default prints an 216throws an exception (with $@ containing the error). The default prints an
110informative message and continues. 217informative message and continues.
111 218
112If this callback throws an exception it will be silently ignored. 219If this callback throws an exception it will be silently ignored.
113 220
221=item $flags = EV::supported_backends
222
223=item $flags = EV::recommended_backends
224
225=item $flags = EV::embeddable_backends
226
227Returns the set (see C<EV::BACKEND_*> flags) of backends supported by this
228instance of EV, the set of recommended backends (supposed to be good) for
229this platform and the set of embeddable backends (see EMBED WATCHERS).
230
231=item EV::sleep $seconds
232
233Block the process for the given number of (fractional) seconds.
234
235=item $time = EV::time
236
237Returns the current time in (fractional) seconds since the epoch.
238
114=item $time = EV::now 239=item $time = EV::now
115 240
116Returns the time in (fractional) seconds since the epoch. 241=item $time = $loop->now
117 242
243Returns the time the last event loop iteration has been started. This
244is the time that (relative) timers are based on, and referring to it is
245usually faster then calling EV::time.
246
247=item EV::now_update
248
249=item $loop->now_update
250
251Establishes the current time by querying the kernel, updating the time
252returned by C<EV::now> in the progress. This is a costly operation and
253is usually done automatically within C<EV::loop>.
254
255This function is rarely useful, but when some event callback runs for a
256very long time without entering the event loop, updating libev's idea of
257the current time is a good idea.
258
259=item EV::suspend
260
261=item $loop->suspend
262
263=item EV::resume
264
265=item $loop->resume
266
267These two functions suspend and resume a loop, for use when the loop is
268not used for a while and timeouts should not be processed.
269
270A typical use case would be an interactive program such as a game: When
271the user presses C<^Z> to suspend the game and resumes it an hour later it
272would be best to handle timeouts as if no time had actually passed while
273the program was suspended. This can be achieved by calling C<suspend>
274in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
275C<resume> directly afterwards to resume timer processing.
276
277Effectively, all C<timer> watchers will be delayed by the time spend
278between C<suspend> and C<resume>, and all C<periodic> watchers
279will be rescheduled (that is, they will lose any events that would have
280occured while suspended).
281
282After calling C<suspend> you B<must not> call I<any> function on the given
283loop other than C<resume>, and you B<must not> call C<resume>
284without a previous call to C<suspend>.
285
286Calling C<suspend>/C<resume> has the side effect of updating the event
287loop time (see C<now_update>).
288
289=item $backend = EV::backend
290
291=item $backend = $loop->backend
292
293Returns an integer describing the backend used by libev (EV::BACKEND_SELECT
294or EV::BACKEND_EPOLL).
295
296=item $active = EV::run [$flags]
297
298=item $active = $loop->run ([$flags])
299
300Begin checking for events and calling callbacks. It returns when a
301callback calls EV::unloop or the flasg are nonzero (in which case the
302return value is true) or when there are no active watchers which reference
303the loop (keepalive is true), in which case the return value will be
304false. The returnv alue can generally be interpreted as "if true, there is
305more work left to do".
306
307The $flags argument can be one of the following:
308
309 0 as above
310 EV::RUN_ONCE block at most once (wait, but do not loop)
311 EV::RUN_NOWAIT do not block at all (fetch/handle events but do not wait)
312
313=item EV::break [$how]
314
315=item $loop->break ([$how])
316
317When called with no arguments or an argument of EV::BREAK_ONE, makes the
318innermost call to EV::loop return.
319
320When called with an argument of EV::BREAK_ALL, all calls to EV::loop will
321return as fast as possible.
322
323When called with an argument of EV::BREAK_CANCEL, any pending break will
324be cancelled.
325
118=item $version = EV::version 326=item $count = EV::iteration
119 327
120=item $method = EV::method 328=item $count = $loop->iteration
121 329
122Return version string and event polling method used. 330Return the number of times the event loop has polled for new
331events. Sometimes useful as a generation counter.
123 332
124=item EV::loop $flags # EV::LOOP_ONCE, EV::LOOP_ONESHOT 333=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
125 334
126=item EV::loopexit $after 335=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
127 336
128Exit any active loop or dispatch after C<$after> seconds or immediately if 337This function rolls together an I/O and a timer watcher for a single
129C<$after> is missing or zero. 338one-shot event without the need for managing a watcher object.
130 339
131=item EV::dispatch 340If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
341must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
342| EV::WRITE>, indicating the type of I/O event you want to wait for. If
343you do not want to wait for some I/O event, specify C<undef> for
344C<$fh_or_undef> and C<0> for C<$events>).
132 345
133Same as C<EV::loop 0>. 346If timeout is C<undef> or negative, then there will be no
347timeout. Otherwise a EV::timer with this value will be started.
134 348
135=item EV::event $callback 349When an error occurs or either the timeout or I/O watcher triggers, then
350the callback will be called with the received event set (in general
351you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>,
352C<EV::WRITE> and C<EV::TIMER>).
136 353
137Creates a new event watcher waiting for nothing, calling the given callback. 354EV::once doesn't return anything: the watchers stay active till either
355of them triggers, then they will be stopped and freed, and the callback
356invoked.
138 357
358=item EV::feed_fd_event $fd, $revents
359
360=item $loop->feed_fd_event ($fd, $revents)
361
362Feed an event on a file descriptor into EV. EV will react to this call as
363if the readyness notifications specified by C<$revents> (a combination of
364C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
365
366=item EV::feed_signal_event $signal
367
368Feed a signal event into the default loop. EV will react to this call as
369if the signal specified by C<$signal> had occured.
370
371=item EV::feed_signal $signal
372
373Feed a signal event into EV - unlike C<EV::feed_signal_event>, this works
374regardless of which loop has registered the signal, and is mainly useful
375fro custom signal implementations.
376
377=item EV::set_io_collect_interval $time
378
379=item $loop->set_io_collect_interval ($time)
380
381=item EV::set_timeout_collect_interval $time
382
383=item $loop->set_timeout_collect_interval ($time)
384
385These advanced functions set the minimum block interval when polling for I/O events and the minimum
386wait interval for timer events. See the libev documentation at
387L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP>
388(locally installed as F<EV::libev>) for a more detailed discussion.
389
390=item $count = EV::pending_count
391
392=item $count = $loop->pending_count
393
394Returns the number of currently pending watchers.
395
396=item EV::invoke_pending
397
398=item $loop->invoke_pending
399
400Invoke all currently pending watchers.
401
402=back
403
404
405=head1 WATCHER OBJECTS
406
407A watcher is an object that gets created to record your interest in some
408event. For instance, if you want to wait for STDIN to become readable, you
409would create an EV::io watcher for that:
410
411 my $watcher = EV::io *STDIN, EV::READ, sub {
412 my ($watcher, $revents) = @_;
413 warn "yeah, STDIN should now be readable without blocking!\n"
414 };
415
416All watchers can be active (waiting for events) or inactive (paused). Only
417active watchers will have their callbacks invoked. All callbacks will be
418called with at least two arguments: the watcher and a bitmask of received
419events.
420
421Each watcher type has its associated bit in revents, so you can use the
422same callback for multiple watchers. The event mask is named after the
423type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
424EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
425(which can set both EV::READ and EV::WRITE bits).
426
427In the rare case where one wants to create a watcher but not start it at
428the same time, each constructor has a variant with a trailing C<_ns> in
429its name, e.g. EV::io has a non-starting variant EV::io_ns and so on.
430
431Please note that a watcher will automatically be stopped when the watcher
432object is destroyed, so you I<need> to keep the watcher objects returned by
433the constructors.
434
435Also, all methods changing some aspect of a watcher (->set, ->priority,
436->fh and so on) automatically stop and start it again if it is active,
437which means pending events get lost.
438
439=head2 COMMON WATCHER METHODS
440
441This section lists methods common to all watchers.
442
443=over 4
444
445=item $w->start
446
447Starts a watcher if it isn't active already. Does nothing to an already
448active watcher. By default, all watchers start out in the active state
449(see the description of the C<_ns> variants if you need stopped watchers).
450
451=item $w->stop
452
453Stop a watcher if it is active. Also clear any pending events (events that
454have been received but that didn't yet result in a callback invocation),
455regardless of whether the watcher was active or not.
456
457=item $bool = $w->is_active
458
459Returns true if the watcher is active, false otherwise.
460
461=item $current_data = $w->data
462
463=item $old_data = $w->data ($new_data)
464
465Queries a freely usable data scalar on the watcher and optionally changes
466it. This is a way to associate custom data with a watcher:
467
468 my $w = EV::timer 60, 0, sub {
469 warn $_[0]->data;
470 };
471 $w->data ("print me!");
472
473=item $current_cb = $w->cb
474
475=item $old_cb = $w->cb ($new_cb)
476
477Queries the callback on the watcher and optionally changes it. You can do
478this at any time without the watcher restarting.
479
480=item $current_priority = $w->priority
481
482=item $old_priority = $w->priority ($new_priority)
483
484Queries the priority on the watcher and optionally changes it. Pending
485watchers with higher priority will be invoked first. The valid range of
486priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
487-2). If the priority is outside this range it will automatically be
488normalised to the nearest valid priority.
489
490The default priority of any newly-created watcher is 0.
491
492Note that the priority semantics have not yet been fleshed out and are
493subject to almost certain change.
494
495=item $w->invoke ($revents)
496
497Call the callback *now* with the given event mask.
498
499=item $w->feed_event ($revents)
500
501Feed some events on this watcher into EV. EV will react to this call as if
502the watcher had received the given C<$revents> mask.
503
504=item $revents = $w->clear_pending
505
506If the watcher is pending, this function clears its pending status and
507returns its C<$revents> bitset (as if its callback was invoked). If the
508watcher isn't pending it does nothing and returns C<0>.
509
510=item $previous_state = $w->keepalive ($bool)
511
512Normally, C<EV::loop> will return when there are no active watchers
513(which is a "deadlock" because no progress can be made anymore). This is
514convenient because it allows you to start your watchers (and your jobs),
515call C<EV::loop> once and when it returns you know that all your jobs are
516finished (or they forgot to register some watchers for their task :).
517
518Sometimes, however, this gets in your way, for example when the module
519that calls C<EV::loop> (usually the main program) is not the same module
520as a long-living watcher (for example a DNS client module written by
521somebody else even). Then you might want any outstanding requests to be
522handled, but you would not want to keep C<EV::loop> from returning just
523because you happen to have this long-running UDP port watcher.
524
525In this case you can clear the keepalive status, which means that even
526though your watcher is active, it won't keep C<EV::loop> from returning.
527
528The initial value for keepalive is true (enabled), and you can change it
529any time.
530
531Example: Register an I/O watcher for some UDP socket but do not keep the
532event loop from running just because of that watcher.
533
534 my $udp_socket = ...
535 my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... };
536 $udp_watcher->keepalive (0);
537
538=item $loop = $w->loop
539
540Return the loop that this watcher is attached to.
541
542=back
543
544
545=head1 WATCHER TYPES
546
547Each of the following subsections describes a single watcher type.
548
549=head3 I/O WATCHERS - is this file descriptor readable or writable?
550
551=over 4
552
139=item my $w = EV::io $fileno_or_fh, $eventmask, $callback 553=item $w = EV::io $fileno_or_fh, $eventmask, $callback
140 554
141=item my $w = EV::io_ns $fileno_or_fh, $eventmask, $callback 555=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
556
557=item $w = $loop->io ($fileno_or_fh, $eventmask, $callback)
558
559=item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback)
142 560
143As long as the returned watcher object is alive, call the C<$callback> 561As long as the returned watcher object is alive, call the C<$callback>
144when the events specified in C<$eventmask> happen. Initially, the timeout 562when at least one of events specified in C<$eventmask> occurs.
145is disabled.
146 563
147You can additionall set a timeout to occur on the watcher, but note that
148this timeout will not be reset when you get an I/O event in the EV::PERSIST
149case, and reaching a timeout will always stop the watcher even in the
150EV::PERSIST case.
151
152If you want a timeout to occur only after a specific time of inactivity, set
153a repeating timeout and do NOT use EV::PERSIST.
154
155Eventmask can be one or more of these constants ORed together: 564The $eventmask can be one or more of these constants ORed together:
156 565
157 EV::READ wait until read() wouldn't block anymore 566 EV::READ wait until read() wouldn't block anymore
158 EV::WRITE wait until write() wouldn't block anymore 567 EV::WRITE wait until write() wouldn't block anymore
159 EV::PERSIST stay active after a (non-timeout) event occured
160 568
161The C<io_ns> variant doesn't add/start the newly created watcher. 569The C<io_ns> variant doesn't start (activate) the newly created watcher.
162 570
163=item my $w = EV::timed_io $fileno_or_fh, $eventmask, $timeout, $callback 571=item $w->set ($fileno_or_fh, $eventmask)
164 572
165=item my $w = EV::timed_io_ns $fileno_or_fh, $eventmask, $timeout, $callback 573Reconfigures the watcher, see the constructor above for details. Can be
574called at any time.
166 575
167Same as C<io> and C<io_ns>, but also specifies a timeout (as if there was 576=item $current_fh = $w->fh
168a call to C<< $w->timeout ($timout, 1) >>. The persist flag is not allowed
169and will automatically be cleared. The watcher will be restarted after each event.
170 577
171If the timeout is zero or undef, no timeout will be set, and a normal 578=item $old_fh = $w->fh ($new_fh)
172watcher (with the persist flag set!) will be created.
173 579
174This has the effect of timing out after the specified period of inactivity 580Returns the previously set filehandle and optionally set a new one.
175has happened.
176 581
177Due to the design of libevent, this is also relatively inefficient, having 582=item $current_eventmask = $w->events
178one or two io watchers and a separate timeout watcher that you reset on
179activity (by calling its C<start> method) is usually more efficient.
180 583
584=item $old_eventmask = $w->events ($new_eventmask)
585
586Returns the previously set event mask and optionally set a new one.
587
588=back
589
590
591=head3 TIMER WATCHERS - relative and optionally repeating timeouts
592
593=over 4
594
181=item my $w = EV::timer $after, $repeat, $callback 595=item $w = EV::timer $after, $repeat, $callback
182 596
183=item my $w = EV::timer_ns $after, $repeat, $callback 597=item $w = EV::timer_ns $after, $repeat, $callback
184 598
185Calls the callback after C<$after> seconds. If C<$repeat> is true, the 599=item $w = $loop->timer ($after, $repeat, $callback)
186timer will be restarted after the callback returns. This means that the
187callback would be called roughly every C<$after> seconds, prolonged by the
188time the callback takes.
189 600
601=item $w = $loop->timer_ns ($after, $repeat, $callback)
602
603Calls the callback after C<$after> seconds (which may be fractional). If
604C<$repeat> is non-zero, the timer will be restarted (with the $repeat
605value as $after) after the callback returns.
606
607This means that the callback would be called roughly after C<$after>
608seconds, and then every C<$repeat> seconds. The timer does his best not
609to drift, but it will not invoke the timer more often then once per event
610loop iteration, and might drift in other cases. If that isn't acceptable,
611look at EV::periodic, which can provide long-term stable timers.
612
613The timer is based on a monotonic clock, that is, if somebody is sitting
614in front of the machine while the timer is running and changes the system
615clock, the timer will nevertheless run (roughly) the same time.
616
190The C<timer_ns> variant doesn't add/start the newly created watcher. 617The C<timer_ns> variant doesn't start (activate) the newly created watcher.
191 618
192=item my $w = EV::timer_abs $at, $interval, $callback 619=item $w->set ($after, $repeat)
193 620
194=item my $w = EV::timer_abs_ns $at, $interval, $callback 621Reconfigures the watcher, see the constructor above for details. Can be called at
622any time.
195 623
196Similar to EV::timer, but the time is given as an absolute point in time 624=item $w->again
197(C<$at>), plus an optional C<$interval>.
198 625
199If the C<$interval> is zero, then the callback will be called at the time 626Similar to the C<start> method, but has special semantics for repeating timers:
200C<$at> if that is in the future, or as soon as possible if its in the
201past. It will not automatically repeat.
202 627
203If the C<$interval> is nonzero, then the watcher will always be scheduled 628If the timer is active and non-repeating, it will be stopped.
204to time out at the next C<$at + integer * $interval> time.
205 629
206This can be used to schedule a callback to run at very regular intervals, 630If the timer is active and repeating, reset the timeout to occur
207as long as the processing time is less then the interval (otherwise 631C<$repeat> seconds after now.
208obviously events will be skipped). 632
633If the timer is inactive and repeating, start it using the repeat value.
634
635Otherwise do nothing.
636
637This behaviour is useful when you have a timeout for some IO
638operation. You create a timer object with the same value for C<$after> and
639C<$repeat>, and then, in the read/write watcher, run the C<again> method
640on the timeout.
641
642=back
643
644
645=head3 PERIODIC WATCHERS - to cron or not to cron?
646
647=over 4
648
649=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
650
651=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
652
653=item $w = $loop->periodic ($at, $interval, $reschedule_cb, $callback)
654
655=item $w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback)
656
657Similar to EV::timer, but is not based on relative timeouts but on
658absolute times. Apart from creating "simple" timers that trigger "at" the
659specified time, it can also be used for non-drifting absolute timers and
660more complex, cron-like, setups that are not adversely affected by time
661jumps (i.e. when the system clock is changed by explicit date -s or other
662means such as ntpd). It is also the most complex watcher type in EV.
663
664It has three distinct "modes":
665
666=over 4
667
668=item * absolute timer ($interval = $reschedule_cb = 0)
669
670This time simply fires at the wallclock time C<$at> and doesn't repeat. It
671will not adjust when a time jump occurs, that is, if it is to be run
672at January 1st 2011 then it will run when the system time reaches or
673surpasses this time.
674
675=item * repeating interval timer ($interval > 0, $reschedule_cb = 0)
676
677In this mode the watcher will always be scheduled to time out at the
678next C<$at + N * $interval> time (for some integer N) and then repeat,
679regardless of any time jumps.
680
681This can be used to create timers that do not drift with respect to system
682time:
683
684 my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" };
685
686That doesn't mean there will always be 3600 seconds in between triggers,
687but only that the the callback will be called when the system time shows a
688full hour (UTC).
209 689
210Another way to think about it (for the mathematically inclined) is that 690Another way to think about it (for the mathematically inclined) is that
211C<timer_abs> will try to tun the callback at the next possible time where 691EV::periodic will try to run the callback in this mode at the next
212C<$time = $at (mod $interval)>, regardless of any time jumps. 692possible time where C<$time = $at (mod $interval)>, regardless of any time
693jumps.
213 694
695=item * manual reschedule mode ($reschedule_cb = coderef)
696
697In this mode $interval and $at are both being ignored. Instead, each
698time the periodic watcher gets scheduled, the reschedule callback
699($reschedule_cb) will be called with the watcher as first, and the current
700time as second argument.
701
702I<This callback MUST NOT stop or destroy this or any other periodic
703watcher, ever, and MUST NOT call any event loop functions or methods>. If
704you need to stop it, return 1e30 and stop it afterwards. You may create
705and start a C<EV::prepare> watcher for this task.
706
707It must return the next time to trigger, based on the passed time value
708(that is, the lowest time value larger than or equal to to the second
709argument). It will usually be called just before the callback will be
710triggered, but might be called at other times, too.
711
712This can be used to create very complex timers, such as a timer that
713triggers on each midnight, local time (actually 24 hours after the last
714midnight, to keep the example simple. If you know a way to do it correctly
715in about the same space (without requiring elaborate modules), drop me a
716note :):
717
718 my $daily = EV::periodic 0, 0, sub {
719 my ($w, $now) = @_;
720
721 use Time::Local ();
722 my (undef, undef, undef, $d, $m, $y) = localtime $now;
723 86400 + Time::Local::timelocal 0, 0, 0, $d, $m, $y
724 }, sub {
725 print "it's midnight or likely shortly after, now\n";
726 };
727
728=back
729
214The C<timer_abs_ns> variant doesn't add/start the newly created watcher. 730The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
215 731
732=item $w->set ($at, $interval, $reschedule_cb)
733
734Reconfigures the watcher, see the constructor above for details. Can be called at
735any time.
736
737=item $w->again
738
739Simply stops and starts the watcher again.
740
741=item $time = $w->at
742
743Return the time that the watcher is expected to trigger next.
744
745=back
746
747
748=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
749
750=over 4
751
216=item my $w = EV::signal $signal, $callback 752=item $w = EV::signal $signal, $callback
217 753
218=item my $w = EV::signal_ns $signal, $callback 754=item $w = EV::signal_ns $signal, $callback
219 755
756=item $w = $loop->signal ($signal, $callback)
757
758=item $w = $loop->signal_ns ($signal, $callback)
759
220Call the callback when $signal is received (the signal can be specified 760Call the callback when $signal is received (the signal can be specified by
221by number or by name, just as with kill or %SIG). Signal watchers are 761number or by name, just as with C<kill> or C<%SIG>).
222persistent no natter what. 762
763Only one event loop can grab a given signal - attempting to grab the same
764signal from two EV loops will crash the program immediately or cause data
765corruption.
223 766
224EV will grab the signal for the process (the kernel only allows one 767EV will grab the signal for the process (the kernel only allows one
225component to receive signals) when you start a signal watcher, and 768component to receive a signal at a time) when you start a signal watcher,
226removes it again when you stop it. Pelr does the same when you add/remove 769and removes it again when you stop it. Perl does the same when you
227callbacks to %SIG, so watch out. 770add/remove callbacks to C<%SIG>, so watch out.
228 771
229Unfortunately, only one handler can be registered per signal. Screw 772You can have as many signal watchers per signal as you want.
230libevent.
231 773
232The C<signal_ns> variant doesn't add/start the newly created watcher. 774The C<signal_ns> variant doesn't start (activate) the newly created watcher.
233 775
234=back 776=item $w->set ($signal)
235 777
236=head1 THE EV::Event CLASS 778Reconfigures the watcher, see the constructor above for details. Can be
779called at any time.
237 780
238All EV functions creating an event watcher (designated by C<my $w =>
239above) support the following methods on the returned watcher object:
240
241=over 4
242
243=item $w->add ($timeout)
244
245Stops and (re-)starts the event watcher, setting the optional timeout to
246the given value, or clearing the timeout if none is given.
247
248=item $w->start
249
250Stops and (re-)starts the event watcher without touching the timeout.
251
252=item $w->del
253
254=item $w->stop
255
256Stop the event watcher if it was started.
257
258=item $current_callback = $w->cb
259
260=item $old_callback = $w->cb ($new_callback)
261
262Return the previously set callback and optionally set a new one.
263
264=item $current_fh = $w->fh
265
266=item $old_fh = $w->fh ($new_fh)
267
268Returns the previously set filehandle and optionally set a new one (also
269clears the EV::SIGNAL flag when setting a filehandle).
270
271=item $current_signal = $w->signal 781=item $current_signum = $w->signal
272 782
273=item $old_signal = $w->signal ($new_signal) 783=item $old_signum = $w->signal ($new_signal)
274 784
785Returns the previously set signal (always as a number not name) and
786optionally set a new one.
787
788=back
789
790
791=head3 CHILD WATCHERS - watch out for process status changes
792
793=over 4
794
795=item $w = EV::child $pid, $trace, $callback
796
797=item $w = EV::child_ns $pid, $trace, $callback
798
799=item $w = $loop->child ($pid, $trace, $callback)
800
801=item $w = $loop->child_ns ($pid, $trace, $callback)
802
803Call the callback when a status change for pid C<$pid> (or any pid
804if C<$pid> is 0) has been received (a status change happens when the
805process terminates or is killed, or, when trace is true, additionally when
806it is stopped or continued). More precisely: when the process receives
807a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
808changed/zombie children and call the callback.
809
810It is valid (and fully supported) to install a child watcher after a child
811has exited but before the event loop has started its next iteration (for
812example, first you C<fork>, then the new child process might exit, and
813only then do you install a child watcher in the parent for the new pid).
814
815You can access both exit (or tracing) status and pid by using the
816C<rstatus> and C<rpid> methods on the watcher object.
817
818You can have as many pid watchers per pid as you want, they will all be
819called.
820
821The C<child_ns> variant doesn't start (activate) the newly created watcher.
822
823=item $w->set ($pid, $trace)
824
825Reconfigures the watcher, see the constructor above for details. Can be called at
826any time.
827
828=item $current_pid = $w->pid
829
275Returns the previously set signal number and optionally set a new one (also sets 830Returns the previously set process id and optionally set a new one.
276the EV::SIGNAL flag when setting a signal).
277 831
278=item $current_eventmask = $w->events 832=item $exit_status = $w->rstatus
279 833
280=item $old_eventmask = $w->events ($new_eventmask) 834Return the exit/wait status (as returned by waitpid, see the waitpid entry
835in perlfunc).
281 836
837=item $pid = $w->rpid
838
839Return the pid of the awaited child (useful when you have installed a
840watcher for all pids).
841
842=back
843
844
845=head3 STAT WATCHERS - did the file attributes just change?
846
847=over 4
848
849=item $w = EV::stat $path, $interval, $callback
850
851=item $w = EV::stat_ns $path, $interval, $callback
852
853=item $w = $loop->stat ($path, $interval, $callback)
854
855=item $w = $loop->stat_ns ($path, $interval, $callback)
856
857Call the callback when a file status change has been detected on
858C<$path>. The C<$path> does not need to exist, changing from "path exists"
859to "path does not exist" is a status change like any other.
860
861The C<$interval> is a recommended polling interval for systems where
862OS-supported change notifications don't exist or are not supported. If
863you use C<0> then an unspecified default is used (which is highly
864recommended!), which is to be expected to be around five seconds usually.
865
866This watcher type is not meant for massive numbers of stat watchers,
867as even with OS-supported change notifications, this can be
868resource-intensive.
869
870The C<stat_ns> variant doesn't start (activate) the newly created watcher.
871
872=item ... = $w->stat
873
874This call is very similar to the perl C<stat> built-in: It stats (using
875C<lstat>) the path specified in the watcher and sets perls stat cache (as
876well as EV's idea of the current stat values) to the values found.
877
878In scalar context, a boolean is return indicating success or failure of
879the stat. In list context, the same 13-value list as with stat is returned
880(except that the blksize and blocks fields are not reliable).
881
882In the case of an error, errno is set to C<ENOENT> (regardless of the
883actual error value) and the C<nlink> value is forced to zero (if the stat
884was successful then nlink is guaranteed to be non-zero).
885
886See also the next two entries for more info.
887
888=item ... = $w->attr
889
890Just like C<< $w->stat >>, but without the initial stat'ing: this returns
891the values most recently detected by EV. See the next entry for more info.
892
893=item ... = $w->prev
894
895Just like C<< $w->stat >>, but without the initial stat'ing: this returns
896the previous set of values, before the change.
897
898That is, when the watcher callback is invoked, C<< $w->prev >> will be set
899to the values found I<before> a change was detected, while C<< $w->attr >>
900returns the values found leading to the change detection. The difference (if any)
901between C<prev> and C<attr> is what triggered the callback.
902
903If you did something to the filesystem object and do not want to trigger
904yet another change, you can call C<stat> to update EV's idea of what the
905current attributes are.
906
907=item $w->set ($path, $interval)
908
909Reconfigures the watcher, see the constructor above for details. Can be
910called at any time.
911
912=item $current_path = $w->path
913
914=item $old_path = $w->path ($new_path)
915
282Returns the previously set event mask and optionally set a new one. 916Returns the previously set path and optionally set a new one.
283 917
284=item $w->timeout ($after, $repeat) 918=item $current_interval = $w->interval
285 919
286Resets the timeout (see C<EV::timer> for details). 920=item $old_interval = $w->interval ($new_interval)
287 921
288=item $w->timeout_abs ($at, $interval) 922Returns the previously set interval and optionally set a new one. Can be
923used to query the actual interval used.
289 924
290Resets the timeout (see C<EV::timer_abs> for details).
291
292=item $w->priority_set ($priority)
293
294Set the priority of the watcher to C<$priority> (0 <= $priority < $EV::NPRI).
295
296=back 925=back
297 926
927
928=head3 IDLE WATCHERS - when you've got nothing better to do...
929
930=over 4
931
932=item $w = EV::idle $callback
933
934=item $w = EV::idle_ns $callback
935
936=item $w = $loop->idle ($callback)
937
938=item $w = $loop->idle_ns ($callback)
939
940Call the callback when there are no other pending watchers of the same or
941higher priority (excluding check, prepare and other idle watchers of the
942same or lower priority, of course). They are called idle watchers because
943when the watcher is the highest priority pending event in the process, the
944process is considered to be idle at that priority.
945
946If you want a watcher that is only ever called when I<no> other events are
947outstanding you have to set the priority to C<EV::MINPRI>.
948
949The process will not block as long as any idle watchers are active, and
950they will be called repeatedly until stopped.
951
952For example, if you have idle watchers at priority C<0> and C<1>, and
953an I/O watcher at priority C<0>, then the idle watcher at priority C<1>
954and the I/O watcher will always run when ready. Only when the idle watcher
955at priority C<1> is stopped and the I/O watcher at priority C<0> is not
956pending with the C<0>-priority idle watcher be invoked.
957
958The C<idle_ns> variant doesn't start (activate) the newly created watcher.
959
960=back
961
962
963=head3 PREPARE WATCHERS - customise your event loop!
964
965=over 4
966
967=item $w = EV::prepare $callback
968
969=item $w = EV::prepare_ns $callback
970
971=item $w = $loop->prepare ($callback)
972
973=item $w = $loop->prepare_ns ($callback)
974
975Call the callback just before the process would block. You can still
976create/modify any watchers at this point.
977
978See the EV::check watcher, below, for explanations and an example.
979
980The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
981
982=back
983
984
985=head3 CHECK WATCHERS - customise your event loop even more!
986
987=over 4
988
989=item $w = EV::check $callback
990
991=item $w = EV::check_ns $callback
992
993=item $w = $loop->check ($callback)
994
995=item $w = $loop->check_ns ($callback)
996
997Call the callback just after the process wakes up again (after it has
998gathered events), but before any other callbacks have been invoked.
999
1000This can be used to integrate other event-based software into the EV
1001mainloop: You register a prepare callback and in there, you create io and
1002timer watchers as required by the other software. Here is a real-world
1003example of integrating Net::SNMP (with some details left out):
1004
1005 our @snmp_watcher;
1006
1007 our $snmp_prepare = EV::prepare sub {
1008 # do nothing unless active
1009 $dispatcher->{_event_queue_h}
1010 or return;
1011
1012 # make the dispatcher handle any outstanding stuff
1013 ... not shown
1014
1015 # create an I/O watcher for each and every socket
1016 @snmp_watcher = (
1017 (map { EV::io $_, EV::READ, sub { } }
1018 keys %{ $dispatcher->{_descriptors} }),
1019
1020 EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
1021 ? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
1022 0, sub { },
1023 );
1024 };
1025
1026The callbacks are irrelevant (and are not even being called), the
1027only purpose of those watchers is to wake up the process as soon as
1028one of those events occurs (socket readable, or timer timed out). The
1029corresponding EV::check watcher will then clean up:
1030
1031 our $snmp_check = EV::check sub {
1032 # destroy all watchers
1033 @snmp_watcher = ();
1034
1035 # make the dispatcher handle any new stuff
1036 ... not shown
1037 };
1038
1039The callbacks of the created watchers will not be called as the watchers
1040are destroyed before this can happen (remember EV::check gets called
1041first).
1042
1043The C<check_ns> variant doesn't start (activate) the newly created watcher.
1044
1045=item EV::CHECK constant issues
1046
1047Like all other watcher types, there is a bitmask constant for use in
1048C<$revents> and other places. The C<EV::CHECK> is special as it has
1049the same name as the C<CHECK> sub called by Perl. This doesn't cause
1050big issues on newer perls (beginning with 5.8.9), but it means thatthe
1051constant must be I<inlined>, i.e. runtime calls will not work. That means
1052that as long as you always C<use EV> and then C<EV::CHECK> you are on the
1053safe side.
1054
1055=back
1056
1057
1058=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
1059
1060Fork watchers are called when a C<fork ()> was detected. The invocation
1061is done before the event loop blocks next and before C<check> watchers
1062are being called, and only in the child after the fork.
1063
1064=over 4
1065
1066=item $w = EV::fork $callback
1067
1068=item $w = EV::fork_ns $callback
1069
1070=item $w = $loop->fork ($callback)
1071
1072=item $w = $loop->fork_ns ($callback)
1073
1074Call the callback before the event loop is resumed in the child process
1075after a fork.
1076
1077The C<fork_ns> variant doesn't start (activate) the newly created watcher.
1078
1079=back
1080
1081
1082=head3 EMBED WATCHERS - when one backend isn't enough...
1083
1084This is a rather advanced watcher type that lets you embed one event loop
1085into another (currently only IO events are supported in the embedded
1086loop, other types of watchers might be handled in a delayed or incorrect
1087fashion and must not be used).
1088
1089See the libev documentation at
1090L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_>
1091(locally installed as F<EV::libev>) for more details.
1092
1093In short, this watcher is most useful on BSD systems without working
1094kqueue to still be able to handle a large number of sockets:
1095
1096 my $socket_loop;
1097
1098 # check wether we use SELECT or POLL _and_ KQUEUE is supported
1099 if (
1100 (EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT))
1101 && (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE)
1102 ) {
1103 # use kqueue for sockets
1104 $socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV;
1105 }
1106
1107 # use the default loop otherwise
1108 $socket_loop ||= EV::default_loop;
1109
1110=over 4
1111
1112=item $w = EV::embed $otherloop[, $callback]
1113
1114=item $w = EV::embed_ns $otherloop[, $callback]
1115
1116=item $w = $loop->embed ($otherloop[, $callback])
1117
1118=item $w = $loop->embed_ns ($otherloop[, $callback])
1119
1120Call the callback when the embedded event loop (C<$otherloop>) has any
1121I/O activity. The C<$callback> is optional: if it is missing, then the
1122embedded event loop will be managed automatically (which is recommended),
1123otherwise you have to invoke C<sweep> yourself.
1124
1125The C<embed_ns> variant doesn't start (activate) the newly created watcher.
1126
1127=back
1128
1129=head3 ASYNC WATCHERS - how to wake up another event loop
1130
1131Async watchers are provided by EV, but have little use in perl directly,
1132as perl neither supports threads running in parallel nor direct access to
1133signal handlers or other contexts where they could be of value.
1134
1135It is, however, possible to use them from the XS level.
1136
1137Please see the libev documentation for further details.
1138
1139=over 4
1140
1141=item $w = EV::async $callback
1142
1143=item $w = EV::async_ns $callback
1144
1145=item $w = $loop->async ($callback)
1146
1147=item $w = $loop->async_ns ($callback)
1148
1149=item $w->send
1150
1151=item $bool = $w->async_pending
1152
1153=back
1154
1155=head3 CLEANUP WATCHERS - how to clean up when the event loop goes away
1156
1157Cleanup watchers are not supported on the Perl level, they can only be
1158used via XS currently.
1159
1160
1161=head1 PERL SIGNALS
1162
1163While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
1164with EV is as the same as any other C library: Perl-signals will only be
1165handled when Perl runs, which means your signal handler might be invoked
1166only the next time an event callback is invoked.
1167
1168The solution is to use EV signal watchers (see C<EV::signal>), which will
1169ensure proper operations with regards to other event watchers.
1170
1171If you cannot do this for whatever reason, you can also force a watcher
1172to be called on every event loop iteration by installing a C<EV::check>
1173watcher:
1174
1175 my $async_check = EV::check sub { };
1176
1177This ensures that perl gets into control for a short time to handle any
1178pending signals, and also ensures (slightly) slower overall operation.
1179
298=head1 THREADS 1180=head1 ITHREADS
299 1181
300Threads are not supported by this in any way. Perl pseudo-threads is evil 1182Ithreads are not supported by this module in any way. Perl pseudo-threads
301and must die. 1183is evil stuff and must die. Real threads as provided by Coro are fully
1184supported (and enhanced support is available via L<Coro::EV>).
1185
1186=head1 FORK
1187
1188Most of the "improved" event delivering mechanisms of modern operating
1189systems have quite a few problems with fork(2) (to put it bluntly: it is
1190not supported and usually destructive). Libev makes it possible to work
1191around this by having a function that recreates the kernel state after
1192fork in the child.
1193
1194On non-win32 platforms, this module requires the pthread_atfork
1195functionality to do this automatically for you. This function is quite
1196buggy on most BSDs, though, so YMMV. The overhead for this is quite
1197negligible, because everything the function currently does is set a flag
1198that is checked only when the event loop gets used the next time, so when
1199you do fork but not use EV, the overhead is minimal.
1200
1201On win32, there is no notion of fork so all this doesn't apply, of course.
302 1202
303=cut 1203=cut
304 1204
305our $DIED = sub { 1205our $DIED = sub {
306 warn "EV: error in callback (ignoring): $@"; 1206 warn "EV: error in callback (ignoring): $@";
307}; 1207};
308 1208
309init; 1209default_loop
310 1210 or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_FLAGS}?';
311push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
312 1211
3131; 12121;
314 1213
315=head1 SEE ALSO 1214=head1 SEE ALSO
316 1215
317 L<EV::DNS>, L<event(3)>, L<event.h>, L<evdns.h>. 1216L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS>
318 L<EV::AnyEvent>. 1217(asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as event
1218loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient thread
1219integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
1220event-loop agnostic and portable event driven programming.
319 1221
320=head1 AUTHOR 1222=head1 AUTHOR
321 1223
322 Marc Lehmann <schmorp@schmorp.de> 1224 Marc Lehmann <schmorp@schmorp.de>
323 http://home.schmorp.de/ 1225 http://home.schmorp.de/
324 1226
325=cut 1227=cut
326 1228

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines