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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.320 by root, Mon Apr 12 02:50:31 2010 UTC vs.
Revision 1.383 by root, Fri Sep 2 04:41:16 2011 UTC

1=head1 NAME 1=head1 NAME
2 2
3AnyEvent - the DBI of event loop programming 3AnyEvent - the DBI of event loop programming
4 4
5EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt 5EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt,
6and POE are various supported event loops/environments. 6FLTK and POE are various supported event loops/environments.
7 7
8=head1 SYNOPSIS 8=head1 SYNOPSIS
9 9
10 use AnyEvent; 10 use AnyEvent;
11 11
12 # if you prefer function calls, look at the L<AE> manpage for 12 # if you prefer function calls, look at the AE manpage for
13 # an alternative API. 13 # an alternative API.
14 14
15 # file handle or descriptor readable 15 # file handle or descriptor readable
16 my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... }); 16 my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
17 17
18 # one-shot or repeating timers 18 # one-shot or repeating timers
19 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... }); 19 my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
20 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ... 20 my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
21 21
22 print AnyEvent->now; # prints current event loop time 22 print AnyEvent->now; # prints current event loop time
23 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time. 23 print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
24 24
25 # POSIX signal 25 # POSIX signal
46in a tutorial or some gentle introduction, have a look at the 46in a tutorial or some gentle introduction, have a look at the
47L<AnyEvent::Intro> manpage. 47L<AnyEvent::Intro> manpage.
48 48
49=head1 SUPPORT 49=head1 SUPPORT
50 50
51An FAQ document is available as L<AnyEvent::FAQ>.
52
51There is a mailinglist for discussing all things AnyEvent, and an IRC 53There also is a mailinglist for discussing all things AnyEvent, and an IRC
52channel, too. 54channel, too.
53 55
54See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software 56See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
55Repository>, at L<http://anyevent.schmorp.de>, for more info. 57Repository>, at L<http://anyevent.schmorp.de>, for more info.
56 58
76module users into the same thing by forcing them to use the same event 78module users into the same thing by forcing them to use the same event
77model you use. 79model you use.
78 80
79For modules like POE or IO::Async (which is a total misnomer as it is 81For modules like POE or IO::Async (which is a total misnomer as it is
80actually doing all I/O I<synchronously>...), using them in your module is 82actually doing all I/O I<synchronously>...), using them in your module is
81like joining a cult: After you joined, you are dependent on them and you 83like joining a cult: After you join, you are dependent on them and you
82cannot use anything else, as they are simply incompatible to everything 84cannot use anything else, as they are simply incompatible to everything
83that isn't them. What's worse, all the potential users of your 85that isn't them. What's worse, all the potential users of your
84module are I<also> forced to use the same event loop you use. 86module are I<also> forced to use the same event loop you use.
85 87
86AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works 88AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
87fine. AnyEvent + Tk works fine etc. etc. but none of these work together 89fine. AnyEvent + Tk works fine etc. etc. but none of these work together
88with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if 90with the rest: POE + EV? No go. Tk + Event? No go. Again: if your module
89your module uses one of those, every user of your module has to use it, 91uses one of those, every user of your module has to use it, too. But if
90too. But if your module uses AnyEvent, it works transparently with all 92your module uses AnyEvent, it works transparently with all event models it
91event models it supports (including stuff like IO::Async, as long as those 93supports (including stuff like IO::Async, as long as those use one of the
92use one of the supported event loops. It is trivial to add new event loops 94supported event loops. It is easy to add new event loops to AnyEvent, too,
93to AnyEvent, too, so it is future-proof). 95so it is future-proof).
94 96
95In addition to being free of having to use I<the one and only true event 97In addition to being free of having to use I<the one and only true event
96model>, AnyEvent also is free of bloat and policy: with POE or similar 98model>, AnyEvent also is free of bloat and policy: with POE or similar
97modules, you get an enormous amount of code and strict rules you have to 99modules, you get an enormous amount of code and strict rules you have to
98follow. AnyEvent, on the other hand, is lean and up to the point, by only 100follow. AnyEvent, on the other hand, is lean and to the point, by only
99offering the functionality that is necessary, in as thin as a wrapper as 101offering the functionality that is necessary, in as thin as a wrapper as
100technically possible. 102technically possible.
101 103
102Of course, AnyEvent comes with a big (and fully optional!) toolbox 104Of course, AnyEvent comes with a big (and fully optional!) toolbox
103of useful functionality, such as an asynchronous DNS resolver, 100% 105of useful functionality, such as an asynchronous DNS resolver, 100%
109useful) and you want to force your users to use the one and only event 111useful) and you want to force your users to use the one and only event
110model, you should I<not> use this module. 112model, you should I<not> use this module.
111 113
112=head1 DESCRIPTION 114=head1 DESCRIPTION
113 115
114L<AnyEvent> provides an identical interface to multiple event loops. This 116L<AnyEvent> provides a uniform interface to various event loops. This
115allows module authors to utilise an event loop without forcing module 117allows module authors to use event loop functionality without forcing
116users to use the same event loop (as only a single event loop can coexist 118module users to use a specific event loop implementation (since more
117peacefully at any one time). 119than one event loop cannot coexist peacefully).
118 120
119The interface itself is vaguely similar, but not identical to the L<Event> 121The interface itself is vaguely similar, but not identical to the L<Event>
120module. 122module.
121 123
122During the first call of any watcher-creation method, the module tries 124During the first call of any watcher-creation method, the module tries
123to detect the currently loaded event loop by probing whether one of the 125to detect the currently loaded event loop by probing whether one of the
124following modules is already loaded: L<EV>, 126following modules is already loaded: L<EV>, L<AnyEvent::Loop>,
125L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>, 127L<Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. The first one
126L<POE>. The first one found is used. If none are found, the module tries 128found is used. If none are detected, the module tries to load the first
127to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl 129four modules in the order given; but note that if L<EV> is not
128adaptor should always succeed) in the order given. The first one that can 130available, the pure-perl L<AnyEvent::Loop> should always work, so
129be successfully loaded will be used. If, after this, still none could be 131the other two are not normally tried.
130found, AnyEvent will fall back to a pure-perl event loop, which is not
131very efficient, but should work everywhere.
132 132
133Because AnyEvent first checks for modules that are already loaded, loading 133Because AnyEvent first checks for modules that are already loaded, loading
134an event model explicitly before first using AnyEvent will likely make 134an event model explicitly before first using AnyEvent will likely make
135that model the default. For example: 135that model the default. For example:
136 136
138 use AnyEvent; 138 use AnyEvent;
139 139
140 # .. AnyEvent will likely default to Tk 140 # .. AnyEvent will likely default to Tk
141 141
142The I<likely> means that, if any module loads another event model and 142The I<likely> means that, if any module loads another event model and
143starts using it, all bets are off. Maybe you should tell their authors to 143starts using it, all bets are off - this case should be very rare though,
144use AnyEvent so their modules work together with others seamlessly... 144as very few modules hardcode event loops without announcing this very
145loudly.
145 146
146The pure-perl implementation of AnyEvent is called 147The pure-perl implementation of AnyEvent is called C<AnyEvent::Loop>. Like
147C<AnyEvent::Impl::Perl>. Like other event modules you can load it 148other event modules you can load it explicitly and enjoy the high
148explicitly and enjoy the high availability of that event loop :) 149availability of that event loop :)
149 150
150=head1 WATCHERS 151=head1 WATCHERS
151 152
152AnyEvent has the central concept of a I<watcher>, which is an object that 153AnyEvent has the central concept of a I<watcher>, which is an object that
153stores relevant data for each kind of event you are waiting for, such as 154stores relevant data for each kind of event you are waiting for, such as
158callback when the event occurs (of course, only when the event model 159callback when the event occurs (of course, only when the event model
159is in control). 160is in control).
160 161
161Note that B<callbacks must not permanently change global variables> 162Note that B<callbacks must not permanently change global variables>
162potentially in use by the event loop (such as C<$_> or C<$[>) and that B<< 163potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
163callbacks must not C<die> >>. The former is good programming practise in 164callbacks must not C<die> >>. The former is good programming practice in
164Perl and the latter stems from the fact that exception handling differs 165Perl and the latter stems from the fact that exception handling differs
165widely between event loops. 166widely between event loops.
166 167
167To disable the watcher you have to destroy it (e.g. by setting the 168To disable a watcher you have to destroy it (e.g. by setting the
168variable you store it in to C<undef> or otherwise deleting all references 169variable you store it in to C<undef> or otherwise deleting all references
169to it). 170to it).
170 171
171All watchers are created by calling a method on the C<AnyEvent> class. 172All watchers are created by calling a method on the C<AnyEvent> class.
172 173
173Many watchers either are used with "recursion" (repeating timers for 174Many watchers either are used with "recursion" (repeating timers for
174example), or need to refer to their watcher object in other ways. 175example), or need to refer to their watcher object in other ways.
175 176
176An any way to achieve that is this pattern: 177One way to achieve that is this pattern:
177 178
178 my $w; $w = AnyEvent->type (arg => value ..., cb => sub { 179 my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
179 # you can use $w here, for example to undef it 180 # you can use $w here, for example to undef it
180 undef $w; 181 undef $w;
181 }); 182 });
213 214
214The I/O watcher might use the underlying file descriptor or a copy of it. 215The I/O watcher might use the underlying file descriptor or a copy of it.
215You must not close a file handle as long as any watcher is active on the 216You must not close a file handle as long as any watcher is active on the
216underlying file descriptor. 217underlying file descriptor.
217 218
218Some event loops issue spurious readyness notifications, so you should 219Some event loops issue spurious readiness notifications, so you should
219always use non-blocking calls when reading/writing from/to your file 220always use non-blocking calls when reading/writing from/to your file
220handles. 221handles.
221 222
222Example: wait for readability of STDIN, then read a line and disable the 223Example: wait for readability of STDIN, then read a line and disable the
223watcher. 224watcher.
247 248
248Although the callback might get passed parameters, their value and 249Although the callback might get passed parameters, their value and
249presence is undefined and you cannot rely on them. Portable AnyEvent 250presence is undefined and you cannot rely on them. Portable AnyEvent
250callbacks cannot use arguments passed to time watcher callbacks. 251callbacks cannot use arguments passed to time watcher callbacks.
251 252
252The callback will normally be invoked once only. If you specify another 253The callback will normally be invoked only once. If you specify another
253parameter, C<interval>, as a strictly positive number (> 0), then the 254parameter, C<interval>, as a strictly positive number (> 0), then the
254callback will be invoked regularly at that interval (in fractional 255callback will be invoked regularly at that interval (in fractional
255seconds) after the first invocation. If C<interval> is specified with a 256seconds) after the first invocation. If C<interval> is specified with a
256false value, then it is treated as if it were missing. 257false value, then it is treated as if it were not specified at all.
257 258
258The callback will be rescheduled before invoking the callback, but no 259The callback will be rescheduled before invoking the callback, but no
259attempt is done to avoid timer drift in most backends, so the interval is 260attempt is made to avoid timer drift in most backends, so the interval is
260only approximate. 261only approximate.
261 262
262Example: fire an event after 7.7 seconds. 263Example: fire an event after 7.7 seconds.
263 264
264 my $w = AnyEvent->timer (after => 7.7, cb => sub { 265 my $w = AnyEvent->timer (after => 7.7, cb => sub {
282 283
283While most event loops expect timers to specified in a relative way, they 284While most event loops expect timers to specified in a relative way, they
284use absolute time internally. This makes a difference when your clock 285use absolute time internally. This makes a difference when your clock
285"jumps", for example, when ntp decides to set your clock backwards from 286"jumps", for example, when ntp decides to set your clock backwards from
286the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to 287the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
287fire "after" a second might actually take six years to finally fire. 288fire "after a second" might actually take six years to finally fire.
288 289
289AnyEvent cannot compensate for this. The only event loop that is conscious 290AnyEvent cannot compensate for this. The only event loop that is conscious
290about these issues is L<EV>, which offers both relative (ev_timer, based 291of these issues is L<EV>, which offers both relative (ev_timer, based
291on true relative time) and absolute (ev_periodic, based on wallclock time) 292on true relative time) and absolute (ev_periodic, based on wallclock time)
292timers. 293timers.
293 294
294AnyEvent always prefers relative timers, if available, matching the 295AnyEvent always prefers relative timers, if available, matching the
295AnyEvent API. 296AnyEvent API.
317I<In almost all cases (in all cases if you don't care), this is the 318I<In almost all cases (in all cases if you don't care), this is the
318function to call when you want to know the current time.> 319function to call when you want to know the current time.>
319 320
320This function is also often faster then C<< AnyEvent->time >>, and 321This function is also often faster then C<< AnyEvent->time >>, and
321thus the preferred method if you want some timestamp (for example, 322thus the preferred method if you want some timestamp (for example,
322L<AnyEvent::Handle> uses this to update it's activity timeouts). 323L<AnyEvent::Handle> uses this to update its activity timeouts).
323 324
324The rest of this section is only of relevance if you try to be very exact 325The rest of this section is only of relevance if you try to be very exact
325with your timing, you can skip it without bad conscience. 326with your timing; you can skip it without a bad conscience.
326 327
327For a practical example of when these times differ, consider L<Event::Lib> 328For a practical example of when these times differ, consider L<Event::Lib>
328and L<EV> and the following set-up: 329and L<EV> and the following set-up:
329 330
330The event loop is running and has just invoked one of your callback at 331The event loop is running and has just invoked one of your callbacks at
331time=500 (assume no other callbacks delay processing). In your callback, 332time=500 (assume no other callbacks delay processing). In your callback,
332you wait a second by executing C<sleep 1> (blocking the process for a 333you wait a second by executing C<sleep 1> (blocking the process for a
333second) and then (at time=501) you create a relative timer that fires 334second) and then (at time=501) you create a relative timer that fires
334after three seconds. 335after three seconds.
335 336
355difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into 356difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
356account. 357account.
357 358
358=item AnyEvent->now_update 359=item AnyEvent->now_update
359 360
360Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache 361Some event loops (such as L<EV> or L<AnyEvent::Loop>) cache the current
361the current time for each loop iteration (see the discussion of L<< 362time for each loop iteration (see the discussion of L<< AnyEvent->now >>,
362AnyEvent->now >>, above). 363above).
363 364
364When a callback runs for a long time (or when the process sleeps), then 365When a callback runs for a long time (or when the process sleeps), then
365this "current" time will differ substantially from the real time, which 366this "current" time will differ substantially from the real time, which
366might affect timers and time-outs. 367might affect timers and time-outs.
367 368
428=head3 Signal Races, Delays and Workarounds 429=head3 Signal Races, Delays and Workarounds
429 430
430Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching 431Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
431callbacks to signals in a generic way, which is a pity, as you cannot 432callbacks to signals in a generic way, which is a pity, as you cannot
432do race-free signal handling in perl, requiring C libraries for 433do race-free signal handling in perl, requiring C libraries for
433this. AnyEvent will try to do it's best, which means in some cases, 434this. AnyEvent will try to do its best, which means in some cases,
434signals will be delayed. The maximum time a signal might be delayed is 435signals will be delayed. The maximum time a signal might be delayed is
435specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This 436specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
436variable can be changed only before the first signal watcher is created, 437variable can be changed only before the first signal watcher is created,
437and should be left alone otherwise. This variable determines how often 438and should be left alone otherwise. This variable determines how often
438AnyEvent polls for signals (in case a wake-up was missed). Higher values 439AnyEvent polls for signals (in case a wake-up was missed). Higher values
440saving. 441saving.
441 442
442All these problems can be avoided by installing the optional 443All these problems can be avoided by installing the optional
443L<Async::Interrupt> module, which works with most event loops. It will not 444L<Async::Interrupt> module, which works with most event loops. It will not
444work with inherently broken event loops such as L<Event> or L<Event::Lib> 445work with inherently broken event loops such as L<Event> or L<Event::Lib>
445(and not with L<POE> currently, as POE does it's own workaround with 446(and not with L<POE> currently, as POE does its own workaround with
446one-second latency). For those, you just have to suffer the delays. 447one-second latency). For those, you just have to suffer the delays.
447 448
448=head2 CHILD PROCESS WATCHERS 449=head2 CHILD PROCESS WATCHERS
449 450
450 $w = AnyEvent->child (pid => <process id>, cb => <callback>); 451 $w = AnyEvent->child (pid => <process id>, cb => <callback>);
451 452
452You can also watch on a child process exit and catch its exit status. 453You can also watch for a child process exit and catch its exit status.
453 454
454The child process is specified by the C<pid> argument (one some backends, 455The child process is specified by the C<pid> argument (on some backends,
455using C<0> watches for any child process exit, on others this will 456using C<0> watches for any child process exit, on others this will
456croak). The watcher will be triggered only when the child process has 457croak). The watcher will be triggered only when the child process has
457finished and an exit status is available, not on any trace events 458finished and an exit status is available, not on any trace events
458(stopped/continued). 459(stopped/continued).
459 460
481thing in an AnyEvent program, you I<have> to create at least one 482thing in an AnyEvent program, you I<have> to create at least one
482watcher before you C<fork> the child (alternatively, you can call 483watcher before you C<fork> the child (alternatively, you can call
483C<AnyEvent::detect>). 484C<AnyEvent::detect>).
484 485
485As most event loops do not support waiting for child events, they will be 486As most event loops do not support waiting for child events, they will be
486emulated by AnyEvent in most cases, in which the latency and race problems 487emulated by AnyEvent in most cases, in which case the latency and race
487mentioned in the description of signal watchers apply. 488problems mentioned in the description of signal watchers apply.
488 489
489Example: fork a process and wait for it 490Example: fork a process and wait for it
490 491
491 my $done = AnyEvent->condvar; 492 my $done = AnyEvent->condvar;
492 493
506 507
507=head2 IDLE WATCHERS 508=head2 IDLE WATCHERS
508 509
509 $w = AnyEvent->idle (cb => <callback>); 510 $w = AnyEvent->idle (cb => <callback>);
510 511
511Repeatedly invoke the callback after the process becomes idle, until 512This will repeatedly invoke the callback after the process becomes idle,
512either the watcher is destroyed or new events have been detected. 513until either the watcher is destroyed or new events have been detected.
513 514
514Idle watchers are useful when there is a need to do something, but it 515Idle watchers are useful when there is a need to do something, but it
515is not so important (or wise) to do it instantly. The callback will be 516is not so important (or wise) to do it instantly. The callback will be
516invoked only when there is "nothing better to do", which is usually 517invoked only when there is "nothing better to do", which is usually
517defined as "all outstanding events have been handled and no new events 518defined as "all outstanding events have been handled and no new events
556will actively watch for new events and call your callbacks. 557will actively watch for new events and call your callbacks.
557 558
558AnyEvent is slightly different: it expects somebody else to run the event 559AnyEvent is slightly different: it expects somebody else to run the event
559loop and will only block when necessary (usually when told by the user). 560loop and will only block when necessary (usually when told by the user).
560 561
561The instrument to do that is called a "condition variable", so called 562The tool to do that is called a "condition variable", so called because
562because they represent a condition that must become true. 563they represent a condition that must become true.
563 564
564Now is probably a good time to look at the examples further below. 565Now is probably a good time to look at the examples further below.
565 566
566Condition variables can be created by calling the C<< AnyEvent->condvar 567Condition variables can be created by calling the C<< AnyEvent->condvar
567>> method, usually without arguments. The only argument pair allowed is 568>> method, usually without arguments. The only argument pair allowed is
572After creation, the condition variable is "false" until it becomes "true" 573After creation, the condition variable is "false" until it becomes "true"
573by calling the C<send> method (or calling the condition variable as if it 574by calling the C<send> method (or calling the condition variable as if it
574were a callback, read about the caveats in the description for the C<< 575were a callback, read about the caveats in the description for the C<<
575->send >> method). 576->send >> method).
576 577
577Condition variables are similar to callbacks, except that you can 578Since condition variables are the most complex part of the AnyEvent API, here are
578optionally wait for them. They can also be called merge points - points 579some different mental models of what they are - pick the ones you can connect to:
579in time where multiple outstanding events have been processed. And yet 580
580another way to call them is transactions - each condition variable can be 581=over 4
581used to represent a transaction, which finishes at some point and delivers 582
582a result. And yet some people know them as "futures" - a promise to 583=item * Condition variables are like callbacks - you can call them (and pass them instead
583compute/deliver something that you can wait for. 584of callbacks). Unlike callbacks however, you can also wait for them to be called.
585
586=item * Condition variables are signals - one side can emit or send them,
587the other side can wait for them, or install a handler that is called when
588the signal fires.
589
590=item * Condition variables are like "Merge Points" - points in your program
591where you merge multiple independent results/control flows into one.
592
593=item * Condition variables represent a transaction - functions that start
594some kind of transaction can return them, leaving the caller the choice
595between waiting in a blocking fashion, or setting a callback.
596
597=item * Condition variables represent future values, or promises to deliver
598some result, long before the result is available.
599
600=back
584 601
585Condition variables are very useful to signal that something has finished, 602Condition variables are very useful to signal that something has finished,
586for example, if you write a module that does asynchronous http requests, 603for example, if you write a module that does asynchronous http requests,
587then a condition variable would be the ideal candidate to signal the 604then a condition variable would be the ideal candidate to signal the
588availability of results. The user can either act when the callback is 605availability of results. The user can either act when the callback is
601 618
602Condition variables are represented by hash refs in perl, and the keys 619Condition variables are represented by hash refs in perl, and the keys
603used by AnyEvent itself are all named C<_ae_XXX> to make subclassing 620used by AnyEvent itself are all named C<_ae_XXX> to make subclassing
604easy (it is often useful to build your own transaction class on top of 621easy (it is often useful to build your own transaction class on top of
605AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call 622AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
606it's C<new> method in your own C<new> method. 623its C<new> method in your own C<new> method.
607 624
608There are two "sides" to a condition variable - the "producer side" which 625There are two "sides" to a condition variable - the "producer side" which
609eventually calls C<< -> send >>, and the "consumer side", which waits 626eventually calls C<< -> send >>, and the "consumer side", which waits
610for the send to occur. 627for the send to occur.
611 628
676they were a code reference). Calling them directly is the same as calling 693they were a code reference). Calling them directly is the same as calling
677C<send>. 694C<send>.
678 695
679=item $cv->croak ($error) 696=item $cv->croak ($error)
680 697
681Similar to send, but causes all call's to C<< ->recv >> to invoke 698Similar to send, but causes all calls to C<< ->recv >> to invoke
682C<Carp::croak> with the given error message/object/scalar. 699C<Carp::croak> with the given error message/object/scalar.
683 700
684This can be used to signal any errors to the condition variable 701This can be used to signal any errors to the condition variable
685user/consumer. Doing it this way instead of calling C<croak> directly 702user/consumer. Doing it this way instead of calling C<croak> directly
686delays the error detetcion, but has the overwhelmign advantage that it 703delays the error detection, but has the overwhelming advantage that it
687diagnoses the error at the place where the result is expected, and not 704diagnoses the error at the place where the result is expected, and not
688deep in some event clalback without connection to the actual code causing 705deep in some event callback with no connection to the actual code causing
689the problem. 706the problem.
690 707
691=item $cv->begin ([group callback]) 708=item $cv->begin ([group callback])
692 709
693=item $cv->end 710=item $cv->end
731one call to C<begin>, so the condvar waits for all calls to C<end> before 748one call to C<begin>, so the condvar waits for all calls to C<end> before
732sending. 749sending.
733 750
734The ping example mentioned above is slightly more complicated, as the 751The ping example mentioned above is slightly more complicated, as the
735there are results to be passwd back, and the number of tasks that are 752there are results to be passwd back, and the number of tasks that are
736begung can potentially be zero: 753begun can potentially be zero:
737 754
738 my $cv = AnyEvent->condvar; 755 my $cv = AnyEvent->condvar;
739 756
740 my %result; 757 my %result;
741 $cv->begin (sub { shift->send (\%result) }); 758 $cv->begin (sub { shift->send (\%result) });
762to be called once the counter reaches C<0>, and second, it ensures that 779to be called once the counter reaches C<0>, and second, it ensures that
763C<send> is called even when C<no> hosts are being pinged (the loop 780C<send> is called even when C<no> hosts are being pinged (the loop
764doesn't execute once). 781doesn't execute once).
765 782
766This is the general pattern when you "fan out" into multiple (but 783This is the general pattern when you "fan out" into multiple (but
767potentially none) subrequests: use an outer C<begin>/C<end> pair to set 784potentially zero) subrequests: use an outer C<begin>/C<end> pair to set
768the callback and ensure C<end> is called at least once, and then, for each 785the callback and ensure C<end> is called at least once, and then, for each
769subrequest you start, call C<begin> and for each subrequest you finish, 786subrequest you start, call C<begin> and for each subrequest you finish,
770call C<end>. 787call C<end>.
771 788
772=back 789=back
779=over 4 796=over 4
780 797
781=item $cv->recv 798=item $cv->recv
782 799
783Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak 800Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
784>> methods have been called on c<$cv>, while servicing other watchers 801>> methods have been called on C<$cv>, while servicing other watchers
785normally. 802normally.
786 803
787You can only wait once on a condition - additional calls are valid but 804You can only wait once on a condition - additional calls are valid but
788will return immediately. 805will return immediately.
789 806
806caller decide whether the call will block or not (for example, by coupling 823caller decide whether the call will block or not (for example, by coupling
807condition variables with some kind of request results and supporting 824condition variables with some kind of request results and supporting
808callbacks so the caller knows that getting the result will not block, 825callbacks so the caller knows that getting the result will not block,
809while still supporting blocking waits if the caller so desires). 826while still supporting blocking waits if the caller so desires).
810 827
811You can ensure that C<< -recv >> never blocks by setting a callback and 828You can ensure that C<< ->recv >> never blocks by setting a callback and
812only calling C<< ->recv >> from within that callback (or at a later 829only calling C<< ->recv >> from within that callback (or at a later
813time). This will work even when the event loop does not support blocking 830time). This will work even when the event loop does not support blocking
814waits otherwise. 831waits otherwise.
815 832
816=item $bool = $cv->ready 833=item $bool = $cv->ready
821=item $cb = $cv->cb ($cb->($cv)) 838=item $cb = $cv->cb ($cb->($cv))
822 839
823This is a mutator function that returns the callback set and optionally 840This is a mutator function that returns the callback set and optionally
824replaces it before doing so. 841replaces it before doing so.
825 842
826The callback will be called when the condition becomes (or already was) 843The callback will be called when the condition becomes "true", i.e. when
827"true", i.e. when C<send> or C<croak> are called (or were called), with 844C<send> or C<croak> are called, with the only argument being the
828the only argument being the condition variable itself. Calling C<recv> 845condition variable itself. If the condition is already true, the
846callback is called immediately when it is set. Calling C<recv> inside
829inside the callback or at any later time is guaranteed not to block. 847the callback or at any later time is guaranteed not to block.
830 848
831=back 849=back
832 850
833=head1 SUPPORTED EVENT LOOPS/BACKENDS 851=head1 SUPPORTED EVENT LOOPS/BACKENDS
834 852
842use. If EV is not installed, then AnyEvent will fall back to its own 860use. If EV is not installed, then AnyEvent will fall back to its own
843pure-perl implementation, which is available everywhere as it comes with 861pure-perl implementation, which is available everywhere as it comes with
844AnyEvent itself. 862AnyEvent itself.
845 863
846 AnyEvent::Impl::EV based on EV (interface to libev, best choice). 864 AnyEvent::Impl::EV based on EV (interface to libev, best choice).
847 AnyEvent::Impl::Perl pure-perl implementation, fast and portable. 865 AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
848 866
849=item Backends that are transparently being picked up when they are used. 867=item Backends that are transparently being picked up when they are used.
850 868
851These will be used when they are currently loaded when the first watcher 869These will be used if they are already loaded when the first watcher
852is created, in which case it is assumed that the application is using 870is created, in which case it is assumed that the application is using
853them. This means that AnyEvent will automatically pick the right backend 871them. This means that AnyEvent will automatically pick the right backend
854when the main program loads an event module before anything starts to 872when the main program loads an event module before anything starts to
855create watchers. Nothing special needs to be done by the main program. 873create watchers. Nothing special needs to be done by the main program.
856 874
858 AnyEvent::Impl::Glib based on Glib, slow but very stable. 876 AnyEvent::Impl::Glib based on Glib, slow but very stable.
859 AnyEvent::Impl::Tk based on Tk, very broken. 877 AnyEvent::Impl::Tk based on Tk, very broken.
860 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 878 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
861 AnyEvent::Impl::POE based on POE, very slow, some limitations. 879 AnyEvent::Impl::POE based on POE, very slow, some limitations.
862 AnyEvent::Impl::Irssi used when running within irssi. 880 AnyEvent::Impl::Irssi used when running within irssi.
881 AnyEvent::Impl::IOAsync based on IO::Async.
882 AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
883 AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding).
863 884
864=item Backends with special needs. 885=item Backends with special needs.
865 886
866Qt requires the Qt::Application to be instantiated first, but will 887Qt requires the Qt::Application to be instantiated first, but will
867otherwise be picked up automatically. As long as the main program 888otherwise be picked up automatically. As long as the main program
868instantiates the application before any AnyEvent watchers are created, 889instantiates the application before any AnyEvent watchers are created,
869everything should just work. 890everything should just work.
870 891
871 AnyEvent::Impl::Qt based on Qt. 892 AnyEvent::Impl::Qt based on Qt.
872 893
873Support for IO::Async can only be partial, as it is too broken and
874architecturally limited to even support the AnyEvent API. It also
875is the only event loop that needs the loop to be set explicitly, so
876it can only be used by a main program knowing about AnyEvent. See
877L<AnyEvent::Impl::Async> for the gory details.
878
879 AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
880
881=item Event loops that are indirectly supported via other backends. 894=item Event loops that are indirectly supported via other backends.
882 895
883Some event loops can be supported via other modules: 896Some event loops can be supported via other modules:
884 897
885There is no direct support for WxWidgets (L<Wx>) or L<Prima>. 898There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
910Contains C<undef> until the first watcher is being created, before the 923Contains C<undef> until the first watcher is being created, before the
911backend has been autodetected. 924backend has been autodetected.
912 925
913Afterwards it contains the event model that is being used, which is the 926Afterwards it contains the event model that is being used, which is the
914name of the Perl class implementing the model. This class is usually one 927name of the Perl class implementing the model. This class is usually one
915of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the 928of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
916case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it 929case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
917will be C<urxvt::anyevent>). 930will be C<urxvt::anyevent>).
918 931
919=item AnyEvent::detect 932=item AnyEvent::detect
920 933
921Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model 934Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
922if necessary. You should only call this function right before you would 935if necessary. You should only call this function right before you would
923have created an AnyEvent watcher anyway, that is, as late as possible at 936have created an AnyEvent watcher anyway, that is, as late as possible at
924runtime, and not e.g. while initialising of your module. 937runtime, and not e.g. during initialisation of your module.
938
939The effect of calling this function is as if a watcher had been created
940(specifically, actions that happen "when the first watcher is created"
941happen when calling detetc as well).
925 942
926If you need to do some initialisation before AnyEvent watchers are 943If you need to do some initialisation before AnyEvent watchers are
927created, use C<post_detect>. 944created, use C<post_detect>.
928 945
929=item $guard = AnyEvent::post_detect { BLOCK } 946=item $guard = AnyEvent::post_detect { BLOCK }
930 947
931Arranges for the code block to be executed as soon as the event model is 948Arranges for the code block to be executed as soon as the event model is
932autodetected (or immediately if this has already happened). 949autodetected (or immediately if that has already happened).
933 950
934The block will be executed I<after> the actual backend has been detected 951The block will be executed I<after> the actual backend has been detected
935(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been 952(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
936created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do 953created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
937other initialisations - see the sources of L<AnyEvent::Strict> or 954other initialisations - see the sources of L<AnyEvent::Strict> or
946that automatically removes the callback again when it is destroyed (or 963that automatically removes the callback again when it is destroyed (or
947C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for 964C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
948a case where this is useful. 965a case where this is useful.
949 966
950Example: Create a watcher for the IO::AIO module and store it in 967Example: Create a watcher for the IO::AIO module and store it in
951C<$WATCHER>. Only do so after the event loop is initialised, though. 968C<$WATCHER>, but do so only do so after the event loop is initialised.
952 969
953 our WATCHER; 970 our WATCHER;
954 971
955 my $guard = AnyEvent::post_detect { 972 my $guard = AnyEvent::post_detect {
956 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb); 973 $WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
964 $WATCHER ||= $guard; 981 $WATCHER ||= $guard;
965 982
966=item @AnyEvent::post_detect 983=item @AnyEvent::post_detect
967 984
968If there are any code references in this array (you can C<push> to it 985If there are any code references in this array (you can C<push> to it
969before or after loading AnyEvent), then they will called directly after 986before or after loading AnyEvent), then they will be called directly
970the event loop has been chosen. 987after the event loop has been chosen.
971 988
972You should check C<$AnyEvent::MODEL> before adding to this array, though: 989You should check C<$AnyEvent::MODEL> before adding to this array, though:
973if it is defined then the event loop has already been detected, and the 990if it is defined then the event loop has already been detected, and the
974array will be ignored. 991array will be ignored.
975 992
992 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent 1009 # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
993 # as soon as it is 1010 # as soon as it is
994 push @AnyEvent::post_detect, sub { require Coro::AnyEvent }; 1011 push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
995 } 1012 }
996 1013
1014=item AnyEvent::postpone { BLOCK }
1015
1016Arranges for the block to be executed as soon as possible, but not before
1017the call itself returns. In practise, the block will be executed just
1018before the event loop polls for new events, or shortly afterwards.
1019
1020This function never returns anything (to make the C<return postpone { ...
1021}> idiom more useful.
1022
1023To understand the usefulness of this function, consider a function that
1024asynchronously does something for you and returns some transaction
1025object or guard to let you cancel the operation. For example,
1026C<AnyEvent::Socket::tcp_connect>:
1027
1028 # start a conenction attempt unless one is active
1029 $self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
1030 delete $self->{connect_guard};
1031 ...
1032 };
1033
1034Imagine that this function could instantly call the callback, for
1035example, because it detects an obvious error such as a negative port
1036number. Invoking the callback before the function returns causes problems
1037however: the callback will be called and will try to delete the guard
1038object. But since the function hasn't returned yet, there is nothing to
1039delete. When the function eventually returns it will assign the guard
1040object to C<< $self->{connect_guard} >>, where it will likely never be
1041deleted, so the program thinks it is still trying to connect.
1042
1043This is where C<AnyEvent::postpone> should be used. Instead of calling the
1044callback directly on error:
1045
1046 $cb->(undef), return # signal error to callback, BAD!
1047 if $some_error_condition;
1048
1049It should use C<postpone>:
1050
1051 AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
1052 if $some_error_condition;
1053
1054=item AnyEvent::log $level, $msg[, @args]
1055
1056Log the given C<$msg> at the given C<$level>.
1057
1058If L<AnyEvent::Log> is not loaded then this function makes a simple test
1059to see whether the message will be logged. If the test succeeds it will
1060load AnyEvent::Log and call C<AnyEvent::Log::log> - consequently, look at
1061the L<AnyEvent::Log> documentation for details.
1062
1063If the test fails it will simply return. Right now this happens when a
1064numerical loglevel is used and it is larger than the level specified via
1065C<$ENV{PERL_ANYEVENT_VERBOSE}>.
1066
1067If you want to sprinkle loads of logging calls around your code, consider
1068creating a logger callback with the C<AnyEvent::Log::logger> function,
1069which can reduce typing, codesize and can reduce the logging overhead
1070enourmously.
1071
997=back 1072=back
998 1073
999=head1 WHAT TO DO IN A MODULE 1074=head1 WHAT TO DO IN A MODULE
1000 1075
1001As a module author, you should C<use AnyEvent> and call AnyEvent methods 1076As a module author, you should C<use AnyEvent> and call AnyEvent methods
1011because it will stall the whole program, and the whole point of using 1086because it will stall the whole program, and the whole point of using
1012events is to stay interactive. 1087events is to stay interactive.
1013 1088
1014It is fine, however, to call C<< ->recv >> when the user of your module 1089It is fine, however, to call C<< ->recv >> when the user of your module
1015requests it (i.e. if you create a http request object ad have a method 1090requests it (i.e. if you create a http request object ad have a method
1016called C<results> that returns the results, it should call C<< ->recv >> 1091called C<results> that returns the results, it may call C<< ->recv >>
1017freely, as the user of your module knows what she is doing. always). 1092freely, as the user of your module knows what she is doing. Always).
1018 1093
1019=head1 WHAT TO DO IN THE MAIN PROGRAM 1094=head1 WHAT TO DO IN THE MAIN PROGRAM
1020 1095
1021There will always be a single main program - the only place that should 1096There will always be a single main program - the only place that should
1022dictate which event model to use. 1097dictate which event model to use.
1023 1098
1024If it doesn't care, it can just "use AnyEvent" and use it itself, or not 1099If the program is not event-based, it need not do anything special, even
1025do anything special (it does not need to be event-based) and let AnyEvent 1100when it depends on a module that uses an AnyEvent. If the program itself
1026decide which implementation to chose if some module relies on it. 1101uses AnyEvent, but does not care which event loop is used, all it needs
1102to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
1103available loop implementation.
1027 1104
1028If the main program relies on a specific event model - for example, in 1105If the main program relies on a specific event model - for example, in
1029Gtk2 programs you have to rely on the Glib module - you should load the 1106Gtk2 programs you have to rely on the Glib module - you should load the
1030event module before loading AnyEvent or any module that uses it: generally 1107event module before loading AnyEvent or any module that uses it: generally
1031speaking, you should load it as early as possible. The reason is that 1108speaking, you should load it as early as possible. The reason is that
1032modules might create watchers when they are loaded, and AnyEvent will 1109modules might create watchers when they are loaded, and AnyEvent will
1033decide on the event model to use as soon as it creates watchers, and it 1110decide on the event model to use as soon as it creates watchers, and it
1034might chose the wrong one unless you load the correct one yourself. 1111might choose the wrong one unless you load the correct one yourself.
1035 1112
1036You can chose to use a pure-perl implementation by loading the 1113You can chose to use a pure-perl implementation by loading the
1037C<AnyEvent::Impl::Perl> module, which gives you similar behaviour 1114C<AnyEvent::Loop> module, which gives you similar behaviour
1038everywhere, but letting AnyEvent chose the model is generally better. 1115everywhere, but letting AnyEvent chose the model is generally better.
1039 1116
1040=head2 MAINLOOP EMULATION 1117=head2 MAINLOOP EMULATION
1041 1118
1042Sometimes (often for short test scripts, or even standalone programs who 1119Sometimes (often for short test scripts, or even standalone programs who
1055 1132
1056 1133
1057=head1 OTHER MODULES 1134=head1 OTHER MODULES
1058 1135
1059The following is a non-exhaustive list of additional modules that use 1136The following is a non-exhaustive list of additional modules that use
1060AnyEvent as a client and can therefore be mixed easily with other AnyEvent 1137AnyEvent as a client and can therefore be mixed easily with other
1061modules and other event loops in the same program. Some of the modules 1138AnyEvent modules and other event loops in the same program. Some of the
1062come with AnyEvent, most are available via CPAN. 1139modules come as part of AnyEvent, the others are available via CPAN (see
1140L<http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for
1141a longer non-exhaustive list), and the list is heavily biased towards
1142modules of the AnyEvent author himself :)
1063 1143
1064=over 4 1144=over 4
1065 1145
1066=item L<AnyEvent::Util> 1146=item L<AnyEvent::Util>
1067 1147
1068Contains various utility functions that replace often-used but blocking 1148Contains various utility functions that replace often-used blocking
1069functions such as C<inet_aton> by event-/callback-based versions. 1149functions such as C<inet_aton> with event/callback-based versions.
1070 1150
1071=item L<AnyEvent::Socket> 1151=item L<AnyEvent::Socket>
1072 1152
1073Provides various utility functions for (internet protocol) sockets, 1153Provides various utility functions for (internet protocol) sockets,
1074addresses and name resolution. Also functions to create non-blocking tcp 1154addresses and name resolution. Also functions to create non-blocking tcp
1076 1156
1077=item L<AnyEvent::Handle> 1157=item L<AnyEvent::Handle>
1078 1158
1079Provide read and write buffers, manages watchers for reads and writes, 1159Provide read and write buffers, manages watchers for reads and writes,
1080supports raw and formatted I/O, I/O queued and fully transparent and 1160supports raw and formatted I/O, I/O queued and fully transparent and
1081non-blocking SSL/TLS (via L<AnyEvent::TLS>. 1161non-blocking SSL/TLS (via L<AnyEvent::TLS>).
1082 1162
1083=item L<AnyEvent::DNS> 1163=item L<AnyEvent::DNS>
1084 1164
1085Provides rich asynchronous DNS resolver capabilities. 1165Provides rich asynchronous DNS resolver capabilities.
1086 1166
1167=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
1168
1169Implement event-based interfaces to the protocols of the same name (for
1170the curious, IGS is the International Go Server and FCP is the Freenet
1171Client Protocol).
1172
1087=item L<AnyEvent::HTTP> 1173=item L<AnyEvent::AIO>
1088 1174
1089A simple-to-use HTTP library that is capable of making a lot of concurrent 1175Truly asynchronous (as opposed to non-blocking) I/O, should be in the
1090HTTP requests. 1176toolbox of every event programmer. AnyEvent::AIO transparently fuses
1177L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
1178file I/O, and much more.
1179
1180=item L<AnyEvent::Filesys::Notify>
1181
1182AnyEvent is good for non-blocking stuff, but it can't detect file or
1183path changes (e.g. "watch this directory for new files", "watch this
1184file for changes"). The L<AnyEvent::Filesys::Notify> module promises to
1185do just that in a portbale fashion, supporting inotify on GNU/Linux and
1186some weird, without doubt broken, stuff on OS X to monitor files. It can
1187fall back to blocking scans at regular intervals transparently on other
1188platforms, so it's about as portable as it gets.
1189
1190(I haven't used it myself, but I haven't heard anybody complaining about
1191it yet).
1192
1193=item L<AnyEvent::DBI>
1194
1195Executes L<DBI> requests asynchronously in a proxy process for you,
1196notifying you in an event-based way when the operation is finished.
1091 1197
1092=item L<AnyEvent::HTTPD> 1198=item L<AnyEvent::HTTPD>
1093 1199
1094Provides a simple web application server framework. 1200A simple embedded webserver.
1095 1201
1096=item L<AnyEvent::FastPing> 1202=item L<AnyEvent::FastPing>
1097 1203
1098The fastest ping in the west. 1204The fastest ping in the west.
1099 1205
1100=item L<AnyEvent::DBI>
1101
1102Executes L<DBI> requests asynchronously in a proxy process.
1103
1104=item L<AnyEvent::AIO>
1105
1106Truly asynchronous I/O, should be in the toolbox of every event
1107programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
1108together.
1109
1110=item L<AnyEvent::BDB>
1111
1112Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
1113L<BDB> and AnyEvent together.
1114
1115=item L<AnyEvent::GPSD>
1116
1117A non-blocking interface to gpsd, a daemon delivering GPS information.
1118
1119=item L<AnyEvent::IRC>
1120
1121AnyEvent based IRC client module family (replacing the older Net::IRC3).
1122
1123=item L<AnyEvent::XMPP>
1124
1125AnyEvent based XMPP (Jabber protocol) module family (replacing the older
1126Net::XMPP2>.
1127
1128=item L<AnyEvent::IGS>
1129
1130A non-blocking interface to the Internet Go Server protocol (used by
1131L<App::IGS>).
1132
1133=item L<Net::FCP>
1134
1135AnyEvent-based implementation of the Freenet Client Protocol, birthplace
1136of AnyEvent.
1137
1138=item L<Event::ExecFlow>
1139
1140High level API for event-based execution flow control.
1141
1142=item L<Coro> 1206=item L<Coro>
1143 1207
1144Has special support for AnyEvent via L<Coro::AnyEvent>. 1208Has special support for AnyEvent via L<Coro::AnyEvent>, which allows you
1209to simply invert the flow control - don't call us, we will call you:
1210
1211 async {
1212 Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it
1213 print "5 seconds later!\n";
1214
1215 Coro::AnyEvent::readable *STDIN; # uses an I/O watcher
1216 my $line = <STDIN>; # works for ttys
1217
1218 AnyEvent::HTTP::http_get "url", Coro::rouse_cb;
1219 my ($body, $hdr) = Coro::rouse_wait;
1220 };
1145 1221
1146=back 1222=back
1147 1223
1148=cut 1224=cut
1149 1225
1150package AnyEvent; 1226package AnyEvent;
1151 1227
1152# basically a tuned-down version of common::sense 1228# basically a tuned-down version of common::sense
1153sub common_sense { 1229sub common_sense {
1154 # from common:.sense 1.0 1230 # from common:.sense 3.4
1155 ${^WARNING_BITS} = "\xfc\x3f\x33\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x00"; 1231 ${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
1156 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl) 1232 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
1157 $^H |= 0x00000600; 1233 $^H |= 0x00000600;
1158} 1234}
1159 1235
1160BEGIN { AnyEvent::common_sense } 1236BEGIN { AnyEvent::common_sense }
1161 1237
1162use Carp (); 1238use Carp ();
1163 1239
1164our $VERSION = '5.26'; 1240our $VERSION = '6.02';
1165our $MODEL; 1241our $MODEL;
1166
1167our $AUTOLOAD;
1168our @ISA; 1242our @ISA;
1169
1170our @REGISTRY; 1243our @REGISTRY;
1171
1172our $VERBOSE; 1244our $VERBOSE;
1245our $MAX_SIGNAL_LATENCY = 10;
1246our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
1173 1247
1174BEGIN { 1248BEGIN {
1175 require "AnyEvent/constants.pl"; 1249 require "AnyEvent/constants.pl";
1176 1250
1177 eval "sub TAINT (){" . (${^TAINT}*1) . "}"; 1251 eval "sub TAINT (){" . (${^TAINT}*1) . "}";
1178 1252
1179 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV} 1253 delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
1180 if ${^TAINT}; 1254 if ${^TAINT};
1181 1255
1182 $VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1; 1256 $ENV{"PERL_ANYEVENT_$_"} = $ENV{"AE_$_"}
1257 for grep s/^AE_// && !exists $ENV{"PERL_ANYEVENT_$_"}, keys %ENV;
1183 1258
1184} 1259 @ENV{grep /^PERL_ANYEVENT_/, keys %ENV} = ()
1260 if ${^TAINT};
1185 1261
1186our $MAX_SIGNAL_LATENCY = 10; 1262 # $ENV{PERL_ANYEVENT_xxx} now valid
1187 1263
1188our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred 1264 $VERBOSE = length $ENV{PERL_ANYEVENT_VERBOSE} ? $ENV{PERL_ANYEVENT_VERBOSE}*1 : 3;
1189 1265
1190{
1191 my $idx; 1266 my $idx;
1192 $PROTOCOL{$_} = ++$idx 1267 $PROTOCOL{$_} = ++$idx
1193 for reverse split /\s*,\s*/, 1268 for reverse split /\s*,\s*/,
1194 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; 1269 $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
1195} 1270}
1196 1271
1272our @post_detect;
1273
1274sub post_detect(&) {
1275 my ($cb) = @_;
1276
1277 push @post_detect, $cb;
1278
1279 defined wantarray
1280 ? bless \$cb, "AnyEvent::Util::postdetect"
1281 : ()
1282}
1283
1284sub AnyEvent::Util::postdetect::DESTROY {
1285 @post_detect = grep $_ != ${$_[0]}, @post_detect;
1286}
1287
1288our $POSTPONE_W;
1289our @POSTPONE;
1290
1291sub _postpone_exec {
1292 undef $POSTPONE_W;
1293
1294 &{ shift @POSTPONE }
1295 while @POSTPONE;
1296}
1297
1298sub postpone(&) {
1299 push @POSTPONE, shift;
1300
1301 $POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
1302
1303 ()
1304}
1305
1306sub log($$;@) {
1307 # only load the big bloated module when we actually are about to log something
1308 if ($_[0] <= $VERBOSE) { # also catches non-numeric levels(!)
1309 require AnyEvent::Log;
1310 # AnyEvent::Log overwrites this function
1311 goto &log;
1312 }
1313
1314 0 # not logged
1315}
1316
1317if (length $ENV{PERL_ANYEVENT_LOG}) {
1318 require AnyEvent::Log; # AnyEvent::Log does the thing for us
1319}
1320
1197my @models = ( 1321our @models = (
1198 [EV:: => AnyEvent::Impl::EV:: , 1], 1322 [EV:: => AnyEvent::Impl::EV:: , 1],
1199 [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1], 1323 [AnyEvent::Loop:: => AnyEvent::Impl::Perl:: , 1],
1200 # everything below here will not (normally) be autoprobed 1324 # everything below here will not (normally) be autoprobed
1201 # as the pureperl backend should work everywhere 1325 # as the pure perl backend should work everywhere
1202 # and is usually faster 1326 # and is usually faster
1203 [Event:: => AnyEvent::Impl::Event::, 1], 1327 [Event:: => AnyEvent::Impl::Event::, 1],
1204 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers 1328 [Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
1205 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy 1329 [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
1206 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package 1330 [Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
1207 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles 1331 [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
1208 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program 1332 [Qt:: => AnyEvent::Impl::Qt::], # requires special main program
1209 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza 1333 [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
1210 [Wx:: => AnyEvent::Impl::POE::], 1334 [Wx:: => AnyEvent::Impl::POE::],
1211 [Prima:: => AnyEvent::Impl::POE::], 1335 [Prima:: => AnyEvent::Impl::POE::],
1212 # IO::Async is just too broken - we would need workarounds for its 1336 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # a bitch to autodetect
1213 # byzantine signal and broken child handling, among others. 1337 [Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
1214 # IO::Async is rather hard to detect, as it doesn't have any 1338 [FLTK:: => AnyEvent::Impl::FLTK::],
1215 # obvious default class.
1216 [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
1217 [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
1218 [IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
1219 [AnyEvent::Impl::IOAsync:: => AnyEvent::Impl::IOAsync::], # requires special main program
1220); 1339);
1221 1340
1222our %method = map +($_ => 1), 1341our @isa_hook;
1342
1343sub _isa_set {
1344 my @pkg = ("AnyEvent", (map $_->[0], grep defined, @isa_hook), $MODEL);
1345
1346 @{"$pkg[$_-1]::ISA"} = $pkg[$_]
1347 for 1 .. $#pkg;
1348
1349 grep $_ && $_->[1], @isa_hook
1350 and AE::_reset ();
1351}
1352
1353# used for hooking AnyEvent::Strict and AnyEvent::Debug::Wrap into the class hierarchy
1354sub _isa_hook($$;$) {
1355 my ($i, $pkg, $reset_ae) = @_;
1356
1357 $isa_hook[$i] = $pkg ? [$pkg, $reset_ae] : undef;
1358
1359 _isa_set;
1360}
1361
1362# all autoloaded methods reserve the complete glob, not just the method slot.
1363# due to bugs in perls method cache implementation.
1223 qw(io timer time now now_update signal child idle condvar one_event DESTROY); 1364our @methods = qw(io timer time now now_update signal child idle condvar);
1224
1225our @post_detect;
1226
1227sub post_detect(&) {
1228 my ($cb) = @_;
1229
1230 push @post_detect, $cb;
1231
1232 defined wantarray
1233 ? bless \$cb, "AnyEvent::Util::postdetect"
1234 : ()
1235}
1236
1237sub AnyEvent::Util::postdetect::DESTROY {
1238 @post_detect = grep $_ != ${$_[0]}, @post_detect;
1239}
1240 1365
1241sub detect() { 1366sub detect() {
1367 return $MODEL if $MODEL; # some programs keep references to detect
1368
1369 local $!; # for good measure
1370 local $SIG{__DIE__}; # we use eval
1371
1242 # free some memory 1372 # free some memory
1243 *detect = sub () { $MODEL }; 1373 *detect = sub () { $MODEL };
1374 # undef &func doesn't correctly update the method cache. grmbl.
1375 # so we delete the whole glob. grmbl.
1376 # otoh, perl doesn't let me undef an active usb, but it lets me free
1377 # a glob with an active sub. hrm. i hope it works, but perl is
1378 # usually buggy in this department. sigh.
1379 delete @{"AnyEvent::"}{@methods};
1380 undef @methods;
1244 1381
1245 local $!; # for good measure
1246 local $SIG{__DIE__};
1247
1248 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { 1382 if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z0-9:]+)$/) {
1249 my $model = "AnyEvent::Impl::$1"; 1383 my $model = $1;
1384 $model = "AnyEvent::Impl::$model" unless $model =~ s/::$//;
1250 if (eval "require $model") { 1385 if (eval "require $model") {
1386 AnyEvent::log 7 => "loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.";
1251 $MODEL = $model; 1387 $MODEL = $model;
1252 warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
1253 } else { 1388 } else {
1254 warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE; 1389 AnyEvent::log 5 => "unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@";
1255 } 1390 }
1256 } 1391 }
1257 1392
1258 # check for already loaded models 1393 # check for already loaded models
1259 unless ($MODEL) { 1394 unless ($MODEL) {
1260 for (@REGISTRY, @models) { 1395 for (@REGISTRY, @models) {
1261 my ($package, $model) = @$_; 1396 my ($package, $model) = @$_;
1262 if (${"$package\::VERSION"} > 0) { 1397 if (${"$package\::VERSION"} > 0) {
1263 if (eval "require $model") { 1398 if (eval "require $model") {
1399 AnyEvent::log 7 => "autodetected model '$model', using it.";
1264 $MODEL = $model; 1400 $MODEL = $model;
1265 warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
1266 last; 1401 last;
1267 } 1402 }
1268 } 1403 }
1269 } 1404 }
1270 1405
1276 $autoload 1411 $autoload
1277 and eval "require $package" 1412 and eval "require $package"
1278 and ${"$package\::VERSION"} > 0 1413 and ${"$package\::VERSION"} > 0
1279 and eval "require $model" 1414 and eval "require $model"
1280 ) { 1415 ) {
1416 AnyEvent::log 7 => "autoloaded model '$model', using it.";
1281 $MODEL = $model; 1417 $MODEL = $model;
1282 warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1283 last; 1418 last;
1284 } 1419 }
1285 } 1420 }
1286 1421
1287 $MODEL 1422 $MODEL
1288 or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n"; 1423 or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?";
1289 } 1424 }
1290 } 1425 }
1291 1426
1292 @models = (); # free probe data 1427 # free memory only needed for probing
1428 undef @models;
1429 undef @REGISTRY;
1293 1430
1294 push @{"$MODEL\::ISA"}, "AnyEvent::Base"; 1431 push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1295 unshift @ISA, $MODEL;
1296 1432
1297 # now nuke some methods that are overriden by the backend. 1433 # now nuke some methods that are overridden by the backend.
1298 # SUPER is not allowed. 1434 # SUPER usage is not allowed in these.
1299 for (qw(time signal child idle)) { 1435 for (qw(time signal child idle)) {
1300 undef &{"AnyEvent::Base::$_"} 1436 undef &{"AnyEvent::Base::$_"}
1301 if defined &{"$MODEL\::$_"}; 1437 if defined &{"$MODEL\::$_"};
1302 } 1438 }
1303 1439
1304 require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT}; 1440 _isa_set;
1441
1442 # we're officially open!
1443
1444 if ($ENV{PERL_ANYEVENT_STRICT}) {
1445 require AnyEvent::Strict;
1446 }
1447
1448 if ($ENV{PERL_ANYEVENT_DEBUG_WRAP}) {
1449 require AnyEvent::Debug;
1450 AnyEvent::Debug::wrap ($ENV{PERL_ANYEVENT_DEBUG_WRAP});
1451 }
1452
1453 if (length $ENV{PERL_ANYEVENT_DEBUG_SHELL}) {
1454 require AnyEvent::Socket;
1455 require AnyEvent::Debug;
1456
1457 my $shell = $ENV{PERL_ANYEVENT_DEBUG_SHELL};
1458 $shell =~ s/\$\$/$$/g;
1459
1460 my ($host, $service) = AnyEvent::Socket::parse_hostport ($shell);
1461 $AnyEvent::Debug::SHELL = AnyEvent::Debug::shell ($host, $service);
1462 }
1463
1464 # now the anyevent environment is set up as the user told us to, so
1465 # call the actual user code - post detects
1305 1466
1306 (shift @post_detect)->() while @post_detect; 1467 (shift @post_detect)->() while @post_detect;
1468 undef @post_detect;
1307 1469
1308 *post_detect = sub(&) { 1470 *post_detect = sub(&) {
1309 shift->(); 1471 shift->();
1310 1472
1311 undef 1473 undef
1312 }; 1474 };
1313 1475
1314 $MODEL 1476 $MODEL
1315} 1477}
1316 1478
1317sub AUTOLOAD { 1479for my $name (@methods) {
1318 (my $func = $AUTOLOAD) =~ s/.*://; 1480 *$name = sub {
1319
1320 $method{$func}
1321 or Carp::croak "$func: not a valid AnyEvent class method";
1322
1323 detect; 1481 detect;
1324 1482 # we use goto because
1325 my $class = shift; 1483 # a) it makes the thunk more transparent
1326 $class->$func (@_); 1484 # b) it allows us to delete the thunk later
1485 goto &{ UNIVERSAL::can AnyEvent => "SUPER::$name" }
1486 };
1327} 1487}
1328 1488
1329# utility function to dup a filehandle. this is used by many backends 1489# utility function to dup a filehandle. this is used by many backends
1330# to support binding more than one watcher per filehandle (they usually 1490# to support binding more than one watcher per filehandle (they usually
1331# allow only one watcher per fd, so we dup it to get a different one). 1491# allow only one watcher per fd, so we dup it to get a different one).
1355 1515
1356package AE; 1516package AE;
1357 1517
1358our $VERSION = $AnyEvent::VERSION; 1518our $VERSION = $AnyEvent::VERSION;
1359 1519
1520sub _reset() {
1521 eval q{
1360# fall back to the main API by default - backends and AnyEvent::Base 1522 # fall back to the main API by default - backends and AnyEvent::Base
1361# implementations can overwrite these. 1523 # implementations can overwrite these.
1362 1524
1363sub io($$$) { 1525 sub io($$$) {
1364 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2]) 1526 AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
1365} 1527 }
1366 1528
1367sub timer($$$) { 1529 sub timer($$$) {
1368 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2]) 1530 AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
1369} 1531 }
1370 1532
1371sub signal($$) { 1533 sub signal($$) {
1372 AnyEvent->signal (signal => $_[0], cb => $_[1]) 1534 AnyEvent->signal (signal => $_[0], cb => $_[1])
1373} 1535 }
1374 1536
1375sub child($$) { 1537 sub child($$) {
1376 AnyEvent->child (pid => $_[0], cb => $_[1]) 1538 AnyEvent->child (pid => $_[0], cb => $_[1])
1377} 1539 }
1378 1540
1379sub idle($) { 1541 sub idle($) {
1380 AnyEvent->idle (cb => $_[0]) 1542 AnyEvent->idle (cb => $_[0]);
1381} 1543 }
1382 1544
1383sub cv(;&) { 1545 sub cv(;&) {
1384 AnyEvent->condvar (@_ ? (cb => $_[0]) : ()) 1546 AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
1385} 1547 }
1386 1548
1387sub now() { 1549 sub now() {
1388 AnyEvent->now 1550 AnyEvent->now
1389} 1551 }
1390 1552
1391sub now_update() { 1553 sub now_update() {
1392 AnyEvent->now_update 1554 AnyEvent->now_update
1393} 1555 }
1394 1556
1395sub time() { 1557 sub time() {
1396 AnyEvent->time 1558 AnyEvent->time
1559 }
1560
1561 *postpone = \&AnyEvent::postpone;
1562 *log = \&AnyEvent::log;
1563 };
1564 die if $@;
1397} 1565}
1566
1567BEGIN { _reset }
1398 1568
1399package AnyEvent::Base; 1569package AnyEvent::Base;
1400 1570
1401# default implementations for many methods 1571# default implementations for many methods
1402 1572
1403sub time { 1573sub time {
1404 eval q{ # poor man's autoloading {} 1574 eval q{ # poor man's autoloading {}
1405 # probe for availability of Time::HiRes 1575 # probe for availability of Time::HiRes
1406 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") { 1576 if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
1407 warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8; 1577 *time = sub { Time::HiRes::time () };
1408 *AE::time = \&Time::HiRes::time; 1578 *AE::time = \& Time::HiRes::time ;
1579 *now = \&time;
1580 AnyEvent::log 8 => "AnyEvent: using Time::HiRes for sub-second timing accuracy.";
1409 # if (eval "use POSIX (); (POSIX::times())... 1581 # if (eval "use POSIX (); (POSIX::times())...
1410 } else { 1582 } else {
1583 *time = sub { CORE::time };
1584 *AE::time = sub (){ CORE::time };
1585 *now = \&time;
1411 warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE; 1586 AnyEvent::log 3 => "using built-in time(), WARNING, no sub-second resolution!";
1412 *AE::time = sub (){ time }; # epic fail
1413 } 1587 }
1414
1415 *time = sub { AE::time }; # different prototypes
1416 }; 1588 };
1417 die if $@; 1589 die if $@;
1418 1590
1419 &time 1591 &time
1420} 1592}
1421 1593
1422*now = \&time; 1594*now = \&time;
1423
1424sub now_update { } 1595sub now_update { }
1425 1596
1597sub _poll {
1598 Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
1599}
1600
1426# default implementation for ->condvar 1601# default implementation for ->condvar
1602# in fact, the default should not be overwritten
1427 1603
1428sub condvar { 1604sub condvar {
1429 eval q{ # poor man's autoloading {} 1605 eval q{ # poor man's autoloading {}
1430 *condvar = sub { 1606 *condvar = sub {
1431 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar" 1607 bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1509 1685
1510sub signal { 1686sub signal {
1511 eval q{ # poor man's autoloading {} 1687 eval q{ # poor man's autoloading {}
1512 # probe for availability of Async::Interrupt 1688 # probe for availability of Async::Interrupt
1513 if (_have_async_interrupt) { 1689 if (_have_async_interrupt) {
1514 warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8; 1690 AnyEvent::log 8 => "using Async::Interrupt for race-free signal handling.";
1515 1691
1516 $SIGPIPE_R = new Async::Interrupt::EventPipe; 1692 $SIGPIPE_R = new Async::Interrupt::EventPipe;
1517 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec; 1693 $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
1518 1694
1519 } else { 1695 } else {
1520 warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8; 1696 AnyEvent::log 8 => "using emulated perl signal handling with latency timer.";
1521 1697
1522 if (AnyEvent::WIN32) { 1698 if (AnyEvent::WIN32) {
1523 require AnyEvent::Util; 1699 require AnyEvent::Util;
1524 1700
1525 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe (); 1701 ($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1601 : sysread $SIGPIPE_R, (my $dummy), 9; 1777 : sysread $SIGPIPE_R, (my $dummy), 9;
1602 1778
1603 while (%SIG_EV) { 1779 while (%SIG_EV) {
1604 for (keys %SIG_EV) { 1780 for (keys %SIG_EV) {
1605 delete $SIG_EV{$_}; 1781 delete $SIG_EV{$_};
1606 $_->() for values %{ $SIG_CB{$_} || {} }; 1782 &$_ for values %{ $SIG_CB{$_} || {} };
1607 } 1783 }
1608 } 1784 }
1609 }; 1785 };
1610 }; 1786 };
1611 die if $@; 1787 die if $@;
1616# default implementation for ->child 1792# default implementation for ->child
1617 1793
1618our %PID_CB; 1794our %PID_CB;
1619our $CHLD_W; 1795our $CHLD_W;
1620our $CHLD_DELAY_W; 1796our $CHLD_DELAY_W;
1621our $WNOHANG;
1622 1797
1623# used by many Impl's 1798# used by many Impl's
1624sub _emit_childstatus($$) { 1799sub _emit_childstatus($$) {
1625 my (undef, $rpid, $rstatus) = @_; 1800 my (undef, $rpid, $rstatus) = @_;
1626 1801
1633 eval q{ # poor man's autoloading {} 1808 eval q{ # poor man's autoloading {}
1634 *_sigchld = sub { 1809 *_sigchld = sub {
1635 my $pid; 1810 my $pid;
1636 1811
1637 AnyEvent->_emit_childstatus ($pid, $?) 1812 AnyEvent->_emit_childstatus ($pid, $?)
1638 while ($pid = waitpid -1, $WNOHANG) > 0; 1813 while ($pid = waitpid -1, WNOHANG) > 0;
1639 }; 1814 };
1640 1815
1641 *child = sub { 1816 *child = sub {
1642 my (undef, %arg) = @_; 1817 my (undef, %arg) = @_;
1643 1818
1644 defined (my $pid = $arg{pid} + 0) 1819 my $pid = $arg{pid};
1645 or Carp::croak "required option 'pid' is missing"; 1820 my $cb = $arg{cb};
1646 1821
1647 $PID_CB{$pid}{$arg{cb}} = $arg{cb}; 1822 $PID_CB{$pid}{$cb+0} = $cb;
1648
1649 # WNOHANG is almost cetrainly 1 everywhere
1650 $WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
1651 ? 1
1652 : eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1653 1823
1654 unless ($CHLD_W) { 1824 unless ($CHLD_W) {
1655 $CHLD_W = AE::signal CHLD => \&_sigchld; 1825 $CHLD_W = AE::signal CHLD => \&_sigchld;
1656 # child could be a zombie already, so make at least one round 1826 # child could be a zombie already, so make at least one round
1657 &_sigchld; 1827 &_sigchld;
1658 } 1828 }
1659 1829
1660 bless [$pid, $arg{cb}], "AnyEvent::Base::child" 1830 bless [$pid, $cb+0], "AnyEvent::Base::child"
1661 }; 1831 };
1662 1832
1663 *AnyEvent::Base::child::DESTROY = sub { 1833 *AnyEvent::Base::child::DESTROY = sub {
1664 my ($pid, $cb) = @{$_[0]}; 1834 my ($pid, $icb) = @{$_[0]};
1665 1835
1666 delete $PID_CB{$pid}{$cb}; 1836 delete $PID_CB{$pid}{$icb};
1667 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} }; 1837 delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1668 1838
1669 undef $CHLD_W unless keys %PID_CB; 1839 undef $CHLD_W unless keys %PID_CB;
1670 }; 1840 };
1671 }; 1841 };
1684 1854
1685 my ($cb, $w, $rcb) = $arg{cb}; 1855 my ($cb, $w, $rcb) = $arg{cb};
1686 1856
1687 $rcb = sub { 1857 $rcb = sub {
1688 if ($cb) { 1858 if ($cb) {
1689 $w = _time; 1859 $w = AE::time;
1690 &$cb; 1860 &$cb;
1691 $w = _time - $w; 1861 $w = AE::time - $w;
1692 1862
1693 # never use more then 50% of the time for the idle watcher, 1863 # never use more then 50% of the time for the idle watcher,
1694 # within some limits 1864 # within some limits
1695 $w = 0.0001 if $w < 0.0001; 1865 $w = 0.0001 if $w < 0.0001;
1696 $w = 5 if $w > 5; 1866 $w = 5 if $w > 5;
1719 1889
1720package AnyEvent::CondVar; 1890package AnyEvent::CondVar;
1721 1891
1722our @ISA = AnyEvent::CondVar::Base::; 1892our @ISA = AnyEvent::CondVar::Base::;
1723 1893
1894# only to be used for subclassing
1895sub new {
1896 my $class = shift;
1897 bless AnyEvent->condvar (@_), $class
1898}
1899
1724package AnyEvent::CondVar::Base; 1900package AnyEvent::CondVar::Base;
1725 1901
1726#use overload 1902#use overload
1727# '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, 1903# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1728# fallback => 1; 1904# fallback => 1;
1737 1913
1738sub _send { 1914sub _send {
1739 # nop 1915 # nop
1740} 1916}
1741 1917
1918sub _wait {
1919 AnyEvent->_poll until $_[0]{_ae_sent};
1920}
1921
1742sub send { 1922sub send {
1743 my $cv = shift; 1923 my $cv = shift;
1744 $cv->{_ae_sent} = [@_]; 1924 $cv->{_ae_sent} = [@_];
1745 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb}; 1925 (delete $cv->{_ae_cb})->($cv) if $cv->{_ae_cb};
1746 $cv->_send; 1926 $cv->_send;
1753 1933
1754sub ready { 1934sub ready {
1755 $_[0]{_ae_sent} 1935 $_[0]{_ae_sent}
1756} 1936}
1757 1937
1758sub _wait {
1759 $WAITING
1760 and !$_[0]{_ae_sent}
1761 and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
1762
1763 local $WAITING = 1;
1764 AnyEvent->one_event while !$_[0]{_ae_sent};
1765}
1766
1767sub recv { 1938sub recv {
1939 unless ($_[0]{_ae_sent}) {
1940 $WAITING
1941 and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
1942
1943 local $WAITING = 1;
1768 $_[0]->_wait; 1944 $_[0]->_wait;
1945 }
1769 1946
1770 Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak}; 1947 $_[0]{_ae_croak}
1771 wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0] 1948 and Carp::croak $_[0]{_ae_croak};
1949
1950 wantarray
1951 ? @{ $_[0]{_ae_sent} }
1952 : $_[0]{_ae_sent}[0]
1772} 1953}
1773 1954
1774sub cb { 1955sub cb {
1775 my $cv = shift; 1956 my $cv = shift;
1776 1957
1792 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } }; 1973 &{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1793} 1974}
1794 1975
1795# undocumented/compatibility with pre-3.4 1976# undocumented/compatibility with pre-3.4
1796*broadcast = \&send; 1977*broadcast = \&send;
1797*wait = \&_wait; 1978*wait = \&recv;
1798 1979
1799=head1 ERROR AND EXCEPTION HANDLING 1980=head1 ERROR AND EXCEPTION HANDLING
1800 1981
1801In general, AnyEvent does not do any error handling - it relies on the 1982In general, AnyEvent does not do any error handling - it relies on the
1802caller to do that if required. The L<AnyEvent::Strict> module (see also 1983caller to do that if required. The L<AnyEvent::Strict> module (see also
1814$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and 1995$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
1815so on. 1996so on.
1816 1997
1817=head1 ENVIRONMENT VARIABLES 1998=head1 ENVIRONMENT VARIABLES
1818 1999
1819The following environment variables are used by this module or its 2000AnyEvent supports a number of environment variables that tune the
1820submodules. 2001runtime behaviour. They are usually evaluated when AnyEvent is
2002loaded, initialised, or a submodule that uses them is loaded. Many of
2003them also cause AnyEvent to load additional modules - for example,
2004C<PERL_ANYEVENT_DEBUG_WRAP> causes the L<AnyEvent::Debug> module to be
2005loaded.
1821 2006
1822Note that AnyEvent will remove I<all> environment variables starting with 2007All the environment variables documented here start with
1823C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is 2008C<PERL_ANYEVENT_>, which is what AnyEvent considers its own
1824enabled. 2009namespace. Other modules are encouraged (but by no means required) to use
2010C<PERL_ANYEVENT_SUBMODULE> if they have registered the AnyEvent::Submodule
2011namespace on CPAN, for any submodule. For example, L<AnyEvent::HTTP> could
2012be expected to use C<PERL_ANYEVENT_HTTP_PROXY> (it should not access env
2013variables starting with C<AE_>, see below).
2014
2015All variables can also be set via the C<AE_> prefix, that is, instead
2016of setting C<PERL_ANYEVENT_VERBOSE> you can also set C<AE_VERBOSE>. In
2017case there is a clash btween anyevent and another program that uses
2018C<AE_something> you can set the corresponding C<PERL_ANYEVENT_something>
2019variable to the empty string, as those variables take precedence.
2020
2021When AnyEvent is first loaded, it copies all C<AE_xxx> env variables
2022to their C<PERL_ANYEVENT_xxx> counterpart unless that variable already
2023exists. If taint mode is on, then AnyEvent will remove I<all> environment
2024variables starting with C<PERL_ANYEVENT_> from C<%ENV> (or replace them
2025with C<undef> or the empty string, if the corresaponding C<AE_> variable
2026is set).
2027
2028The exact algorithm is currently:
2029
2030 1. if taint mode enabled, delete all PERL_ANYEVENT_xyz variables from %ENV
2031 2. copy over AE_xyz to PERL_ANYEVENT_xyz unless the latter alraedy exists
2032 3. if taint mode enabled, set all PERL_ANYEVENT_xyz variables to undef.
2033
2034This ensures that child processes will not see the C<AE_> variables.
2035
2036The following environment variables are currently known to AnyEvent:
1825 2037
1826=over 4 2038=over 4
1827 2039
1828=item C<PERL_ANYEVENT_VERBOSE> 2040=item C<PERL_ANYEVENT_VERBOSE>
1829 2041
1830By default, AnyEvent will be completely silent except in fatal 2042By default, AnyEvent will only log messages with loglevel C<3>
1831conditions. You can set this environment variable to make AnyEvent more 2043(C<critical>) or higher (see L<AnyEvent::Log>). You can set this
2044environment variable to a numerical loglevel to make AnyEvent more (or
1832talkative. 2045less) talkative.
1833 2046
2047If you want to do more than just set the global logging level
2048you should have a look at C<PERL_ANYEVENT_LOG>, which allows much more
2049complex specifications.
2050
2051When set to C<0> (C<off>), then no messages whatsoever will be logged with
2052the default logging settings.
2053
1834When set to C<1> or higher, causes AnyEvent to warn about unexpected 2054When set to C<5> or higher (C<warn>), causes AnyEvent to warn about
1835conditions, such as not being able to load the event model specified by 2055unexpected conditions, such as not being able to load the event model
1836C<PERL_ANYEVENT_MODEL>. 2056specified by C<PERL_ANYEVENT_MODEL>, or a guard callback throwing an
2057exception - this is the minimum recommended level.
1837 2058
1838When set to C<2> or higher, cause AnyEvent to report to STDERR which event 2059When set to C<7> or higher (info), cause AnyEvent to report which event model it
1839model it chooses. 2060chooses.
1840 2061
1841When set to C<8> or higher, then AnyEvent will report extra information on 2062When set to C<8> or higher (debug), then AnyEvent will report extra information on
1842which optional modules it loads and how it implements certain features. 2063which optional modules it loads and how it implements certain features.
2064
2065=item C<PERL_ANYEVENT_LOG>
2066
2067Accepts rather complex logging specifications. For example, you could log
2068all C<debug> messages of some module to stderr, warnings and above to
2069stderr, and errors and above to syslog, with:
2070
2071 PERL_ANYEVENT_LOG=Some::Module=debug,+log:filter=warn,+%syslog:%syslog=error,syslog
2072
2073For the rather extensive details, see L<AnyEvent::Log>.
2074
2075This variable is evaluated when AnyEvent (or L<AnyEvent::Log>) is loaded,
2076so will take effect even before AnyEvent has initialised itself.
2077
2078Note that specifying this environment variable causes the L<AnyEvent::Log>
2079module to be loaded, while C<PERL_ANYEVENT_VERBOSE> does not, so only
2080using the latter saves a few hundred kB of memory until the first message
2081is being logged.
1843 2082
1844=item C<PERL_ANYEVENT_STRICT> 2083=item C<PERL_ANYEVENT_STRICT>
1845 2084
1846AnyEvent does not do much argument checking by default, as thorough 2085AnyEvent does not do much argument checking by default, as thorough
1847argument checking is very costly. Setting this variable to a true value 2086argument checking is very costly. Setting this variable to a true value
1849check the arguments passed to most method calls. If it finds any problems, 2088check the arguments passed to most method calls. If it finds any problems,
1850it will croak. 2089it will croak.
1851 2090
1852In other words, enables "strict" mode. 2091In other words, enables "strict" mode.
1853 2092
1854Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense> 2093Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
1855>>, it is definitely recommended to keep it off in production. Keeping 2094>>, it is definitely recommended to keep it off in production. Keeping
1856C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs 2095C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
1857can be very useful, however. 2096can be very useful, however.
1858 2097
2098=item C<PERL_ANYEVENT_DEBUG_SHELL>
2099
2100If this env variable is nonempty, then its contents will be interpreted by
2101C<AnyEvent::Socket::parse_hostport> and C<AnyEvent::Debug::shell> (after
2102replacing every occurance of C<$$> by the process pid). The shell object
2103is saved in C<$AnyEvent::Debug::SHELL>.
2104
2105This happens when the first watcher is created.
2106
2107For example, to bind a debug shell on a unix domain socket in
2108F<< /tmp/debug<pid>.sock >>, you could use this:
2109
2110 PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog
2111 # connect with e.g.: socat readline /tmp/debug123.sock
2112
2113Or to bind to tcp port 4545 on localhost:
2114
2115 PERL_ANYEVENT_DEBUG_SHELL=127.0.0.1:4545 perlprog
2116 # connect with e.g.: telnet localhost 4545
2117
2118Note that creating sockets in F</tmp> or on localhost is very unsafe on
2119multiuser systems.
2120
2121=item C<PERL_ANYEVENT_DEBUG_WRAP>
2122
2123Can be set to C<0>, C<1> or C<2> and enables wrapping of all watchers for
2124debugging purposes. See C<AnyEvent::Debug::wrap> for details.
2125
1859=item C<PERL_ANYEVENT_MODEL> 2126=item C<PERL_ANYEVENT_MODEL>
1860 2127
1861This can be used to specify the event model to be used by AnyEvent, before 2128This can be used to specify the event model to be used by AnyEvent, before
1862auto detection and -probing kicks in. It must be a string consisting 2129auto detection and -probing kicks in.
1863entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended 2130
2131It normally is a string consisting entirely of ASCII letters (e.g. C<EV>
2132or C<IOAsync>). The string C<AnyEvent::Impl::> gets prepended and the
1864and the resulting module name is loaded and if the load was successful, 2133resulting module name is loaded and - if the load was successful - used as
1865used as event model. If it fails to load AnyEvent will proceed with 2134event model backend. If it fails to load then AnyEvent will proceed with
1866auto detection and -probing. 2135auto detection and -probing.
1867 2136
1868This functionality might change in future versions. 2137If the string ends with C<::> instead (e.g. C<AnyEvent::Impl::EV::>) then
2138nothing gets prepended and the module name is used as-is (hint: C<::> at
2139the end of a string designates a module name and quotes it appropriately).
1869 2140
1870For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you 2141For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
1871could start your program like this: 2142could start your program like this:
1872 2143
1873 PERL_ANYEVENT_MODEL=Perl perl ... 2144 PERL_ANYEVENT_MODEL=Perl perl ...
1874 2145
1875=item C<PERL_ANYEVENT_PROTOCOLS> 2146=item C<PERL_ANYEVENT_PROTOCOLS>
1891but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4> 2162but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1892- only support IPv4, never try to resolve or contact IPv6 2163- only support IPv4, never try to resolve or contact IPv6
1893addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or 2164addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1894IPv6, but prefer IPv6 over IPv4. 2165IPv6, but prefer IPv6 over IPv4.
1895 2166
2167=item C<PERL_ANYEVENT_HOSTS>
2168
2169This variable, if specified, overrides the F</etc/hosts> file used by
2170L<AnyEvent::Socket>C<::resolve_sockaddr>, i.e. hosts aliases will be read
2171from that file instead.
2172
1896=item C<PERL_ANYEVENT_EDNS0> 2173=item C<PERL_ANYEVENT_EDNS0>
1897 2174
1898Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension 2175Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension for
1899for DNS. This extension is generally useful to reduce DNS traffic, but 2176DNS. This extension is generally useful to reduce DNS traffic, especially
1900some (broken) firewalls drop such DNS packets, which is why it is off by 2177when DNSSEC is involved, but some (broken) firewalls drop such DNS
1901default. 2178packets, which is why it is off by default.
1902 2179
1903Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce 2180Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1904EDNS0 in its DNS requests. 2181EDNS0 in its DNS requests.
1905 2182
1906=item C<PERL_ANYEVENT_MAX_FORKS> 2183=item C<PERL_ANYEVENT_MAX_FORKS>
1914resolver - this is the maximum number of parallel DNS requests that are 2191resolver - this is the maximum number of parallel DNS requests that are
1915sent to the DNS server. 2192sent to the DNS server.
1916 2193
1917=item C<PERL_ANYEVENT_RESOLV_CONF> 2194=item C<PERL_ANYEVENT_RESOLV_CONF>
1918 2195
1919The file to use instead of F</etc/resolv.conf> (or OS-specific 2196The absolute path to a F<resolv.conf>-style file to use instead of
1920configuration) in the default resolver. When set to the empty string, no 2197F</etc/resolv.conf> (or the OS-specific configuration) in the default
1921default config will be used. 2198resolver, or the empty string to select the default configuration.
1922 2199
1923=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>. 2200=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
1924 2201
1925When neither C<ca_file> nor C<ca_path> was specified during 2202When neither C<ca_file> nor C<ca_path> was specified during
1926L<AnyEvent::TLS> context creation, and either of these environment 2203L<AnyEvent::TLS> context creation, and either of these environment
1927variables exist, they will be used to specify CA certificate locations 2204variables are nonempty, they will be used to specify CA certificate
1928instead of a system-dependent default. 2205locations instead of a system-dependent default.
1929 2206
1930=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT> 2207=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
1931 2208
1932When these are set to C<1>, then the respective modules are not 2209When these are set to C<1>, then the respective modules are not
1933loaded. Mostly good for testing AnyEvent itself. 2210loaded. Mostly good for testing AnyEvent itself.
2265(even when used without AnyEvent), but most event loops have acceptable 2542(even when used without AnyEvent), but most event loops have acceptable
2266performance with or without AnyEvent. 2543performance with or without AnyEvent.
2267 2544
2268=item * The overhead AnyEvent adds is usually much smaller than the overhead of 2545=item * The overhead AnyEvent adds is usually much smaller than the overhead of
2269the actual event loop, only with extremely fast event loops such as EV 2546the actual event loop, only with extremely fast event loops such as EV
2270adds AnyEvent significant overhead. 2547does AnyEvent add significant overhead.
2271 2548
2272=item * You should avoid POE like the plague if you want performance or 2549=item * You should avoid POE like the plague if you want performance or
2273reasonable memory usage. 2550reasonable memory usage.
2274 2551
2275=back 2552=back
2505 unless defined $SIG{PIPE}; 2782 unless defined $SIG{PIPE};
2506 2783
2507=head1 RECOMMENDED/OPTIONAL MODULES 2784=head1 RECOMMENDED/OPTIONAL MODULES
2508 2785
2509One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and 2786One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
2510it's built-in modules) are required to use it. 2787its built-in modules) are required to use it.
2511 2788
2512That does not mean that AnyEvent won't take advantage of some additional 2789That does not mean that AnyEvent won't take advantage of some additional
2513modules if they are installed. 2790modules if they are installed.
2514 2791
2515This section explains which additional modules will be used, and how they 2792This section explains which additional modules will be used, and how they
2573the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL. 2850the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
2574 2851
2575=item L<Time::HiRes> 2852=item L<Time::HiRes>
2576 2853
2577This module is part of perl since release 5.008. It will be used when the 2854This module is part of perl since release 5.008. It will be used when the
2578chosen event library does not come with a timing source on it's own. The 2855chosen event library does not come with a timing source of its own. The
2579pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to 2856pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
2580try to use a monotonic clock for timing stability. 2857try to use a monotonic clock for timing stability.
2581 2858
2582=back 2859=back
2583 2860
2584 2861
2646pronounced). 2923pronounced).
2647 2924
2648 2925
2649=head1 SEE ALSO 2926=head1 SEE ALSO
2650 2927
2651Utility functions: L<AnyEvent::Util>. 2928Tutorial/Introduction: L<AnyEvent::Intro>.
2652 2929
2653Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>, 2930FAQ: L<AnyEvent::FAQ>.
2654L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. 2931
2932Utility functions: L<AnyEvent::Util> (misc. grab-bag), L<AnyEvent::Log>
2933(simply logging).
2934
2935Development/Debugging: L<AnyEvent::Strict> (stricter checking),
2936L<AnyEvent::Debug> (interactive shell, watcher tracing).
2937
2938Supported event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>,
2939L<Glib::EV>, L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>,
2940L<Qt>, L<POE>, L<FLTK>.
2655 2941
2656Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>, 2942Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
2657L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, 2943L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
2658L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>, 2944L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
2659L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>. 2945L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>,
2946L<AnyEvent::Impl::FLTK>.
2660 2947
2661Non-blocking file handles, sockets, TCP clients and 2948Non-blocking handles, pipes, stream sockets, TCP clients and
2662servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>. 2949servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
2663 2950
2664Asynchronous DNS: L<AnyEvent::DNS>. 2951Asynchronous DNS: L<AnyEvent::DNS>.
2665 2952
2666Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, 2953Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
2667L<Coro::Event>,
2668 2954
2669Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>, 2955Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
2670L<AnyEvent::HTTP>. 2956L<AnyEvent::HTTP>.
2671 2957
2672 2958
2673=head1 AUTHOR 2959=head1 AUTHOR
2674 2960

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines