ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.148 by root, Sat May 31 00:40:16 2008 UTC vs.
Revision 1.232 by root, Thu Jul 9 01:08:22 2009 UTC

1	=head1 => NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt and POE are various supported
		6	event loops.
6		7
7	=head1 SYNOPSIS	8	=head1 SYNOPSIS
8		9
9	use AnyEvent;	10	use AnyEvent;
10		11
		12	# file descriptor readable
11	my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub {	13	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
		14
		15	# one-shot or repeating timers
		16	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
		17	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
		18
		19	print AnyEvent->now; # prints current event loop time
		20	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
		21
		22	# POSIX signal
		23	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
		24
		25	# child process exit
		26	my $w = AnyEvent->child (pid => $pid, cb => sub {
		27	my ($pid, $status) = @_;
12	...	28	...
13	});	29	});
14		30
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	31	# called when event loop idle (if applicable)
16	...	32	my $w = AnyEvent->idle (cb => sub { ... });
17	});
18		33
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	34	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	35	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	36	$w->recv; # enters "main loop" till $condvar gets ->send
		37	# use a condvar in callback mode:
		38	$w->cb (sub { $_[0]->recv });
22		39
23	=head1 INTRODUCTION/TUTORIAL	40	=head1 INTRODUCTION/TUTORIAL
24		41
25	This manpage is mainly a reference manual. If you are interested	42	This manpage is mainly a reference manual. If you are interested
26	in a tutorial or some gentle introduction, have a look at the	43	in a tutorial or some gentle introduction, have a look at the
…		…
33		50
34	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	51	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
35	policy> and AnyEvent is I<small and efficient>.	52	policy> and AnyEvent is I<small and efficient>.
36		53
37	First and foremost, I<AnyEvent is not an event model> itself, it only	54	First and foremost, I<AnyEvent is not an event model> itself, it only
38	interfaces to whatever event model the main program happens to use in a	55	interfaces to whatever event model the main program happens to use, in a
39	pragmatic way. For event models and certain classes of immortals alike,	56	pragmatic way. For event models and certain classes of immortals alike,
40	the statement "there can only be one" is a bitter reality: In general,	57	the statement "there can only be one" is a bitter reality: In general,
41	only one event loop can be active at the same time in a process. AnyEvent	58	only one event loop can be active at the same time in a process. AnyEvent
42	helps hiding the differences between those event loops.	59	cannot change this, but it can hide the differences between those event
		60	loops.
43		61
44	The goal of AnyEvent is to offer module authors the ability to do event	62	The goal of AnyEvent is to offer module authors the ability to do event
45	programming (waiting for I/O or timer events) without subscribing to a	63	programming (waiting for I/O or timer events) without subscribing to a
46	religion, a way of living, and most importantly: without forcing your	64	religion, a way of living, and most importantly: without forcing your
47	module users into the same thing by forcing them to use the same event	65	module users into the same thing by forcing them to use the same event
48	model you use.	66	model you use.
49		67
50	For modules like POE or IO::Async (which is a total misnomer as it is	68	For modules like POE or IO::Async (which is a total misnomer as it is
51	actually doing all I/O I<synchronously>...), using them in your module is	69	actually doing all I/O I<synchronously>...), using them in your module is
52	like joining a cult: After you joined, you are dependent on them and you	70	like joining a cult: After you joined, you are dependent on them and you
53	cannot use anything else, as it is simply incompatible to everything that	71	cannot use anything else, as they are simply incompatible to everything
54	isn't itself. What's worse, all the potential users of your module are	72	that isn't them. What's worse, all the potential users of your
55	I<also> forced to use the same event loop you use.	73	module are I<also> forced to use the same event loop you use.
56		74
57	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	75	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
58	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	76	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
59	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if	77	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if
60	your module uses one of those, every user of your module has to use it,	78	your module uses one of those, every user of your module has to use it,
61	too. But if your module uses AnyEvent, it works transparently with all	79	too. But if your module uses AnyEvent, it works transparently with all
62	event models it supports (including stuff like POE and IO::Async, as long	80	event models it supports (including stuff like IO::Async, as long as those
63	as those use one of the supported event loops. It is trivial to add new	81	use one of the supported event loops. It is trivial to add new event loops
64	event loops to AnyEvent, too, so it is future-proof).	82	to AnyEvent, too, so it is future-proof).
65		83
66	In addition to being free of having to use I<the one and only true event	84	In addition to being free of having to use I<the one and only true event
67	model>, AnyEvent also is free of bloat and policy: with POE or similar	85	model>, AnyEvent also is free of bloat and policy: with POE or similar
68	modules, you get an enormous amount of code and strict rules you have to	86	modules, you get an enormous amount of code and strict rules you have to
69	follow. AnyEvent, on the other hand, is lean and up to the point, by only	87	follow. AnyEvent, on the other hand, is lean and up to the point, by only
…		…
127	These watchers are normal Perl objects with normal Perl lifetime. After	145	These watchers are normal Perl objects with normal Perl lifetime. After
128	creating a watcher it will immediately "watch" for events and invoke the	146	creating a watcher it will immediately "watch" for events and invoke the
129	callback when the event occurs (of course, only when the event model	147	callback when the event occurs (of course, only when the event model
130	is in control).	148	is in control).
131		149
		150	Note that B<callbacks must not permanently change global variables>
		151	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		152	callbacks must not C<die> >>. The former is good programming practise in
		153	Perl and the latter stems from the fact that exception handling differs
		154	widely between event loops.
		155
132	To disable the watcher you have to destroy it (e.g. by setting the	156	To disable the watcher you have to destroy it (e.g. by setting the
133	variable you store it in to C<undef> or otherwise deleting all references	157	variable you store it in to C<undef> or otherwise deleting all references
134	to it).	158	to it).
135		159
136	All watchers are created by calling a method on the C<AnyEvent> class.	160	All watchers are created by calling a method on the C<AnyEvent> class.
…		…
138	Many watchers either are used with "recursion" (repeating timers for	162	Many watchers either are used with "recursion" (repeating timers for
139	example), or need to refer to their watcher object in other ways.	163	example), or need to refer to their watcher object in other ways.
140		164
141	An any way to achieve that is this pattern:	165	An any way to achieve that is this pattern:
142		166
143	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	167	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
144	# you can use $w here, for example to undef it	168	# you can use $w here, for example to undef it
145	undef $w;	169	undef $w;
146	});	170	});
147		171
148	Note that C<my $w; $w => combination. This is necessary because in Perl,	172	Note that C<my $w; $w => combination. This is necessary because in Perl,
149	my variables are only visible after the statement in which they are	173	my variables are only visible after the statement in which they are
150	declared.	174	declared.
151		175
152	=head2 I/O WATCHERS	176	=head2 I/O WATCHERS
153		177
154	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	178	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
155	with the following mandatory key-value pairs as arguments:	179	with the following mandatory key-value pairs as arguments:
156		180
157	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	181	C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
		182	for events (AnyEvent might or might not keep a reference to this file
		183	handle). Note that only file handles pointing to things for which
		184	non-blocking operation makes sense are allowed. This includes sockets,
		185	most character devices, pipes, fifos and so on, but not for example files
		186	or block devices.
		187
158	for events. C<poll> must be a string that is either C<r> or C<w>,	188	C<poll> must be a string that is either C<r> or C<w>, which creates a
159	which creates a watcher waiting for "r"eadable or "w"ritable events,	189	watcher waiting for "r"eadable or "w"ritable events, respectively.
		190
160	respectively. C<cb> is the callback to invoke each time the file handle	191	C<cb> is the callback to invoke each time the file handle becomes ready.
161	becomes ready.
162		192
163	Although the callback might get passed parameters, their value and	193	Although the callback might get passed parameters, their value and
164	presence is undefined and you cannot rely on them. Portable AnyEvent	194	presence is undefined and you cannot rely on them. Portable AnyEvent
165	callbacks cannot use arguments passed to I/O watcher callbacks.	195	callbacks cannot use arguments passed to I/O watcher callbacks.
166		196
…		…
170		200
171	Some event loops issue spurious readyness notifications, so you should	201	Some event loops issue spurious readyness notifications, so you should
172	always use non-blocking calls when reading/writing from/to your file	202	always use non-blocking calls when reading/writing from/to your file
173	handles.	203	handles.
174		204
175	Example:
176
177	# wait for readability of STDIN, then read a line and disable the watcher	205	Example: wait for readability of STDIN, then read a line and disable the
		206	watcher.
		207
178	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	208	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
179	chomp (my $input = <STDIN>);	209	chomp (my $input = <STDIN>);
180	warn "read: $input\n";	210	warn "read: $input\n";
181	undef $w;	211	undef $w;
182	});	212	});
…		…
192		222
193	Although the callback might get passed parameters, their value and	223	Although the callback might get passed parameters, their value and
194	presence is undefined and you cannot rely on them. Portable AnyEvent	224	presence is undefined and you cannot rely on them. Portable AnyEvent
195	callbacks cannot use arguments passed to time watcher callbacks.	225	callbacks cannot use arguments passed to time watcher callbacks.
196		226
197	The timer callback will be invoked at most once: if you want a repeating	227	The callback will normally be invoked once only. If you specify another
198	timer you have to create a new watcher (this is a limitation by both Tk	228	parameter, C<interval>, as a strictly positive number (> 0), then the
199	and Glib).	229	callback will be invoked regularly at that interval (in fractional
		230	seconds) after the first invocation. If C<interval> is specified with a
		231	false value, then it is treated as if it were missing.
200		232
201	Example:	233	The callback will be rescheduled before invoking the callback, but no
		234	attempt is done to avoid timer drift in most backends, so the interval is
		235	only approximate.
202		236
203	# fire an event after 7.7 seconds	237	Example: fire an event after 7.7 seconds.
		238
204	my $w = AnyEvent->timer (after => 7.7, cb => sub {	239	my $w = AnyEvent->timer (after => 7.7, cb => sub {
205	warn "timeout\n";	240	warn "timeout\n";
206	});	241	});
207		242
208	# to cancel the timer:	243	# to cancel the timer:
209	undef $w;	244	undef $w;
210		245
211	Example 2:
212
213	# fire an event after 0.5 seconds, then roughly every second	246	Example 2: fire an event after 0.5 seconds, then roughly every second.
214	my $w;
215		247
216	my $cb = sub {
217	# cancel the old timer while creating a new one
218	$w = AnyEvent->timer (after => 1, cb => $cb);	248	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
		249	warn "timeout\n";
219	};	250	};
220
221	# start the "loop" by creating the first watcher
222	$w = AnyEvent->timer (after => 0.5, cb => $cb);
223		251
224	=head3 TIMING ISSUES	252	=head3 TIMING ISSUES
225		253
226	There are two ways to handle timers: based on real time (relative, "fire	254	There are two ways to handle timers: based on real time (relative, "fire
227	in 10 seconds") and based on wallclock time (absolute, "fire at 12	255	in 10 seconds") and based on wallclock time (absolute, "fire at 12
…		…
300	In either case, if you care (and in most cases, you don't), then you	328	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	329	can get whatever behaviour you want with any event loop, by taking the
302	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into	330	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
303	account.	331	account.
304		332
		333	=item AnyEvent->now_update
		334
		335	Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache
		336	the current time for each loop iteration (see the discussion of L<<
		337	AnyEvent->now >>, above).
		338
		339	When a callback runs for a long time (or when the process sleeps), then
		340	this "current" time will differ substantially from the real time, which
		341	might affect timers and time-outs.
		342
		343	When this is the case, you can call this method, which will update the
		344	event loop's idea of "current time".
		345
		346	Note that updating the time I<might> cause some events to be handled.
		347
305	=back	348	=back
306		349
307	=head2 SIGNAL WATCHERS	350	=head2 SIGNAL WATCHERS
308		351
309	You can watch for signals using a signal watcher, C<signal> is the signal	352	You can watch for signals using a signal watcher, C<signal> is the signal
310	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	353	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
311	be invoked whenever a signal occurs.	354	callback to be invoked whenever a signal occurs.
312		355
313	Although the callback might get passed parameters, their value and	356	Although the callback might get passed parameters, their value and
314	presence is undefined and you cannot rely on them. Portable AnyEvent	357	presence is undefined and you cannot rely on them. Portable AnyEvent
315	callbacks cannot use arguments passed to signal watcher callbacks.	358	callbacks cannot use arguments passed to signal watcher callbacks.
316		359
…		…
332	=head2 CHILD PROCESS WATCHERS	375	=head2 CHILD PROCESS WATCHERS
333		376
334	You can also watch on a child process exit and catch its exit status.	377	You can also watch on a child process exit and catch its exit status.
335		378
336	The child process is specified by the C<pid> argument (if set to C<0>, it	379	The child process is specified by the C<pid> argument (if set to C<0>, it
337	watches for any child process exit). The watcher will trigger as often	380	watches for any child process exit). The watcher will triggered only when
338	as status change for the child are received. This works by installing a	381	the child process has finished and an exit status is available, not on
339	signal handler for C<SIGCHLD>. The callback will be called with the pid	382	any trace events (stopped/continued).
340	and exit status (as returned by waitpid), so unlike other watcher types,	383
341	you I<can> rely on child watcher callback arguments.	384	The callback will be called with the pid and exit status (as returned by
		385	waitpid), so unlike other watcher types, you I<can> rely on child watcher
		386	callback arguments.
		387
		388	This watcher type works by installing a signal handler for C<SIGCHLD>,
		389	and since it cannot be shared, nothing else should use SIGCHLD or reap
		390	random child processes (waiting for specific child processes, e.g. inside
		391	C<system>, is just fine).
342		392
343	There is a slight catch to child watchers, however: you usually start them	393	There is a slight catch to child watchers, however: you usually start them
344	I<after> the child process was created, and this means the process could	394	I<after> the child process was created, and this means the process could
345	have exited already (and no SIGCHLD will be sent anymore).	395	have exited already (and no SIGCHLD will be sent anymore).
346		396
347	Not all event models handle this correctly (POE doesn't), but even for	397	Not all event models handle this correctly (neither POE nor IO::Async do,
		398	see their AnyEvent::Impl manpages for details), but even for event models
348	event models that I<do> handle this correctly, they usually need to be	399	that I<do> handle this correctly, they usually need to be loaded before
349	loaded before the process exits (i.e. before you fork in the first place).	400	the process exits (i.e. before you fork in the first place). AnyEvent's
		401	pure perl event loop handles all cases correctly regardless of when you
		402	start the watcher.
350		403
351	This means you cannot create a child watcher as the very first thing in an	404	This means you cannot create a child watcher as the very first
352	AnyEvent program, you I<have> to create at least one watcher before you	405	thing in an AnyEvent program, you I<have> to create at least one
353	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	406	watcher before you C<fork> the child (alternatively, you can call
		407	C<AnyEvent::detect>).
354		408
355	Example: fork a process and wait for it	409	Example: fork a process and wait for it
356		410
357	my $done = AnyEvent->condvar;	411	my $done = AnyEvent->condvar;
358		412
359	my $pid = fork or exit 5;	413	my $pid = fork or exit 5;
360		414
361	my $w = AnyEvent->child (	415	my $w = AnyEvent->child (
362	pid => $pid,	416	pid => $pid,
363	cb => sub {	417	cb => sub {
364	my ($pid, $status) = @_;	418	my ($pid, $status) = @_;
365	warn "pid $pid exited with status $status";	419	warn "pid $pid exited with status $status";
366	$done->send;	420	$done->send;
367	},	421	},
368	);	422	);
369		423
370	# do something else, then wait for process exit	424	# do something else, then wait for process exit
371	$done->recv;	425	$done->recv;
		426
		427	=head2 IDLE WATCHERS
		428
		429	Sometimes there is a need to do something, but it is not so important
		430	to do it instantly, but only when there is nothing better to do. This
		431	"nothing better to do" is usually defined to be "no other events need
		432	attention by the event loop".
		433
		434	Idle watchers ideally get invoked when the event loop has nothing
		435	better to do, just before it would block the process to wait for new
		436	events. Instead of blocking, the idle watcher is invoked.
		437
		438	Most event loops unfortunately do not really support idle watchers (only
		439	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
		440	will simply call the callback "from time to time".
		441
		442	Example: read lines from STDIN, but only process them when the
		443	program is otherwise idle:
		444
		445	my @lines; # read data
		446	my $idle_w;
		447	my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
		448	push @lines, scalar <STDIN>;
		449
		450	# start an idle watcher, if not already done
		451	$idle_w ||= AnyEvent->idle (cb => sub {
		452	# handle only one line, when there are lines left
		453	if (my $line = shift @lines) {
		454	print "handled when idle: $line";
		455	} else {
		456	# otherwise disable the idle watcher again
		457	undef $idle_w;
		458	}
		459	});
		460	});
372		461
373	=head2 CONDITION VARIABLES	462	=head2 CONDITION VARIABLES
374		463
375	If you are familiar with some event loops you will know that all of them	464	If you are familiar with some event loops you will know that all of them
376	require you to run some blocking "loop", "run" or similar function that	465	require you to run some blocking "loop", "run" or similar function that
…		…
382	The instrument to do that is called a "condition variable", so called	471	The instrument to do that is called a "condition variable", so called
383	because they represent a condition that must become true.	472	because they represent a condition that must become true.
384		473
385	Condition variables can be created by calling the C<< AnyEvent->condvar	474	Condition variables can be created by calling the C<< AnyEvent->condvar
386	>> method, usually without arguments. The only argument pair allowed is	475	>> method, usually without arguments. The only argument pair allowed is
		476
387	C<cb>, which specifies a callback to be called when the condition variable	477	C<cb>, which specifies a callback to be called when the condition variable
388	becomes true.	478	becomes true, with the condition variable as the first argument (but not
		479	the results).
389		480
390	After creation, the condition variable is "false" until it becomes "true"	481	After creation, the condition variable is "false" until it becomes "true"
391	by calling the C<send> method (or calling the condition variable as if it	482	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<<	483	were a callback, read about the caveats in the description for the C<<
393	->send >> method).	484	->send >> method).
…		…
449		540
450	my $done = AnyEvent->condvar;	541	my $done = AnyEvent->condvar;
451	my $delay = AnyEvent->timer (after => 5, cb => $done);	542	my $delay = AnyEvent->timer (after => 5, cb => $done);
452	$done->recv;	543	$done->recv;
453		544
		545	Example: Imagine an API that returns a condvar and doesn't support
		546	callbacks. This is how you make a synchronous call, for example from
		547	the main program:
		548
		549	use AnyEvent::CouchDB;
		550
		551	...
		552
		553	my @info = $couchdb->info->recv;
		554
		555	And this is how you would just ste a callback to be called whenever the
		556	results are available:
		557
		558	$couchdb->info->cb (sub {
		559	my @info = $_[0]->recv;
		560	});
		561
454	=head3 METHODS FOR PRODUCERS	562	=head3 METHODS FOR PRODUCERS
455		563
456	These methods should only be used by the producing side, i.e. the	564	These methods should only be used by the producing side, i.e. the
457	code/module that eventually sends the signal. Note that it is also	565	code/module that eventually sends the signal. Note that it is also
458	the producer side which creates the condvar in most cases, but it isn't	566	the producer side which creates the condvar in most cases, but it isn't
…		…
491		599
492	=item $cv->begin ([group callback])	600	=item $cv->begin ([group callback])
493		601
494	=item $cv->end	602	=item $cv->end
495		603
496	These two methods are EXPERIMENTAL and MIGHT CHANGE.
497
498	These two methods can be used to combine many transactions/events into	604	These two methods can be used to combine many transactions/events into
499	one. For example, a function that pings many hosts in parallel might want	605	one. For example, a function that pings many hosts in parallel might want
500	to use a condition variable for the whole process.	606	to use a condition variable for the whole process.
501		607
502	Every call to C<< ->begin >> will increment a counter, and every call to	608	Every call to C<< ->begin >> will increment a counter, and every call to
503	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end	609	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
504	>>, the (last) callback passed to C<begin> will be executed. That callback	610	>>, the (last) callback passed to C<begin> will be executed. That callback
505	is I<supposed> to call C<< ->send >>, but that is not required. If no	611	is I<supposed> to call C<< ->send >>, but that is not required. If no
506	callback was set, C<send> will be called without any arguments.	612	callback was set, C<send> will be called without any arguments.
507		613
508	Let's clarify this with the ping example:	614	You can think of C<< $cv->send >> giving you an OR condition (one call
		615	sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
		616	condition (all C<begin> calls must be C<end>'ed before the condvar sends).
		617
		618	Let's start with a simple example: you have two I/O watchers (for example,
		619	STDOUT and STDERR for a program), and you want to wait for both streams to
		620	close before activating a condvar:
		621
		622	my $cv = AnyEvent->condvar;
		623
		624	$cv->begin; # first watcher
		625	my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
		626	defined sysread $fh1, my $buf, 4096
		627	or $cv->end;
		628	});
		629
		630	$cv->begin; # second watcher
		631	my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
		632	defined sysread $fh2, my $buf, 4096
		633	or $cv->end;
		634	});
		635
		636	$cv->recv;
		637
		638	This works because for every event source (EOF on file handle), there is
		639	one call to C<begin>, so the condvar waits for all calls to C<end> before
		640	sending.
		641
		642	The ping example mentioned above is slightly more complicated, as the
		643	there are results to be passwd back, and the number of tasks that are
		644	begung can potentially be zero:
509		645
510	my $cv = AnyEvent->condvar;	646	my $cv = AnyEvent->condvar;
511		647
512	my %result;	648	my %result;
513	$cv->begin (sub { $cv->send (\%result) });	649	$cv->begin (sub { $cv->send (\%result) });
…		…
533	loop, which serves two important purposes: first, it sets the callback	669	loop, which serves two important purposes: first, it sets the callback
534	to be called once the counter reaches C<0>, and second, it ensures that	670	to be called once the counter reaches C<0>, and second, it ensures that
535	C<send> is called even when C<no> hosts are being pinged (the loop	671	C<send> is called even when C<no> hosts are being pinged (the loop
536	doesn't execute once).	672	doesn't execute once).
537		673
538	This is the general pattern when you "fan out" into multiple subrequests:	674	This is the general pattern when you "fan out" into multiple (but
539	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>	675	potentially none) subrequests: use an outer C<begin>/C<end> pair to set
540	is called at least once, and then, for each subrequest you start, call	676	the callback and ensure C<end> is called at least once, and then, for each
541	C<begin> and for each subrequest you finish, call C<end>.	677	subrequest you start, call C<begin> and for each subrequest you finish,
		678	call C<end>.
542		679
543	=back	680	=back
544		681
545	=head3 METHODS FOR CONSUMERS	682	=head3 METHODS FOR CONSUMERS
546		683
…		…
591	=item $bool = $cv->ready	728	=item $bool = $cv->ready
592		729
593	Returns true when the condition is "true", i.e. whether C<send> or	730	Returns true when the condition is "true", i.e. whether C<send> or
594	C<croak> have been called.	731	C<croak> have been called.
595		732
596	=item $cb = $cv->cb ([new callback])	733	=item $cb = $cv->cb ($cb->($cv))
597		734
598	This is a mutator function that returns the callback set and optionally	735	This is a mutator function that returns the callback set and optionally
599	replaces it before doing so.	736	replaces it before doing so.
600		737
601	The callback will be called when the condition becomes "true", i.e. when	738	The callback will be called when the condition becomes "true", i.e. when
602	C<send> or C<croak> are called. Calling C<recv> inside the callback	739	C<send> or C<croak> are called, with the only argument being the condition
603	or at any later time is guaranteed not to block.	740	variable itself. Calling C<recv> inside the callback or at any later time
		741	is guaranteed not to block.
		742
		743	=back
		744
		745	=head1 SUPPORTED EVENT LOOPS/BACKENDS
		746
		747	The available backend classes are (every class has its own manpage):
		748
		749	=over 4
		750
		751	=item Backends that are autoprobed when no other event loop can be found.
		752
		753	EV is the preferred backend when no other event loop seems to be in
		754	use. If EV is not installed, then AnyEvent will try Event, and, failing
		755	that, will fall back to its own pure-perl implementation, which is
		756	available everywhere as it comes with AnyEvent itself.
		757
		758	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
		759	AnyEvent::Impl::Event based on Event, very stable, few glitches.
		760	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
		761
		762	=item Backends that are transparently being picked up when they are used.
		763
		764	These will be used when they are currently loaded when the first watcher
		765	is created, in which case it is assumed that the application is using
		766	them. This means that AnyEvent will automatically pick the right backend
		767	when the main program loads an event module before anything starts to
		768	create watchers. Nothing special needs to be done by the main program.
		769
		770	AnyEvent::Impl::Glib based on Glib, slow but very stable.
		771	AnyEvent::Impl::Tk based on Tk, very broken.
		772	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		773	AnyEvent::Impl::POE based on POE, very slow, some limitations.
		774
		775	=item Backends with special needs.
		776
		777	Qt requires the Qt::Application to be instantiated first, but will
		778	otherwise be picked up automatically. As long as the main program
		779	instantiates the application before any AnyEvent watchers are created,
		780	everything should just work.
		781
		782	AnyEvent::Impl::Qt based on Qt.
		783
		784	Support for IO::Async can only be partial, as it is too broken and
		785	architecturally limited to even support the AnyEvent API. It also
		786	is the only event loop that needs the loop to be set explicitly, so
		787	it can only be used by a main program knowing about AnyEvent. See
		788	L<AnyEvent::Impl::Async> for the gory details.
		789
		790	AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
		791
		792	=item Event loops that are indirectly supported via other backends.
		793
		794	Some event loops can be supported via other modules:
		795
		796	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		797
		798	B<WxWidgets> has no support for watching file handles. However, you can
		799	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		800	polls 20 times per second, which was considered to be too horrible to even
		801	consider for AnyEvent.
		802
		803	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		804	backend, so it can be supported through POE.
		805
		806	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		807	load L<POE> when detecting them, in the hope that POE will pick them up,
		808	in which case everything will be automatic.
604		809
605	=back	810	=back
606		811
607	=head1 GLOBAL VARIABLES AND FUNCTIONS	812	=head1 GLOBAL VARIABLES AND FUNCTIONS
608		813
…		…
613	Contains C<undef> until the first watcher is being created. Then it	818	Contains C<undef> until the first watcher is being created. Then it
614	contains the event model that is being used, which is the name of the	819	contains the event model that is being used, which is the name of the
615	Perl class implementing the model. This class is usually one of the	820	Perl class implementing the model. This class is usually one of the
616	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	821	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
617	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	822	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
618
619	The known classes so far are:
620
621	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
622	AnyEvent::Impl::Event based on Event, second best choice.
623	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
624	AnyEvent::Impl::Glib based on Glib, third-best choice.
625	AnyEvent::Impl::Tk based on Tk, very bad choice.
626	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
627	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
628	AnyEvent::Impl::POE based on POE, not generic enough for full support.
629
630	There is no support for WxWidgets, as WxWidgets has no support for
631	watching file handles. However, you can use WxWidgets through the
632	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
633	second, which was considered to be too horrible to even consider for
634	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
635	it's adaptor.
636
637	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
638	autodetecting them.
639		823
640	=item AnyEvent::detect	824	=item AnyEvent::detect
641		825
642	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	826	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
643	if necessary. You should only call this function right before you would	827	if necessary. You should only call this function right before you would
…		…
726		910
727		911
728	=head1 OTHER MODULES	912	=head1 OTHER MODULES
729		913
730	The following is a non-exhaustive list of additional modules that use	914	The following is a non-exhaustive list of additional modules that use
731	AnyEvent and can therefore be mixed easily with other AnyEvent modules	915	AnyEvent as a client and can therefore be mixed easily with other AnyEvent
732	in the same program. Some of the modules come with AnyEvent, some are	916	modules and other event loops in the same program. Some of the modules
733	available via CPAN.	917	come with AnyEvent, most are available via CPAN.
734		918
735	=over 4	919	=over 4
736		920
737	=item L<AnyEvent::Util>	921	=item L<AnyEvent::Util>
738		922
739	Contains various utility functions that replace often-used but blocking	923	Contains various utility functions that replace often-used but blocking
740	functions such as C<inet_aton> by event-/callback-based versions.	924	functions such as C<inet_aton> by event-/callback-based versions.
741
742	=item L<AnyEvent::Handle>
743
744	Provide read and write buffers and manages watchers for reads and writes.
745		925
746	=item L<AnyEvent::Socket>	926	=item L<AnyEvent::Socket>
747		927
748	Provides various utility functions for (internet protocol) sockets,	928	Provides various utility functions for (internet protocol) sockets,
749	addresses and name resolution. Also functions to create non-blocking tcp	929	addresses and name resolution. Also functions to create non-blocking tcp
750	connections or tcp servers, with IPv6 and SRV record support and more.	930	connections or tcp servers, with IPv6 and SRV record support and more.
751		931
		932	=item L<AnyEvent::Handle>
		933
		934	Provide read and write buffers, manages watchers for reads and writes,
		935	supports raw and formatted I/O, I/O queued and fully transparent and
		936	non-blocking SSL/TLS (via L<AnyEvent::TLS>.
		937
752	=item L<AnyEvent::DNS>	938	=item L<AnyEvent::DNS>
753		939
754	Provides rich asynchronous DNS resolver capabilities.	940	Provides rich asynchronous DNS resolver capabilities.
755		941
		942	=item L<AnyEvent::HTTP>
		943
		944	A simple-to-use HTTP library that is capable of making a lot of concurrent
		945	HTTP requests.
		946
756	=item L<AnyEvent::HTTPD>	947	=item L<AnyEvent::HTTPD>
757		948
758	Provides a simple web application server framework.	949	Provides a simple web application server framework.
759		950
760	=item L<AnyEvent::FastPing>	951	=item L<AnyEvent::FastPing>
761		952
762	The fastest ping in the west.	953	The fastest ping in the west.
763		954
		955	=item L<AnyEvent::DBI>
		956
		957	Executes L<DBI> requests asynchronously in a proxy process.
		958
		959	=item L<AnyEvent::AIO>
		960
		961	Truly asynchronous I/O, should be in the toolbox of every event
		962	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
		963	together.
		964
		965	=item L<AnyEvent::BDB>
		966
		967	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
		968	L<BDB> and AnyEvent together.
		969
		970	=item L<AnyEvent::GPSD>
		971
		972	A non-blocking interface to gpsd, a daemon delivering GPS information.
		973
764	=item L<Net::IRC3>	974	=item L<AnyEvent::IRC>
765		975
766	AnyEvent based IRC client module family.	976	AnyEvent based IRC client module family (replacing the older Net::IRC3).
767		977
768	=item L<Net::XMPP2>	978	=item L<AnyEvent::XMPP>
769		979
770	AnyEvent based XMPP (Jabber protocol) module family.	980	AnyEvent based XMPP (Jabber protocol) module family (replacing the older
		981	Net::XMPP2>.
		982
		983	=item L<AnyEvent::IGS>
		984
		985	A non-blocking interface to the Internet Go Server protocol (used by
		986	L<App::IGS>).
771		987
772	=item L<Net::FCP>	988	=item L<Net::FCP>
773		989
774	AnyEvent-based implementation of the Freenet Client Protocol, birthplace	990	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
775	of AnyEvent.	991	of AnyEvent.
…		…
780		996
781	=item L<Coro>	997	=item L<Coro>
782		998
783	Has special support for AnyEvent via L<Coro::AnyEvent>.	999	Has special support for AnyEvent via L<Coro::AnyEvent>.
784		1000
785	=item L<AnyEvent::AIO>, L<IO::AIO>
786
787	Truly asynchronous I/O, should be in the toolbox of every event
788	programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
789	together.
790
791	=item L<AnyEvent::BDB>, L<BDB>
792
793	Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
794	IO::AIO and AnyEvent together.
795
796	=item L<IO::Lambda>
797
798	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
799
800	=back	1001	=back
801		1002
802	=cut	1003	=cut
803		1004
804	package AnyEvent;	1005	package AnyEvent;
805		1006
806	no warnings;	1007	no warnings;
807	use strict;	1008	use strict qw(vars subs);
808		1009
809	use Carp;	1010	use Carp;
810		1011
811	our $VERSION = 4.11;	1012	our $VERSION = 4.801;
812	our $MODEL;	1013	our $MODEL;
813		1014
814	our $AUTOLOAD;	1015	our $AUTOLOAD;
815	our @ISA;	1016	our @ISA;
816		1017
817	our @REGISTRY;	1018	our @REGISTRY;
818		1019
819	our $WIN32;	1020	our $WIN32;
820		1021
821	BEGIN {	1022	BEGIN {
822	my $win32 = ! ! ($^O =~ /mswin32/i);	1023	eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
823	eval "sub WIN32(){ $win32 }";	1024	eval "sub TAINT(){ " . (${^TAINT}*1) . " }";
		1025
		1026	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1027	if ${^TAINT};
824	}	1028	}
825		1029
826	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1030	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
827		1031
828	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1032	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
…		…
839	[Event:: => AnyEvent::Impl::Event::],	1043	[Event:: => AnyEvent::Impl::Event::],
840	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	1044	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
841	# everything below here will not be autoprobed	1045	# everything below here will not be autoprobed
842	# as the pureperl backend should work everywhere	1046	# as the pureperl backend should work everywhere
843	# and is usually faster	1047	# and is usually faster
844	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
845	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers	1048	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
846	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy	1049	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		1050	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
		1051	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
847	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1052	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
848	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
849	[Wx:: => AnyEvent::Impl::POE::],	1053	[Wx:: => AnyEvent::Impl::POE::],
850	[Prima:: => AnyEvent::Impl::POE::],	1054	[Prima:: => AnyEvent::Impl::POE::],
		1055	# IO::Async is just too broken - we would need workarounds for its
		1056	# byzantine signal and broken child handling, among others.
		1057	# IO::Async is rather hard to detect, as it doesn't have any
		1058	# obvious default class.
		1059	# [IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
		1060	# [IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
		1061	# [IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
851	);	1062	);
852		1063
853	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);	1064	our %method = map +($_ => 1),
		1065	qw(io timer time now now_update signal child idle condvar one_event DESTROY);
854		1066
855	our @post_detect;	1067	our @post_detect;
856		1068
857	sub post_detect(&) {	1069	sub post_detect(&) {
858	my ($cb) = @_;	1070	my ($cb) = @_;
…		…
863	1	1075	1
864	} else {	1076	} else {
865	push @post_detect, $cb;	1077	push @post_detect, $cb;
866		1078
867	defined wantarray	1079	defined wantarray
868	? bless \$cb, "AnyEvent::Util::PostDetect"	1080	? bless \$cb, "AnyEvent::Util::postdetect"
869	: ()	1081	: ()
870	}	1082	}
871	}	1083	}
872		1084
873	sub AnyEvent::Util::PostDetect::DESTROY {	1085	sub AnyEvent::Util::postdetect::DESTROY {
874	@post_detect = grep $_ != ${$_[0]}, @post_detect;	1086	@post_detect = grep $_ != ${$_[0]}, @post_detect;
875	}	1087	}
876		1088
877	sub detect() {	1089	sub detect() {
878	unless ($MODEL) {	1090	unless ($MODEL) {
…		…
915	last;	1127	last;
916	}	1128	}
917	}	1129	}
918		1130
919	$MODEL	1131	$MODEL
920	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	1132	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n";
921	}	1133	}
922	}	1134	}
923		1135
		1136	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1137
924	unshift @ISA, $MODEL;	1138	unshift @ISA, $MODEL;
925	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	1139
		1140	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
926		1141
927	(shift @post_detect)->() while @post_detect;	1142	(shift @post_detect)->() while @post_detect;
928	}	1143	}
929		1144
930	$MODEL	1145	$MODEL
…		…
940		1155
941	my $class = shift;	1156	my $class = shift;
942	$class->$func (@_);	1157	$class->$func (@_);
943	}	1158	}
944		1159
		1160	# utility function to dup a filehandle. this is used by many backends
		1161	# to support binding more than one watcher per filehandle (they usually
		1162	# allow only one watcher per fd, so we dup it to get a different one).
		1163	sub _dupfh($$;$$) {
		1164	my ($poll, $fh, $r, $w) = @_;
		1165
		1166	# cygwin requires the fh mode to be matching, unix doesn't
		1167	my ($rw, $mode) = $poll eq "r" ? ($r, "<") : ($w, ">");
		1168
		1169	open my $fh2, "$mode&", $fh
		1170	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
		1171
		1172	# we assume CLOEXEC is already set by perl in all important cases
		1173
		1174	($fh2, $rw)
		1175	}
		1176
945	package AnyEvent::Base;	1177	package AnyEvent::Base;
946		1178
947	# default implementation for now and time	1179	# default implementations for many methods
948		1180
949	use Time::HiRes ();	1181	BEGIN {
		1182	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1183	*_time = \&Time::HiRes::time;
		1184	# if (eval "use POSIX (); (POSIX::times())...
		1185	} else {
		1186	*_time = sub { time }; # epic fail
		1187	}
		1188	}
950		1189
951	sub time { Time::HiRes::time }	1190	sub time { _time }
952	sub now { Time::HiRes::time }	1191	sub now { _time }
		1192	sub now_update { }
953		1193
954	# default implementation for ->condvar	1194	# default implementation for ->condvar
955		1195
956	sub condvar {	1196	sub condvar {
957	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1197	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
958	}	1198	}
959		1199
960	# default implementation for ->signal	1200	# default implementation for ->signal
961		1201
962	our %SIG_CB;	1202	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1203
		1204	sub _signal_exec {
		1205	sysread $SIGPIPE_R, my $dummy, 4;
		1206
		1207	while (%SIG_EV) {
		1208	for (keys %SIG_EV) {
		1209	delete $SIG_EV{$_};
		1210	$_->() for values %{ $SIG_CB{$_} || {} };
		1211	}
		1212	}
		1213	}
963		1214
964	sub signal {	1215	sub signal {
965	my (undef, %arg) = @_;	1216	my (undef, %arg) = @_;
966		1217
		1218	unless ($SIGPIPE_R) {
		1219	require Fcntl;
		1220
		1221	if (AnyEvent::WIN32) {
		1222	require AnyEvent::Util;
		1223
		1224	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1225	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R) if $SIGPIPE_R;
		1226	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W) if $SIGPIPE_W; # just in case
		1227	} else {
		1228	pipe $SIGPIPE_R, $SIGPIPE_W;
		1229	fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;
		1230	fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case
		1231
		1232	# not strictly required, as $^F is normally 2, but let's make sure...
		1233	fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
		1234	fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
		1235	}
		1236
		1237	$SIGPIPE_R
		1238	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1239
		1240	$SIG_IO = AnyEvent->io (fh => $SIGPIPE_R, poll => "r", cb => \&_signal_exec);
		1241	}
		1242
967	my $signal = uc $arg{signal}	1243	my $signal = uc $arg{signal}
968	or Carp::croak "required option 'signal' is missing";	1244	or Carp::croak "required option 'signal' is missing";
969		1245
970	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1246	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
971	$SIG{$signal} ||= sub {	1247	$SIG{$signal} ||= sub {
972	$_->() for values %{ $SIG_CB{$signal} || {} };	1248	local $!;
		1249	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1250	undef $SIG_EV{$signal};
973	};	1251	};
974		1252
975	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1253	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
976	}	1254	}
977		1255
978	sub AnyEvent::Base::Signal::DESTROY {	1256	sub AnyEvent::Base::signal::DESTROY {
979	my ($signal, $cb) = @{$_[0]};	1257	my ($signal, $cb) = @{$_[0]};
980		1258
981	delete $SIG_CB{$signal}{$cb};	1259	delete $SIG_CB{$signal}{$cb};
982		1260
		1261	# delete doesn't work with older perls - they then
		1262	# print weird messages, or just unconditionally exit
		1263	# instead of getting the default action.
983	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1264	undef $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
984	}	1265	}
985		1266
986	# default implementation for ->child	1267	# default implementation for ->child
987		1268
988	our %PID_CB;	1269	our %PID_CB;
989	our $CHLD_W;	1270	our $CHLD_W;
990	our $CHLD_DELAY_W;	1271	our $CHLD_DELAY_W;
991	our $PID_IDLE;
992	our $WNOHANG;	1272	our $WNOHANG;
993		1273
994	sub _child_wait {	1274	sub _sigchld {
995	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1275	while (0 < (my $pid = waitpid -1, $WNOHANG)) {
996	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1276	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),
997	(values %{ $PID_CB{0} || {} });	1277	(values %{ $PID_CB{0} || {} });
998	}	1278	}
999
1000	undef $PID_IDLE;
1001	}
1002
1003	sub _sigchld {
1004	# make sure we deliver these changes "synchronous" with the event loop.
1005	$CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
1006	undef $CHLD_DELAY_W;
1007	&_child_wait;
1008	});
1009	}	1279	}
1010		1280
1011	sub child {	1281	sub child {
1012	my (undef, %arg) = @_;	1282	my (undef, %arg) = @_;
1013		1283
1014	defined (my $pid = $arg{pid} + 0)	1284	defined (my $pid = $arg{pid} + 0)
1015	or Carp::croak "required option 'pid' is missing";	1285	or Carp::croak "required option 'pid' is missing";
1016		1286
1017	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1287	$PID_CB{$pid}{$arg{cb}} = $arg{cb};
1018		1288
1019	unless ($WNOHANG) {
1020	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;	1289	$WNOHANG ||= eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1021	}
1022		1290
1023	unless ($CHLD_W) {	1291	unless ($CHLD_W) {
1024	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1292	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
1025	# child could be a zombie already, so make at least one round	1293	# child could be a zombie already, so make at least one round
1026	&_sigchld;	1294	&_sigchld;
1027	}	1295	}
1028		1296
1029	bless [$pid, $arg{cb}], "AnyEvent::Base::Child"	1297	bless [$pid, $arg{cb}], "AnyEvent::Base::child"
1030	}	1298	}
1031		1299
1032	sub AnyEvent::Base::Child::DESTROY {	1300	sub AnyEvent::Base::child::DESTROY {
1033	my ($pid, $cb) = @{$_[0]};	1301	my ($pid, $cb) = @{$_[0]};
1034		1302
1035	delete $PID_CB{$pid}{$cb};	1303	delete $PID_CB{$pid}{$cb};
1036	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1304	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1037		1305
1038	undef $CHLD_W unless keys %PID_CB;	1306	undef $CHLD_W unless keys %PID_CB;
		1307	}
		1308
		1309	# idle emulation is done by simply using a timer, regardless
		1310	# of whether the process is idle or not, and not letting
		1311	# the callback use more than 50% of the time.
		1312	sub idle {
		1313	my (undef, %arg) = @_;
		1314
		1315	my ($cb, $w, $rcb) = $arg{cb};
		1316
		1317	$rcb = sub {
		1318	if ($cb) {
		1319	$w = _time;
		1320	&$cb;
		1321	$w = _time - $w;
		1322
		1323	# never use more then 50% of the time for the idle watcher,
		1324	# within some limits
		1325	$w = 0.0001 if $w < 0.0001;
		1326	$w = 5 if $w > 5;
		1327
		1328	$w = AnyEvent->timer (after => $w, cb => $rcb);
		1329	} else {
		1330	# clean up...
		1331	undef $w;
		1332	undef $rcb;
		1333	}
		1334	};
		1335
		1336	$w = AnyEvent->timer (after => 0.05, cb => $rcb);
		1337
		1338	bless \\$cb, "AnyEvent::Base::idle"
		1339	}
		1340
		1341	sub AnyEvent::Base::idle::DESTROY {
		1342	undef $${$_[0]};
1039	}	1343	}
1040		1344
1041	package AnyEvent::CondVar;	1345	package AnyEvent::CondVar;
1042		1346
1043	our @ISA = AnyEvent::CondVar::Base::;	1347	our @ISA = AnyEvent::CondVar::Base::;
…		…
1095	}	1399	}
1096		1400
1097	# undocumented/compatibility with pre-3.4	1401	# undocumented/compatibility with pre-3.4
1098	*broadcast = \&send;	1402	*broadcast = \&send;
1099	*wait = \&_wait;	1403	*wait = \&_wait;
		1404
		1405	=head1 ERROR AND EXCEPTION HANDLING
		1406
		1407	In general, AnyEvent does not do any error handling - it relies on the
		1408	caller to do that if required. The L<AnyEvent::Strict> module (see also
		1409	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1410	checking of all AnyEvent methods, however, which is highly useful during
		1411	development.
		1412
		1413	As for exception handling (i.e. runtime errors and exceptions thrown while
		1414	executing a callback), this is not only highly event-loop specific, but
		1415	also not in any way wrapped by this module, as this is the job of the main
		1416	program.
		1417
		1418	The pure perl event loop simply re-throws the exception (usually
		1419	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1420	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1421	so on.
		1422
		1423	=head1 ENVIRONMENT VARIABLES
		1424
		1425	The following environment variables are used by this module or its
		1426	submodules.
		1427
		1428	Note that AnyEvent will remove I<all> environment variables starting with
		1429	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		1430	enabled.
		1431
		1432	=over 4
		1433
		1434	=item C<PERL_ANYEVENT_VERBOSE>
		1435
		1436	By default, AnyEvent will be completely silent except in fatal
		1437	conditions. You can set this environment variable to make AnyEvent more
		1438	talkative.
		1439
		1440	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		1441	conditions, such as not being able to load the event model specified by
		1442	C<PERL_ANYEVENT_MODEL>.
		1443
		1444	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		1445	model it chooses.
		1446
		1447	=item C<PERL_ANYEVENT_STRICT>
		1448
		1449	AnyEvent does not do much argument checking by default, as thorough
		1450	argument checking is very costly. Setting this variable to a true value
		1451	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1452	check the arguments passed to most method calls. If it finds any problems,
		1453	it will croak.
		1454
		1455	In other words, enables "strict" mode.
		1456
		1457	Unlike C<use strict>, it is definitely recommended to keep it off in
		1458	production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while
		1459	developing programs can be very useful, however.
		1460
		1461	=item C<PERL_ANYEVENT_MODEL>
		1462
		1463	This can be used to specify the event model to be used by AnyEvent, before
		1464	auto detection and -probing kicks in. It must be a string consisting
		1465	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		1466	and the resulting module name is loaded and if the load was successful,
		1467	used as event model. If it fails to load AnyEvent will proceed with
		1468	auto detection and -probing.
		1469
		1470	This functionality might change in future versions.
		1471
		1472	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		1473	could start your program like this:
		1474
		1475	PERL_ANYEVENT_MODEL=Perl perl ...
		1476
		1477	=item C<PERL_ANYEVENT_PROTOCOLS>
		1478
		1479	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
		1480	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
		1481	of auto probing).
		1482
		1483	Must be set to a comma-separated list of protocols or address families,
		1484	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		1485	used, and preference will be given to protocols mentioned earlier in the
		1486	list.
		1487
		1488	This variable can effectively be used for denial-of-service attacks
		1489	against local programs (e.g. when setuid), although the impact is likely
		1490	small, as the program has to handle conenction and other failures anyways.
		1491
		1492	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
		1493	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
		1494	- only support IPv4, never try to resolve or contact IPv6
		1495	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		1496	IPv6, but prefer IPv6 over IPv4.
		1497
		1498	=item C<PERL_ANYEVENT_EDNS0>
		1499
		1500	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
		1501	for DNS. This extension is generally useful to reduce DNS traffic, but
		1502	some (broken) firewalls drop such DNS packets, which is why it is off by
		1503	default.
		1504
		1505	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		1506	EDNS0 in its DNS requests.
		1507
		1508	=item C<PERL_ANYEVENT_MAX_FORKS>
		1509
		1510	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1511	will create in parallel.
		1512
		1513	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		1514
		1515	The default value for the C<max_outstanding> parameter for the default DNS
		1516	resolver - this is the maximum number of parallel DNS requests that are
		1517	sent to the DNS server.
		1518
		1519	=item C<PERL_ANYEVENT_RESOLV_CONF>
		1520
		1521	The file to use instead of F</etc/resolv.conf> (or OS-specific
		1522	configuration) in the default resolver. When set to the empty string, no
		1523	default config will be used.
		1524
		1525	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		1526
		1527	When neither C<ca_file> nor C<ca_path> was specified during
		1528	L<AnyEvent::TLS> context creation, and either of these environment
		1529	variables exist, they will be used to specify CA certificate locations
		1530	instead of a system-dependent default.
		1531
		1532	=back
1100		1533
1101	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	1534	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1102		1535
1103	This is an advanced topic that you do not normally need to use AnyEvent in	1536	This is an advanced topic that you do not normally need to use AnyEvent in
1104	a module. This section is only of use to event loop authors who want to	1537	a module. This section is only of use to event loop authors who want to
…		…
1138		1571
1139	I<rxvt-unicode> also cheats a bit by not providing blocking access to	1572	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1140	condition variables: code blocking while waiting for a condition will	1573	condition variables: code blocking while waiting for a condition will
1141	C<die>. This still works with most modules/usages, and blocking calls must	1574	C<die>. This still works with most modules/usages, and blocking calls must
1142	not be done in an interactive application, so it makes sense.	1575	not be done in an interactive application, so it makes sense.
1143
1144	=head1 ENVIRONMENT VARIABLES
1145
1146	The following environment variables are used by this module:
1147
1148	=over 4
1149
1150	=item C<PERL_ANYEVENT_VERBOSE>
1151
1152	By default, AnyEvent will be completely silent except in fatal
1153	conditions. You can set this environment variable to make AnyEvent more
1154	talkative.
1155
1156	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1157	conditions, such as not being able to load the event model specified by
1158	C<PERL_ANYEVENT_MODEL>.
1159
1160	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1161	model it chooses.
1162
1163	=item C<PERL_ANYEVENT_MODEL>
1164
1165	This can be used to specify the event model to be used by AnyEvent, before
1166	auto detection and -probing kicks in. It must be a string consisting
1167	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1168	and the resulting module name is loaded and if the load was successful,
1169	used as event model. If it fails to load AnyEvent will proceed with
1170	auto detection and -probing.
1171
1172	This functionality might change in future versions.
1173
1174	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1175	could start your program like this:
1176
1177	PERL_ANYEVENT_MODEL=Perl perl ...
1178
1179	=item C<PERL_ANYEVENT_PROTOCOLS>
1180
1181	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1182	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1183	of auto probing).
1184
1185	Must be set to a comma-separated list of protocols or address families,
1186	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1187	used, and preference will be given to protocols mentioned earlier in the
1188	list.
1189
1190	This variable can effectively be used for denial-of-service attacks
1191	against local programs (e.g. when setuid), although the impact is likely
1192	small, as the program has to handle connection errors already-
1193
1194	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1195	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1196	- only support IPv4, never try to resolve or contact IPv6
1197	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1198	IPv6, but prefer IPv6 over IPv4.
1199
1200	=item C<PERL_ANYEVENT_EDNS0>
1201
1202	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1203	for DNS. This extension is generally useful to reduce DNS traffic, but
1204	some (broken) firewalls drop such DNS packets, which is why it is off by
1205	default.
1206
1207	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1208	EDNS0 in its DNS requests.
1209
1210	=item C<PERL_ANYEVENT_MAX_FORKS>
1211
1212	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1213	will create in parallel.
1214
1215	=back
1216		1576
1217	=head1 EXAMPLE PROGRAM	1577	=head1 EXAMPLE PROGRAM
1218		1578
1219	The following program uses an I/O watcher to read data from STDIN, a timer	1579	The following program uses an I/O watcher to read data from STDIN, a timer
1220	to display a message once per second, and a condition variable to quit the	1580	to display a message once per second, and a condition variable to quit the
…		…
1414	watcher.	1774	watcher.
1415		1775
1416	=head3 Results	1776	=head3 Results
1417		1777
1418	name watchers bytes create invoke destroy comment	1778	name watchers bytes create invoke destroy comment
1419	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	1779	EV/EV 400000 224 0.47 0.35 0.27 EV native interface
1420	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers	1780	EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers
1421	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal	1781	CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal
1422	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation	1782	Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation
1423	Event/Event 16000 516 31.88 31.30 0.85 Event native interface	1783	Event/Event 16000 517 32.20 31.80 0.81 Event native interface
1424	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers	1784	Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers
		1785	IOAsync/Any 16000 989 38.10 32.77 11.13 via IO::Async::Loop::IO_Poll
		1786	IOAsync/Any 16000 990 37.59 29.50 10.61 via IO::Async::Loop::Epoll
1425	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour	1787	Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour
1426	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers	1788	Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers
1427	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event	1789	POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event
1428	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select	1790	POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select
1429		1791
1430	=head3 Discussion	1792	=head3 Discussion
1431		1793
1432	The benchmark does I<not> measure scalability of the event loop very	1794	The benchmark does I<not> measure scalability of the event loop very
1433	well. For example, a select-based event loop (such as the pure perl one)	1795	well. For example, a select-based event loop (such as the pure perl one)
…		…
1458	performance becomes really bad with lots of file descriptors (and few of	1820	performance becomes really bad with lots of file descriptors (and few of
1459	them active), of course, but this was not subject of this benchmark.	1821	them active), of course, but this was not subject of this benchmark.
1460		1822
1461	The C<Event> module has a relatively high setup and callback invocation	1823	The C<Event> module has a relatively high setup and callback invocation
1462	cost, but overall scores in on the third place.	1824	cost, but overall scores in on the third place.
		1825
		1826	C<IO::Async> performs admirably well, about on par with C<Event>, even
		1827	when using its pure perl backend.
1463		1828
1464	C<Glib>'s memory usage is quite a bit higher, but it features a	1829	C<Glib>'s memory usage is quite a bit higher, but it features a
1465	faster callback invocation and overall ends up in the same class as	1830	faster callback invocation and overall ends up in the same class as
1466	C<Event>. However, Glib scales extremely badly, doubling the number of	1831	C<Event>. However, Glib scales extremely badly, doubling the number of
1467	watchers increases the processing time by more than a factor of four,	1832	watchers increases the processing time by more than a factor of four,
…		…
1545	it to another server. This includes deleting the old timeout and creating	1910	it to another server. This includes deleting the old timeout and creating
1546	a new one that moves the timeout into the future.	1911	a new one that moves the timeout into the future.
1547		1912
1548	=head3 Results	1913	=head3 Results
1549		1914
1550	name sockets create request	1915	name sockets create request
1551	EV 20000 69.01 11.16	1916	EV 20000 69.01 11.16
1552	Perl 20000 73.32 35.87	1917	Perl 20000 73.32 35.87
		1918	IOAsync 20000 157.00 98.14 epoll
		1919	IOAsync 20000 159.31 616.06 poll
1553	Event 20000 212.62 257.32	1920	Event 20000 212.62 257.32
1554	Glib 20000 651.16 1896.30	1921	Glib 20000 651.16 1896.30
1555	POE 20000 349.67 12317.24 uses POE::Loop::Event	1922	POE 20000 349.67 12317.24 uses POE::Loop::Event
1556		1923
1557	=head3 Discussion	1924	=head3 Discussion
1558		1925
1559	This benchmark I<does> measure scalability and overall performance of the	1926	This benchmark I<does> measure scalability and overall performance of the
1560	particular event loop.	1927	particular event loop.
…		…
1562	EV is again fastest. Since it is using epoll on my system, the setup time	1929	EV is again fastest. Since it is using epoll on my system, the setup time
1563	is relatively high, though.	1930	is relatively high, though.
1564		1931
1565	Perl surprisingly comes second. It is much faster than the C-based event	1932	Perl surprisingly comes second. It is much faster than the C-based event
1566	loops Event and Glib.	1933	loops Event and Glib.
		1934
		1935	IO::Async performs very well when using its epoll backend, and still quite
		1936	good compared to Glib when using its pure perl backend.
1567		1937
1568	Event suffers from high setup time as well (look at its code and you will	1938	Event suffers from high setup time as well (look at its code and you will
1569	understand why). Callback invocation also has a high overhead compared to	1939	understand why). Callback invocation also has a high overhead compared to
1570	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	1940	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1571	uses select or poll in basically all documented configurations.	1941	uses select or poll in basically all documented configurations.
…		…
1634	=item * C-based event loops perform very well with small number of	2004	=item * C-based event loops perform very well with small number of
1635	watchers, as the management overhead dominates.	2005	watchers, as the management overhead dominates.
1636		2006
1637	=back	2007	=back
1638		2008
		2009	=head2 THE IO::Lambda BENCHMARK
		2010
		2011	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2012	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2013	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2014	shouldn't come as a surprise to anybody). As such, the benchmark is
		2015	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2016	very optimal. But how would AnyEvent compare when used without the extra
		2017	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2018
		2019	The benchmark itself creates an echo-server, and then, for 500 times,
		2020	connects to the echo server, sends a line, waits for the reply, and then
		2021	creates the next connection. This is a rather bad benchmark, as it doesn't
		2022	test the efficiency of the framework or much non-blocking I/O, but it is a
		2023	benchmark nevertheless.
		2024
		2025	name runtime
		2026	Lambda/select 0.330 sec
		2027	+ optimized 0.122 sec
		2028	Lambda/AnyEvent 0.327 sec
		2029	+ optimized 0.138 sec
		2030	Raw sockets/select 0.077 sec
		2031	POE/select, components 0.662 sec
		2032	POE/select, raw sockets 0.226 sec
		2033	POE/select, optimized 0.404 sec
		2034
		2035	AnyEvent/select/nb 0.085 sec
		2036	AnyEvent/EV/nb 0.068 sec
		2037	+state machine 0.134 sec
		2038
		2039	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2040	benchmarks actually make blocking connects and use 100% blocking I/O,
		2041	defeating the purpose of an event-based solution. All of the newly
		2042	written AnyEvent benchmarks use 100% non-blocking connects (using
		2043	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2044	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2045	generally require a lot more bookkeeping and event handling than blocking
		2046	connects (which involve a single syscall only).
		2047
		2048	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2049	offers similar expressive power as POE and IO::Lambda, using conventional
		2050	Perl syntax. This means that both the echo server and the client are 100%
		2051	non-blocking, further placing it at a disadvantage.
		2052
		2053	As you can see, the AnyEvent + EV combination even beats the
		2054	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2055	backend easily beats IO::Lambda and POE.
		2056
		2057	And even the 100% non-blocking version written using the high-level (and
		2058	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda by a
		2059	large margin, even though it does all of DNS, tcp-connect and socket I/O
		2060	in a non-blocking way.
		2061
		2062	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2063	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2064	part of the IO::lambda distribution and were used without any changes.
		2065
		2066
		2067	=head1 SIGNALS
		2068
		2069	AnyEvent currently installs handlers for these signals:
		2070
		2071	=over 4
		2072
		2073	=item SIGCHLD
		2074
		2075	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
		2076	emulation for event loops that do not support them natively. Also, some
		2077	event loops install a similar handler.
		2078
		2079	If, when AnyEvent is loaded, SIGCHLD is set to IGNORE, then AnyEvent will
		2080	reset it to default, to avoid losing child exit statuses.
		2081
		2082	=item SIGPIPE
		2083
		2084	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
		2085	when AnyEvent gets loaded.
		2086
		2087	The rationale for this is that AnyEvent users usually do not really depend
		2088	on SIGPIPE delivery (which is purely an optimisation for shell use, or
		2089	badly-written programs), but C<SIGPIPE> can cause spurious and rare
		2090	program exits as a lot of people do not expect C<SIGPIPE> when writing to
		2091	some random socket.
		2092
		2093	The rationale for installing a no-op handler as opposed to ignoring it is
		2094	that this way, the handler will be restored to defaults on exec.
		2095
		2096	Feel free to install your own handler, or reset it to defaults.
		2097
		2098	=back
		2099
		2100	=cut
		2101
		2102	undef $SIG{CHLD}
		2103	if $SIG{CHLD} eq 'IGNORE';
		2104
		2105	$SIG{PIPE} = sub { }
		2106	unless defined $SIG{PIPE};
1639		2107
1640	=head1 FORK	2108	=head1 FORK
1641		2109
1642	Most event libraries are not fork-safe. The ones who are usually are	2110	Most event libraries are not fork-safe. The ones who are usually are
1643	because they rely on inefficient but fork-safe C<select> or C<poll>	2111	because they rely on inefficient but fork-safe C<select> or C<poll>
…		…
1657	specified in the variable.	2125	specified in the variable.
1658		2126
1659	You can make AnyEvent completely ignore this variable by deleting it	2127	You can make AnyEvent completely ignore this variable by deleting it
1660	before the first watcher gets created, e.g. with a C<BEGIN> block:	2128	before the first watcher gets created, e.g. with a C<BEGIN> block:
1661		2129
1662	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	2130	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1663		2131
1664	use AnyEvent;	2132	use AnyEvent;
1665		2133
1666	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2134	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1667	be used to probe what backend is used and gain other information (which is	2135	be used to probe what backend is used and gain other information (which is
1668	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	2136	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		2137	$ENV{PERL_ANYEVENT_STRICT}.
		2138
		2139	Note that AnyEvent will remove I<all> environment variables starting with
		2140	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2141	enabled.
		2142
		2143
		2144	=head1 BUGS
		2145
		2146	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		2147	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		2148	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		2149	memleaks, such as leaking on C<map> and C<grep> but it is usually not as
		2150	pronounced).
1669		2151
1670		2152
1671	=head1 SEE ALSO	2153	=head1 SEE ALSO
1672		2154
1673	Utility functions: L<AnyEvent::Util>.	2155	Utility functions: L<AnyEvent::Util>.
…		…
1676	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	2158	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1677		2159
1678	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	2160	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1679	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	2161	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1680	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	2162	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1681	L<AnyEvent::Impl::POE>.	2163	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>.
1682		2164
1683	Non-blocking file handles, sockets, TCP clients and	2165	Non-blocking file handles, sockets, TCP clients and
1684	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	2166	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1685		2167
1686	Asynchronous DNS: L<AnyEvent::DNS>.	2168	Asynchronous DNS: L<AnyEvent::DNS>.
1687		2169
1688	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	2170	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>,
		2171	L<Coro::Event>,
1689		2172
1690	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	2173	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>,
		2174	L<AnyEvent::HTTP>.
1691		2175
1692		2176
1693	=head1 AUTHOR	2177	=head1 AUTHOR
1694		2178
1695	Marc Lehmann <schmorp@schmorp.de>	2179	Marc Lehmann <schmorp@schmorp.de>
1696	http://home.schmorp.de/	2180	http://home.schmorp.de/
1697		2181
1698	=cut	2182	=cut
1699		2183
1700	1	2184	1
1701		2185

Diff Legend

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