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

Comparing EV/EV.pm (file contents):
Revision 1.103 by root, Thu Oct 2 07:49:09 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
76no warnings; 121use common::sense;
77use strict;
78 122
79BEGIN { 123BEGIN {
80 our $VERSION = '3.44'; 124 our $VERSION = '4.11';
81 use XSLoader; 125 use XSLoader;
82 XSLoader::load "EV", $VERSION; 126 XSLoader::load "EV", $VERSION;
83} 127}
84 128
85@EV::IO::ISA = 129@EV::IO::ISA =
… …
112default loop as this is fastest (perl-wise), best supported by other 156default loop as this is fastest (perl-wise), best supported by other
113modules (e.g. AnyEvent or Coro) and most portable event loop. 157modules (e.g. AnyEvent or Coro) and most portable event loop.
114 158
115For specific programs you can create additional event loops dynamically. 159For specific programs you can create additional event loops dynamically.
116 160
117If 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
118sockets 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
119I<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
120will 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
121the 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.
122 166
123=over 4 167=over 4
124 168
125=item $loop = new EV::loop [$flags] 169=item $loop = new EV::Loop [$flags]
126 170
127Create 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
128C<ev_loop_new ()> function description in the libev documentation 172the C<ev_loop_new ()> function description in the libev documentation
129(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>,
130for more info. 174or locally-installed as F<EV::libev> manpage) for more info.
131 175
132The loop will automatically be destroyed when it is no longer referenced 176The loop will automatically be destroyed when it is no longer referenced
133by any watcher and the loop object goes out of scope. 177by any watcher and the loop object goes out of scope.
134 178
135If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK> 179If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK>
… …
142Must 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
143the 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
144this function automatically, at some performance loss (refer to the libev 188this function automatically, at some performance loss (refer to the libev
145documentation). 189documentation).
146 190
147=item $loop->loop_verify 191=item $loop->verify
148 192
149Calls C<ev_verify> to make internal consistency checks (for debugging 193Calls C<ev_verify> to make internal consistency checks (for debugging
150libev) 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
151corrupted. 195corrupted.
152 196
… …
194=item $time = EV::now 238=item $time = EV::now
195 239
196=item $time = $loop->now 240=item $time = $loop->now
197 241
198Returns the time the last event loop iteration has been started. This 242Returns the time the last event loop iteration has been started. This
199is 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
200usually faster then calling EV::time. 244usually faster then calling EV::time.
201 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
202=item $backend = EV::backend 288=item $backend = EV::backend
203 289
204=item $backend = $loop->backend 290=item $backend = $loop->backend
205 291
206Returns an integer describing the backend used by libev (EV::METHOD_SELECT 292Returns an integer describing the backend used by libev (EV::BACKEND_SELECT
207or EV::METHOD_EPOLL). 293or EV::BACKEND_EPOLL).
208 294
209=item EV::loop [$flags] 295=item $active = EV::run [$flags]
210 296
211=item $loop->loop ([$flags]) 297=item $active = $loop->run ([$flags])
212 298
213Begin checking for events and calling callbacks. It returns when a 299Begin checking for events and calling callbacks. It returns when a
214callback 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".
215 305
216The $flags argument can be one of the following: 306The $flags argument can be one of the following:
217 307
218 0 as above 308 0 as above
219 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)
220 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)
221 311
222=item EV::unloop [$how] 312=item EV::break [$how]
223 313
224=item $loop->unloop ([$how]) 314=item $loop->break ([$how])
225 315
226When 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
227innermost call to EV::loop return. 317innermost call to EV::loop return.
228 318
229When 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
230fast as possible. 320return as fast as possible.
231 321
232=item $count = EV::loop_count 322When called with an argument of EV::BREAK_CANCEL, any pending break will
323be cancelled.
233 324
325=item $count = EV::iteration
326
234=item $count = $loop->loop_count 327=item $count = $loop->iteration
235 328
236Return the number of times the event loop has polled for new 329Return the number of times the event loop has polled for new
237events. Sometiems useful as a generation counter. 330events. Sometimes useful as a generation counter.
238 331
239=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents) 332=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
240 333
241=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents)) 334=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
242 335
… …
253timeout. Otherwise a EV::timer with this value will be started. 346timeout. Otherwise a EV::timer with this value will be started.
254 347
255When 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
256the callback will be called with the received event set (in general 349the callback will be called with the received event set (in general
257you 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>,
258C<EV::WRITE> and C<EV::TIMEOUT>). 351C<EV::WRITE> and C<EV::TIMER>).
259 352
260EV::once doesn't return anything: the watchers stay active till either 353EV::once doesn't return anything: the watchers stay active till either
261of 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
262invoked. 355invoked.
263 356
264=item EV::feed_fd_event ($fd, $revents) 357=item EV::feed_fd_event $fd, $revents
265 358
266=item $loop->feed_fd_event ($fd, $revents) 359=item $loop->feed_fd_event ($fd, $revents)
267 360
268Feed 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
269if the readyness notifications specified by C<$revents> (a combination of 362if the readyness notifications specified by C<$revents> (a combination of
270C<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>.
271 364
272=item EV::feed_signal_event ($signal) 365=item EV::feed_signal_event $signal
273 366
274Feed 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
275specified 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.
276 375
277=item EV::set_io_collect_interval $time 376=item EV::set_io_collect_interval $time
278 377
279=item $loop->set_io_collect_interval ($time) 378=item $loop->set_io_collect_interval ($time)
280 379
… …
282 381
283=item $loop->set_timeout_collect_interval ($time) 382=item $loop->set_timeout_collect_interval ($time)
284 383
285These 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
286wait interval for timer events. See the libev documentation at 385wait interval for timer events. See the libev documentation at
287L<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>
288a 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.
289 400
290=back 401=back
291 402
292 403
293=head1 WATCHER OBJECTS 404=head1 WATCHER OBJECTS
… …
306called 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
307events. 418events.
308 419
309Each 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
310same callback for multiple watchers. The event mask is named after the 421same callback for multiple watchers. The event mask is named after the
311type, 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,
312EV::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
313(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).
314uses EV::TIMEOUT).
315 425
316In 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
317the 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
318its 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.
319 429
… …
398 508
399=item $previous_state = $w->keepalive ($bool) 509=item $previous_state = $w->keepalive ($bool)
400 510
401Normally, C<EV::loop> will return when there are no active watchers 511Normally, C<EV::loop> will return when there are no active watchers
402(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
403convinient because it allows you to start your watchers (and your jobs), 513convenient because it allows you to start your watchers (and your jobs),
404call 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
405finished (or they forgot to register some watchers for their task :). 515finished (or they forgot to register some watchers for their task :).
406 516
407Sometimes, however, this gets in your way, for example when the module 517Sometimes, however, this gets in your way, for example when the module
408that 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
… …
412because you happen to have this long-running UDP port watcher. 522because you happen to have this long-running UDP port watcher.
413 523
414In 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
415though 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.
416 526
417The 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
418any time. 528any time.
419 529
420Example: 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
421event loop from running just because of that watcher. 531event loop from running just because of that watcher.
422 532
… …
640 750
641=item $w = EV::signal $signal, $callback 751=item $w = EV::signal $signal, $callback
642 752
643=item $w = EV::signal_ns $signal, $callback 753=item $w = EV::signal_ns $signal, $callback
644 754
755=item $w = $loop->signal ($signal, $callback)
756
757=item $w = $loop->signal_ns ($signal, $callback)
758
645Call 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
646number 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.
647 765
648EV 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
649component 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,
650and 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
651add/remove callbacks to C<%SIG>, so watch out. 769add/remove callbacks to C<%SIG>, so watch out.
… …
876=item $w = $loop->check_ns ($callback) 994=item $w = $loop->check_ns ($callback)
877 995
878Call 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
879gathered events), but before any other callbacks have been invoked. 997gathered events), but before any other callbacks have been invoked.
880 998
881This is used to integrate other event-based software into the EV 999This can be used to integrate other event-based software into the EV
882mainloop: 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
883timer 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
884example of integrating Net::SNMP (with some details left out): 1002example of integrating Net::SNMP (with some details left out):
885 1003
886 our @snmp_watcher; 1004 our @snmp_watcher;
… …
916 # make the dispatcher handle any new stuff 1034 # make the dispatcher handle any new stuff
917 ... not shown 1035 ... not shown
918 }; 1036 };
919 1037
920The 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
921are destroyed before this cna happen (remember EV::check gets called 1039are destroyed before this can happen (remember EV::check gets called
922first). 1040first).
923 1041
924The 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.
925 1053
926=back 1054=back
927 1055
928 1056
929=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
… …
957loop, 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
958fashion and must not be used). 1086fashion and must not be used).
959 1087
960See the libev documentation at 1088See the libev documentation at
961L<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_>
962for more details. 1090(locally installed as F<EV::libev>) for more details.
963 1091
964In short, this watcher is most useful on BSD systems without working 1092In short, this watcher is most useful on BSD systems without working
965kqueue to still be able to handle a large number of sockets: 1093kqueue to still be able to handle a large number of sockets:
966 1094
967 my $socket_loop; 1095 my $socket_loop;
… …
997 1125
998=back 1126=back
999 1127
1000=head3 ASYNC WATCHERS - how to wake up another event loop 1128=head3 ASYNC WATCHERS - how to wake up another event loop
1001 1129
1002Async 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,
1003neither supports threads nor direct access to signal handlers or other 1131as perl neither supports threads running in parallel nor direct access to
1004contexts where they could be of value. 1132signal handlers or other contexts where they could be of value.
1005 1133
1006It is, however, possible to use them from the XS level. 1134It is, however, possible to use them from the XS level.
1007 1135
1008Please see the libev documentation for further details. 1136Please see the libev documentation for further details.
1009 1137
… …
1011 1139
1012=item $w = EV::async $callback 1140=item $w = EV::async $callback
1013 1141
1014=item $w = EV::async_ns $callback 1142=item $w = EV::async_ns $callback
1015 1143
1144=item $w = $loop->async ($callback)
1145
1146=item $w = $loop->async_ns ($callback)
1147
1016=item $w->send 1148=item $w->send
1017 1149
1018=item $bool = $w->async_pending 1150=item $bool = $w->async_pending
1019 1151
1020=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.
1021 1158
1022 1159
1023=head1 PERL SIGNALS 1160=head1 PERL SIGNALS
1024 1161
1025While 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
… …
1037 my $async_check = EV::check sub { }; 1174 my $async_check = EV::check sub { };
1038 1175
1039This 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
1040pending signals, and also ensures (slightly) slower overall operation. 1177pending signals, and also ensures (slightly) slower overall operation.
1041 1178
1042=head1 THREADS 1179=head1 ITHREADS
1043 1180
1044Threads 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
1045is 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
1046on thread support for it. 1183supported (and enhanced support is available via L<Coro::EV>).
1047 1184
1048=head1 FORK 1185=head1 FORK
1049 1186
1050Most of the "improved" event delivering mechanisms of modern operating 1187Most of the "improved" event delivering mechanisms of modern operating
1051systems 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
… …
1073 1210
10741; 12111;
1075 1212
1076=head1 SEE ALSO 1213=head1 SEE ALSO
1077 1214
1215L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS>
1078L<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
1079event 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
1080coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for 1218integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
1081event-loop agnostic and portable event driven programming. 1219event-loop agnostic and portable event driven programming.
1082 1220
1083=head1 AUTHOR 1221=head1 AUTHOR
1084 1222
1085 Marc Lehmann <schmorp@schmorp.de> 1223 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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