ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.191 by root, Fri Nov 21 01:35:59 2008 UTC vs.
Revision 1.410 by root, Fri Mar 1 06:03:21 2013 UTC

1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - the DBI of event loop programming
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt,
		6	FLTK and POE are various supported event loops/environments.
6		7
7	=head1 SYNOPSIS	8	=head1 SYNOPSIS
8		9
9	use AnyEvent;	10	use AnyEvent;
10		11
		12	# if you prefer function calls, look at the AE manpage for
		13	# an alternative API.
		14
		15	# file handle or descriptor readable
11	my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { ... });	16	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
12		17
		18	# one-shot or repeating timers
13	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });	19	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
14	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...	20	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
15		21
16	print AnyEvent->now; # prints current event loop time	22	print AnyEvent->now; # prints current event loop time
17	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.	23	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
18		24
		25	# POSIX signal
19	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });	26	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
20		27
		28	# child process exit
21	my $w = AnyEvent->child (pid => $pid, cb => sub {	29	my $w = AnyEvent->child (pid => $pid, cb => sub {
22	my ($pid, $status) = @_;	30	my ($pid, $status) = @_;
23	...	31	...
24	});	32	});
		33
		34	# called when event loop idle (if applicable)
		35	my $w = AnyEvent->idle (cb => sub { ... });
25		36
26	my $w = AnyEvent->condvar; # stores whether a condition was flagged	37	my $w = AnyEvent->condvar; # stores whether a condition was flagged
27	$w->send; # wake up current and all future recv's	38	$w->send; # wake up current and all future recv's
28	$w->recv; # enters "main loop" till $condvar gets ->send	39	$w->recv; # enters "main loop" till $condvar gets ->send
29	# use a condvar in callback mode:	40	# use a condvar in callback mode:
…		…
32	=head1 INTRODUCTION/TUTORIAL	43	=head1 INTRODUCTION/TUTORIAL
33		44
34	This manpage is mainly a reference manual. If you are interested	45	This manpage is mainly a reference manual. If you are interested
35	in a tutorial or some gentle introduction, have a look at the	46	in a tutorial or some gentle introduction, have a look at the
36	L<AnyEvent::Intro> manpage.	47	L<AnyEvent::Intro> manpage.
		48
		49	=head1 SUPPORT
		50
		51	An FAQ document is available as L<AnyEvent::FAQ>.
		52
		53	There also is a mailinglist for discussing all things AnyEvent, and an IRC
		54	channel, too.
		55
		56	See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
		57	Repository>, at L<http://anyevent.schmorp.de>, for more info.
37		58
38	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	59	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
39		60
40	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	61	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
41	nowadays. So what is different about AnyEvent?	62	nowadays. So what is different about AnyEvent?
…		…
57	module users into the same thing by forcing them to use the same event	78	module users into the same thing by forcing them to use the same event
58	model you use.	79	model you use.
59		80
60	For modules like POE or IO::Async (which is a total misnomer as it is	81	For modules like POE or IO::Async (which is a total misnomer as it is
61	actually doing all I/O I<synchronously>...), using them in your module is	82	actually doing all I/O I<synchronously>...), using them in your module is
62	like joining a cult: After you joined, you are dependent on them and you	83	like joining a cult: After you join, you are dependent on them and you
63	cannot use anything else, as they are simply incompatible to everything	84	cannot use anything else, as they are simply incompatible to everything
64	that isn't them. What's worse, all the potential users of your	85	that isn't them. What's worse, all the potential users of your
65	module are I<also> forced to use the same event loop you use.	86	module are I<also> forced to use the same event loop you use.
66		87
67	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	88	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
68	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	89	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
69	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if	90	with the rest: POE + EV? No go. Tk + Event? No go. Again: if your module
70	your module uses one of those, every user of your module has to use it,	91	uses one of those, every user of your module has to use it, too. But if
71	too. But if your module uses AnyEvent, it works transparently with all	92	your module uses AnyEvent, it works transparently with all event models it
72	event models it supports (including stuff like IO::Async, as long as those	93	supports (including stuff like IO::Async, as long as those use one of the
73	use one of the supported event loops. It is trivial to add new event loops	94	supported event loops. It is easy to add new event loops to AnyEvent, too,
74	to AnyEvent, too, so it is future-proof).	95	so it is future-proof).
75		96
76	In addition to being free of having to use I<the one and only true event	97	In addition to being free of having to use I<the one and only true event
77	model>, AnyEvent also is free of bloat and policy: with POE or similar	98	model>, AnyEvent also is free of bloat and policy: with POE or similar
78	modules, you get an enormous amount of code and strict rules you have to	99	modules, you get an enormous amount of code and strict rules you have to
79	follow. AnyEvent, on the other hand, is lean and up to the point, by only	100	follow. AnyEvent, on the other hand, is lean and to the point, by only
80	offering the functionality that is necessary, in as thin as a wrapper as	101	offering the functionality that is necessary, in as thin as a wrapper as
81	technically possible.	102	technically possible.
82		103
83	Of course, AnyEvent comes with a big (and fully optional!) toolbox	104	Of course, AnyEvent comes with a big (and fully optional!) toolbox
84	of useful functionality, such as an asynchronous DNS resolver, 100%	105	of useful functionality, such as an asynchronous DNS resolver, 100%
…		…
90	useful) and you want to force your users to use the one and only event	111	useful) and you want to force your users to use the one and only event
91	model, you should I<not> use this module.	112	model, you should I<not> use this module.
92		113
93	=head1 DESCRIPTION	114	=head1 DESCRIPTION
94		115
95	L<AnyEvent> provides an identical interface to multiple event loops. This	116	L<AnyEvent> provides a uniform interface to various event loops. This
96	allows module authors to utilise an event loop without forcing module	117	allows module authors to use event loop functionality without forcing
97	users to use the same event loop (as only a single event loop can coexist	118	module users to use a specific event loop implementation (since more
98	peacefully at any one time).	119	than one event loop cannot coexist peacefully).
99		120
100	The interface itself is vaguely similar, but not identical to the L<Event>	121	The interface itself is vaguely similar, but not identical to the L<Event>
101	module.	122	module.
102		123
103	During the first call of any watcher-creation method, the module tries	124	During the first call of any watcher-creation method, the module tries
104	to detect the currently loaded event loop by probing whether one of the	125	to detect the currently loaded event loop by probing whether one of the
105	following modules is already loaded: L<EV>,	126	following modules is already loaded: L<EV>, L<AnyEvent::Loop>,
106	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,	127	L<Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. The first one
107	L<POE>. The first one found is used. If none are found, the module tries	128	found is used. If none are detected, the module tries to load the first
108	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl	129	four modules in the order given; but note that if L<EV> is not
109	adaptor should always succeed) in the order given. The first one that can	130	available, the pure-perl L<AnyEvent::Loop> should always work, so
110	be successfully loaded will be used. If, after this, still none could be	131	the other two are not normally tried.
111	found, AnyEvent will fall back to a pure-perl event loop, which is not
112	very efficient, but should work everywhere.
113		132
114	Because AnyEvent first checks for modules that are already loaded, loading	133	Because AnyEvent first checks for modules that are already loaded, loading
115	an event model explicitly before first using AnyEvent will likely make	134	an event model explicitly before first using AnyEvent will likely make
116	that model the default. For example:	135	that model the default. For example:
117		136
…		…
119	use AnyEvent;	138	use AnyEvent;
120		139
121	# .. AnyEvent will likely default to Tk	140	# .. AnyEvent will likely default to Tk
122		141
123	The I<likely> means that, if any module loads another event model and	142	The I<likely> means that, if any module loads another event model and
124	starts using it, all bets are off. Maybe you should tell their authors to	143	starts using it, all bets are off - this case should be very rare though,
125	use AnyEvent so their modules work together with others seamlessly...	144	as very few modules hardcode event loops without announcing this very
		145	loudly.
126		146
127	The pure-perl implementation of AnyEvent is called	147	The pure-perl implementation of AnyEvent is called C<AnyEvent::Loop>. Like
128	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	148	other event modules you can load it explicitly and enjoy the high
129	explicitly and enjoy the high availability of that event loop :)	149	availability of that event loop :)
130		150
131	=head1 WATCHERS	151	=head1 WATCHERS
132		152
133	AnyEvent has the central concept of a I<watcher>, which is an object that	153	AnyEvent has the central concept of a I<watcher>, which is an object that
134	stores relevant data for each kind of event you are waiting for, such as	154	stores relevant data for each kind of event you are waiting for, such as
…		…
137	These watchers are normal Perl objects with normal Perl lifetime. After	157	These watchers are normal Perl objects with normal Perl lifetime. After
138	creating a watcher it will immediately "watch" for events and invoke the	158	creating a watcher it will immediately "watch" for events and invoke the
139	callback when the event occurs (of course, only when the event model	159	callback when the event occurs (of course, only when the event model
140	is in control).	160	is in control).
141		161
		162	Note that B<callbacks must not permanently change global variables>
		163	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		164	callbacks must not C<die> >>. The former is good programming practice in
		165	Perl and the latter stems from the fact that exception handling differs
		166	widely between event loops.
		167
142	To disable the watcher you have to destroy it (e.g. by setting the	168	To disable a watcher you have to destroy it (e.g. by setting the
143	variable you store it in to C<undef> or otherwise deleting all references	169	variable you store it in to C<undef> or otherwise deleting all references
144	to it).	170	to it).
145		171
146	All watchers are created by calling a method on the C<AnyEvent> class.	172	All watchers are created by calling a method on the C<AnyEvent> class.
147		173
148	Many watchers either are used with "recursion" (repeating timers for	174	Many watchers either are used with "recursion" (repeating timers for
149	example), or need to refer to their watcher object in other ways.	175	example), or need to refer to their watcher object in other ways.
150		176
151	An any way to achieve that is this pattern:	177	One way to achieve that is this pattern:
152		178
153	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	179	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
154	# you can use $w here, for example to undef it	180	# you can use $w here, for example to undef it
155	undef $w;	181	undef $w;
156	});	182	});
…		…
159	my variables are only visible after the statement in which they are	185	my variables are only visible after the statement in which they are
160	declared.	186	declared.
161		187
162	=head2 I/O WATCHERS	188	=head2 I/O WATCHERS
163		189
		190	$w = AnyEvent->io (
		191	fh => <filehandle_or_fileno>,
		192	poll => <"r" or "w">,
		193	cb => <callback>,
		194	);
		195
164	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	196	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
165	with the following mandatory key-value pairs as arguments:	197	with the following mandatory key-value pairs as arguments:
166		198
167	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events	199	C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
168	(AnyEvent might or might not keep a reference to this file handle). C<poll>	200	for events (AnyEvent might or might not keep a reference to this file
		201	handle). Note that only file handles pointing to things for which
		202	non-blocking operation makes sense are allowed. This includes sockets,
		203	most character devices, pipes, fifos and so on, but not for example files
		204	or block devices.
		205
169	must be a string that is either C<r> or C<w>, which creates a watcher	206	C<poll> must be a string that is either C<r> or C<w>, which creates a
170	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the	207	watcher waiting for "r"eadable or "w"ritable events, respectively.
		208
171	callback to invoke each time the file handle becomes ready.	209	C<cb> is the callback to invoke each time the file handle becomes ready.
172		210
173	Although the callback might get passed parameters, their value and	211	Although the callback might get passed parameters, their value and
174	presence is undefined and you cannot rely on them. Portable AnyEvent	212	presence is undefined and you cannot rely on them. Portable AnyEvent
175	callbacks cannot use arguments passed to I/O watcher callbacks.	213	callbacks cannot use arguments passed to I/O watcher callbacks.
176		214
177	The I/O watcher might use the underlying file descriptor or a copy of it.	215	The I/O watcher might use the underlying file descriptor or a copy of it.
178	You must not close a file handle as long as any watcher is active on the	216	You must not close a file handle as long as any watcher is active on the
179	underlying file descriptor.	217	underlying file descriptor.
180		218
181	Some event loops issue spurious readyness notifications, so you should	219	Some event loops issue spurious readiness notifications, so you should
182	always use non-blocking calls when reading/writing from/to your file	220	always use non-blocking calls when reading/writing from/to your file
183	handles.	221	handles.
184		222
185	Example: wait for readability of STDIN, then read a line and disable the	223	Example: wait for readability of STDIN, then read a line and disable the
186	watcher.	224	watcher.
…		…
191	undef $w;	229	undef $w;
192	});	230	});
193		231
194	=head2 TIME WATCHERS	232	=head2 TIME WATCHERS
195		233
		234	$w = AnyEvent->timer (after => <seconds>, cb => <callback>);
		235
		236	$w = AnyEvent->timer (
		237	after => <fractional_seconds>,
		238	interval => <fractional_seconds>,
		239	cb => <callback>,
		240	);
		241
196	You can create a time watcher by calling the C<< AnyEvent->timer >>	242	You can create a time watcher by calling the C<< AnyEvent->timer >>
197	method with the following mandatory arguments:	243	method with the following mandatory arguments:
198		244
199	C<after> specifies after how many seconds (fractional values are	245	C<after> specifies after how many seconds (fractional values are
200	supported) the callback should be invoked. C<cb> is the callback to invoke	246	supported) the callback should be invoked. C<cb> is the callback to invoke
…		…
202		248
203	Although the callback might get passed parameters, their value and	249	Although the callback might get passed parameters, their value and
204	presence is undefined and you cannot rely on them. Portable AnyEvent	250	presence is undefined and you cannot rely on them. Portable AnyEvent
205	callbacks cannot use arguments passed to time watcher callbacks.	251	callbacks cannot use arguments passed to time watcher callbacks.
206		252
207	The callback will normally be invoked once only. If you specify another	253	The callback will normally be invoked only once. If you specify another
208	parameter, C<interval>, as a strictly positive number (> 0), then the	254	parameter, C<interval>, as a strictly positive number (> 0), then the
209	callback will be invoked regularly at that interval (in fractional	255	callback will be invoked regularly at that interval (in fractional
210	seconds) after the first invocation. If C<interval> is specified with a	256	seconds) after the first invocation. If C<interval> is specified with a
211	false value, then it is treated as if it were missing.	257	false value, then it is treated as if it were not specified at all.
212		258
213	The callback will be rescheduled before invoking the callback, but no	259	The callback will be rescheduled before invoking the callback, but no
214	attempt is done to avoid timer drift in most backends, so the interval is	260	attempt is made to avoid timer drift in most backends, so the interval is
215	only approximate.	261	only approximate.
216		262
217	Example: fire an event after 7.7 seconds.	263	Example: fire an event after 7.7 seconds.
218		264
219	my $w = AnyEvent->timer (after => 7.7, cb => sub {	265	my $w = AnyEvent->timer (after => 7.7, cb => sub {
…		…
237		283
238	While most event loops expect timers to specified in a relative way, they	284	While most event loops expect timers to specified in a relative way, they
239	use absolute time internally. This makes a difference when your clock	285	use absolute time internally. This makes a difference when your clock
240	"jumps", for example, when ntp decides to set your clock backwards from	286	"jumps", for example, when ntp decides to set your clock backwards from
241	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to	287	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
242	fire "after" a second might actually take six years to finally fire.	288	fire "after a second" might actually take six years to finally fire.
243		289
244	AnyEvent cannot compensate for this. The only event loop that is conscious	290	AnyEvent cannot compensate for this. The only event loop that is conscious
245	about these issues is L<EV>, which offers both relative (ev_timer, based	291	of these issues is L<EV>, which offers both relative (ev_timer, based
246	on true relative time) and absolute (ev_periodic, based on wallclock time)	292	on true relative time) and absolute (ev_periodic, based on wallclock time)
247	timers.	293	timers.
248		294
249	AnyEvent always prefers relative timers, if available, matching the	295	AnyEvent always prefers relative timers, if available, matching the
250	AnyEvent API.	296	AnyEvent API.
…		…
272	I<In almost all cases (in all cases if you don't care), this is the	318	I<In almost all cases (in all cases if you don't care), this is the
273	function to call when you want to know the current time.>	319	function to call when you want to know the current time.>
274		320
275	This function is also often faster then C<< AnyEvent->time >>, and	321	This function is also often faster then C<< AnyEvent->time >>, and
276	thus the preferred method if you want some timestamp (for example,	322	thus the preferred method if you want some timestamp (for example,
277	L<AnyEvent::Handle> uses this to update it's activity timeouts).	323	L<AnyEvent::Handle> uses this to update its activity timeouts).
278		324
279	The rest of this section is only of relevance if you try to be very exact	325	The rest of this section is only of relevance if you try to be very exact
280	with your timing, you can skip it without bad conscience.	326	with your timing; you can skip it without a bad conscience.
281		327
282	For a practical example of when these times differ, consider L<Event::Lib>	328	For a practical example of when these times differ, consider L<Event::Lib>
283	and L<EV> and the following set-up:	329	and L<EV> and the following set-up:
284		330
285	The event loop is running and has just invoked one of your callback at	331	The event loop is running and has just invoked one of your callbacks at
286	time=500 (assume no other callbacks delay processing). In your callback,	332	time=500 (assume no other callbacks delay processing). In your callback,
287	you wait a second by executing C<sleep 1> (blocking the process for a	333	you wait a second by executing C<sleep 1> (blocking the process for a
288	second) and then (at time=501) you create a relative timer that fires	334	second) and then (at time=501) you create a relative timer that fires
289	after three seconds.	335	after three seconds.
290		336
…		…
308	In either case, if you care (and in most cases, you don't), then you	354	In either case, if you care (and in most cases, you don't), then you
309	can get whatever behaviour you want with any event loop, by taking the	355	can get whatever behaviour you want with any event loop, by taking the
310	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into	356	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
311	account.	357	account.
312		358
		359	=item AnyEvent->now_update
		360
		361	Some event loops (such as L<EV> or L<AnyEvent::Loop>) cache the current
		362	time for each loop iteration (see the discussion of L<< AnyEvent->now >>,
		363	above).
		364
		365	When a callback runs for a long time (or when the process sleeps), then
		366	this "current" time will differ substantially from the real time, which
		367	might affect timers and time-outs.
		368
		369	When this is the case, you can call this method, which will update the
		370	event loop's idea of "current time".
		371
		372	A typical example would be a script in a web server (e.g. C<mod_perl>) -
		373	when mod_perl executes the script, then the event loop will have the wrong
		374	idea about the "current time" (being potentially far in the past, when the
		375	script ran the last time). In that case you should arrange a call to C<<
		376	AnyEvent->now_update >> each time the web server process wakes up again
		377	(e.g. at the start of your script, or in a handler).
		378
		379	Note that updating the time I<might> cause some events to be handled.
		380
313	=back	381	=back
314		382
315	=head2 SIGNAL WATCHERS	383	=head2 SIGNAL WATCHERS
		384
		385	$w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
316		386
317	You can watch for signals using a signal watcher, C<signal> is the signal	387	You can watch for signals using a signal watcher, C<signal> is the signal
318	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl	388	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
319	callback to be invoked whenever a signal occurs.	389	callback to be invoked whenever a signal occurs.
320		390
…		…
326	invocation, and callback invocation will be synchronous. Synchronous means	396	invocation, and callback invocation will be synchronous. Synchronous means
327	that it might take a while until the signal gets handled by the process,	397	that it might take a while until the signal gets handled by the process,
328	but it is guaranteed not to interrupt any other callbacks.	398	but it is guaranteed not to interrupt any other callbacks.
329		399
330	The main advantage of using these watchers is that you can share a signal	400	The main advantage of using these watchers is that you can share a signal
331	between multiple watchers.	401	between multiple watchers, and AnyEvent will ensure that signals will not
		402	interrupt your program at bad times.
332		403
333	This watcher might use C<%SIG>, so programs overwriting those signals	404	This watcher might use C<%SIG> (depending on the event loop used),
334	directly will likely not work correctly.	405	so programs overwriting those signals directly will likely not work
		406	correctly.
335		407
336	Example: exit on SIGINT	408	Example: exit on SIGINT
337		409
338	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });	410	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
339		411
		412	=head3 Restart Behaviour
		413
		414	While restart behaviour is up to the event loop implementation, most will
		415	not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's
		416	pure perl implementation).
		417
		418	=head3 Safe/Unsafe Signals
		419
		420	Perl signals can be either "safe" (synchronous to opcode handling)
		421	or "unsafe" (asynchronous) - the former might delay signal delivery
		422	indefinitely, the latter might corrupt your memory.
		423
		424	AnyEvent signal handlers are, in addition, synchronous to the event loop,
		425	i.e. they will not interrupt your running perl program but will only be
		426	called as part of the normal event handling (just like timer, I/O etc.
		427	callbacks, too).
		428
		429	=head3 Signal Races, Delays and Workarounds
		430
		431	Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support
		432	attaching callbacks to signals in a generic way, which is a pity,
		433	as you cannot do race-free signal handling in perl, requiring
		434	C libraries for this. AnyEvent will try to do its best, which
		435	means in some cases, signals will be delayed. The maximum time
		436	a signal might be delayed is 10 seconds by default, but can
		437	be overriden via C<$ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY}> or
		438	C<$AnyEvent::MAX_SIGNAL_LATENCY> - see the L<ENVIRONMENT VARIABLES>
		439	section for details.
		440
		441	All these problems can be avoided by installing the optional
		442	L<Async::Interrupt> module, which works with most event loops. It will not
		443	work with inherently broken event loops such as L<Event> or L<Event::Lib>
		444	(and not with L<POE> currently). For those, you just have to suffer the
		445	delays.
		446
340	=head2 CHILD PROCESS WATCHERS	447	=head2 CHILD PROCESS WATCHERS
341		448
		449	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
		450
342	You can also watch on a child process exit and catch its exit status.	451	You can also watch for a child process exit and catch its exit status.
343		452
344	The child process is specified by the C<pid> argument (if set to C<0>, it	453	The child process is specified by the C<pid> argument (on some backends,
345	watches for any child process exit). The watcher will triggered only when	454	using C<0> watches for any child process exit, on others this will
346	the child process has finished and an exit status is available, not on	455	croak). The watcher will be triggered only when the child process has
347	any trace events (stopped/continued).	456	finished and an exit status is available, not on any trace events
		457	(stopped/continued).
348		458
349	The callback will be called with the pid and exit status (as returned by	459	The callback will be called with the pid and exit status (as returned by
350	waitpid), so unlike other watcher types, you I<can> rely on child watcher	460	waitpid), so unlike other watcher types, you I<can> rely on child watcher
351	callback arguments.	461	callback arguments.
352		462
…		…
357		467
358	There is a slight catch to child watchers, however: you usually start them	468	There is a slight catch to child watchers, however: you usually start them
359	I<after> the child process was created, and this means the process could	469	I<after> the child process was created, and this means the process could
360	have exited already (and no SIGCHLD will be sent anymore).	470	have exited already (and no SIGCHLD will be sent anymore).
361		471
362	Not all event models handle this correctly (POE doesn't), but even for	472	Not all event models handle this correctly (neither POE nor IO::Async do,
		473	see their AnyEvent::Impl manpages for details), but even for event models
363	event models that I<do> handle this correctly, they usually need to be	474	that I<do> handle this correctly, they usually need to be loaded before
364	loaded before the process exits (i.e. before you fork in the first place).	475	the process exits (i.e. before you fork in the first place). AnyEvent's
		476	pure perl event loop handles all cases correctly regardless of when you
		477	start the watcher.
365		478
366	This means you cannot create a child watcher as the very first thing in an	479	This means you cannot create a child watcher as the very first
367	AnyEvent program, you I<have> to create at least one watcher before you	480	thing in an AnyEvent program, you I<have> to create at least one
368	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	481	watcher before you C<fork> the child (alternatively, you can call
		482	C<AnyEvent::detect>).
		483
		484	As most event loops do not support waiting for child events, they will be
		485	emulated by AnyEvent in most cases, in which case the latency and race
		486	problems mentioned in the description of signal watchers apply.
369		487
370	Example: fork a process and wait for it	488	Example: fork a process and wait for it
371		489
372	my $done = AnyEvent->condvar;	490	my $done = AnyEvent->condvar;
373		491
…		…
383	);	501	);
384		502
385	# do something else, then wait for process exit	503	# do something else, then wait for process exit
386	$done->recv;	504	$done->recv;
387		505
		506	=head2 IDLE WATCHERS
		507
		508	$w = AnyEvent->idle (cb => <callback>);
		509
		510	This will repeatedly invoke the callback after the process becomes idle,
		511	until either the watcher is destroyed or new events have been detected.
		512
		513	Idle watchers are useful when there is a need to do something, but it
		514	is not so important (or wise) to do it instantly. The callback will be
		515	invoked only when there is "nothing better to do", which is usually
		516	defined as "all outstanding events have been handled and no new events
		517	have been detected". That means that idle watchers ideally get invoked
		518	when the event loop has just polled for new events but none have been
		519	detected. Instead of blocking to wait for more events, the idle watchers
		520	will be invoked.
		521
		522	Unfortunately, most event loops do not really support idle watchers (only
		523	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
		524	will simply call the callback "from time to time".
		525
		526	Example: read lines from STDIN, but only process them when the
		527	program is otherwise idle:
		528
		529	my @lines; # read data
		530	my $idle_w;
		531	my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
		532	push @lines, scalar <STDIN>;
		533
		534	# start an idle watcher, if not already done
		535	$idle_w ||= AnyEvent->idle (cb => sub {
		536	# handle only one line, when there are lines left
		537	if (my $line = shift @lines) {
		538	print "handled when idle: $line";
		539	} else {
		540	# otherwise disable the idle watcher again
		541	undef $idle_w;
		542	}
		543	});
		544	});
		545
388	=head2 CONDITION VARIABLES	546	=head2 CONDITION VARIABLES
		547
		548	$cv = AnyEvent->condvar;
		549
		550	$cv->send (<list>);
		551	my @res = $cv->recv;
389		552
390	If you are familiar with some event loops you will know that all of them	553	If you are familiar with some event loops you will know that all of them
391	require you to run some blocking "loop", "run" or similar function that	554	require you to run some blocking "loop", "run" or similar function that
392	will actively watch for new events and call your callbacks.	555	will actively watch for new events and call your callbacks.
393		556
394	AnyEvent is different, it expects somebody else to run the event loop and	557	AnyEvent is slightly different: it expects somebody else to run the event
395	will only block when necessary (usually when told by the user).	558	loop and will only block when necessary (usually when told by the user).
396		559
397	The instrument to do that is called a "condition variable", so called	560	The tool to do that is called a "condition variable", so called because
398	because they represent a condition that must become true.	561	they represent a condition that must become true.
		562
		563	Now is probably a good time to look at the examples further below.
399		564
400	Condition variables can be created by calling the C<< AnyEvent->condvar	565	Condition variables can be created by calling the C<< AnyEvent->condvar
401	>> method, usually without arguments. The only argument pair allowed is	566	>> method, usually without arguments. The only argument pair allowed is
402
403	C<cb>, which specifies a callback to be called when the condition variable	567	C<cb>, which specifies a callback to be called when the condition variable
404	becomes true, with the condition variable as the first argument (but not	568	becomes true, with the condition variable as the first argument (but not
405	the results).	569	the results).
406		570
407	After creation, the condition variable is "false" until it becomes "true"	571	After creation, the condition variable is "false" until it becomes "true"
408	by calling the C<send> method (or calling the condition variable as if it	572	by calling the C<send> method (or calling the condition variable as if it
409	were a callback, read about the caveats in the description for the C<<	573	were a callback, read about the caveats in the description for the C<<
410	->send >> method).	574	->send >> method).
411		575
412	Condition variables are similar to callbacks, except that you can	576	Since condition variables are the most complex part of the AnyEvent API, here are
413	optionally wait for them. They can also be called merge points - points	577	some different mental models of what they are - pick the ones you can connect to:
414	in time where multiple outstanding events have been processed. And yet	578
415	another way to call them is transactions - each condition variable can be	579	=over 4
416	used to represent a transaction, which finishes at some point and delivers	580
417	a result.	581	=item * Condition variables are like callbacks - you can call them (and pass them instead
		582	of callbacks). Unlike callbacks however, you can also wait for them to be called.
		583
		584	=item * Condition variables are signals - one side can emit or send them,
		585	the other side can wait for them, or install a handler that is called when
		586	the signal fires.
		587
		588	=item * Condition variables are like "Merge Points" - points in your program
		589	where you merge multiple independent results/control flows into one.
		590
		591	=item * Condition variables represent a transaction - functions that start
		592	some kind of transaction can return them, leaving the caller the choice
		593	between waiting in a blocking fashion, or setting a callback.
		594
		595	=item * Condition variables represent future values, or promises to deliver
		596	some result, long before the result is available.
		597
		598	=back
418		599
419	Condition variables are very useful to signal that something has finished,	600	Condition variables are very useful to signal that something has finished,
420	for example, if you write a module that does asynchronous http requests,	601	for example, if you write a module that does asynchronous http requests,
421	then a condition variable would be the ideal candidate to signal the	602	then a condition variable would be the ideal candidate to signal the
422	availability of results. The user can either act when the callback is	603	availability of results. The user can either act when the callback is
…		…
435		616
436	Condition variables are represented by hash refs in perl, and the keys	617	Condition variables are represented by hash refs in perl, and the keys
437	used by AnyEvent itself are all named C<_ae_XXX> to make subclassing	618	used by AnyEvent itself are all named C<_ae_XXX> to make subclassing
438	easy (it is often useful to build your own transaction class on top of	619	easy (it is often useful to build your own transaction class on top of
439	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call	620	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
440	it's C<new> method in your own C<new> method.	621	its C<new> method in your own C<new> method.
441		622
442	There are two "sides" to a condition variable - the "producer side" which	623	There are two "sides" to a condition variable - the "producer side" which
443	eventually calls C<< -> send >>, and the "consumer side", which waits	624	eventually calls C<< -> send >>, and the "consumer side", which waits
444	for the send to occur.	625	for the send to occur.
445		626
446	Example: wait for a timer.	627	Example: wait for a timer.
447		628
448	# wait till the result is ready	629	# condition: "wait till the timer is fired"
449	my $result_ready = AnyEvent->condvar;	630	my $timer_fired = AnyEvent->condvar;
450		631
451	# do something such as adding a timer	632	# create the timer - we could wait for, say
452	# or socket watcher the calls $result_ready->send	633	# a handle becomign ready, or even an
453	# when the "result" is ready.	634	# AnyEvent::HTTP request to finish, but
454	# in this case, we simply use a timer:	635	# in this case, we simply use a timer:
455	my $w = AnyEvent->timer (	636	my $w = AnyEvent->timer (
456	after => 1,	637	after => 1,
457	cb => sub { $result_ready->send },	638	cb => sub { $timer_fired->send },
458	);	639	);
459		640
460	# this "blocks" (while handling events) till the callback	641	# this "blocks" (while handling events) till the callback
461	# calls send	642	# calls ->send
462	$result_ready->recv;	643	$timer_fired->recv;
463		644
464	Example: wait for a timer, but take advantage of the fact that	645	Example: wait for a timer, but take advantage of the fact that condition
465	condition variables are also code references.	646	variables are also callable directly.
466		647
467	my $done = AnyEvent->condvar;	648	my $done = AnyEvent->condvar;
468	my $delay = AnyEvent->timer (after => 5, cb => $done);	649	my $delay = AnyEvent->timer (after => 5, cb => $done);
469	$done->recv;	650	$done->recv;
470		651
…		…
476		657
477	...	658	...
478		659
479	my @info = $couchdb->info->recv;	660	my @info = $couchdb->info->recv;
480		661
481	And this is how you would just ste a callback to be called whenever the	662	And this is how you would just set a callback to be called whenever the
482	results are available:	663	results are available:
483		664
484	$couchdb->info->cb (sub {	665	$couchdb->info->cb (sub {
485	my @info = $_[0]->recv;	666	my @info = $_[0]->recv;
486	});	667	});
…		…
504	immediately from within send.	685	immediately from within send.
505		686
506	Any arguments passed to the C<send> call will be returned by all	687	Any arguments passed to the C<send> call will be returned by all
507	future C<< ->recv >> calls.	688	future C<< ->recv >> calls.
508		689
509	Condition variables are overloaded so one can call them directly	690	Condition variables are overloaded so one can call them directly (as if
510	(as a code reference). Calling them directly is the same as calling	691	they were a code reference). Calling them directly is the same as calling
511	C<send>. Note, however, that many C-based event loops do not handle	692	C<send>.
512	overloading, so as tempting as it may be, passing a condition variable
513	instead of a callback does not work. Both the pure perl and EV loops
514	support overloading, however, as well as all functions that use perl to
515	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
516	example).
517		693
518	=item $cv->croak ($error)	694	=item $cv->croak ($error)
519		695
520	Similar to send, but causes all call's to C<< ->recv >> to invoke	696	Similar to send, but causes all calls to C<< ->recv >> to invoke
521	C<Carp::croak> with the given error message/object/scalar.	697	C<Carp::croak> with the given error message/object/scalar.
522		698
523	This can be used to signal any errors to the condition variable	699	This can be used to signal any errors to the condition variable
524	user/consumer.	700	user/consumer. Doing it this way instead of calling C<croak> directly
		701	delays the error detection, but has the overwhelming advantage that it
		702	diagnoses the error at the place where the result is expected, and not
		703	deep in some event callback with no connection to the actual code causing
		704	the problem.
525		705
526	=item $cv->begin ([group callback])	706	=item $cv->begin ([group callback])
527		707
528	=item $cv->end	708	=item $cv->end
529
530	These two methods are EXPERIMENTAL and MIGHT CHANGE.
531		709
532	These two methods can be used to combine many transactions/events into	710	These two methods can be used to combine many transactions/events into
533	one. For example, a function that pings many hosts in parallel might want	711	one. For example, a function that pings many hosts in parallel might want
534	to use a condition variable for the whole process.	712	to use a condition variable for the whole process.
535		713
536	Every call to C<< ->begin >> will increment a counter, and every call to	714	Every call to C<< ->begin >> will increment a counter, and every call to
537	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end	715	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
538	>>, the (last) callback passed to C<begin> will be executed. That callback	716	>>, the (last) callback passed to C<begin> will be executed, passing the
539	is I<supposed> to call C<< ->send >>, but that is not required. If no	717	condvar as first argument. That callback is I<supposed> to call C<< ->send
540	callback was set, C<send> will be called without any arguments.	718	>>, but that is not required. If no group callback was set, C<send> will
		719	be called without any arguments.
541		720
542	Let's clarify this with the ping example:	721	You can think of C<< $cv->send >> giving you an OR condition (one call
		722	sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
		723	condition (all C<begin> calls must be C<end>'ed before the condvar sends).
		724
		725	Let's start with a simple example: you have two I/O watchers (for example,
		726	STDOUT and STDERR for a program), and you want to wait for both streams to
		727	close before activating a condvar:
543		728
544	my $cv = AnyEvent->condvar;	729	my $cv = AnyEvent->condvar;
545		730
		731	$cv->begin; # first watcher
		732	my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
		733	defined sysread $fh1, my $buf, 4096
		734	or $cv->end;
		735	});
		736
		737	$cv->begin; # second watcher
		738	my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
		739	defined sysread $fh2, my $buf, 4096
		740	or $cv->end;
		741	});
		742
		743	$cv->recv;
		744
		745	This works because for every event source (EOF on file handle), there is
		746	one call to C<begin>, so the condvar waits for all calls to C<end> before
		747	sending.
		748
		749	The ping example mentioned above is slightly more complicated, as the
		750	there are results to be passwd back, and the number of tasks that are
		751	begun can potentially be zero:
		752
		753	my $cv = AnyEvent->condvar;
		754
546	my %result;	755	my %result;
547	$cv->begin (sub { $cv->send (\%result) });	756	$cv->begin (sub { shift->send (\%result) });
548		757
549	for my $host (@list_of_hosts) {	758	for my $host (@list_of_hosts) {
550	$cv->begin;	759	$cv->begin;
551	ping_host_then_call_callback $host, sub {	760	ping_host_then_call_callback $host, sub {
552	$result{$host} = ...;	761	$result{$host} = ...;
…		…
554	};	763	};
555	}	764	}
556		765
557	$cv->end;	766	$cv->end;
558		767
		768	...
		769
		770	my $results = $cv->recv;
		771
559	This code fragment supposedly pings a number of hosts and calls	772	This code fragment supposedly pings a number of hosts and calls
560	C<send> after results for all then have have been gathered - in any	773	C<send> after results for all then have have been gathered - in any
561	order. To achieve this, the code issues a call to C<begin> when it starts	774	order. To achieve this, the code issues a call to C<begin> when it starts
562	each ping request and calls C<end> when it has received some result for	775	each ping request and calls C<end> when it has received some result for
563	it. Since C<begin> and C<end> only maintain a counter, the order in which	776	it. Since C<begin> and C<end> only maintain a counter, the order in which
…		…
567	loop, which serves two important purposes: first, it sets the callback	780	loop, which serves two important purposes: first, it sets the callback
568	to be called once the counter reaches C<0>, and second, it ensures that	781	to be called once the counter reaches C<0>, and second, it ensures that
569	C<send> is called even when C<no> hosts are being pinged (the loop	782	C<send> is called even when C<no> hosts are being pinged (the loop
570	doesn't execute once).	783	doesn't execute once).
571		784
572	This is the general pattern when you "fan out" into multiple subrequests:	785	This is the general pattern when you "fan out" into multiple (but
573	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>	786	potentially zero) subrequests: use an outer C<begin>/C<end> pair to set
574	is called at least once, and then, for each subrequest you start, call	787	the callback and ensure C<end> is called at least once, and then, for each
575	C<begin> and for each subrequest you finish, call C<end>.	788	subrequest you start, call C<begin> and for each subrequest you finish,
		789	call C<end>.
576		790
577	=back	791	=back
578		792
579	=head3 METHODS FOR CONSUMERS	793	=head3 METHODS FOR CONSUMERS
580		794
…		…
584	=over 4	798	=over 4
585		799
586	=item $cv->recv	800	=item $cv->recv
587		801
588	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak	802	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
589	>> methods have been called on c<$cv>, while servicing other watchers	803	>> methods have been called on C<$cv>, while servicing other watchers
590	normally.	804	normally.
591		805
592	You can only wait once on a condition - additional calls are valid but	806	You can only wait once on a condition - additional calls are valid but
593	will return immediately.	807	will return immediately.
594		808
…		…
596	function will call C<croak>.	810	function will call C<croak>.
597		811
598	In list context, all parameters passed to C<send> will be returned,	812	In list context, all parameters passed to C<send> will be returned,
599	in scalar context only the first one will be returned.	813	in scalar context only the first one will be returned.
600		814
		815	Note that doing a blocking wait in a callback is not supported by any
		816	event loop, that is, recursive invocation of a blocking C<< ->recv >> is
		817	not allowed and the C<recv> call will C<croak> if such a condition is
		818	detected. This requirement can be dropped by relying on L<Coro::AnyEvent>
		819	, which allows you to do a blocking C<< ->recv >> from any thread
		820	that doesn't run the event loop itself. L<Coro::AnyEvent> is loaded
		821	automatically when L<Coro> is used with L<AnyEvent>, so code does not need
		822	to do anything special to take advantage of that: any code that would
		823	normally block your program because it calls C<recv>, be executed in an
		824	C<async> thread instead without blocking other threads.
		825
601	Not all event models support a blocking wait - some die in that case	826	Not all event models support a blocking wait - some die in that case
602	(programs might want to do that to stay interactive), so I<if you are	827	(programs might want to do that to stay interactive), so I<if you are
603	using this from a module, never require a blocking wait>, but let the	828	using this from a module, never require a blocking wait>. Instead, let the
604	caller decide whether the call will block or not (for example, by coupling	829	caller decide whether the call will block or not (for example, by coupling
605	condition variables with some kind of request results and supporting	830	condition variables with some kind of request results and supporting
606	callbacks so the caller knows that getting the result will not block,	831	callbacks so the caller knows that getting the result will not block,
607	while still supporting blocking waits if the caller so desires).	832	while still supporting blocking waits if the caller so desires).
608		833
609	Another reason I<never> to C<< ->recv >> in a module is that you cannot
610	sensibly have two C<< ->recv >>'s in parallel, as that would require
611	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
612	can supply.
613
614	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
615	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
616	versions and also integrates coroutines into AnyEvent, making blocking
617	C<< ->recv >> calls perfectly safe as long as they are done from another
618	coroutine (one that doesn't run the event loop).
619
620	You can ensure that C<< -recv >> never blocks by setting a callback and	834	You can ensure that C<< ->recv >> never blocks by setting a callback and
621	only calling C<< ->recv >> from within that callback (or at a later	835	only calling C<< ->recv >> from within that callback (or at a later
622	time). This will work even when the event loop does not support blocking	836	time). This will work even when the event loop does not support blocking
623	waits otherwise.	837	waits otherwise.
624		838
625	=item $bool = $cv->ready	839	=item $bool = $cv->ready
…		…
631		845
632	This is a mutator function that returns the callback set and optionally	846	This is a mutator function that returns the callback set and optionally
633	replaces it before doing so.	847	replaces it before doing so.
634		848
635	The callback will be called when the condition becomes "true", i.e. when	849	The callback will be called when the condition becomes "true", i.e. when
636	C<send> or C<croak> are called, with the only argument being the condition	850	C<send> or C<croak> are called, with the only argument being the
637	variable itself. Calling C<recv> inside the callback or at any later time	851	condition variable itself. If the condition is already true, the
638	is guaranteed not to block.	852	callback is called immediately when it is set. Calling C<recv> inside
		853	the callback or at any later time is guaranteed not to block.
639		854
640	=back	855	=back
641		856
		857	=head1 SUPPORTED EVENT LOOPS/BACKENDS
		858
		859	The available backend classes are (every class has its own manpage):
		860
		861	=over 4
		862
		863	=item Backends that are autoprobed when no other event loop can be found.
		864
		865	EV is the preferred backend when no other event loop seems to be in
		866	use. If EV is not installed, then AnyEvent will fall back to its own
		867	pure-perl implementation, which is available everywhere as it comes with
		868	AnyEvent itself.
		869
		870	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
		871	AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
		872
		873	=item Backends that are transparently being picked up when they are used.
		874
		875	These will be used if they are already loaded when the first watcher
		876	is created, in which case it is assumed that the application is using
		877	them. This means that AnyEvent will automatically pick the right backend
		878	when the main program loads an event module before anything starts to
		879	create watchers. Nothing special needs to be done by the main program.
		880
		881	AnyEvent::Impl::Event based on Event, very stable, few glitches.
		882	AnyEvent::Impl::Glib based on Glib, slow but very stable.
		883	AnyEvent::Impl::Tk based on Tk, very broken.
		884	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		885	AnyEvent::Impl::POE based on POE, very slow, some limitations.
		886	AnyEvent::Impl::Irssi used when running within irssi.
		887	AnyEvent::Impl::IOAsync based on IO::Async.
		888	AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
		889	AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding).
		890
		891	=item Backends with special needs.
		892
		893	Qt requires the Qt::Application to be instantiated first, but will
		894	otherwise be picked up automatically. As long as the main program
		895	instantiates the application before any AnyEvent watchers are created,
		896	everything should just work.
		897
		898	AnyEvent::Impl::Qt based on Qt.
		899
		900	=item Event loops that are indirectly supported via other backends.
		901
		902	Some event loops can be supported via other modules:
		903
		904	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		905
		906	B<WxWidgets> has no support for watching file handles. However, you can
		907	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		908	polls 20 times per second, which was considered to be too horrible to even
		909	consider for AnyEvent.
		910
		911	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		912	backend, so it can be supported through POE.
		913
		914	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		915	load L<POE> when detecting them, in the hope that POE will pick them up,
		916	in which case everything will be automatic.
		917
		918	=back
		919
642	=head1 GLOBAL VARIABLES AND FUNCTIONS	920	=head1 GLOBAL VARIABLES AND FUNCTIONS
643		921
		922	These are not normally required to use AnyEvent, but can be useful to
		923	write AnyEvent extension modules.
		924
644	=over 4	925	=over 4
645		926
646	=item $AnyEvent::MODEL	927	=item $AnyEvent::MODEL
647		928
648	Contains C<undef> until the first watcher is being created. Then it	929	Contains C<undef> until the first watcher is being created, before the
		930	backend has been autodetected.
		931
649	contains the event model that is being used, which is the name of the	932	Afterwards it contains the event model that is being used, which is the
650	Perl class implementing the model. This class is usually one of the	933	name of the Perl class implementing the model. This class is usually one
651	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	934	of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
652	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	935	case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
653		936	will be C<urxvt::anyevent>).
654	The known classes so far are:
655
656	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
657	AnyEvent::Impl::Event based on Event, second best choice.
658	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
659	AnyEvent::Impl::Glib based on Glib, third-best choice.
660	AnyEvent::Impl::Tk based on Tk, very bad choice.
661	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
662	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
663	AnyEvent::Impl::POE based on POE, not generic enough for full support.
664
665	There is no support for WxWidgets, as WxWidgets has no support for
666	watching file handles. However, you can use WxWidgets through the
667	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
668	second, which was considered to be too horrible to even consider for
669	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
670	it's adaptor.
671
672	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
673	autodetecting them.
674		937
675	=item AnyEvent::detect	938	=item AnyEvent::detect
676		939
677	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	940	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
678	if necessary. You should only call this function right before you would	941	if necessary. You should only call this function right before you would
679	have created an AnyEvent watcher anyway, that is, as late as possible at	942	have created an AnyEvent watcher anyway, that is, as late as possible at
680	runtime.	943	runtime, and not e.g. during initialisation of your module.
		944
		945	The effect of calling this function is as if a watcher had been created
		946	(specifically, actions that happen "when the first watcher is created"
		947	happen when calling detetc as well).
		948
		949	If you need to do some initialisation before AnyEvent watchers are
		950	created, use C<post_detect>.
681		951
682	=item $guard = AnyEvent::post_detect { BLOCK }	952	=item $guard = AnyEvent::post_detect { BLOCK }
683		953
684	Arranges for the code block to be executed as soon as the event model is	954	Arranges for the code block to be executed as soon as the event model is
685	autodetected (or immediately if this has already happened).	955	autodetected (or immediately if that has already happened).
		956
		957	The block will be executed I<after> the actual backend has been detected
		958	(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
		959	created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
		960	other initialisations - see the sources of L<AnyEvent::Strict> or
		961	L<AnyEvent::AIO> to see how this is used.
		962
		963	The most common usage is to create some global watchers, without forcing
		964	event module detection too early, for example, L<AnyEvent::AIO> creates
		965	and installs the global L<IO::AIO> watcher in a C<post_detect> block to
		966	avoid autodetecting the event module at load time.
686		967
687	If called in scalar or list context, then it creates and returns an object	968	If called in scalar or list context, then it creates and returns an object
688	that automatically removes the callback again when it is destroyed. See	969	that automatically removes the callback again when it is destroyed (or
		970	C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
689	L<Coro::BDB> for a case where this is useful.	971	a case where this is useful.
		972
		973	Example: Create a watcher for the IO::AIO module and store it in
		974	C<$WATCHER>, but do so only do so after the event loop is initialised.
		975
		976	our WATCHER;
		977
		978	my $guard = AnyEvent::post_detect {
		979	$WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
		980	};
		981
		982	# the ||= is important in case post_detect immediately runs the block,
		983	# as to not clobber the newly-created watcher. assigning both watcher and
		984	# post_detect guard to the same variable has the advantage of users being
		985	# able to just C<undef $WATCHER> if the watcher causes them grief.
		986
		987	$WATCHER ||= $guard;
690		988
691	=item @AnyEvent::post_detect	989	=item @AnyEvent::post_detect
692		990
693	If there are any code references in this array (you can C<push> to it	991	If there are any code references in this array (you can C<push> to it
694	before or after loading AnyEvent), then they will called directly after	992	before or after loading AnyEvent), then they will be called directly
695	the event loop has been chosen.	993	after the event loop has been chosen.
696		994
697	You should check C<$AnyEvent::MODEL> before adding to this array, though:	995	You should check C<$AnyEvent::MODEL> before adding to this array, though:
698	if it contains a true value then the event loop has already been detected,	996	if it is defined then the event loop has already been detected, and the
699	and the array will be ignored.	997	array will be ignored.
700		998
701	Best use C<AnyEvent::post_detect { BLOCK }> instead.	999	Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
		1000	it, as it takes care of these details.
		1001
		1002	This variable is mainly useful for modules that can do something useful
		1003	when AnyEvent is used and thus want to know when it is initialised, but do
		1004	not need to even load it by default. This array provides the means to hook
		1005	into AnyEvent passively, without loading it.
		1006
		1007	Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
		1008	together, you could put this into Coro (this is the actual code used by
		1009	Coro to accomplish this):
		1010
		1011	if (defined $AnyEvent::MODEL) {
		1012	# AnyEvent already initialised, so load Coro::AnyEvent
		1013	require Coro::AnyEvent;
		1014	} else {
		1015	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
		1016	# as soon as it is
		1017	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
		1018	}
		1019
		1020	=item AnyEvent::postpone { BLOCK }
		1021
		1022	Arranges for the block to be executed as soon as possible, but not before
		1023	the call itself returns. In practise, the block will be executed just
		1024	before the event loop polls for new events, or shortly afterwards.
		1025
		1026	This function never returns anything (to make the C<return postpone { ...
		1027	}> idiom more useful.
		1028
		1029	To understand the usefulness of this function, consider a function that
		1030	asynchronously does something for you and returns some transaction
		1031	object or guard to let you cancel the operation. For example,
		1032	C<AnyEvent::Socket::tcp_connect>:
		1033
		1034	# start a conenction attempt unless one is active
		1035	$self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
		1036	delete $self->{connect_guard};
		1037	...
		1038	};
		1039
		1040	Imagine that this function could instantly call the callback, for
		1041	example, because it detects an obvious error such as a negative port
		1042	number. Invoking the callback before the function returns causes problems
		1043	however: the callback will be called and will try to delete the guard
		1044	object. But since the function hasn't returned yet, there is nothing to
		1045	delete. When the function eventually returns it will assign the guard
		1046	object to C<< $self->{connect_guard} >>, where it will likely never be
		1047	deleted, so the program thinks it is still trying to connect.
		1048
		1049	This is where C<AnyEvent::postpone> should be used. Instead of calling the
		1050	callback directly on error:
		1051
		1052	$cb->(undef), return # signal error to callback, BAD!
		1053	if $some_error_condition;
		1054
		1055	It should use C<postpone>:
		1056
		1057	AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
		1058	if $some_error_condition;
		1059
		1060	=item AnyEvent::log $level, $msg[, @args]
		1061
		1062	Log the given C<$msg> at the given C<$level>.
		1063
		1064	If L<AnyEvent::Log> is not loaded then this function makes a simple test
		1065	to see whether the message will be logged. If the test succeeds it will
		1066	load AnyEvent::Log and call C<AnyEvent::Log::log> - consequently, look at
		1067	the L<AnyEvent::Log> documentation for details.
		1068
		1069	If the test fails it will simply return. Right now this happens when a
		1070	numerical loglevel is used and it is larger than the level specified via
		1071	C<$ENV{PERL_ANYEVENT_VERBOSE}>.
		1072
		1073	If you want to sprinkle loads of logging calls around your code, consider
		1074	creating a logger callback with the C<AnyEvent::Log::logger> function,
		1075	which can reduce typing, codesize and can reduce the logging overhead
		1076	enourmously.
702		1077
703	=back	1078	=back
704		1079
705	=head1 WHAT TO DO IN A MODULE	1080	=head1 WHAT TO DO IN A MODULE
706		1081
…		…
717	because it will stall the whole program, and the whole point of using	1092	because it will stall the whole program, and the whole point of using
718	events is to stay interactive.	1093	events is to stay interactive.
719		1094
720	It is fine, however, to call C<< ->recv >> when the user of your module	1095	It is fine, however, to call C<< ->recv >> when the user of your module
721	requests it (i.e. if you create a http request object ad have a method	1096	requests it (i.e. if you create a http request object ad have a method
722	called C<results> that returns the results, it should call C<< ->recv >>	1097	called C<results> that returns the results, it may call C<< ->recv >>
723	freely, as the user of your module knows what she is doing. always).	1098	freely, as the user of your module knows what she is doing. Always).
724		1099
725	=head1 WHAT TO DO IN THE MAIN PROGRAM	1100	=head1 WHAT TO DO IN THE MAIN PROGRAM
726		1101
727	There will always be a single main program - the only place that should	1102	There will always be a single main program - the only place that should
728	dictate which event model to use.	1103	dictate which event model to use.
729		1104
730	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	1105	If the program is not event-based, it need not do anything special, even
731	do anything special (it does not need to be event-based) and let AnyEvent	1106	when it depends on a module that uses an AnyEvent. If the program itself
732	decide which implementation to chose if some module relies on it.	1107	uses AnyEvent, but does not care which event loop is used, all it needs
		1108	to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
		1109	available loop implementation.
733		1110
734	If the main program relies on a specific event model - for example, in	1111	If the main program relies on a specific event model - for example, in
735	Gtk2 programs you have to rely on the Glib module - you should load the	1112	Gtk2 programs you have to rely on the Glib module - you should load the
736	event module before loading AnyEvent or any module that uses it: generally	1113	event module before loading AnyEvent or any module that uses it: generally
737	speaking, you should load it as early as possible. The reason is that	1114	speaking, you should load it as early as possible. The reason is that
738	modules might create watchers when they are loaded, and AnyEvent will	1115	modules might create watchers when they are loaded, and AnyEvent will
739	decide on the event model to use as soon as it creates watchers, and it	1116	decide on the event model to use as soon as it creates watchers, and it
740	might chose the wrong one unless you load the correct one yourself.	1117	might choose the wrong one unless you load the correct one yourself.
741		1118
742	You can chose to use a pure-perl implementation by loading the	1119	You can chose to use a pure-perl implementation by loading the
743	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour	1120	C<AnyEvent::Loop> module, which gives you similar behaviour
744	everywhere, but letting AnyEvent chose the model is generally better.	1121	everywhere, but letting AnyEvent chose the model is generally better.
745		1122
746	=head2 MAINLOOP EMULATION	1123	=head2 MAINLOOP EMULATION
747		1124
748	Sometimes (often for short test scripts, or even standalone programs who	1125	Sometimes (often for short test scripts, or even standalone programs who
…		…
761		1138
762		1139
763	=head1 OTHER MODULES	1140	=head1 OTHER MODULES
764		1141
765	The following is a non-exhaustive list of additional modules that use	1142	The following is a non-exhaustive list of additional modules that use
766	AnyEvent and can therefore be mixed easily with other AnyEvent modules	1143	AnyEvent as a client and can therefore be mixed easily with other
767	in the same program. Some of the modules come with AnyEvent, some are	1144	AnyEvent modules and other event loops in the same program. Some of the
768	available via CPAN.	1145	modules come as part of AnyEvent, the others are available via CPAN (see
		1146	L<http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for
		1147	a longer non-exhaustive list), and the list is heavily biased towards
		1148	modules of the AnyEvent author himself :)
769		1149
770	=over 4	1150	=over 4
771		1151
772	=item L<AnyEvent::Util>	1152	=item L<AnyEvent::Util>
773		1153
774	Contains various utility functions that replace often-used but blocking	1154	Contains various utility functions that replace often-used blocking
775	functions such as C<inet_aton> by event-/callback-based versions.	1155	functions such as C<inet_aton> with event/callback-based versions.
776		1156
777	=item L<AnyEvent::Socket>	1157	=item L<AnyEvent::Socket>
778		1158
779	Provides various utility functions for (internet protocol) sockets,	1159	Provides various utility functions for (internet protocol) sockets,
780	addresses and name resolution. Also functions to create non-blocking tcp	1160	addresses and name resolution. Also functions to create non-blocking tcp
…		…
782		1162
783	=item L<AnyEvent::Handle>	1163	=item L<AnyEvent::Handle>
784		1164
785	Provide read and write buffers, manages watchers for reads and writes,	1165	Provide read and write buffers, manages watchers for reads and writes,
786	supports raw and formatted I/O, I/O queued and fully transparent and	1166	supports raw and formatted I/O, I/O queued and fully transparent and
787	non-blocking SSL/TLS.	1167	non-blocking SSL/TLS (via L<AnyEvent::TLS>).
788		1168
789	=item L<AnyEvent::DNS>	1169	=item L<AnyEvent::DNS>
790		1170
791	Provides rich asynchronous DNS resolver capabilities.	1171	Provides rich asynchronous DNS resolver capabilities.
792		1172
		1173	=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
		1174
		1175	Implement event-based interfaces to the protocols of the same name (for
		1176	the curious, IGS is the International Go Server and FCP is the Freenet
		1177	Client Protocol).
		1178
793	=item L<AnyEvent::HTTP>	1179	=item L<AnyEvent::AIO>
794		1180
795	A simple-to-use HTTP library that is capable of making a lot of concurrent	1181	Truly asynchronous (as opposed to non-blocking) I/O, should be in the
796	HTTP requests.	1182	toolbox of every event programmer. AnyEvent::AIO transparently fuses
		1183	L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
		1184	file I/O, and much more.
		1185
		1186	=item L<AnyEvent::Filesys::Notify>
		1187
		1188	AnyEvent is good for non-blocking stuff, but it can't detect file or
		1189	path changes (e.g. "watch this directory for new files", "watch this
		1190	file for changes"). The L<AnyEvent::Filesys::Notify> module promises to
		1191	do just that in a portbale fashion, supporting inotify on GNU/Linux and
		1192	some weird, without doubt broken, stuff on OS X to monitor files. It can
		1193	fall back to blocking scans at regular intervals transparently on other
		1194	platforms, so it's about as portable as it gets.
		1195
		1196	(I haven't used it myself, but I haven't heard anybody complaining about
		1197	it yet).
		1198
		1199	=item L<AnyEvent::DBI>
		1200
		1201	Executes L<DBI> requests asynchronously in a proxy process for you,
		1202	notifying you in an event-based way when the operation is finished.
797		1203
798	=item L<AnyEvent::HTTPD>	1204	=item L<AnyEvent::HTTPD>
799		1205
800	Provides a simple web application server framework.	1206	A simple embedded webserver.
801		1207
802	=item L<AnyEvent::FastPing>	1208	=item L<AnyEvent::FastPing>
803		1209
804	The fastest ping in the west.	1210	The fastest ping in the west.
805		1211
806	=item L<AnyEvent::DBI>
807
808	Executes L<DBI> requests asynchronously in a proxy process.
809
810	=item L<AnyEvent::AIO>
811
812	Truly asynchronous I/O, should be in the toolbox of every event
813	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
814	together.
815
816	=item L<AnyEvent::BDB>
817
818	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
819	L<BDB> and AnyEvent together.
820
821	=item L<AnyEvent::GPSD>
822
823	A non-blocking interface to gpsd, a daemon delivering GPS information.
824
825	=item L<AnyEvent::IGS>
826
827	A non-blocking interface to the Internet Go Server protocol (used by
828	L<App::IGS>).
829
830	=item L<AnyEvent::IRC>
831
832	AnyEvent based IRC client module family (replacing the older Net::IRC3).
833
834	=item L<Net::XMPP2>
835
836	AnyEvent based XMPP (Jabber protocol) module family.
837
838	=item L<Net::FCP>
839
840	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
841	of AnyEvent.
842
843	=item L<Event::ExecFlow>
844
845	High level API for event-based execution flow control.
846
847	=item L<Coro>	1212	=item L<Coro>
848		1213
849	Has special support for AnyEvent via L<Coro::AnyEvent>.	1214	Has special support for AnyEvent via L<Coro::AnyEvent>, which allows you
		1215	to simply invert the flow control - don't call us, we will call you:
850		1216
851	=item L<IO::Lambda>	1217	async {
		1218	Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it
		1219	print "5 seconds later!\n";
852		1220
853	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	1221	Coro::AnyEvent::readable *STDIN; # uses an I/O watcher
		1222	my $line = <STDIN>; # works for ttys
		1223
		1224	AnyEvent::HTTP::http_get "url", Coro::rouse_cb;
		1225	my ($body, $hdr) = Coro::rouse_wait;
		1226	};
854		1227
855	=back	1228	=back
856		1229
857	=cut	1230	=cut
858		1231
859	package AnyEvent;	1232	package AnyEvent;
860		1233
861	no warnings;	1234	# basically a tuned-down version of common::sense
862	use strict qw(vars subs);	1235	sub common_sense {
		1236	# from common:.sense 3.5
		1237	local $^W;
		1238	${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
		1239	# use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
		1240	$^H |= 0x00000600;
		1241	}
863		1242
		1243	BEGIN { AnyEvent::common_sense }
		1244
864	use Carp;	1245	use Carp ();
865		1246
866	our $VERSION = 4.33;	1247	our $VERSION = '7.04';
867	our $MODEL;	1248	our $MODEL;
868
869	our $AUTOLOAD;
870	our @ISA;	1249	our @ISA;
871
872	our @REGISTRY;	1250	our @REGISTRY;
873		1251	our $VERBOSE;
874	our $WIN32;	1252	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
		1253	our $MAX_SIGNAL_LATENCY = $ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} || 10; # executes after the BEGIN block below (tainting!)
875		1254
876	BEGIN {	1255	BEGIN {
877	my $win32 = ! ! ($^O =~ /mswin32/i);	1256	require "AnyEvent/constants.pl";
878	eval "sub WIN32(){ $win32 }";
879	}
880		1257
881	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1258	eval "sub TAINT (){" . (${^TAINT}*1) . "}";
882		1259
883	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1260	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1261	if ${^TAINT};
884		1262
885	{	1263	$ENV{"PERL_ANYEVENT_$_"} = $ENV{"AE_$_"}
		1264	for grep s/^AE_// && !exists $ENV{"PERL_ANYEVENT_$_"}, keys %ENV;
		1265
		1266	@ENV{grep /^PERL_ANYEVENT_/, keys %ENV} = ()
		1267	if ${^TAINT};
		1268
		1269	# $ENV{PERL_ANYEVENT_xxx} now valid
		1270
		1271	$VERBOSE = length $ENV{PERL_ANYEVENT_VERBOSE} ? $ENV{PERL_ANYEVENT_VERBOSE}*1 : 4;
		1272
886	my $idx;	1273	my $idx;
887	$PROTOCOL{$_} = ++$idx	1274	$PROTOCOL{$_} = ++$idx
888	for reverse split /\s*,\s*/,	1275	for reverse split /\s*,\s*/,
889	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";	1276	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
890	}	1277	}
891		1278
		1279	our @post_detect;
		1280
		1281	sub post_detect(&) {
		1282	my ($cb) = @_;
		1283
		1284	push @post_detect, $cb;
		1285
		1286	defined wantarray
		1287	? bless \$cb, "AnyEvent::Util::postdetect"
		1288	: ()
		1289	}
		1290
		1291	sub AnyEvent::Util::postdetect::DESTROY {
		1292	@post_detect = grep $_ != ${$_[0]}, @post_detect;
		1293	}
		1294
		1295	our $POSTPONE_W;
		1296	our @POSTPONE;
		1297
		1298	sub _postpone_exec {
		1299	undef $POSTPONE_W;
		1300
		1301	&{ shift @POSTPONE }
		1302	while @POSTPONE;
		1303	}
		1304
		1305	sub postpone(&) {
		1306	push @POSTPONE, shift;
		1307
		1308	$POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
		1309
		1310	()
		1311	}
		1312
		1313	sub log($$;@) {
		1314	# only load the big bloated module when we actually are about to log something
		1315	if ($_[0] <= ($VERBOSE || 1)) { # also catches non-numeric levels(!) and fatal
		1316	local ($!, $@);
		1317	require AnyEvent::Log; # among other things, sets $VERBOSE to 9
		1318	# AnyEvent::Log overwrites this function
		1319	goto &log;
		1320	}
		1321
		1322	0 # not logged
		1323	}
		1324
		1325	sub _logger($;$) {
		1326	my ($level, $renabled) = @_;
		1327
		1328	$$renabled = $level <= $VERBOSE;
		1329
		1330	my $logger = [(caller)[0], $level, $renabled];
		1331
		1332	$AnyEvent::Log::LOGGER{$logger+0} = $logger;
		1333
		1334	# return unless defined wantarray;
		1335	#
		1336	# require AnyEvent::Util;
		1337	# my $guard = AnyEvent::Util::guard (sub {
		1338	# # "clean up"
		1339	# delete $LOGGER{$logger+0};
		1340	# });
		1341	#
		1342	# sub {
		1343	# return 0 unless $$renabled;
		1344	#
		1345	# $guard if 0; # keep guard alive, but don't cause runtime overhead
		1346	# require AnyEvent::Log unless $AnyEvent::Log::VERSION;
		1347	# package AnyEvent::Log;
		1348	# _log ($logger->[0], $level, @_) # logger->[0] has been converted at load time
		1349	# }
		1350	}
		1351
		1352	if (length $ENV{PERL_ANYEVENT_LOG}) {
		1353	require AnyEvent::Log; # AnyEvent::Log does the thing for us
		1354	}
		1355
892	my @models = (	1356	our @models = (
893	[EV:: => AnyEvent::Impl::EV::],	1357	[EV:: => AnyEvent::Impl::EV::],
894	[Event:: => AnyEvent::Impl::Event::],
895	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	1358	[AnyEvent::Loop:: => AnyEvent::Impl::Perl::],
896	# everything below here will not be autoprobed	1359	# everything below here will not (normally) be autoprobed
897	# as the pureperl backend should work everywhere	1360	# as the pure perl backend should work everywhere
898	# and is usually faster	1361	# and is usually faster
		1362	[Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package, so msut be near the top
		1363	[Event:: => AnyEvent::Impl::Event::], # slow, stable
		1364	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
		1365	# everything below here should not be autoloaded
		1366	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
899	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles	1367	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
900	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
901	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
902	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1368	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
903	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	1369	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
904	[Wx:: => AnyEvent::Impl::POE::],	1370	[Wx:: => AnyEvent::Impl::POE::],
905	[Prima:: => AnyEvent::Impl::POE::],	1371	[Prima:: => AnyEvent::Impl::POE::],
		1372	[IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # a bitch to autodetect
		1373	[Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
		1374	[FLTK:: => AnyEvent::Impl::FLTK::],
906	);	1375	);
907		1376
908	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);	1377	our @isa_hook;
909		1378
910	our @post_detect;	1379	sub _isa_set {
		1380	my @pkg = ("AnyEvent", (map $_->[0], grep defined, @isa_hook), $MODEL);
911		1381
		1382	@{"$pkg[$_-1]::ISA"} = $pkg[$_]
		1383	for 1 .. $#pkg;
		1384
		1385	grep $_ && $_->[1], @isa_hook
		1386	and AE::_reset ();
		1387	}
		1388
		1389	# used for hooking AnyEvent::Strict and AnyEvent::Debug::Wrap into the class hierarchy
		1390	sub _isa_hook($$;$) {
		1391	my ($i, $pkg, $reset_ae) = @_;
		1392
		1393	$isa_hook[$i] = $pkg ? [$pkg, $reset_ae] : undef;
		1394
		1395	_isa_set;
		1396	}
		1397
		1398	# all autoloaded methods reserve the complete glob, not just the method slot.
		1399	# due to bugs in perls method cache implementation.
		1400	our @methods = qw(io timer time now now_update signal child idle condvar);
		1401
912	sub post_detect(&) {	1402	sub detect() {
913	my ($cb) = @_;	1403	return $MODEL if $MODEL; # some programs keep references to detect
914		1404
915	if ($MODEL) {	1405	# IO::Async::Loop::AnyEvent is extremely evil, refuse to work with it
916	$cb->();	1406	# the author knows about the problems and what it does to AnyEvent as a whole
		1407	# (and the ability of others to use AnyEvent), but simply wants to abuse AnyEvent
		1408	# anyway.
		1409	AnyEvent::log fatal => "IO::Async::Loop::AnyEvent detected - that module is broken by\n"
		1410	. "design, abuses internals and breaks AnyEvent - will not continue."
		1411	if exists $INC{"IO/Async/Loop/AnyEvent.pm"};
917		1412
918	1	1413	local $!; # for good measure
		1414	local $SIG{__DIE__}; # we use eval
		1415
		1416	# free some memory
		1417	*detect = sub () { $MODEL };
		1418	# undef &func doesn't correctly update the method cache. grmbl.
		1419	# so we delete the whole glob. grmbl.
		1420	# otoh, perl doesn't let me undef an active usb, but it lets me free
		1421	# a glob with an active sub. hrm. i hope it works, but perl is
		1422	# usually buggy in this department. sigh.
		1423	delete @{"AnyEvent::"}{@methods};
		1424	undef @methods;
		1425
		1426	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z0-9:]+)$/) {
		1427	my $model = $1;
		1428	$model = "AnyEvent::Impl::$model" unless $model =~ s/::$//;
		1429	if (eval "require $model") {
		1430	AnyEvent::log 7 => "Loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.";
		1431	$MODEL = $model;
919	} else {	1432	} else {
920	push @post_detect, $cb;	1433	AnyEvent::log 4 => "Unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@";
921		1434	}
922	defined wantarray
923	? bless \$cb, "AnyEvent::Util::PostDetect"
924	: ()
925	}	1435	}
926	}
927		1436
928	sub AnyEvent::Util::PostDetect::DESTROY {	1437	# check for already loaded models
929	@post_detect = grep $_ != ${$_[0]}, @post_detect;
930	}
931
932	sub detect() {
933	unless ($MODEL) {	1438	unless ($MODEL) {
934	no strict 'refs';	1439	for (@REGISTRY, @models) {
935	local $SIG{__DIE__};	1440	my ($package, $model) = @$_;
936		1441	if (${"$package\::VERSION"} > 0) {
937	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
938	my $model = "AnyEvent::Impl::$1";
939	if (eval "require $model") {	1442	if (eval "require $model") {
		1443	AnyEvent::log 7 => "Autodetected model '$model', using it.";
940	$MODEL = $model;	1444	$MODEL = $model;
941	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;	1445	last;
942	} else {	1446	} else {
943	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;	1447	AnyEvent::log 8 => "Detected event loop $package, but cannot load '$model', skipping: $@";
		1448	}
944	}	1449	}
945	}	1450	}
946		1451
947	# check for already loaded models
948	unless ($MODEL) {	1452	unless ($MODEL) {
		1453	# try to autoload a model
949	for (@REGISTRY, @models) {	1454	for (@REGISTRY, @models) {
950	my ($package, $model) = @$_;	1455	my ($package, $model) = @$_;
		1456	if (
		1457	eval "require $package"
951	if (${"$package\::VERSION"} > 0) {	1458	and ${"$package\::VERSION"} > 0
952	if (eval "require $model") {	1459	and eval "require $model"
		1460	) {
		1461	AnyEvent::log 7 => "Autoloaded model '$model', using it.";
953	$MODEL = $model;	1462	$MODEL = $model;
954	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;
955	last;	1463	last;
956	}
957	}	1464	}
958	}	1465	}
959		1466
960	unless ($MODEL) {
961	# try to load a model
962
963	for (@REGISTRY, @models) {
964	my ($package, $model) = @$_;
965	if (eval "require $package"
966	and ${"$package\::VERSION"} > 0
967	and eval "require $model") {
968	$MODEL = $model;
969	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
970	last;
971	}
972	}
973
974	$MODEL	1467	$MODEL
975	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	1468	or AnyEvent::log fatal => "Backend autodetection failed - did you properly install AnyEvent?";
976	}
977	}	1469	}
978
979	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
980
981	unshift @ISA, $MODEL;
982
983	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
984
985	(shift @post_detect)->() while @post_detect;
986	}	1470	}
987		1471
		1472	# free memory only needed for probing
		1473	undef @models;
		1474	undef @REGISTRY;
		1475
		1476	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1477
		1478	# now nuke some methods that are overridden by the backend.
		1479	# SUPER usage is not allowed in these.
		1480	for (qw(time signal child idle)) {
		1481	undef &{"AnyEvent::Base::$_"}
		1482	if defined &{"$MODEL\::$_"};
		1483	}
		1484
		1485	_isa_set;
		1486
		1487	# we're officially open!
		1488
		1489	if ($ENV{PERL_ANYEVENT_STRICT}) {
		1490	require AnyEvent::Strict;
		1491	}
		1492
		1493	if ($ENV{PERL_ANYEVENT_DEBUG_WRAP}) {
		1494	require AnyEvent::Debug;
		1495	AnyEvent::Debug::wrap ($ENV{PERL_ANYEVENT_DEBUG_WRAP});
		1496	}
		1497
		1498	if (length $ENV{PERL_ANYEVENT_DEBUG_SHELL}) {
		1499	require AnyEvent::Socket;
		1500	require AnyEvent::Debug;
		1501
		1502	my $shell = $ENV{PERL_ANYEVENT_DEBUG_SHELL};
		1503	$shell =~ s/\$\$/$$/g;
		1504
		1505	my ($host, $service) = AnyEvent::Socket::parse_hostport ($shell);
		1506	$AnyEvent::Debug::SHELL = AnyEvent::Debug::shell ($host, $service);
		1507	}
		1508
		1509	# now the anyevent environment is set up as the user told us to, so
		1510	# call the actual user code - post detects
		1511
		1512	(shift @post_detect)->() while @post_detect;
		1513	undef @post_detect;
		1514
		1515	*post_detect = sub(&) {
		1516	shift->();
		1517
		1518	undef
		1519	};
		1520
988	$MODEL	1521	$MODEL
989	}	1522	}
990		1523
991	sub AUTOLOAD {	1524	for my $name (@methods) {
992	(my $func = $AUTOLOAD) =~ s/.*://;	1525	*$name = sub {
993		1526	detect;
994	$method{$func}	1527	# we use goto because
995	or croak "$func: not a valid method for AnyEvent objects";	1528	# a) it makes the thunk more transparent
996		1529	# b) it allows us to delete the thunk later
997	detect unless $MODEL;	1530	goto &{ UNIVERSAL::can AnyEvent => "SUPER::$name" }
998		1531	};
999	my $class = shift;
1000	$class->$func (@_);
1001	}	1532	}
1002		1533
1003	# utility function to dup a filehandle. this is used by many backends	1534	# utility function to dup a filehandle. this is used by many backends
1004	# to support binding more than one watcher per filehandle (they usually	1535	# to support binding more than one watcher per filehandle (they usually
1005	# allow only one watcher per fd, so we dup it to get a different one).	1536	# allow only one watcher per fd, so we dup it to get a different one).
1006	sub _dupfh($$$$) {	1537	sub _dupfh($$;$$) {
1007	my ($poll, $fh, $r, $w) = @_;	1538	my ($poll, $fh, $r, $w) = @_;
1008		1539
1009	require Fcntl;
1010
1011	# cygwin requires the fh mode to be matching, unix doesn't	1540	# cygwin requires the fh mode to be matching, unix doesn't
1012	my ($rw, $mode) = $poll eq "r" ? ($r, "<")	1541	my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
1013	: $poll eq "w" ? ($w, ">")
1014	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1015		1542
1016	open my $fh2, "$mode&" . fileno $fh	1543	open my $fh2, $mode, $fh
1017	or die "cannot dup() filehandle: $!";	1544	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
1018		1545
1019	# we assume CLOEXEC is already set by perl in all important cases	1546	# we assume CLOEXEC is already set by perl in all important cases
1020		1547
1021	($fh2, $rw)	1548	($fh2, $rw)
1022	}	1549	}
1023		1550
		1551	=head1 SIMPLIFIED AE API
		1552
		1553	Starting with version 5.0, AnyEvent officially supports a second, much
		1554	simpler, API that is designed to reduce the calling, typing and memory
		1555	overhead by using function call syntax and a fixed number of parameters.
		1556
		1557	See the L<AE> manpage for details.
		1558
		1559	=cut
		1560
		1561	package AE;
		1562
		1563	our $VERSION = $AnyEvent::VERSION;
		1564
		1565	sub _reset() {
		1566	eval q{
		1567	# fall back to the main API by default - backends and AnyEvent::Base
		1568	# implementations can overwrite these.
		1569
		1570	sub io($$$) {
		1571	AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
		1572	}
		1573
		1574	sub timer($$$) {
		1575	AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
		1576	}
		1577
		1578	sub signal($$) {
		1579	AnyEvent->signal (signal => $_[0], cb => $_[1])
		1580	}
		1581
		1582	sub child($$) {
		1583	AnyEvent->child (pid => $_[0], cb => $_[1])
		1584	}
		1585
		1586	sub idle($) {
		1587	AnyEvent->idle (cb => $_[0]);
		1588	}
		1589
		1590	sub cv(;&) {
		1591	AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
		1592	}
		1593
		1594	sub now() {
		1595	AnyEvent->now
		1596	}
		1597
		1598	sub now_update() {
		1599	AnyEvent->now_update
		1600	}
		1601
		1602	sub time() {
		1603	AnyEvent->time
		1604	}
		1605
		1606	*postpone = \&AnyEvent::postpone;
		1607	*log = \&AnyEvent::log;
		1608	};
		1609	die if $@;
		1610	}
		1611
		1612	BEGIN { _reset }
		1613
1024	package AnyEvent::Base;	1614	package AnyEvent::Base;
1025		1615
1026	# default implementation for now and time	1616	# default implementations for many methods
1027		1617
1028	BEGIN {	1618	sub time {
		1619	eval q{ # poor man's autoloading {}
		1620	# probe for availability of Time::HiRes
1029	if (eval "use Time::HiRes (); time (); 1") {	1621	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1622	*time = sub { Time::HiRes::time () };
1030	*_time = \&Time::HiRes::time;	1623	*AE::time = \& Time::HiRes::time ;
		1624	*now = \&time;
		1625	AnyEvent::log 8 => "using Time::HiRes for sub-second timing accuracy.";
1031	# if (eval "use POSIX (); (POSIX::times())...	1626	# if (eval "use POSIX (); (POSIX::times())...
1032	} else {	1627	} else {
1033	*_time = sub { time }; # epic fail	1628	*time = sub { CORE::time };
		1629	*AE::time = sub (){ CORE::time };
		1630	*now = \&time;
		1631	AnyEvent::log 3 => "Using built-in time(), no sub-second resolution!";
		1632	}
		1633	};
		1634	die if $@;
		1635
		1636	&time
		1637	}
		1638
		1639	*now = \&time;
		1640	sub now_update { }
		1641
		1642	sub _poll {
		1643	Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
		1644	}
		1645
		1646	# default implementation for ->condvar
		1647	# in fact, the default should not be overwritten
		1648
		1649	sub condvar {
		1650	eval q{ # poor man's autoloading {}
		1651	*condvar = sub {
		1652	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
		1653	};
		1654
		1655	*AE::cv = sub (;&) {
		1656	bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
		1657	};
		1658	};
		1659	die if $@;
		1660
		1661	&condvar
		1662	}
		1663
		1664	# default implementation for ->signal
		1665
		1666	our $HAVE_ASYNC_INTERRUPT;
		1667
		1668	sub _have_async_interrupt() {
		1669	$HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
		1670	&& eval "use Async::Interrupt 1.02 (); 1")
		1671	unless defined $HAVE_ASYNC_INTERRUPT;
		1672
		1673	$HAVE_ASYNC_INTERRUPT
		1674	}
		1675
		1676	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1677	our (%SIG_ASY, %SIG_ASY_W);
		1678	our ($SIG_COUNT, $SIG_TW);
		1679
		1680	# install a dummy wakeup watcher to reduce signal catching latency
		1681	# used by Impls
		1682	sub _sig_add() {
		1683	unless ($SIG_COUNT++) {
		1684	# try to align timer on a full-second boundary, if possible
		1685	my $NOW = AE::now;
		1686
		1687	$SIG_TW = AE::timer
		1688	$MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
		1689	$MAX_SIGNAL_LATENCY,
		1690	sub { } # just for the PERL_ASYNC_CHECK
		1691	;
1034	}	1692	}
1035	}	1693	}
1036		1694
1037	sub time { _time }	1695	sub _sig_del {
1038	sub now { _time }	1696	undef $SIG_TW
1039		1697	unless --$SIG_COUNT;
1040	# default implementation for ->condvar
1041
1042	sub condvar {
1043	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
1044	}	1698	}
1045		1699
1046	# default implementation for ->signal	1700	our $_sig_name_init; $_sig_name_init = sub {
		1701	eval q{ # poor man's autoloading {}
		1702	undef $_sig_name_init;
1047		1703
1048	our %SIG_CB;	1704	if (_have_async_interrupt) {
		1705	*sig2num = \&Async::Interrupt::sig2num;
		1706	*sig2name = \&Async::Interrupt::sig2name;
		1707	} else {
		1708	require Config;
		1709
		1710	my %signame2num;
		1711	@signame2num{ split ' ', $Config::Config{sig_name} }
		1712	= split ' ', $Config::Config{sig_num};
		1713
		1714	my @signum2name;
		1715	@signum2name[values %signame2num] = keys %signame2num;
		1716
		1717	*sig2num = sub($) {
		1718	$_[0] > 0 ? shift : $signame2num{+shift}
		1719	};
		1720	*sig2name = sub ($) {
		1721	$_[0] > 0 ? $signum2name[+shift] : shift
		1722	};
		1723	}
		1724	};
		1725	die if $@;
		1726	};
		1727
		1728	sub sig2num ($) { &$_sig_name_init; &sig2num }
		1729	sub sig2name($) { &$_sig_name_init; &sig2name }
1049		1730
1050	sub signal {	1731	sub signal {
		1732	eval q{ # poor man's autoloading {}
		1733	# probe for availability of Async::Interrupt
		1734	if (_have_async_interrupt) {
		1735	AnyEvent::log 8 => "Using Async::Interrupt for race-free signal handling.";
		1736
		1737	$SIGPIPE_R = new Async::Interrupt::EventPipe;
		1738	$SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
		1739
		1740	} else {
		1741	AnyEvent::log 8 => "Using emulated perl signal handling with latency timer.";
		1742
		1743	if (AnyEvent::WIN32) {
		1744	require AnyEvent::Util;
		1745
		1746	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1747	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
		1748	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
		1749	} else {
		1750	pipe $SIGPIPE_R, $SIGPIPE_W;
		1751	fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
		1752	fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
		1753
		1754	# not strictly required, as $^F is normally 2, but let's make sure...
		1755	fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1756	fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1757	}
		1758
		1759	$SIGPIPE_R
		1760	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1761
		1762	$SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
		1763	}
		1764
		1765	*signal = $HAVE_ASYNC_INTERRUPT
		1766	? sub {
1051	my (undef, %arg) = @_;	1767	my (undef, %arg) = @_;
1052		1768
		1769	# async::interrupt
1053	my $signal = uc $arg{signal}	1770	my $signal = sig2num $arg{signal};
1054	or Carp::croak "required option 'signal' is missing";
1055
1056	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1771	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1772
		1773	$SIG_ASY{$signal} ||= new Async::Interrupt
		1774	cb => sub { undef $SIG_EV{$signal} },
		1775	signal => $signal,
		1776	pipe => [$SIGPIPE_R->filenos],
		1777	pipe_autodrain => 0,
		1778	;
		1779
		1780	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1781	}
		1782	: sub {
		1783	my (undef, %arg) = @_;
		1784
		1785	# pure perl
		1786	my $signal = sig2name $arg{signal};
		1787	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1788
1057	$SIG{$signal} ||= sub {	1789	$SIG{$signal} ||= sub {
		1790	local $!;
		1791	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1792	undef $SIG_EV{$signal};
		1793	};
		1794
		1795	# can't do signal processing without introducing races in pure perl,
		1796	# so limit the signal latency.
		1797	_sig_add;
		1798
		1799	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1800	}
		1801	;
		1802
		1803	*AnyEvent::Base::signal::DESTROY = sub {
		1804	my ($signal, $cb) = @{$_[0]};
		1805
		1806	_sig_del;
		1807
		1808	delete $SIG_CB{$signal}{$cb};
		1809
		1810	$HAVE_ASYNC_INTERRUPT
		1811	? delete $SIG_ASY{$signal}
		1812	: # delete doesn't work with older perls - they then
		1813	# print weird messages, or just unconditionally exit
		1814	# instead of getting the default action.
		1815	undef $SIG{$signal}
		1816	unless keys %{ $SIG_CB{$signal} };
		1817	};
		1818
		1819	*_signal_exec = sub {
		1820	$HAVE_ASYNC_INTERRUPT
		1821	? $SIGPIPE_R->drain
		1822	: sysread $SIGPIPE_R, (my $dummy), 9;
		1823
		1824	while (%SIG_EV) {
		1825	for (keys %SIG_EV) {
		1826	delete $SIG_EV{$_};
1058	$_->() for values %{ $SIG_CB{$signal} || {} };	1827	&$_ for values %{ $SIG_CB{$_} || {} };
		1828	}
		1829	}
		1830	};
1059	};	1831	};
		1832	die if $@;
1060		1833
1061	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1834	&signal
1062	}
1063
1064	sub AnyEvent::Base::Signal::DESTROY {
1065	my ($signal, $cb) = @{$_[0]};
1066
1067	delete $SIG_CB{$signal}{$cb};
1068
1069	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1070	}	1835	}
1071		1836
1072	# default implementation for ->child	1837	# default implementation for ->child
1073		1838
1074	our %PID_CB;	1839	our %PID_CB;
1075	our $CHLD_W;	1840	our $CHLD_W;
1076	our $CHLD_DELAY_W;	1841	our $CHLD_DELAY_W;
1077	our $PID_IDLE;
1078	our $WNOHANG;
1079		1842
1080	sub _child_wait {	1843	# used by many Impl's
1081	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1844	sub _emit_childstatus($$) {
		1845	my (undef, $rpid, $rstatus) = @_;
		1846
		1847	$_->($rpid, $rstatus)
1082	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1848	for values %{ $PID_CB{$rpid} || {} },
1083	(values %{ $PID_CB{0} || {} });	1849	values %{ $PID_CB{0} || {} };
1084	}
1085
1086	undef $PID_IDLE;
1087	}
1088
1089	sub _sigchld {
1090	# make sure we deliver these changes "synchronous" with the event loop.
1091	$CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
1092	undef $CHLD_DELAY_W;
1093	&_child_wait;
1094	});
1095	}	1850	}
1096		1851
1097	sub child {	1852	sub child {
		1853	eval q{ # poor man's autoloading {}
		1854	*_sigchld = sub {
		1855	my $pid;
		1856
		1857	AnyEvent->_emit_childstatus ($pid, $?)
		1858	while ($pid = waitpid -1, WNOHANG) > 0;
		1859	};
		1860
		1861	*child = sub {
1098	my (undef, %arg) = @_;	1862	my (undef, %arg) = @_;
1099		1863
1100	defined (my $pid = $arg{pid} + 0)	1864	my $pid = $arg{pid};
1101	or Carp::croak "required option 'pid' is missing";	1865	my $cb = $arg{cb};
1102		1866
1103	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1867	$PID_CB{$pid}{$cb+0} = $cb;
1104		1868
1105	unless ($WNOHANG) {
1106	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1107	}
1108
1109	unless ($CHLD_W) {	1869	unless ($CHLD_W) {
1110	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1870	$CHLD_W = AE::signal CHLD => \&_sigchld;
1111	# child could be a zombie already, so make at least one round	1871	# child could be a zombie already, so make at least one round
1112	&_sigchld;	1872	&_sigchld;
1113	}	1873	}
1114		1874
1115	bless [$pid, $arg{cb}], "AnyEvent::Base::Child"	1875	bless [$pid, $cb+0], "AnyEvent::Base::child"
1116	}	1876	};
1117		1877
1118	sub AnyEvent::Base::Child::DESTROY {	1878	*AnyEvent::Base::child::DESTROY = sub {
1119	my ($pid, $cb) = @{$_[0]};	1879	my ($pid, $icb) = @{$_[0]};
1120		1880
1121	delete $PID_CB{$pid}{$cb};	1881	delete $PID_CB{$pid}{$icb};
1122	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1882	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1123		1883
1124	undef $CHLD_W unless keys %PID_CB;	1884	undef $CHLD_W unless keys %PID_CB;
		1885	};
		1886	};
		1887	die if $@;
		1888
		1889	&child
		1890	}
		1891
		1892	# idle emulation is done by simply using a timer, regardless
		1893	# of whether the process is idle or not, and not letting
		1894	# the callback use more than 50% of the time.
		1895	sub idle {
		1896	eval q{ # poor man's autoloading {}
		1897	*idle = sub {
		1898	my (undef, %arg) = @_;
		1899
		1900	my ($cb, $w, $rcb) = $arg{cb};
		1901
		1902	$rcb = sub {
		1903	if ($cb) {
		1904	$w = AE::time;
		1905	&$cb;
		1906	$w = AE::time - $w;
		1907
		1908	# never use more then 50% of the time for the idle watcher,
		1909	# within some limits
		1910	$w = 0.0001 if $w < 0.0001;
		1911	$w = 5 if $w > 5;
		1912
		1913	$w = AE::timer $w, 0, $rcb;
		1914	} else {
		1915	# clean up...
		1916	undef $w;
		1917	undef $rcb;
		1918	}
		1919	};
		1920
		1921	$w = AE::timer 0.05, 0, $rcb;
		1922
		1923	bless \\$cb, "AnyEvent::Base::idle"
		1924	};
		1925
		1926	*AnyEvent::Base::idle::DESTROY = sub {
		1927	undef $${$_[0]};
		1928	};
		1929	};
		1930	die if $@;
		1931
		1932	&idle
1125	}	1933	}
1126		1934
1127	package AnyEvent::CondVar;	1935	package AnyEvent::CondVar;
1128		1936
1129	our @ISA = AnyEvent::CondVar::Base::;	1937	our @ISA = AnyEvent::CondVar::Base::;
1130		1938
		1939	# only to be used for subclassing
		1940	sub new {
		1941	my $class = shift;
		1942	bless AnyEvent->condvar (@_), $class
		1943	}
		1944
1131	package AnyEvent::CondVar::Base;	1945	package AnyEvent::CondVar::Base;
1132		1946
1133	use overload	1947	#use overload
1134	'&{}' => sub { my $self = shift; sub { $self->send (@_) } },	1948	# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1135	fallback => 1;	1949	# fallback => 1;
		1950
		1951	# save 300+ kilobytes by dirtily hardcoding overloading
		1952	${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
		1953	*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
		1954	*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
		1955	${'AnyEvent::CondVar::Base::()'} = 1; # fallback
		1956
		1957	our $WAITING;
1136		1958
1137	sub _send {	1959	sub _send {
1138	# nop	1960	# nop
		1961	}
		1962
		1963	sub _wait {
		1964	AnyEvent->_poll until $_[0]{_ae_sent};
1139	}	1965	}
1140		1966
1141	sub send {	1967	sub send {
1142	my $cv = shift;	1968	my $cv = shift;
1143	$cv->{_ae_sent} = [@_];	1969	$cv->{_ae_sent} = [@_];
…		…
1152		1978
1153	sub ready {	1979	sub ready {
1154	$_[0]{_ae_sent}	1980	$_[0]{_ae_sent}
1155	}	1981	}
1156		1982
1157	sub _wait {
1158	AnyEvent->one_event while !$_[0]{_ae_sent};
1159	}
1160
1161	sub recv {	1983	sub recv {
		1984	unless ($_[0]{_ae_sent}) {
		1985	$WAITING
		1986	and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
		1987
		1988	local $WAITING = 1;
1162	$_[0]->_wait;	1989	$_[0]->_wait;
		1990	}
1163		1991
1164	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};	1992	$_[0]{_ae_croak}
1165	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]	1993	and Carp::croak $_[0]{_ae_croak};
		1994
		1995	wantarray
		1996	? @{ $_[0]{_ae_sent} }
		1997	: $_[0]{_ae_sent}[0]
1166	}	1998	}
1167		1999
1168	sub cb {	2000	sub cb {
1169	$_[0]{_ae_cb} = $_[1] if @_ > 1;	2001	my $cv = shift;
		2002
		2003	@_
		2004	and $cv->{_ae_cb} = shift
		2005	and $cv->{_ae_sent}
		2006	and (delete $cv->{_ae_cb})->($cv);
		2007
1170	$_[0]{_ae_cb}	2008	$cv->{_ae_cb}
1171	}	2009	}
1172		2010
1173	sub begin {	2011	sub begin {
1174	++$_[0]{_ae_counter};	2012	++$_[0]{_ae_counter};
1175	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;	2013	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;
…		…
1180	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };	2018	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1181	}	2019	}
1182		2020
1183	# undocumented/compatibility with pre-3.4	2021	# undocumented/compatibility with pre-3.4
1184	*broadcast = \&send;	2022	*broadcast = \&send;
1185	*wait = \&_wait;	2023	*wait = \&recv;
1186		2024
1187	=head1 ERROR AND EXCEPTION HANDLING	2025	=head1 ERROR AND EXCEPTION HANDLING
1188		2026
1189	In general, AnyEvent does not do any error handling - it relies on the	2027	In general, AnyEvent does not do any error handling - it relies on the
1190	caller to do that if required. The L<AnyEvent::Strict> module (see also	2028	caller to do that if required. The L<AnyEvent::Strict> module (see also
…		…
1202	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and	2040	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
1203	so on.	2041	so on.
1204		2042
1205	=head1 ENVIRONMENT VARIABLES	2043	=head1 ENVIRONMENT VARIABLES
1206		2044
1207	The following environment variables are used by this module or its	2045	AnyEvent supports a number of environment variables that tune the
1208	submodules:	2046	runtime behaviour. They are usually evaluated when AnyEvent is
		2047	loaded, initialised, or a submodule that uses them is loaded. Many of
		2048	them also cause AnyEvent to load additional modules - for example,
		2049	C<PERL_ANYEVENT_DEBUG_WRAP> causes the L<AnyEvent::Debug> module to be
		2050	loaded.
		2051
		2052	All the environment variables documented here start with
		2053	C<PERL_ANYEVENT_>, which is what AnyEvent considers its own
		2054	namespace. Other modules are encouraged (but by no means required) to use
		2055	C<PERL_ANYEVENT_SUBMODULE> if they have registered the AnyEvent::Submodule
		2056	namespace on CPAN, for any submodule. For example, L<AnyEvent::HTTP> could
		2057	be expected to use C<PERL_ANYEVENT_HTTP_PROXY> (it should not access env
		2058	variables starting with C<AE_>, see below).
		2059
		2060	All variables can also be set via the C<AE_> prefix, that is, instead
		2061	of setting C<PERL_ANYEVENT_VERBOSE> you can also set C<AE_VERBOSE>. In
		2062	case there is a clash btween anyevent and another program that uses
		2063	C<AE_something> you can set the corresponding C<PERL_ANYEVENT_something>
		2064	variable to the empty string, as those variables take precedence.
		2065
		2066	When AnyEvent is first loaded, it copies all C<AE_xxx> env variables
		2067	to their C<PERL_ANYEVENT_xxx> counterpart unless that variable already
		2068	exists. If taint mode is on, then AnyEvent will remove I<all> environment
		2069	variables starting with C<PERL_ANYEVENT_> from C<%ENV> (or replace them
		2070	with C<undef> or the empty string, if the corresaponding C<AE_> variable
		2071	is set).
		2072
		2073	The exact algorithm is currently:
		2074
		2075	1. if taint mode enabled, delete all PERL_ANYEVENT_xyz variables from %ENV
		2076	2. copy over AE_xyz to PERL_ANYEVENT_xyz unless the latter alraedy exists
		2077	3. if taint mode enabled, set all PERL_ANYEVENT_xyz variables to undef.
		2078
		2079	This ensures that child processes will not see the C<AE_> variables.
		2080
		2081	The following environment variables are currently known to AnyEvent:
1209		2082
1210	=over 4	2083	=over 4
1211		2084
1212	=item C<PERL_ANYEVENT_VERBOSE>	2085	=item C<PERL_ANYEVENT_VERBOSE>
1213		2086
1214	By default, AnyEvent will be completely silent except in fatal	2087	By default, AnyEvent will log messages with loglevel C<4> (C<error>) or
1215	conditions. You can set this environment variable to make AnyEvent more	2088	higher (see L<AnyEvent::Log>). You can set this environment variable to a
1216	talkative.	2089	numerical loglevel to make AnyEvent more (or less) talkative.
1217		2090
		2091	If you want to do more than just set the global logging level
		2092	you should have a look at C<PERL_ANYEVENT_LOG>, which allows much more
		2093	complex specifications.
		2094
		2095	When set to C<0> (C<off>), then no messages whatsoever will be logged with
		2096	everything else at defaults.
		2097
1218	When set to C<1> or higher, causes AnyEvent to warn about unexpected	2098	When set to C<5> or higher (C<warn>), AnyEvent warns about unexpected
1219	conditions, such as not being able to load the event model specified by	2099	conditions, such as not being able to load the event model specified by
1220	C<PERL_ANYEVENT_MODEL>.	2100	C<PERL_ANYEVENT_MODEL>, or a guard callback throwing an exception - this
		2101	is the minimum recommended level for use during development.
1221		2102
1222	When set to C<2> or higher, cause AnyEvent to report to STDERR which event	2103	When set to C<7> or higher (info), AnyEvent reports which event model it
1223	model it chooses.	2104	chooses.
		2105
		2106	When set to C<8> or higher (debug), then AnyEvent will report extra
		2107	information on which optional modules it loads and how it implements
		2108	certain features.
		2109
		2110	=item C<PERL_ANYEVENT_LOG>
		2111
		2112	Accepts rather complex logging specifications. For example, you could log
		2113	all C<debug> messages of some module to stderr, warnings and above to
		2114	stderr, and errors and above to syslog, with:
		2115
		2116	PERL_ANYEVENT_LOG=Some::Module=debug,+log:filter=warn,+%syslog:%syslog=error,syslog
		2117
		2118	For the rather extensive details, see L<AnyEvent::Log>.
		2119
		2120	This variable is evaluated when AnyEvent (or L<AnyEvent::Log>) is loaded,
		2121	so will take effect even before AnyEvent has initialised itself.
		2122
		2123	Note that specifying this environment variable causes the L<AnyEvent::Log>
		2124	module to be loaded, while C<PERL_ANYEVENT_VERBOSE> does not, so only
		2125	using the latter saves a few hundred kB of memory unless a module
		2126	explicitly needs the extra features of AnyEvent::Log.
1224		2127
1225	=item C<PERL_ANYEVENT_STRICT>	2128	=item C<PERL_ANYEVENT_STRICT>
1226		2129
1227	AnyEvent does not do much argument checking by default, as thorough	2130	AnyEvent does not do much argument checking by default, as thorough
1228	argument checking is very costly. Setting this variable to a true value	2131	argument checking is very costly. Setting this variable to a true value
1229	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly	2132	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1230	check the arguments passed to most method calls. If it finds any problems	2133	check the arguments passed to most method calls. If it finds any problems,
1231	it will croak.	2134	it will croak.
1232		2135
1233	In other words, enables "strict" mode.	2136	In other words, enables "strict" mode.
1234		2137
1235	Unlike C<use strict>, it is definitely recommended ot keep it off in	2138	Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
1236	production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while	2139	>>, it is definitely recommended to keep it off in production. Keeping
1237	developing programs can be very useful, however.	2140	C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
		2141	can be very useful, however.
		2142
		2143	=item C<PERL_ANYEVENT_DEBUG_SHELL>
		2144
		2145	If this env variable is nonempty, then its contents will be interpreted by
		2146	C<AnyEvent::Socket::parse_hostport> and C<AnyEvent::Debug::shell> (after
		2147	replacing every occurance of C<$$> by the process pid). The shell object
		2148	is saved in C<$AnyEvent::Debug::SHELL>.
		2149
		2150	This happens when the first watcher is created.
		2151
		2152	For example, to bind a debug shell on a unix domain socket in
		2153	F<< /tmp/debug<pid>.sock >>, you could use this:
		2154
		2155	PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog
		2156	# connect with e.g.: socat readline /tmp/debug123.sock
		2157
		2158	Or to bind to tcp port 4545 on localhost:
		2159
		2160	PERL_ANYEVENT_DEBUG_SHELL=127.0.0.1:4545 perlprog
		2161	# connect with e.g.: telnet localhost 4545
		2162
		2163	Note that creating sockets in F</tmp> or on localhost is very unsafe on
		2164	multiuser systems.
		2165
		2166	=item C<PERL_ANYEVENT_DEBUG_WRAP>
		2167
		2168	Can be set to C<0>, C<1> or C<2> and enables wrapping of all watchers for
		2169	debugging purposes. See C<AnyEvent::Debug::wrap> for details.
1238		2170
1239	=item C<PERL_ANYEVENT_MODEL>	2171	=item C<PERL_ANYEVENT_MODEL>
1240		2172
1241	This can be used to specify the event model to be used by AnyEvent, before	2173	This can be used to specify the event model to be used by AnyEvent, before
1242	auto detection and -probing kicks in. It must be a string consisting	2174	auto detection and -probing kicks in.
1243	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended	2175
		2176	It normally is a string consisting entirely of ASCII letters (e.g. C<EV>
		2177	or C<IOAsync>). The string C<AnyEvent::Impl::> gets prepended and the
1244	and the resulting module name is loaded and if the load was successful,	2178	resulting module name is loaded and - if the load was successful - used as
1245	used as event model. If it fails to load AnyEvent will proceed with	2179	event model backend. If it fails to load then AnyEvent will proceed with
1246	auto detection and -probing.	2180	auto detection and -probing.
1247		2181
1248	This functionality might change in future versions.	2182	If the string ends with C<::> instead (e.g. C<AnyEvent::Impl::EV::>) then
		2183	nothing gets prepended and the module name is used as-is (hint: C<::> at
		2184	the end of a string designates a module name and quotes it appropriately).
1249		2185
1250	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you	2186	For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
1251	could start your program like this:	2187	could start your program like this:
1252		2188
1253	PERL_ANYEVENT_MODEL=Perl perl ...	2189	PERL_ANYEVENT_MODEL=Perl perl ...
		2190
		2191	=item C<PERL_ANYEVENT_IO_MODEL>
		2192
		2193	The current file I/O model - see L<AnyEvent::IO> for more info.
		2194
		2195	At the moment, only C<Perl> (small, pure-perl, synchronous) and
		2196	C<IOAIO> (truly asynchronous) are supported. The default is C<IOAIO> if
		2197	L<AnyEvent::AIO> can be loaded, otherwise it is C<Perl>.
1254		2198
1255	=item C<PERL_ANYEVENT_PROTOCOLS>	2199	=item C<PERL_ANYEVENT_PROTOCOLS>
1256		2200
1257	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences	2201	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1258	for IPv4 or IPv6. The default is unspecified (and might change, or be the result	2202	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
…		…
1263	used, and preference will be given to protocols mentioned earlier in the	2207	used, and preference will be given to protocols mentioned earlier in the
1264	list.	2208	list.
1265		2209
1266	This variable can effectively be used for denial-of-service attacks	2210	This variable can effectively be used for denial-of-service attacks
1267	against local programs (e.g. when setuid), although the impact is likely	2211	against local programs (e.g. when setuid), although the impact is likely
1268	small, as the program has to handle connection errors already-	2212	small, as the program has to handle conenction and other failures anyways.
1269		2213
1270	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,	2214	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1271	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>	2215	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1272	- only support IPv4, never try to resolve or contact IPv6	2216	- only support IPv4, never try to resolve or contact IPv6
1273	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or	2217	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1274	IPv6, but prefer IPv6 over IPv4.	2218	IPv6, but prefer IPv6 over IPv4.
1275		2219
		2220	=item C<PERL_ANYEVENT_HOSTS>
		2221
		2222	This variable, if specified, overrides the F</etc/hosts> file used by
		2223	L<AnyEvent::Socket>C<::resolve_sockaddr>, i.e. hosts aliases will be read
		2224	from that file instead.
		2225
1276	=item C<PERL_ANYEVENT_EDNS0>	2226	=item C<PERL_ANYEVENT_EDNS0>
1277		2227
1278	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension	2228	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension for
1279	for DNS. This extension is generally useful to reduce DNS traffic, but	2229	DNS. This extension is generally useful to reduce DNS traffic, especially
1280	some (broken) firewalls drop such DNS packets, which is why it is off by	2230	when DNSSEC is involved, but some (broken) firewalls drop such DNS
1281	default.	2231	packets, which is why it is off by default.
1282		2232
1283	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce	2233	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1284	EDNS0 in its DNS requests.	2234	EDNS0 in its DNS requests.
1285		2235
1286	=item C<PERL_ANYEVENT_MAX_FORKS>	2236	=item C<PERL_ANYEVENT_MAX_FORKS>
1287		2237
1288	The maximum number of child processes that C<AnyEvent::Util::fork_call>	2238	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1289	will create in parallel.	2239	will create in parallel.
		2240
		2241	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		2242
		2243	The default value for the C<max_outstanding> parameter for the default DNS
		2244	resolver - this is the maximum number of parallel DNS requests that are
		2245	sent to the DNS server.
		2246
		2247	=item C<PERL_ANYEVENT_MAX_SIGNAL_LATENCY>
		2248
		2249	Perl has inherently racy signal handling (you can basically choose between
		2250	losing signals and memory corruption) - pure perl event loops (including
		2251	C<AnyEvent::Loop>, when C<Async::Interrupt> isn't available) therefore
		2252	have to poll regularly to avoid losing signals.
		2253
		2254	Some event loops are racy, but don't poll regularly, and some event loops
		2255	are written in C but are still racy. For those event loops, AnyEvent
		2256	installs a timer that regularly wakes up the event loop.
		2257
		2258	By default, the interval for this timer is C<10> seconds, but you can
		2259	override this delay with this environment variable (or by setting
		2260	the C<$AnyEvent::MAX_SIGNAL_LATENCY> variable before creating signal
		2261	watchers).
		2262
		2263	Lower values increase CPU (and energy) usage, higher values can introduce
		2264	long delays when reaping children or waiting for signals.
		2265
		2266	The L<AnyEvent::Async> module, if available, will be used to avoid this
		2267	polling (with most event loops).
		2268
		2269	=item C<PERL_ANYEVENT_RESOLV_CONF>
		2270
		2271	The absolute path to a F<resolv.conf>-style file to use instead of
		2272	F</etc/resolv.conf> (or the OS-specific configuration) in the default
		2273	resolver, or the empty string to select the default configuration.
		2274
		2275	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		2276
		2277	When neither C<ca_file> nor C<ca_path> was specified during
		2278	L<AnyEvent::TLS> context creation, and either of these environment
		2279	variables are nonempty, they will be used to specify CA certificate
		2280	locations instead of a system-dependent default.
		2281
		2282	=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
		2283
		2284	When these are set to C<1>, then the respective modules are not
		2285	loaded. Mostly good for testing AnyEvent itself.
1290		2286
1291	=back	2287	=back
1292		2288
1293	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	2289	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1294		2290
…		…
1352	warn "read: $input\n"; # output what has been read	2348	warn "read: $input\n"; # output what has been read
1353	$cv->send if $input =~ /^q/i; # quit program if /^q/i	2349	$cv->send if $input =~ /^q/i; # quit program if /^q/i
1354	},	2350	},
1355	);	2351	);
1356		2352
1357	my $time_watcher; # can only be used once
1358
1359	sub new_timer {
1360	$timer = AnyEvent->timer (after => 1, cb => sub {	2353	my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1361	warn "timeout\n"; # print 'timeout' about every second	2354	warn "timeout\n"; # print 'timeout' at most every second
1362	&new_timer; # and restart the time
1363	});	2355	});
1364	}
1365
1366	new_timer; # create first timer
1367		2356
1368	$cv->recv; # wait until user enters /^q/i	2357	$cv->recv; # wait until user enters /^q/i
1369		2358
1370	=head1 REAL-WORLD EXAMPLE	2359	=head1 REAL-WORLD EXAMPLE
1371		2360
…		…
1444		2433
1445	The actual code goes further and collects all errors (C<die>s, exceptions)	2434	The actual code goes further and collects all errors (C<die>s, exceptions)
1446	that occurred during request processing. The C<result> method detects	2435	that occurred during request processing. The C<result> method detects
1447	whether an exception as thrown (it is stored inside the $txn object)	2436	whether an exception as thrown (it is stored inside the $txn object)
1448	and just throws the exception, which means connection errors and other	2437	and just throws the exception, which means connection errors and other
1449	problems get reported tot he code that tries to use the result, not in a	2438	problems get reported to the code that tries to use the result, not in a
1450	random callback.	2439	random callback.
1451		2440
1452	All of this enables the following usage styles:	2441	All of this enables the following usage styles:
1453		2442
1454	1. Blocking:	2443	1. Blocking:
…		…
1502	through AnyEvent. The benchmark creates a lot of timers (with a zero	2491	through AnyEvent. The benchmark creates a lot of timers (with a zero
1503	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,	2492	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1504	which it is), lets them fire exactly once and destroys them again.	2493	which it is), lets them fire exactly once and destroys them again.
1505		2494
1506	Source code for this benchmark is found as F<eg/bench> in the AnyEvent	2495	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1507	distribution.	2496	distribution. It uses the L<AE> interface, which makes a real difference
		2497	for the EV and Perl backends only.
1508		2498
1509	=head3 Explanation of the columns	2499	=head3 Explanation of the columns
1510		2500
1511	I<watcher> is the number of event watchers created/destroyed. Since	2501	I<watcher> is the number of event watchers created/destroyed. Since
1512	different event models feature vastly different performances, each event	2502	different event models feature vastly different performances, each event
…		…
1533	watcher.	2523	watcher.
1534		2524
1535	=head3 Results	2525	=head3 Results
1536		2526
1537	name watchers bytes create invoke destroy comment	2527	name watchers bytes create invoke destroy comment
1538	EV/EV 400000 224 0.47 0.35 0.27 EV native interface	2528	EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1539	EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers	2529	EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1540	CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal	2530	Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1541	Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation	2531	Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1542	Event/Event 16000 517 32.20 31.80 0.81 Event native interface	2532	Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1543	Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers	2533	Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
		2534	IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
		2535	IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1544	Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour	2536	Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1545	Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers	2537	Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1546	POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event	2538	POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1547	POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select	2539	POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1548		2540
1549	=head3 Discussion	2541	=head3 Discussion
1550		2542
1551	The benchmark does I<not> measure scalability of the event loop very	2543	The benchmark does I<not> measure scalability of the event loop very
1552	well. For example, a select-based event loop (such as the pure perl one)	2544	well. For example, a select-based event loop (such as the pure perl one)
…		…
1564	benchmark machine, handling an event takes roughly 1600 CPU cycles with	2556	benchmark machine, handling an event takes roughly 1600 CPU cycles with
1565	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU	2557	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1566	cycles with POE.	2558	cycles with POE.
1567		2559
1568	C<EV> is the sole leader regarding speed and memory use, which are both	2560	C<EV> is the sole leader regarding speed and memory use, which are both
1569	maximal/minimal, respectively. Even when going through AnyEvent, it uses	2561	maximal/minimal, respectively. When using the L<AE> API there is zero
		2562	overhead (when going through the AnyEvent API create is about 5-6 times
		2563	slower, with other times being equal, so still uses far less memory than
1570	far less memory than any other event loop and is still faster than Event	2564	any other event loop and is still faster than Event natively).
1571	natively.
1572		2565
1573	The pure perl implementation is hit in a few sweet spots (both the	2566	The pure perl implementation is hit in a few sweet spots (both the
1574	constant timeout and the use of a single fd hit optimisations in the perl	2567	constant timeout and the use of a single fd hit optimisations in the perl
1575	interpreter and the backend itself). Nevertheless this shows that it	2568	interpreter and the backend itself). Nevertheless this shows that it
1576	adds very little overhead in itself. Like any select-based backend its	2569	adds very little overhead in itself. Like any select-based backend its
1577	performance becomes really bad with lots of file descriptors (and few of	2570	performance becomes really bad with lots of file descriptors (and few of
1578	them active), of course, but this was not subject of this benchmark.	2571	them active), of course, but this was not subject of this benchmark.
1579		2572
1580	The C<Event> module has a relatively high setup and callback invocation	2573	The C<Event> module has a relatively high setup and callback invocation
1581	cost, but overall scores in on the third place.	2574	cost, but overall scores in on the third place.
		2575
		2576	C<IO::Async> performs admirably well, about on par with C<Event>, even
		2577	when using its pure perl backend.
1582		2578
1583	C<Glib>'s memory usage is quite a bit higher, but it features a	2579	C<Glib>'s memory usage is quite a bit higher, but it features a
1584	faster callback invocation and overall ends up in the same class as	2580	faster callback invocation and overall ends up in the same class as
1585	C<Event>. However, Glib scales extremely badly, doubling the number of	2581	C<Event>. However, Glib scales extremely badly, doubling the number of
1586	watchers increases the processing time by more than a factor of four,	2582	watchers increases the processing time by more than a factor of four,
…		…
1621	(even when used without AnyEvent), but most event loops have acceptable	2617	(even when used without AnyEvent), but most event loops have acceptable
1622	performance with or without AnyEvent.	2618	performance with or without AnyEvent.
1623		2619
1624	=item * The overhead AnyEvent adds is usually much smaller than the overhead of	2620	=item * The overhead AnyEvent adds is usually much smaller than the overhead of
1625	the actual event loop, only with extremely fast event loops such as EV	2621	the actual event loop, only with extremely fast event loops such as EV
1626	adds AnyEvent significant overhead.	2622	does AnyEvent add significant overhead.
1627		2623
1628	=item * You should avoid POE like the plague if you want performance or	2624	=item * You should avoid POE like the plague if you want performance or
1629	reasonable memory usage.	2625	reasonable memory usage.
1630		2626
1631	=back	2627	=back
…		…
1647	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100	2643	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1648	(1%) are active. This mirrors the activity of large servers with many	2644	(1%) are active. This mirrors the activity of large servers with many
1649	connections, most of which are idle at any one point in time.	2645	connections, most of which are idle at any one point in time.
1650		2646
1651	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent	2647	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1652	distribution.	2648	distribution. It uses the L<AE> interface, which makes a real difference
		2649	for the EV and Perl backends only.
1653		2650
1654	=head3 Explanation of the columns	2651	=head3 Explanation of the columns
1655		2652
1656	I<sockets> is the number of sockets, and twice the number of "servers" (as	2653	I<sockets> is the number of sockets, and twice the number of "servers" (as
1657	each server has a read and write socket end).	2654	each server has a read and write socket end).
…		…
1664	it to another server. This includes deleting the old timeout and creating	2661	it to another server. This includes deleting the old timeout and creating
1665	a new one that moves the timeout into the future.	2662	a new one that moves the timeout into the future.
1666		2663
1667	=head3 Results	2664	=head3 Results
1668		2665
1669	name sockets create request	2666	name sockets create request
1670	EV 20000 69.01 11.16	2667	EV 20000 62.66 7.99
1671	Perl 20000 73.32 35.87	2668	Perl 20000 68.32 32.64
1672	Event 20000 212.62 257.32	2669	IOAsync 20000 174.06 101.15 epoll
1673	Glib 20000 651.16 1896.30	2670	IOAsync 20000 174.67 610.84 poll
		2671	Event 20000 202.69 242.91
		2672	Glib 20000 557.01 1689.52
1674	POE 20000 349.67 12317.24 uses POE::Loop::Event	2673	POE 20000 341.54 12086.32 uses POE::Loop::Event
1675		2674
1676	=head3 Discussion	2675	=head3 Discussion
1677		2676
1678	This benchmark I<does> measure scalability and overall performance of the	2677	This benchmark I<does> measure scalability and overall performance of the
1679	particular event loop.	2678	particular event loop.
…		…
1681	EV is again fastest. Since it is using epoll on my system, the setup time	2680	EV is again fastest. Since it is using epoll on my system, the setup time
1682	is relatively high, though.	2681	is relatively high, though.
1683		2682
1684	Perl surprisingly comes second. It is much faster than the C-based event	2683	Perl surprisingly comes second. It is much faster than the C-based event
1685	loops Event and Glib.	2684	loops Event and Glib.
		2685
		2686	IO::Async performs very well when using its epoll backend, and still quite
		2687	good compared to Glib when using its pure perl backend.
1686		2688
1687	Event suffers from high setup time as well (look at its code and you will	2689	Event suffers from high setup time as well (look at its code and you will
1688	understand why). Callback invocation also has a high overhead compared to	2690	understand why). Callback invocation also has a high overhead compared to
1689	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	2691	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1690	uses select or poll in basically all documented configurations.	2692	uses select or poll in basically all documented configurations.
…		…
1753	=item * C-based event loops perform very well with small number of	2755	=item * C-based event loops perform very well with small number of
1754	watchers, as the management overhead dominates.	2756	watchers, as the management overhead dominates.
1755		2757
1756	=back	2758	=back
1757		2759
		2760	=head2 THE IO::Lambda BENCHMARK
		2761
		2762	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2763	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2764	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2765	shouldn't come as a surprise to anybody). As such, the benchmark is
		2766	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2767	very optimal. But how would AnyEvent compare when used without the extra
		2768	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2769
		2770	The benchmark itself creates an echo-server, and then, for 500 times,
		2771	connects to the echo server, sends a line, waits for the reply, and then
		2772	creates the next connection. This is a rather bad benchmark, as it doesn't
		2773	test the efficiency of the framework or much non-blocking I/O, but it is a
		2774	benchmark nevertheless.
		2775
		2776	name runtime
		2777	Lambda/select 0.330 sec
		2778	+ optimized 0.122 sec
		2779	Lambda/AnyEvent 0.327 sec
		2780	+ optimized 0.138 sec
		2781	Raw sockets/select 0.077 sec
		2782	POE/select, components 0.662 sec
		2783	POE/select, raw sockets 0.226 sec
		2784	POE/select, optimized 0.404 sec
		2785
		2786	AnyEvent/select/nb 0.085 sec
		2787	AnyEvent/EV/nb 0.068 sec
		2788	+state machine 0.134 sec
		2789
		2790	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2791	benchmarks actually make blocking connects and use 100% blocking I/O,
		2792	defeating the purpose of an event-based solution. All of the newly
		2793	written AnyEvent benchmarks use 100% non-blocking connects (using
		2794	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2795	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2796	generally require a lot more bookkeeping and event handling than blocking
		2797	connects (which involve a single syscall only).
		2798
		2799	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2800	offers similar expressive power as POE and IO::Lambda, using conventional
		2801	Perl syntax. This means that both the echo server and the client are 100%
		2802	non-blocking, further placing it at a disadvantage.
		2803
		2804	As you can see, the AnyEvent + EV combination even beats the
		2805	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2806	backend easily beats IO::Lambda and POE.
		2807
		2808	And even the 100% non-blocking version written using the high-level (and
		2809	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
		2810	higher level ("unoptimised") abstractions by a large margin, even though
		2811	it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
		2812
		2813	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2814	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2815	part of the IO::Lambda distribution and were used without any changes.
		2816
1758		2817
1759	=head1 SIGNALS	2818	=head1 SIGNALS
1760		2819
1761	AnyEvent currently installs handlers for these signals:	2820	AnyEvent currently installs handlers for these signals:
1762		2821
…		…
1765	=item SIGCHLD	2824	=item SIGCHLD
1766		2825
1767	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher	2826	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
1768	emulation for event loops that do not support them natively. Also, some	2827	emulation for event loops that do not support them natively. Also, some
1769	event loops install a similar handler.	2828	event loops install a similar handler.
		2829
		2830	Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
		2831	AnyEvent will reset it to default, to avoid losing child exit statuses.
1770		2832
1771	=item SIGPIPE	2833	=item SIGPIPE
1772		2834
1773	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>	2835	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
1774	when AnyEvent gets loaded.	2836	when AnyEvent gets loaded.
…		…
1786		2848
1787	=back	2849	=back
1788		2850
1789	=cut	2851	=cut
1790		2852
		2853	undef $SIG{CHLD}
		2854	if $SIG{CHLD} eq 'IGNORE';
		2855
1791	$SIG{PIPE} = sub { }	2856	$SIG{PIPE} = sub { }
1792	unless defined $SIG{PIPE};	2857	unless defined $SIG{PIPE};
1793		2858
		2859	=head1 RECOMMENDED/OPTIONAL MODULES
		2860
		2861	One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
		2862	its built-in modules) are required to use it.
		2863
		2864	That does not mean that AnyEvent won't take advantage of some additional
		2865	modules if they are installed.
		2866
		2867	This section explains which additional modules will be used, and how they
		2868	affect AnyEvent's operation.
		2869
		2870	=over 4
		2871
		2872	=item L<Async::Interrupt>
		2873
		2874	This slightly arcane module is used to implement fast signal handling: To
		2875	my knowledge, there is no way to do completely race-free and quick
		2876	signal handling in pure perl. To ensure that signals still get
		2877	delivered, AnyEvent will start an interval timer to wake up perl (and
		2878	catch the signals) with some delay (default is 10 seconds, look for
		2879	C<$AnyEvent::MAX_SIGNAL_LATENCY>).
		2880
		2881	If this module is available, then it will be used to implement signal
		2882	catching, which means that signals will not be delayed, and the event loop
		2883	will not be interrupted regularly, which is more efficient (and good for
		2884	battery life on laptops).
		2885
		2886	This affects not just the pure-perl event loop, but also other event loops
		2887	that have no signal handling on their own (e.g. Glib, Tk, Qt).
		2888
		2889	Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
		2890	and either employ their own workarounds (POE) or use AnyEvent's workaround
		2891	(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
		2892	does nothing for those backends.
		2893
		2894	=item L<EV>
		2895
		2896	This module isn't really "optional", as it is simply one of the backend
		2897	event loops that AnyEvent can use. However, it is simply the best event
		2898	loop available in terms of features, speed and stability: It supports
		2899	the AnyEvent API optimally, implements all the watcher types in XS, does
		2900	automatic timer adjustments even when no monotonic clock is available,
		2901	can take avdantage of advanced kernel interfaces such as C<epoll> and
		2902	C<kqueue>, and is the fastest backend I<by far>. You can even embed
		2903	L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
		2904
		2905	If you only use backends that rely on another event loop (e.g. C<Tk>),
		2906	then this module will do nothing for you.
		2907
		2908	=item L<Guard>
		2909
		2910	The guard module, when used, will be used to implement
		2911	C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
		2912	lot less memory), but otherwise doesn't affect guard operation much. It is
		2913	purely used for performance.
		2914
		2915	=item L<JSON> and L<JSON::XS>
		2916
		2917	One of these modules is required when you want to read or write JSON data
		2918	via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
		2919	advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
		2920
		2921	=item L<Net::SSLeay>
		2922
		2923	Implementing TLS/SSL in Perl is certainly interesting, but not very
		2924	worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
		2925	the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
		2926
		2927	=item L<Time::HiRes>
		2928
		2929	This module is part of perl since release 5.008. It will be used when the
		2930	chosen event library does not come with a timing source of its own. The
		2931	pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
		2932	try to use a monotonic clock for timing stability.
		2933
		2934	=item L<AnyEvent::AIO> (and L<IO::AIO>)
		2935
		2936	The default implementation of L<AnyEvent::IO> is to do I/O synchronously,
		2937	stopping programs while they access the disk, which is fine for a lot of
		2938	programs.
		2939
		2940	Installing AnyEvent::AIO (and its IO::AIO dependency) makes it switch to
		2941	a true asynchronous implementation, so event processing can continue even
		2942	while waiting for disk I/O.
		2943
		2944	=back
		2945
1794		2946
1795	=head1 FORK	2947	=head1 FORK
1796		2948
1797	Most event libraries are not fork-safe. The ones who are usually are	2949	Most event libraries are not fork-safe. The ones who are usually are
1798	because they rely on inefficient but fork-safe C<select> or C<poll>	2950	because they rely on inefficient but fork-safe C<select> or C<poll> calls
1799	calls. Only L<EV> is fully fork-aware.	2951	- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
		2952	are usually badly thought-out hacks that are incompatible with fork in
		2953	one way or another. Only L<EV> is fully fork-aware and ensures that you
		2954	continue event-processing in both parent and child (or both, if you know
		2955	what you are doing).
		2956
		2957	This means that, in general, you cannot fork and do event processing in
		2958	the child if the event library was initialised before the fork (which
		2959	usually happens when the first AnyEvent watcher is created, or the library
		2960	is loaded).
1800		2961
1801	If you have to fork, you must either do so I<before> creating your first	2962	If you have to fork, you must either do so I<before> creating your first
1802	watcher OR you must not use AnyEvent at all in the child.	2963	watcher OR you must not use AnyEvent at all in the child OR you must do
		2964	something completely out of the scope of AnyEvent.
		2965
		2966	The problem of doing event processing in the parent I<and> the child
		2967	is much more complicated: even for backends that I<are> fork-aware or
		2968	fork-safe, their behaviour is not usually what you want: fork clones all
		2969	watchers, that means all timers, I/O watchers etc. are active in both
		2970	parent and child, which is almost never what you want. USing C<exec>
		2971	to start worker children from some kind of manage rprocess is usually
		2972	preferred, because it is much easier and cleaner, at the expense of having
		2973	to have another binary.
1803		2974
1804		2975
1805	=head1 SECURITY CONSIDERATIONS	2976	=head1 SECURITY CONSIDERATIONS
1806		2977
1807	AnyEvent can be forced to load any event model via	2978	AnyEvent can be forced to load any event model via
…		…
1819	use AnyEvent;	2990	use AnyEvent;
1820		2991
1821	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2992	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1822	be used to probe what backend is used and gain other information (which is	2993	be used to probe what backend is used and gain other information (which is
1823	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and	2994	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1824	$ENV{PERL_ANYEGENT_STRICT}.	2995	$ENV{PERL_ANYEVENT_STRICT}.
		2996
		2997	Note that AnyEvent will remove I<all> environment variables starting with
		2998	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2999	enabled.
1825		3000
1826		3001
1827	=head1 BUGS	3002	=head1 BUGS
1828		3003
1829	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard	3004	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1830	to work around. If you suffer from memleaks, first upgrade to Perl 5.10	3005	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1831	and check wether the leaks still show up. (Perl 5.10.0 has other annoying	3006	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1832	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as	3007	memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1833	pronounced).	3008	pronounced).
1834		3009
1835		3010
1836	=head1 SEE ALSO	3011	=head1 SEE ALSO
1837		3012
1838	Utility functions: L<AnyEvent::Util>.	3013	Tutorial/Introduction: L<AnyEvent::Intro>.
1839		3014
1840	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,	3015	FAQ: L<AnyEvent::FAQ>.
1841	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	3016
		3017	Utility functions: L<AnyEvent::Util> (misc. grab-bag), L<AnyEvent::Log>
		3018	(simply logging).
		3019
		3020	Development/Debugging: L<AnyEvent::Strict> (stricter checking),
		3021	L<AnyEvent::Debug> (interactive shell, watcher tracing).
		3022
		3023	Supported event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>,
		3024	L<Glib::EV>, L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>,
		3025	L<Qt>, L<POE>, L<FLTK>.
1842		3026
1843	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	3027	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1844	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	3028	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1845	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	3029	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
		3030	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>,
1846	L<AnyEvent::Impl::POE>.	3031	L<AnyEvent::Impl::FLTK>.
1847		3032
1848	Non-blocking file handles, sockets, TCP clients and	3033	Non-blocking handles, pipes, stream sockets, TCP clients and
1849	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	3034	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
		3035
		3036	Asynchronous File I/O: L<AnyEvent::IO>.
1850		3037
1851	Asynchronous DNS: L<AnyEvent::DNS>.	3038	Asynchronous DNS: L<AnyEvent::DNS>.
1852		3039
1853	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	3040	Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
1854		3041
1855	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	3042	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
		3043	L<AnyEvent::HTTP>.
1856		3044
1857		3045
1858	=head1 AUTHOR	3046	=head1 AUTHOR
1859		3047
1860	Marc Lehmann <schmorp@schmorp.de>	3048	Marc Lehmann <schmorp@schmorp.de>
1861	http://home.schmorp.de/	3049	http://anyevent.schmorp.de
1862		3050
1863	=cut	3051	=cut
1864		3052
1865	1	3053	1
1866		3054

Diff Legend

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