… | |
… | |
17 | }); |
17 | }); |
18 | |
18 | |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
20 | $w->send; # wake up current and all future recv's |
20 | $w->send; # wake up current and all future recv's |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
21 | $w->recv; # enters "main loop" till $condvar gets ->send |
|
|
22 | |
|
|
23 | =head1 INTRODUCTION/TUTORIAL |
|
|
24 | |
|
|
25 | This manpage is mainly a reference manual. If you are interested |
|
|
26 | in a tutorial or some gentle introduction, have a look at the |
|
|
27 | L<AnyEvent::Intro> manpage. |
22 | |
28 | |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
29 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
24 | |
30 | |
25 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
31 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
26 | nowadays. So what is different about AnyEvent? |
32 | nowadays. So what is different about AnyEvent? |
… | |
… | |
48 | isn't itself. What's worse, all the potential users of your module are |
54 | isn't itself. What's worse, all the potential users of your module are |
49 | I<also> forced to use the same event loop you use. |
55 | I<also> forced to use the same event loop you use. |
50 | |
56 | |
51 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
57 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
52 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
58 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
53 | with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if |
59 | with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if |
54 | your module uses one of those, every user of your module has to use it, |
60 | your module uses one of those, every user of your module has to use it, |
55 | too. But if your module uses AnyEvent, it works transparently with all |
61 | too. But if your module uses AnyEvent, it works transparently with all |
56 | event models it supports (including stuff like POE and IO::Async, as long |
62 | event models it supports (including stuff like POE and IO::Async, as long |
57 | as those use one of the supported event loops. It is trivial to add new |
63 | as those use one of the supported event loops. It is trivial to add new |
58 | event loops to AnyEvent, too, so it is future-proof). |
64 | event loops to AnyEvent, too, so it is future-proof). |
… | |
… | |
62 | modules, you get an enormous amount of code and strict rules you have to |
68 | modules, you get an enormous amount of code and strict rules you have to |
63 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
69 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
64 | offering the functionality that is necessary, in as thin as a wrapper as |
70 | offering the functionality that is necessary, in as thin as a wrapper as |
65 | technically possible. |
71 | technically possible. |
66 | |
72 | |
|
|
73 | Of course, AnyEvent comes with a big (and fully optional!) toolbox |
|
|
74 | of useful functionality, such as an asynchronous DNS resolver, 100% |
|
|
75 | non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms |
|
|
76 | such as Windows) and lots of real-world knowledge and workarounds for |
|
|
77 | platform bugs and differences. |
|
|
78 | |
67 | Of course, if you want lots of policy (this can arguably be somewhat |
79 | Now, if you I<do want> lots of policy (this can arguably be somewhat |
68 | useful) and you want to force your users to use the one and only event |
80 | useful) and you want to force your users to use the one and only event |
69 | model, you should I<not> use this module. |
81 | model, you should I<not> use this module. |
70 | |
82 | |
71 | =head1 DESCRIPTION |
83 | =head1 DESCRIPTION |
72 | |
84 | |
… | |
… | |
102 | starts using it, all bets are off. Maybe you should tell their authors to |
114 | starts using it, all bets are off. Maybe you should tell their authors to |
103 | use AnyEvent so their modules work together with others seamlessly... |
115 | use AnyEvent so their modules work together with others seamlessly... |
104 | |
116 | |
105 | The pure-perl implementation of AnyEvent is called |
117 | The pure-perl implementation of AnyEvent is called |
106 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
118 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
107 | explicitly. |
119 | explicitly and enjoy the high availability of that event loop :) |
108 | |
120 | |
109 | =head1 WATCHERS |
121 | =head1 WATCHERS |
110 | |
122 | |
111 | AnyEvent has the central concept of a I<watcher>, which is an object that |
123 | AnyEvent has the central concept of a I<watcher>, which is an object that |
112 | stores relevant data for each kind of event you are waiting for, such as |
124 | stores relevant data for each kind of event you are waiting for, such as |
… | |
… | |
226 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
238 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
227 | timers. |
239 | timers. |
228 | |
240 | |
229 | AnyEvent always prefers relative timers, if available, matching the |
241 | AnyEvent always prefers relative timers, if available, matching the |
230 | AnyEvent API. |
242 | AnyEvent API. |
|
|
243 | |
|
|
244 | AnyEvent has two additional methods that return the "current time": |
|
|
245 | |
|
|
246 | =over 4 |
|
|
247 | |
|
|
248 | =item AnyEvent->time |
|
|
249 | |
|
|
250 | This returns the "current wallclock time" as a fractional number of |
|
|
251 | seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time> |
|
|
252 | return, and the result is guaranteed to be compatible with those). |
|
|
253 | |
|
|
254 | It progresses independently of any event loop processing, i.e. each call |
|
|
255 | will check the system clock, which usually gets updated frequently. |
|
|
256 | |
|
|
257 | =item AnyEvent->now |
|
|
258 | |
|
|
259 | This also returns the "current wallclock time", but unlike C<time>, above, |
|
|
260 | this value might change only once per event loop iteration, depending on |
|
|
261 | the event loop (most return the same time as C<time>, above). This is the |
|
|
262 | time that AnyEvent's timers get scheduled against. |
|
|
263 | |
|
|
264 | I<In almost all cases (in all cases if you don't care), this is the |
|
|
265 | function to call when you want to know the current time.> |
|
|
266 | |
|
|
267 | This function is also often faster then C<< AnyEvent->time >>, and |
|
|
268 | thus the preferred method if you want some timestamp (for example, |
|
|
269 | L<AnyEvent::Handle> uses this to update it's activity timeouts). |
|
|
270 | |
|
|
271 | The rest of this section is only of relevance if you try to be very exact |
|
|
272 | with your timing, you can skip it without bad conscience. |
|
|
273 | |
|
|
274 | For a practical example of when these times differ, consider L<Event::Lib> |
|
|
275 | and L<EV> and the following set-up: |
|
|
276 | |
|
|
277 | The event loop is running and has just invoked one of your callback at |
|
|
278 | time=500 (assume no other callbacks delay processing). In your callback, |
|
|
279 | you wait a second by executing C<sleep 1> (blocking the process for a |
|
|
280 | second) and then (at time=501) you create a relative timer that fires |
|
|
281 | after three seconds. |
|
|
282 | |
|
|
283 | With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will |
|
|
284 | both return C<501>, because that is the current time, and the timer will |
|
|
285 | be scheduled to fire at time=504 (C<501> + C<3>). |
|
|
286 | |
|
|
287 | With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current |
|
|
288 | time), but C<< AnyEvent->now >> returns C<500>, as that is the time the |
|
|
289 | last event processing phase started. With L<EV>, your timer gets scheduled |
|
|
290 | to run at time=503 (C<500> + C<3>). |
|
|
291 | |
|
|
292 | In one sense, L<Event::Lib> is more exact, as it uses the current time |
|
|
293 | regardless of any delays introduced by event processing. However, most |
|
|
294 | callbacks do not expect large delays in processing, so this causes a |
|
|
295 | higher drift (and a lot more system calls to get the current time). |
|
|
296 | |
|
|
297 | In another sense, L<EV> is more exact, as your timer will be scheduled at |
|
|
298 | the same time, regardless of how long event processing actually took. |
|
|
299 | |
|
|
300 | In either case, if you care (and in most cases, you don't), then you |
|
|
301 | can get whatever behaviour you want with any event loop, by taking the |
|
|
302 | difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into |
|
|
303 | account. |
|
|
304 | |
|
|
305 | =back |
231 | |
306 | |
232 | =head2 SIGNAL WATCHERS |
307 | =head2 SIGNAL WATCHERS |
233 | |
308 | |
234 | You can watch for signals using a signal watcher, C<signal> is the signal |
309 | You can watch for signals using a signal watcher, C<signal> is the signal |
235 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
310 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
… | |
… | |
311 | >> method, usually without arguments. The only argument pair allowed is |
386 | >> method, usually without arguments. The only argument pair allowed is |
312 | C<cb>, which specifies a callback to be called when the condition variable |
387 | C<cb>, which specifies a callback to be called when the condition variable |
313 | becomes true. |
388 | becomes true. |
314 | |
389 | |
315 | After creation, the condition variable is "false" until it becomes "true" |
390 | After creation, the condition variable is "false" until it becomes "true" |
316 | by calling the C<send> method. |
391 | by calling the C<send> method (or calling the condition variable as if it |
|
|
392 | were a callback, read about the caveats in the description for the C<< |
|
|
393 | ->send >> method). |
317 | |
394 | |
318 | Condition variables are similar to callbacks, except that you can |
395 | Condition variables are similar to callbacks, except that you can |
319 | optionally wait for them. They can also be called merge points - points |
396 | optionally wait for them. They can also be called merge points - points |
320 | in time where multiple outstanding events have been processed. And yet |
397 | in time where multiple outstanding events have been processed. And yet |
321 | another way to call them is transactions - each condition variable can be |
398 | another way to call them is transactions - each condition variable can be |
… | |
… | |
347 | |
424 | |
348 | There are two "sides" to a condition variable - the "producer side" which |
425 | There are two "sides" to a condition variable - the "producer side" which |
349 | eventually calls C<< -> send >>, and the "consumer side", which waits |
426 | eventually calls C<< -> send >>, and the "consumer side", which waits |
350 | for the send to occur. |
427 | for the send to occur. |
351 | |
428 | |
352 | Example: |
429 | Example: wait for a timer. |
353 | |
430 | |
354 | # wait till the result is ready |
431 | # wait till the result is ready |
355 | my $result_ready = AnyEvent->condvar; |
432 | my $result_ready = AnyEvent->condvar; |
356 | |
433 | |
357 | # do something such as adding a timer |
434 | # do something such as adding a timer |
… | |
… | |
365 | |
442 | |
366 | # this "blocks" (while handling events) till the callback |
443 | # this "blocks" (while handling events) till the callback |
367 | # calls send |
444 | # calls send |
368 | $result_ready->recv; |
445 | $result_ready->recv; |
369 | |
446 | |
|
|
447 | Example: wait for a timer, but take advantage of the fact that |
|
|
448 | condition variables are also code references. |
|
|
449 | |
|
|
450 | my $done = AnyEvent->condvar; |
|
|
451 | my $delay = AnyEvent->timer (after => 5, cb => $done); |
|
|
452 | $done->recv; |
|
|
453 | |
370 | =head3 METHODS FOR PRODUCERS |
454 | =head3 METHODS FOR PRODUCERS |
371 | |
455 | |
372 | These methods should only be used by the producing side, i.e. the |
456 | These methods should only be used by the producing side, i.e. the |
373 | code/module that eventually sends the signal. Note that it is also |
457 | code/module that eventually sends the signal. Note that it is also |
374 | the producer side which creates the condvar in most cases, but it isn't |
458 | the producer side which creates the condvar in most cases, but it isn't |
… | |
… | |
385 | If a callback has been set on the condition variable, it is called |
469 | If a callback has been set on the condition variable, it is called |
386 | immediately from within send. |
470 | immediately from within send. |
387 | |
471 | |
388 | Any arguments passed to the C<send> call will be returned by all |
472 | Any arguments passed to the C<send> call will be returned by all |
389 | future C<< ->recv >> calls. |
473 | future C<< ->recv >> calls. |
|
|
474 | |
|
|
475 | Condition variables are overloaded so one can call them directly |
|
|
476 | (as a code reference). Calling them directly is the same as calling |
|
|
477 | C<send>. Note, however, that many C-based event loops do not handle |
|
|
478 | overloading, so as tempting as it may be, passing a condition variable |
|
|
479 | instead of a callback does not work. Both the pure perl and EV loops |
|
|
480 | support overloading, however, as well as all functions that use perl to |
|
|
481 | invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for |
|
|
482 | example). |
390 | |
483 | |
391 | =item $cv->croak ($error) |
484 | =item $cv->croak ($error) |
392 | |
485 | |
393 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
486 | Similar to send, but causes all call's to C<< ->recv >> to invoke |
394 | C<Carp::croak> with the given error message/object/scalar. |
487 | C<Carp::croak> with the given error message/object/scalar. |
… | |
… | |
504 | |
597 | |
505 | This is a mutator function that returns the callback set and optionally |
598 | This is a mutator function that returns the callback set and optionally |
506 | replaces it before doing so. |
599 | replaces it before doing so. |
507 | |
600 | |
508 | The callback will be called when the condition becomes "true", i.e. when |
601 | The callback will be called when the condition becomes "true", i.e. when |
509 | C<send> or C<croak> are called. Calling C<recv> inside the callback |
602 | C<send> or C<croak> are called, with the only argument being the condition |
510 | or at any later time is guaranteed not to block. |
603 | variable itself. Calling C<recv> inside the callback or at any later time |
|
|
604 | is guaranteed not to block. |
511 | |
605 | |
512 | =back |
606 | =back |
513 | |
607 | |
514 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
608 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
515 | |
609 | |
… | |
… | |
601 | |
695 | |
602 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
696 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
603 | do anything special (it does not need to be event-based) and let AnyEvent |
697 | do anything special (it does not need to be event-based) and let AnyEvent |
604 | decide which implementation to chose if some module relies on it. |
698 | decide which implementation to chose if some module relies on it. |
605 | |
699 | |
606 | If the main program relies on a specific event model. For example, in |
700 | If the main program relies on a specific event model - for example, in |
607 | Gtk2 programs you have to rely on the Glib module. You should load the |
701 | Gtk2 programs you have to rely on the Glib module - you should load the |
608 | event module before loading AnyEvent or any module that uses it: generally |
702 | event module before loading AnyEvent or any module that uses it: generally |
609 | speaking, you should load it as early as possible. The reason is that |
703 | speaking, you should load it as early as possible. The reason is that |
610 | modules might create watchers when they are loaded, and AnyEvent will |
704 | modules might create watchers when they are loaded, and AnyEvent will |
611 | decide on the event model to use as soon as it creates watchers, and it |
705 | decide on the event model to use as soon as it creates watchers, and it |
612 | might chose the wrong one unless you load the correct one yourself. |
706 | might chose the wrong one unless you load the correct one yourself. |
613 | |
707 | |
614 | You can chose to use a rather inefficient pure-perl implementation by |
708 | You can chose to use a pure-perl implementation by loading the |
615 | loading the C<AnyEvent::Impl::Perl> module, which gives you similar |
709 | C<AnyEvent::Impl::Perl> module, which gives you similar behaviour |
616 | behaviour everywhere, but letting AnyEvent chose is generally better. |
710 | everywhere, but letting AnyEvent chose the model is generally better. |
|
|
711 | |
|
|
712 | =head2 MAINLOOP EMULATION |
|
|
713 | |
|
|
714 | Sometimes (often for short test scripts, or even standalone programs who |
|
|
715 | only want to use AnyEvent), you do not want to run a specific event loop. |
|
|
716 | |
|
|
717 | In that case, you can use a condition variable like this: |
|
|
718 | |
|
|
719 | AnyEvent->condvar->recv; |
|
|
720 | |
|
|
721 | This has the effect of entering the event loop and looping forever. |
|
|
722 | |
|
|
723 | Note that usually your program has some exit condition, in which case |
|
|
724 | it is better to use the "traditional" approach of storing a condition |
|
|
725 | variable somewhere, waiting for it, and sending it when the program should |
|
|
726 | exit cleanly. |
|
|
727 | |
617 | |
728 | |
618 | =head1 OTHER MODULES |
729 | =head1 OTHER MODULES |
619 | |
730 | |
620 | The following is a non-exhaustive list of additional modules that use |
731 | The following is a non-exhaustive list of additional modules that use |
621 | AnyEvent and can therefore be mixed easily with other AnyEvent modules |
732 | AnyEvent and can therefore be mixed easily with other AnyEvent modules |
… | |
… | |
637 | |
748 | |
638 | Provides various utility functions for (internet protocol) sockets, |
749 | Provides various utility functions for (internet protocol) sockets, |
639 | addresses and name resolution. Also functions to create non-blocking tcp |
750 | addresses and name resolution. Also functions to create non-blocking tcp |
640 | connections or tcp servers, with IPv6 and SRV record support and more. |
751 | connections or tcp servers, with IPv6 and SRV record support and more. |
641 | |
752 | |
|
|
753 | =item L<AnyEvent::DNS> |
|
|
754 | |
|
|
755 | Provides rich asynchronous DNS resolver capabilities. |
|
|
756 | |
642 | =item L<AnyEvent::HTTPD> |
757 | =item L<AnyEvent::HTTPD> |
643 | |
758 | |
644 | Provides a simple web application server framework. |
759 | Provides a simple web application server framework. |
645 | |
|
|
646 | =item L<AnyEvent::DNS> |
|
|
647 | |
|
|
648 | Provides rich asynchronous DNS resolver capabilities. |
|
|
649 | |
760 | |
650 | =item L<AnyEvent::FastPing> |
761 | =item L<AnyEvent::FastPing> |
651 | |
762 | |
652 | The fastest ping in the west. |
763 | The fastest ping in the west. |
653 | |
764 | |
… | |
… | |
696 | no warnings; |
807 | no warnings; |
697 | use strict; |
808 | use strict; |
698 | |
809 | |
699 | use Carp; |
810 | use Carp; |
700 | |
811 | |
701 | our $VERSION = '4.0'; |
812 | our $VERSION = 4.11; |
702 | our $MODEL; |
813 | our $MODEL; |
703 | |
814 | |
704 | our $AUTOLOAD; |
815 | our $AUTOLOAD; |
705 | our @ISA; |
816 | our @ISA; |
706 | |
817 | |
|
|
818 | our @REGISTRY; |
|
|
819 | |
|
|
820 | our $WIN32; |
|
|
821 | |
|
|
822 | BEGIN { |
|
|
823 | my $win32 = ! ! ($^O =~ /mswin32/i); |
|
|
824 | eval "sub WIN32(){ $win32 }"; |
|
|
825 | } |
|
|
826 | |
707 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
827 | our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1; |
708 | |
828 | |
709 | our @REGISTRY; |
829 | our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred |
710 | |
|
|
711 | our %PROTOCOL; # (ipv4|ipv6) => (1|2) |
|
|
712 | |
830 | |
713 | { |
831 | { |
714 | my $idx; |
832 | my $idx; |
715 | $PROTOCOL{$_} = ++$idx |
833 | $PROTOCOL{$_} = ++$idx |
|
|
834 | for reverse split /\s*,\s*/, |
716 | for split /\s*,\s*/, $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
835 | $ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6"; |
717 | } |
836 | } |
718 | |
837 | |
719 | my @models = ( |
838 | my @models = ( |
720 | [EV:: => AnyEvent::Impl::EV::], |
839 | [EV:: => AnyEvent::Impl::EV::], |
721 | [Event:: => AnyEvent::Impl::Event::], |
840 | [Event:: => AnyEvent::Impl::Event::], |
722 | [Tk:: => AnyEvent::Impl::Tk::], |
|
|
723 | [Wx:: => AnyEvent::Impl::POE::], |
|
|
724 | [Prima:: => AnyEvent::Impl::POE::], |
|
|
725 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
841 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
726 | # everything below here will not be autoprobed as the pureperl backend should work everywhere |
842 | # everything below here will not be autoprobed |
727 | [Glib:: => AnyEvent::Impl::Glib::], |
843 | # as the pureperl backend should work everywhere |
|
|
844 | # and is usually faster |
|
|
845 | [Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles |
|
|
846 | [Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers |
728 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
847 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
729 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
848 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
730 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
849 | [POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza |
|
|
850 | [Wx:: => AnyEvent::Impl::POE::], |
|
|
851 | [Prima:: => AnyEvent::Impl::POE::], |
731 | ); |
852 | ); |
732 | |
853 | |
733 | our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY); |
854 | our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY); |
734 | |
855 | |
735 | our @post_detect; |
856 | our @post_detect; |
736 | |
857 | |
737 | sub post_detect(&) { |
858 | sub post_detect(&) { |
738 | my ($cb) = @_; |
859 | my ($cb) = @_; |
… | |
… | |
755 | } |
876 | } |
756 | |
877 | |
757 | sub detect() { |
878 | sub detect() { |
758 | unless ($MODEL) { |
879 | unless ($MODEL) { |
759 | no strict 'refs'; |
880 | no strict 'refs'; |
|
|
881 | local $SIG{__DIE__}; |
760 | |
882 | |
761 | if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { |
883 | if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { |
762 | my $model = "AnyEvent::Impl::$1"; |
884 | my $model = "AnyEvent::Impl::$1"; |
763 | if (eval "require $model") { |
885 | if (eval "require $model") { |
764 | $MODEL = $model; |
886 | $MODEL = $model; |
… | |
… | |
821 | $class->$func (@_); |
943 | $class->$func (@_); |
822 | } |
944 | } |
823 | |
945 | |
824 | package AnyEvent::Base; |
946 | package AnyEvent::Base; |
825 | |
947 | |
|
|
948 | # default implementation for now and time |
|
|
949 | |
|
|
950 | use Time::HiRes (); |
|
|
951 | |
|
|
952 | sub time { Time::HiRes::time } |
|
|
953 | sub now { Time::HiRes::time } |
|
|
954 | |
826 | # default implementation for ->condvar |
955 | # default implementation for ->condvar |
827 | |
956 | |
828 | sub condvar { |
957 | sub condvar { |
829 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
958 | bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar:: |
830 | } |
959 | } |
… | |
… | |
887 | or Carp::croak "required option 'pid' is missing"; |
1016 | or Carp::croak "required option 'pid' is missing"; |
888 | |
1017 | |
889 | $PID_CB{$pid}{$arg{cb}} = $arg{cb}; |
1018 | $PID_CB{$pid}{$arg{cb}} = $arg{cb}; |
890 | |
1019 | |
891 | unless ($WNOHANG) { |
1020 | unless ($WNOHANG) { |
892 | $WNOHANG = eval { require POSIX; &POSIX::WNOHANG } || 1; |
1021 | $WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1; |
893 | } |
1022 | } |
894 | |
1023 | |
895 | unless ($CHLD_W) { |
1024 | unless ($CHLD_W) { |
896 | $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); |
1025 | $CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld); |
897 | # child could be a zombie already, so make at least one round |
1026 | # child could be a zombie already, so make at least one round |
… | |
… | |
913 | package AnyEvent::CondVar; |
1042 | package AnyEvent::CondVar; |
914 | |
1043 | |
915 | our @ISA = AnyEvent::CondVar::Base::; |
1044 | our @ISA = AnyEvent::CondVar::Base::; |
916 | |
1045 | |
917 | package AnyEvent::CondVar::Base; |
1046 | package AnyEvent::CondVar::Base; |
|
|
1047 | |
|
|
1048 | use overload |
|
|
1049 | '&{}' => sub { my $self = shift; sub { $self->send (@_) } }, |
|
|
1050 | fallback => 1; |
918 | |
1051 | |
919 | sub _send { |
1052 | sub _send { |
920 | # nop |
1053 | # nop |
921 | } |
1054 | } |
922 | |
1055 | |
… | |
… | |
1072 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1205 | some (broken) firewalls drop such DNS packets, which is why it is off by |
1073 | default. |
1206 | default. |
1074 | |
1207 | |
1075 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1208 | Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce |
1076 | EDNS0 in its DNS requests. |
1209 | EDNS0 in its DNS requests. |
|
|
1210 | |
|
|
1211 | =item C<PERL_ANYEVENT_MAX_FORKS> |
|
|
1212 | |
|
|
1213 | The maximum number of child processes that C<AnyEvent::Util::fork_call> |
|
|
1214 | will create in parallel. |
1077 | |
1215 | |
1078 | =back |
1216 | =back |
1079 | |
1217 | |
1080 | =head1 EXAMPLE PROGRAM |
1218 | =head1 EXAMPLE PROGRAM |
1081 | |
1219 | |