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

Comparing EV/EV.pm (file contents):
Revision 1.99 by root, Tue Jul 8 09:37:37 2008 UTC vs.
Revision 1.138 by root, Sun May 6 16:30:27 2012 UTC

… …
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
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.
55 64
56=head1 DESCRIPTION 65=head1 DESCRIPTION
57 66
58This module provides an interface to libev 67This 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
60below is comprehensive, one might also consult the documentation of libev 69below is comprehensive, one might also consult the documentation of
61itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>) for more 70libev itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod> or
62subtle details on watcher semantics or some discussion on the available 71F<perldoc EV::libev>) for more subtle details on watcher semantics or some
63backends, or how to force a specific backend with C<LIBEV_FLAGS>, or just 72discussion on the available backends, or how to force a specific backend
64about in any case because it has much more detailed information. 73with C<LIBEV_FLAGS>, or just about in any case because it has much more
74detailed information.
65 75
66This module is very fast and scalable. It is actually so fast that you 76This module is very fast and scalable. It is actually so fast that you
67can use it through the L<AnyEvent> module, stay portable to other event 77can use it through the L<AnyEvent> module, stay portable to other event
68loops (if you don't rely on any watcher types not available through it) 78loops (if you don't rely on any watcher types not available through it)
69and still be faster than with any other event loop currently supported in 79and still be faster than with any other event loop currently supported in
70Perl. 80Perl.
71 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.
116
72=cut 117=cut
73 118
74package EV; 119package EV;
75 120
76use strict; 121use common::sense;
77 122
78BEGIN { 123BEGIN {
79 our $VERSION = '3.42'; 124 our $VERSION = '4.11';
80 use XSLoader; 125 use XSLoader;
81 XSLoader::load "EV", $VERSION; 126 XSLoader::load "EV", $VERSION;
82} 127}
83 128
84@EV::IO::ISA = 129@EV::IO::ISA =
… …
111default loop as this is fastest (perl-wise), best supported by other 156default loop as this is fastest (perl-wise), best supported by other
112modules (e.g. AnyEvent or Coro) and most portable event loop. 157modules (e.g. AnyEvent or Coro) and most portable event loop.
113 158
114For specific programs you can create additional event loops dynamically. 159For specific programs you can create additional event loops dynamically.
115 160
116If you want to take avdantage of kqueue (which often works properly for 161If you want to take advantage of kqueue (which often works properly for
117sockets only) even though the default loop doesn't enable it, you can 162sockets only) even though the default loop doesn't enable it, you can
118I<embed> a kqueue loop into the default loop: running the default loop 163I<embed> a kqueue loop into the default loop: running the default loop
119will then also service the kqueue loop to some extent. See the example in 164will then also service the kqueue loop to some extent. See the example in
120the section about embed watchers for an example on how to achieve that. 165the section about embed watchers for an example on how to achieve that.
121 166
122=over 4 167=over 4
123 168
124=item $loop = new EV::loop [$flags] 169=item $loop = new EV::Loop [$flags]
125 170
126Create a new event loop as per the specified flags. Please refer to the 171Create a new event loop as per the specified flags. Please refer to
127C<ev_loop_new ()> function description in the libev documentation 172the C<ev_loop_new ()> function description in the libev documentation
128(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>,
129for more info. 174or locally-installed as F<EV::libev> manpage) for more info.
130 175
131The loop will automatically be destroyed when it is no longer referenced 176The loop will automatically be destroyed when it is no longer referenced
132by any watcher and the loop object goes out of scope. 177by any watcher and the loop object goes out of scope.
133 178
134Using C<EV::FLAG_FORKCHECK> is recommended, as only the default event loop 179If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK>
135is protected by this module. 180is recommended, as only the default event loop is protected by this
181module. If you I<are> embedding this loop in the default loop, this is not
182necessary, as C<EV::embed> automatically does the right thing on fork.
136 183
137=item $loop->loop_fork 184=item $loop->loop_fork
138 185
139Must be called after a fork in the child, before entering or continuing 186Must be called after a fork in the child, before entering or continuing
140the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls 187the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
141this function automatically, at some performance loss (refer to the libev 188this function automatically, at some performance loss (refer to the libev
142documentation). 189documentation).
143 190
144=item $loop->loop_verify 191=item $loop->verify
145 192
146Calls C<ev_verify> to make internal consistency checks (for debugging 193Calls C<ev_verify> to make internal consistency checks (for debugging
147libev) and abort the program if any data structures were found to be 194libev) and abort the program if any data structures were found to be
148corrupted. 195corrupted.
149 196
… …
191=item $time = EV::now 238=item $time = EV::now
192 239
193=item $time = $loop->now 240=item $time = $loop->now
194 241
195Returns the time the last event loop iteration has been started. This 242Returns the time the last event loop iteration has been started. This
196is the time that (relative) timers are based on, and refering to it is 243is the time that (relative) timers are based on, and referring to it is
197usually faster then calling EV::time. 244usually faster then calling EV::time.
198 245
246=item EV::now_update
247
248=item $loop->now_update
249
250Establishes the current time by querying the kernel, updating the time
251returned by C<EV::now> in the progress. This is a costly operation and
252is usually done automatically within C<EV::loop>.
253
254This function is rarely useful, but when some event callback runs for a
255very long time without entering the event loop, updating libev's idea of
256the 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
266These two functions suspend and resume a loop, for use when the loop is
267not used for a while and timeouts should not be processed.
268
269A typical use case would be an interactive program such as a game: When
270the user presses C<^Z> to suspend the game and resumes it an hour later it
271would be best to handle timeouts as if no time had actually passed while
272the program was suspended. This can be achieved by calling C<suspend>
273in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
274C<resume> directly afterwards to resume timer processing.
275
276Effectively, all C<timer> watchers will be delayed by the time spend
277between C<suspend> and C<resume>, and all C<periodic> watchers
278will be rescheduled (that is, they will lose any events that would have
279occured while suspended).
280
281After calling C<suspend> you B<must not> call I<any> function on the given
282loop other than C<resume>, and you B<must not> call C<resume>
283without a previous call to C<suspend>.
284
285Calling C<suspend>/C<resume> has the side effect of updating the event
286loop time (see C<now_update>).
287
199=item $backend = EV::backend 288=item $backend = EV::backend
200 289
201=item $backend = $loop->backend 290=item $backend = $loop->backend
202 291
203Returns an integer describing the backend used by libev (EV::METHOD_SELECT 292Returns an integer describing the backend used by libev (EV::BACKEND_SELECT
204or EV::METHOD_EPOLL). 293or EV::BACKEND_EPOLL).
205 294
206=item EV::loop [$flags] 295=item $active = EV::run [$flags]
207 296
208=item $loop->loop ([$flags]) 297=item $active = $loop->run ([$flags])
209 298
210Begin checking for events and calling callbacks. It returns when a 299Begin checking for events and calling callbacks. It returns when a
211callback calls EV::unloop. 300callback calls EV::unloop or the flasg are nonzero (in which case the
301return value is true) or when there are no active watchers which reference
302the loop (keepalive is true), in which case the return value will be
303false. The returnv alue can generally be interpreted as "if true, there is
304more work left to do".
212 305
213The $flags argument can be one of the following: 306The $flags argument can be one of the following:
214 307
215 0 as above 308 0 as above
216 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)
217 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)
218 311
219=item EV::unloop [$how] 312=item EV::break [$how]
220 313
221=item $loop->unloop ([$how]) 314=item $loop->break ([$how])
222 315
223When called with no arguments or an argument of EV::UNLOOP_ONE, makes the 316When called with no arguments or an argument of EV::BREAK_ONE, makes the
224innermost call to EV::loop return. 317innermost call to EV::loop return.
225 318
226When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as 319When called with an argument of EV::BREAK_ALL, all calls to EV::loop will
227fast as possible. 320return as fast as possible.
228 321
229=item $count = EV::loop_count 322When called with an argument of EV::BREAK_CANCEL, any pending break will
323be cancelled.
230 324
325=item $count = EV::iteration
326
231=item $count = $loop->loop_count 327=item $count = $loop->iteration
232 328
233Return the number of times the event loop has polled for new 329Return the number of times the event loop has polled for new
234events. Sometiems useful as a generation counter. 330events. Sometimes useful as a generation counter.
235 331
236=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) 332=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
237 333
238=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) 334=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
239 335
… …
250timeout. Otherwise a EV::timer with this value will be started. 346timeout. Otherwise a EV::timer with this value will be started.
251 347
252When an error occurs or either the timeout or I/O watcher triggers, then 348When an error occurs or either the timeout or I/O watcher triggers, then
253the callback will be called with the received event set (in general 349the callback will be called with the received event set (in general
254you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, 350you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>,
255C<EV::WRITE> and C<EV::TIMEOUT>). 351C<EV::WRITE> and C<EV::TIMER>).
256 352
257EV::once doesn't return anything: the watchers stay active till either 353EV::once doesn't return anything: the watchers stay active till either
258of them triggers, then they will be stopped and freed, and the callback 354of them triggers, then they will be stopped and freed, and the callback
259invoked. 355invoked.
260 356
261=item EV::feed_fd_event ($fd, $revents) 357=item EV::feed_fd_event $fd, $revents
262 358
263=item $loop->feed_fd_event ($fd, $revents) 359=item $loop->feed_fd_event ($fd, $revents)
264 360
265Feed an event on a file descriptor into EV. EV will react to this call as 361Feed an event on a file descriptor into EV. EV will react to this call as
266if the readyness notifications specified by C<$revents> (a combination of 362if the readyness notifications specified by C<$revents> (a combination of
267C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>. 363C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
268 364
269=item EV::feed_signal_event ($signal) 365=item EV::feed_signal_event $signal
270 366
271Feed a signal event into EV. EV will react to this call as if the signal 367Feed a signal event into the default loop. EV will react to this call as
272specified by C<$signal> had occured. 368if the signal specified by C<$signal> had occured.
369
370=item EV::feed_signal $signal
371
372Feed a signal event into EV - unlike C<EV::feed_signal_event>, this works
373regardless of which loop has registered the signal, and is mainly useful
374fro custom signal implementations.
273 375
274=item EV::set_io_collect_interval $time 376=item EV::set_io_collect_interval $time
275 377
276=item $loop->set_io_collect_interval ($time) 378=item $loop->set_io_collect_interval ($time)
277 379
… …
279 381
280=item $loop->set_timeout_collect_interval ($time) 382=item $loop->set_timeout_collect_interval ($time)
281 383
282These advanced functions set the minimum block interval when polling for I/O events and the minimum 384These advanced functions set the minimum block interval when polling for I/O events and the minimum
283wait interval for timer events. See the libev documentation at 385wait interval for timer events. See the libev documentation at
284L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> for 386L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP>
285a more detailed discussion. 387(locally installed as F<EV::libev>) for a more detailed discussion.
388
389=item $count = EV::pending_count
390
391=item $count = $loop->pending_count
392
393Returns the number of currently pending watchers.
394
395=item EV::invoke_pending
396
397=item $loop->invoke_pending
398
399Invoke all currently pending watchers.
286 400
287=back 401=back
288 402
289 403
290=head1 WATCHER OBJECTS 404=head1 WATCHER OBJECTS
… …
303called with at least two arguments: the watcher and a bitmask of received 417called with at least two arguments: the watcher and a bitmask of received
304events. 418events.
305 419
306Each watcher type has its associated bit in revents, so you can use the 420Each watcher type has its associated bit in revents, so you can use the
307same callback for multiple watchers. The event mask is named after the 421same callback for multiple watchers. The event mask is named after the
308type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, 422type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
309EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events 423EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
310(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).
311uses EV::TIMEOUT).
312 425
313In the rare case where one wants to create a watcher but not start it at 426In the rare case where one wants to create a watcher but not start it at
314the same time, each constructor has a variant with a trailing C<_ns> in 427the same time, each constructor has a variant with a trailing C<_ns> in
315its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. 428its name, e.g. EV::io has a non-starting variant EV::io_ns and so on.
316 429
… …
395 508
396=item $previous_state = $w->keepalive ($bool) 509=item $previous_state = $w->keepalive ($bool)
397 510
398Normally, C<EV::loop> will return when there are no active watchers 511Normally, C<EV::loop> will return when there are no active watchers
399(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
400convinient because it allows you to start your watchers (and your jobs), 513convenient because it allows you to start your watchers (and your jobs),
401call C<EV::loop> once and when it returns you know that all your jobs are 514call C<EV::loop> once and when it returns you know that all your jobs are
402finished (or they forgot to register some watchers for their task :). 515finished (or they forgot to register some watchers for their task :).
403 516
404Sometimes, however, this gets in your way, for example when the module 517Sometimes, however, this gets in your way, for example when the module
405that calls C<EV::loop> (usually the main program) is not the same module 518that calls C<EV::loop> (usually the main program) is not the same module
… …
409because you happen to have this long-running UDP port watcher. 522because you happen to have this long-running UDP port watcher.
410 523
411In this case you can clear the keepalive status, which means that even 524In this case you can clear the keepalive status, which means that even
412though your watcher is active, it won't keep C<EV::loop> from returning. 525though your watcher is active, it won't keep C<EV::loop> from returning.
413 526
414The initial value for keepalive is true (enabled), and you cna change it 527The initial value for keepalive is true (enabled), and you can change it
415any time. 528any time.
416 529
417Example: Register an I/O watcher for some UDP socket but do not keep the 530Example: Register an I/O watcher for some UDP socket but do not keep the
418event loop from running just because of that watcher. 531event loop from running just because of that watcher.
419 532
… …
637 750
638=item $w = EV::signal $signal, $callback 751=item $w = EV::signal $signal, $callback
639 752
640=item $w = EV::signal_ns $signal, $callback 753=item $w = EV::signal_ns $signal, $callback
641 754
755=item $w = $loop->signal ($signal, $callback)
756
757=item $w = $loop->signal_ns ($signal, $callback)
758
642Call the callback when $signal is received (the signal can be specified by 759Call the callback when $signal is received (the signal can be specified by
643number or by name, just as with C<kill> or C<%SIG>). 760number or by name, just as with C<kill> or C<%SIG>).
761
762Only one event loop can grab a given signal - attempting to grab the same
763signal from two EV loops will crash the program immediately or cause data
764corruption.
644 765
645EV will grab the signal for the process (the kernel only allows one 766EV will grab the signal for the process (the kernel only allows one
646component to receive a signal at a time) when you start a signal watcher, 767component to receive a signal at a time) when you start a signal watcher,
647and removes it again when you stop it. Perl does the same when you 768and removes it again when you stop it. Perl does the same when you
648add/remove callbacks to C<%SIG>, so watch out. 769add/remove callbacks to C<%SIG>, so watch out.
… …
873=item $w = $loop->check_ns ($callback) 994=item $w = $loop->check_ns ($callback)
874 995
875Call the callback just after the process wakes up again (after it has 996Call the callback just after the process wakes up again (after it has
876gathered events), but before any other callbacks have been invoked. 997gathered events), but before any other callbacks have been invoked.
877 998
878This is used to integrate other event-based software into the EV 999This can be used to integrate other event-based software into the EV
879mainloop: You register a prepare callback and in there, you create io and 1000mainloop: You register a prepare callback and in there, you create io and
880timer watchers as required by the other software. Here is a real-world 1001timer watchers as required by the other software. Here is a real-world
881example of integrating Net::SNMP (with some details left out): 1002example of integrating Net::SNMP (with some details left out):
882 1003
883 our @snmp_watcher; 1004 our @snmp_watcher;
… …
913 # make the dispatcher handle any new stuff 1034 # make the dispatcher handle any new stuff
914 ... not shown 1035 ... not shown
915 }; 1036 };
916 1037
917The callbacks of the created watchers will not be called as the watchers 1038The callbacks of the created watchers will not be called as the watchers
918are destroyed before this cna happen (remember EV::check gets called 1039are destroyed before this can happen (remember EV::check gets called
919first). 1040first).
920 1041
921The C<check_ns> variant doesn't start (activate) the newly created watcher. 1042The C<check_ns> variant doesn't start (activate) the newly created watcher.
1043
1044=item EV::CHECK constant issues
1045
1046Like all other watcher types, there is a bitmask constant for use in
1047C<$revents> and other places. The C<EV::CHECK> is special as it has
1048the same name as the C<CHECK> sub called by Perl. This doesn't cause
1049big issues on newer perls (beginning with 5.8.9), but it means thatthe
1050constant must be I<inlined>, i.e. runtime calls will not work. That means
1051that as long as you always C<use EV> and then C<EV::CHECK> you are on the
1052safe side.
922 1053
923=back 1054=back
924 1055
925 1056
926=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
… …
954loop, other types of watchers might be handled in a delayed or incorrect 1085loop, other types of watchers might be handled in a delayed or incorrect
955fashion and must not be used). 1086fashion and must not be used).
956 1087
957See the libev documentation at 1088See the libev documentation at
958L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_> 1089L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_>
959for more details. 1090(locally installed as F<EV::libev>) for more details.
960 1091
961In short, this watcher is most useful on BSD systems without working 1092In short, this watcher is most useful on BSD systems without working
962kqueue to still be able to handle a large number of sockets: 1093kqueue to still be able to handle a large number of sockets:
963 1094
964 my $socket_loop; 1095 my $socket_loop;
… …
975 # use the default loop otherwise 1106 # use the default loop otherwise
976 $socket_loop ||= EV::default_loop; 1107 $socket_loop ||= EV::default_loop;
977 1108
978=over 4 1109=over 4
979 1110
980=item $w = EV::embed $otherloop, $callback 1111=item $w = EV::embed $otherloop[, $callback]
981 1112
982=item $w = EV::embed_ns $otherloop, $callback 1113=item $w = EV::embed_ns $otherloop[, $callback]
983 1114
984=item $w = $loop->embed ($otherloop, $callback) 1115=item $w = $loop->embed ($otherloop[, $callback])
985 1116
986=item $w = $loop->embed_ns ($otherloop, $callback) 1117=item $w = $loop->embed_ns ($otherloop[, $callback])
987 1118
988Call the callback when the embedded event loop (C<$otherloop>) has any 1119Call the callback when the embedded event loop (C<$otherloop>) has any
989I/O activity. The C<$callback> should alwas be specified as C<undef> in 1120I/O activity. The C<$callback> is optional: if it is missing, then the
990this version of EV, which means the embedded event loop will be managed 1121embedded event loop will be managed automatically (which is recommended),
991automatically. 1122otherwise you have to invoke C<sweep> yourself.
992 1123
993The C<embed_ns> variant doesn't start (activate) the newly created watcher. 1124The C<embed_ns> variant doesn't start (activate) the newly created watcher.
994 1125
995=back 1126=back
996 1127
997=head3 ASYNC WATCHERS - how to wake up another event loop 1128=head3 ASYNC WATCHERS - how to wake up another event loop
998 1129
999Async watchers are provided by EV, but have little use in perl directly, as perl 1130Async watchers are provided by EV, but have little use in perl directly,
1000neither supports threads nor direct access to signal handlers or other 1131as perl neither supports threads running in parallel nor direct access to
1001contexts where they could be of value. 1132signal handlers or other contexts where they could be of value.
1002 1133
1003It is, however, possible to use them from the XS level. 1134It is, however, possible to use them from the XS level.
1004 1135
1005Please see the libev documentation for further details. 1136Please see the libev documentation for further details.
1006 1137
… …
1008 1139
1009=item $w = EV::async $callback 1140=item $w = EV::async $callback
1010 1141
1011=item $w = EV::async_ns $callback 1142=item $w = EV::async_ns $callback
1012 1143
1144=item $w = $loop->async ($callback)
1145
1146=item $w = $loop->async_ns ($callback)
1147
1013=item $w->send 1148=item $w->send
1014 1149
1015=item $bool = $w->async_pending 1150=item $bool = $w->async_pending
1016 1151
1017=back 1152=back
1153
1154=head3 CLEANUP WATCHERS - how to clean up when the event loop goes away
1155
1156Cleanup watchers are not supported on the Perl level, they can only be
1157used via XS currently.
1018 1158
1019 1159
1020=head1 PERL SIGNALS 1160=head1 PERL SIGNALS
1021 1161
1022While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour 1162While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
… …
1034 my $async_check = EV::check sub { }; 1174 my $async_check = EV::check sub { };
1035 1175
1036This ensures that perl gets into control for a short time to handle any 1176This ensures that perl gets into control for a short time to handle any
1037pending signals, and also ensures (slightly) slower overall operation. 1177pending signals, and also ensures (slightly) slower overall operation.
1038 1178
1039=head1 THREADS 1179=head1 ITHREADS
1040 1180
1041Threads are not supported by this module in any way. Perl pseudo-threads 1181Ithreads are not supported by this module in any way. Perl pseudo-threads
1042is evil stuff and must die. As soon as Perl gains real threads I will work 1182is evil stuff and must die. Real threads as provided by Coro are fully
1043on thread support for it. 1183supported (and enhanced support is available via L<Coro::EV>).
1044 1184
1045=head1 FORK 1185=head1 FORK
1046 1186
1047Most of the "improved" event delivering mechanisms of modern operating 1187Most of the "improved" event delivering mechanisms of modern operating
1048systems have quite a few problems with fork(2) (to put it bluntly: it is 1188systems have quite a few problems with fork(2) (to put it bluntly: it is
… …
1070 1210
10711; 12111;
1072 1212
1073=head1 SEE ALSO 1213=head1 SEE ALSO
1074 1214
1215L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS>
1075L<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
1076event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient 1217loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient thread
1077coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for 1218integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
1078event-loop agnostic and portable event driven programming. 1219event-loop agnostic and portable event driven programming.
1079 1220
1080=head1 AUTHOR 1221=head1 AUTHOR
1081 1222
1082 Marc Lehmann <schmorp@schmorp.de> 1223 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines