[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.134 by root, Sun May 25 04:44:04 2008 UTC vs.
Revision 1.183 by root, Wed Oct 1 07:40:39 2008 UTC

…		…
1	=head1 => NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops
6		6
7	=head1 SYNOPSIS	7	=head1 SYNOPSIS
8		8
9	use AnyEvent;	9	use AnyEvent;
10		10
11	my $w = AnyEvent->io (fh => $fh, poll => "r\|w", cb => sub {	11	my $w = AnyEvent->io (fh => $fh, poll => "r\|w", cb => sub { ... });
12	...
13	});
14		12
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	13	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
		14	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
		15
		16	print AnyEvent->now; # prints current event loop time
		17	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
		18
		19	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
		20
		21	my $w = AnyEvent->child (pid => $pid, cb => sub {
		22	my ($pid, $status) = @_;
16	...	23	...
17	});	24	});
18		25
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	26	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	27	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	28	$w->recv; # enters "main loop" till $condvar gets ->send
		29	# use a condvar in callback mode:
		30	$w->cb (sub { $_[0]->recv });
		31
		32	=head1 INTRODUCTION/TUTORIAL
		33
		34	This manpage is mainly a reference manual. If you are interested
		35	in a tutorial or some gentle introduction, have a look at the
		36	L<AnyEvent::Intro> manpage.
22		37
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	38	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		39
25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	40	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26	nowadays. So what is different about AnyEvent?	41	nowadays. So what is different about AnyEvent?
27		42
28	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	43	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
29	policy> and AnyEvent is I<small and efficient>.	44	policy> and AnyEvent is I<small and efficient>.
30		45
31	First and foremost, I<AnyEvent is not an event model> itself, it only	46	First and foremost, I<AnyEvent is not an event model> itself, it only
32	interfaces to whatever event model the main program happens to use in a	47	interfaces to whatever event model the main program happens to use, in a
33	pragmatic way. For event models and certain classes of immortals alike,	48	pragmatic way. For event models and certain classes of immortals alike,
34	the statement "there can only be one" is a bitter reality: In general,	49	the statement "there can only be one" is a bitter reality: In general,
35	only one event loop can be active at the same time in a process. AnyEvent	50	only one event loop can be active at the same time in a process. AnyEvent
36	helps hiding the differences between those event loops.	51	cannot change this, but it can hide the differences between those event
		52	loops.
37		53
38	The goal of AnyEvent is to offer module authors the ability to do event	54	The goal of AnyEvent is to offer module authors the ability to do event
39	programming (waiting for I/O or timer events) without subscribing to a	55	programming (waiting for I/O or timer events) without subscribing to a
40	religion, a way of living, and most importantly: without forcing your	56	religion, a way of living, and most importantly: without forcing your
41	module users into the same thing by forcing them to use the same event	57	module users into the same thing by forcing them to use the same event
42	model you use.	58	model you use.
43		59
44	For modules like POE or IO::Async (which is a total misnomer as it is	60	For modules like POE or IO::Async (which is a total misnomer as it is
45	actually doing all I/O I<synchronously>...), using them in your module is	61	actually doing all I/O I<synchronously>...), using them in your module is
46	like joining a cult: After you joined, you are dependent on them and you	62	like joining a cult: After you joined, you are dependent on them and you
47	cannot use anything else, as it is simply incompatible to everything that	63	cannot use anything else, as they are simply incompatible to everything
48	isn't itself. What's worse, all the potential users of your module are	64	that isn't them. What's worse, all the potential users of your
49	I<also> forced to use the same event loop you use.	65	module are I<also> forced to use the same event loop you use.
50		66
51	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	67	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
52	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	68	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
53	with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if	69	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if
54	your module uses one of those, every user of your module has to use it,	70	your module uses one of those, every user of your module has to use it,
55	too. But if your module uses AnyEvent, it works transparently with all	71	too. But if your module uses AnyEvent, it works transparently with all
56	event models it supports (including stuff like POE and IO::Async, as long	72	event models it supports (including stuff like IO::Async, as long as those
57	as those use one of the supported event loops. It is trivial to add new	73	use one of the supported event loops. It is trivial to add new event loops
58	event loops to AnyEvent, too, so it is future-proof).	74	to AnyEvent, too, so it is future-proof).
59		75
60	In addition to being free of having to use I<the one and only true event	76	In addition to being free of having to use I<the one and only true event
61	model>, AnyEvent also is free of bloat and policy: with POE or similar	77	model>, AnyEvent also is free of bloat and policy: with POE or similar
62	modules, you get an enormous amount of code and strict rules you have to	78	modules, you get an enormous amount of code and strict rules you have to
63	follow. AnyEvent, on the other hand, is lean and up to the point, by only	79	follow. AnyEvent, on the other hand, is lean and up to the point, by only
64	offering the functionality that is necessary, in as thin as a wrapper as	80	offering the functionality that is necessary, in as thin as a wrapper as
65	technically possible.	81	technically possible.
66		82
		83	Of course, AnyEvent comes with a big (and fully optional!) toolbox
		84	of useful functionality, such as an asynchronous DNS resolver, 100%
		85	non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms
		86	such as Windows) and lots of real-world knowledge and workarounds for
		87	platform bugs and differences.
		88
67	Of course, if you want lots of policy (this can arguably be somewhat	89	Now, if you I<do want> lots of policy (this can arguably be somewhat
68	useful) and you want to force your users to use the one and only event	90	useful) and you want to force your users to use the one and only event
69	model, you should I<not> use this module.	91	model, you should I<not> use this module.
70		92
71	=head1 DESCRIPTION	93	=head1 DESCRIPTION
72		94
102	starts using it, all bets are off. Maybe you should tell their authors to	124	starts using it, all bets are off. Maybe you should tell their authors to
103	use AnyEvent so their modules work together with others seamlessly...	125	use AnyEvent so their modules work together with others seamlessly...
104		126
105	The pure-perl implementation of AnyEvent is called	127	The pure-perl implementation of AnyEvent is called
106	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	128	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
107	explicitly.	129	explicitly and enjoy the high availability of that event loop :)
108		130
109	=head1 WATCHERS	131	=head1 WATCHERS
110		132
111	AnyEvent has the central concept of a I<watcher>, which is an object that	133	AnyEvent has the central concept of a I<watcher>, which is an object that
112	stores relevant data for each kind of event you are waiting for, such as	134	stores relevant data for each kind of event you are waiting for, such as
…		…
126	Many watchers either are used with "recursion" (repeating timers for	148	Many watchers either are used with "recursion" (repeating timers for
127	example), or need to refer to their watcher object in other ways.	149	example), or need to refer to their watcher object in other ways.
128		150
129	An any way to achieve that is this pattern:	151	An any way to achieve that is this pattern:
130		152
131	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	153	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
132	# you can use $w here, for example to undef it	154	# you can use $w here, for example to undef it
133	undef $w;	155	undef $w;
134	});	156	});
135		157
136	Note that C<my $w; $w => combination. This is necessary because in Perl,	158	Note that C<my $w; $w => combination. This is necessary because in Perl,
137	my variables are only visible after the statement in which they are	159	my variables are only visible after the statement in which they are
138	declared.	160	declared.
139		161
140	=head2 I/O WATCHERS	162	=head2 I/O WATCHERS
141		163
142	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	164	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
143	with the following mandatory key-value pairs as arguments:	165	with the following mandatory key-value pairs as arguments:
144		166
145	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	167	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events
146	for events. C<poll> must be a string that is either C<r> or C<w>,	168	(AnyEvent might or might not keep a reference to this file handle). C<poll>
147	which creates a watcher waiting for "r"eadable or "w"ritable events,	169	must be a string that is either C<r> or C<w>, which creates a watcher
148	respectively. C<cb> is the callback to invoke each time the file handle	170	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the
149	becomes ready.	171	callback to invoke each time the file handle becomes ready.
150		172
151	Although the callback might get passed parameters, their value and	173	Although the callback might get passed parameters, their value and
152	presence is undefined and you cannot rely on them. Portable AnyEvent	174	presence is undefined and you cannot rely on them. Portable AnyEvent
153	callbacks cannot use arguments passed to I/O watcher callbacks.	175	callbacks cannot use arguments passed to I/O watcher callbacks.
154		176
…		…
158		180
159	Some event loops issue spurious readyness notifications, so you should	181	Some event loops issue spurious readyness notifications, so you should
160	always use non-blocking calls when reading/writing from/to your file	182	always use non-blocking calls when reading/writing from/to your file
161	handles.	183	handles.
162		184
163	Example:
164
165	# wait for readability of STDIN, then read a line and disable the watcher	185	Example: wait for readability of STDIN, then read a line and disable the
		186	watcher.
		187
166	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	188	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
167	chomp (my $input = <STDIN>);	189	chomp (my $input = <STDIN>);
168	warn "read: $input\n";	190	warn "read: $input\n";
169	undef $w;	191	undef $w;
170	});	192	});
…		…
180		202
181	Although the callback might get passed parameters, their value and	203	Although the callback might get passed parameters, their value and
182	presence is undefined and you cannot rely on them. Portable AnyEvent	204	presence is undefined and you cannot rely on them. Portable AnyEvent
183	callbacks cannot use arguments passed to time watcher callbacks.	205	callbacks cannot use arguments passed to time watcher callbacks.
184		206
185	The timer callback will be invoked at most once: if you want a repeating	207	The callback will normally be invoked once only. If you specify another
186	timer you have to create a new watcher (this is a limitation by both Tk	208	parameter, C<interval>, as a strictly positive number (> 0), then the
187	and Glib).	209	callback will be invoked regularly at that interval (in fractional
		210	seconds) after the first invocation. If C<interval> is specified with a
		211	false value, then it is treated as if it were missing.
188		212
189	Example:	213	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
		215	only approximate.
190		216
191	# fire an event after 7.7 seconds	217	Example: fire an event after 7.7 seconds.
		218
192	my $w = AnyEvent->timer (after => 7.7, cb => sub {	219	my $w = AnyEvent->timer (after => 7.7, cb => sub {
193	warn "timeout\n";	220	warn "timeout\n";
194	});	221	});
195		222
196	# to cancel the timer:	223	# to cancel the timer:
197	undef $w;	224	undef $w;
198		225
199	Example 2:
200
201	# fire an event after 0.5 seconds, then roughly every second	226	Example 2: fire an event after 0.5 seconds, then roughly every second.
202	my $w;
203		227
204	my $cb = sub {
205	# cancel the old timer while creating a new one
206	$w = AnyEvent->timer (after => 1, cb => $cb);	228	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
		229	warn "timeout\n";
207	};	230	};
208
209	# start the "loop" by creating the first watcher
210	$w = AnyEvent->timer (after => 0.5, cb => $cb);
211		231
212	=head3 TIMING ISSUES	232	=head3 TIMING ISSUES
213		233
214	There are two ways to handle timers: based on real time (relative, "fire	234	There are two ways to handle timers: based on real time (relative, "fire
215	in 10 seconds") and based on wallclock time (absolute, "fire at 12	235	in 10 seconds") and based on wallclock time (absolute, "fire at 12
…		…
227	timers.	247	timers.
228		248
229	AnyEvent always prefers relative timers, if available, matching the	249	AnyEvent always prefers relative timers, if available, matching the
230	AnyEvent API.	250	AnyEvent API.
231		251
		252	AnyEvent has two additional methods that return the "current time":
		253
		254	=over 4
		255
		256	=item AnyEvent->time
		257
		258	This returns the "current wallclock time" as a fractional number of
		259	seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time>
		260	return, and the result is guaranteed to be compatible with those).
		261
		262	It progresses independently of any event loop processing, i.e. each call
		263	will check the system clock, which usually gets updated frequently.
		264
		265	=item AnyEvent->now
		266
		267	This also returns the "current wallclock time", but unlike C<time>, above,
		268	this value might change only once per event loop iteration, depending on
		269	the event loop (most return the same time as C<time>, above). This is the
		270	time that AnyEvent's timers get scheduled against.
		271
		272	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.>
		274
		275	This function is also often faster then C<< AnyEvent->time >>, and
		276	thus the preferred method if you want some timestamp (for example,
		277	L<AnyEvent::Handle> uses this to update it's activity timeouts).
		278
		279	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.
		281
		282	For a practical example of when these times differ, consider L<Event::Lib>
		283	and L<EV> and the following set-up:
		284
		285	The event loop is running and has just invoked one of your callback at
		286	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
		288	second) and then (at time=501) you create a relative timer that fires
		289	after three seconds.
		290
		291	With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will
		292	both return C<501>, because that is the current time, and the timer will
		293	be scheduled to fire at time=504 (C<501> + C<3>).
		294
		295	With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current
		296	time), but C<< AnyEvent->now >> returns C<500>, as that is the time the
		297	last event processing phase started. With L<EV>, your timer gets scheduled
		298	to run at time=503 (C<500> + C<3>).
		299
		300	In one sense, L<Event::Lib> is more exact, as it uses the current time
		301	regardless of any delays introduced by event processing. However, most
		302	callbacks do not expect large delays in processing, so this causes a
		303	higher drift (and a lot more system calls to get the current time).
		304
		305	In another sense, L<EV> is more exact, as your timer will be scheduled at
		306	the same time, regardless of how long event processing actually took.
		307
		308	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
		310	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
		311	account.
		312
		313	=back
		314
232	=head2 SIGNAL WATCHERS	315	=head2 SIGNAL WATCHERS
233		316
234	You can watch for signals using a signal watcher, C<signal> is the signal	317	You can watch for signals using a signal watcher, C<signal> is the signal
235	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	318	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
236	be invoked whenever a signal occurs.	319	callback to be invoked whenever a signal occurs.
237		320
238	Although the callback might get passed parameters, their value and	321	Although the callback might get passed parameters, their value and
239	presence is undefined and you cannot rely on them. Portable AnyEvent	322	presence is undefined and you cannot rely on them. Portable AnyEvent
240	callbacks cannot use arguments passed to signal watcher callbacks.	323	callbacks cannot use arguments passed to signal watcher callbacks.
241		324
…		…
257	=head2 CHILD PROCESS WATCHERS	340	=head2 CHILD PROCESS WATCHERS
258		341
259	You can also watch on a child process exit and catch its exit status.	342	You can also watch on a child process exit and catch its exit status.
260		343
261	The child process is specified by the C<pid> argument (if set to C<0>, it	344	The child process is specified by the C<pid> argument (if set to C<0>, it
262	watches for any child process exit). The watcher will trigger as often	345	watches for any child process exit). The watcher will triggered only when
263	as status change for the child are received. This works by installing a	346	the child process has finished and an exit status is available, not on
264	signal handler for C<SIGCHLD>. The callback will be called with the pid	347	any trace events (stopped/continued).
265	and exit status (as returned by waitpid), so unlike other watcher types,	348
266	you I<can> rely on child watcher callback arguments.	349	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
		351	callback arguments.
		352
		353	This watcher type works by installing a signal handler for C<SIGCHLD>,
		354	and since it cannot be shared, nothing else should use SIGCHLD or reap
		355	random child processes (waiting for specific child processes, e.g. inside
		356	C<system>, is just fine).
267		357
268	There is a slight catch to child watchers, however: you usually start them	358	There is a slight catch to child watchers, however: you usually start them
269	I<after> the child process was created, and this means the process could	359	I<after> the child process was created, and this means the process could
270	have exited already (and no SIGCHLD will be sent anymore).	360	have exited already (and no SIGCHLD will be sent anymore).
271		361
…		…
277	AnyEvent program, you I<have> to create at least one watcher before you	367	AnyEvent program, you I<have> to create at least one watcher before you
278	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	368	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
279		369
280	Example: fork a process and wait for it	370	Example: fork a process and wait for it
281		371
282	my $done = AnyEvent->condvar;	372	my $done = AnyEvent->condvar;
283		373
284	my $pid = fork or exit 5;	374	my $pid = fork or exit 5;
285		375
286	my $w = AnyEvent->child (	376	my $w = AnyEvent->child (
287	pid => $pid,	377	pid => $pid,
288	cb => sub {	378	cb => sub {
289	my ($pid, $status) = @_;	379	my ($pid, $status) = @_;
290	warn "pid $pid exited with status $status";	380	warn "pid $pid exited with status $status";
291	$done->send;	381	$done->send;
292	},	382	},
293	);	383	);
294		384
295	# do something else, then wait for process exit	385	# do something else, then wait for process exit
296	$done->recv;	386	$done->recv;
297		387
298	=head2 CONDITION VARIABLES	388	=head2 CONDITION VARIABLES
299		389
300	If you are familiar with some event loops you will know that all of them	390	If you are familiar with some event loops you will know that all of them
301	require you to run some blocking "loop", "run" or similar function that	391	require you to run some blocking "loop", "run" or similar function that
…		…
307	The instrument to do that is called a "condition variable", so called	397	The instrument to do that is called a "condition variable", so called
308	because they represent a condition that must become true.	398	because they represent a condition that must become true.
309		399
310	Condition variables can be created by calling the C<< AnyEvent->condvar	400	Condition variables can be created by calling the C<< AnyEvent->condvar
311	>> method, usually without arguments. The only argument pair allowed is	401	>> method, usually without arguments. The only argument pair allowed is
		402
312	C<cb>, which specifies a callback to be called when the condition variable	403	C<cb>, which specifies a callback to be called when the condition variable
313	becomes true.	404	becomes true, with the condition variable as the first argument (but not
		405	the results).
314		406
315	After creation, the condition variable is "false" until it becomes "true"	407	After creation, the condition variable is "false" until it becomes "true"
316	by calling the C<send> method (or calling the condition variable as if it	408	by calling the C<send> method (or calling the condition variable as if it
317	were a callback).	409	were a callback, read about the caveats in the description for the C<<
		410	->send >> method).
318		411
319	Condition variables are similar to callbacks, except that you can	412	Condition variables are similar to callbacks, except that you can
320	optionally wait for them. They can also be called merge points - points	413	optionally wait for them. They can also be called merge points - points
321	in time where multiple outstanding events have been processed. And yet	414	in time where multiple outstanding events have been processed. And yet
322	another way to call them is transactions - each condition variable can be	415	another way to call them is transactions - each condition variable can be
…		…
373		466
374	my $done = AnyEvent->condvar;	467	my $done = AnyEvent->condvar;
375	my $delay = AnyEvent->timer (after => 5, cb => $done);	468	my $delay = AnyEvent->timer (after => 5, cb => $done);
376	$done->recv;	469	$done->recv;
377		470
		471	Example: Imagine an API that returns a condvar and doesn't support
		472	callbacks. This is how you make a synchronous call, for example from
		473	the main program:
		474
		475	use AnyEvent::CouchDB;
		476
		477	...
		478
		479	my @info = $couchdb->info->recv;
		480
		481	And this is how you would just ste a callback to be called whenever the
		482	results are available:
		483
		484	$couchdb->info->cb (sub {
		485	my @info = $_[0]->recv;
		486	});
		487
378	=head3 METHODS FOR PRODUCERS	488	=head3 METHODS FOR PRODUCERS
379		489
380	These methods should only be used by the producing side, i.e. the	490	These methods should only be used by the producing side, i.e. the
381	code/module that eventually sends the signal. Note that it is also	491	code/module that eventually sends the signal. Note that it is also
382	the producer side which creates the condvar in most cases, but it isn't	492	the producer side which creates the condvar in most cases, but it isn't
…		…
394	immediately from within send.	504	immediately from within send.
395		505
396	Any arguments passed to the C<send> call will be returned by all	506	Any arguments passed to the C<send> call will be returned by all
397	future C<< ->recv >> calls.	507	future C<< ->recv >> calls.
398		508
399	Condition variables are overloaded so one can call them directly (as a	509	Condition variables are overloaded so one can call them directly
400	code reference). Calling them directly is the same as calling C<send>.	510	(as 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
		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).
401		517
402	=item $cv->croak ($error)	518	=item $cv->croak ($error)
403		519
404	Similar to send, but causes all call's to C<< ->recv >> to invoke	520	Similar to send, but causes all call's to C<< ->recv >> to invoke
405	C<Carp::croak> with the given error message/object/scalar.	521	C<Carp::croak> with the given error message/object/scalar.
…		…
509	=item $bool = $cv->ready	625	=item $bool = $cv->ready
510		626
511	Returns true when the condition is "true", i.e. whether C<send> or	627	Returns true when the condition is "true", i.e. whether C<send> or
512	C<croak> have been called.	628	C<croak> have been called.
513		629
514	=item $cb = $cv->cb ([new callback])	630	=item $cb = $cv->cb ($cb->($cv))
515		631
516	This is a mutator function that returns the callback set and optionally	632	This is a mutator function that returns the callback set and optionally
517	replaces it before doing so.	633	replaces it before doing so.
518		634
519	The callback will be called when the condition becomes "true", i.e. when	635	The callback will be called when the condition becomes "true", i.e. when
520	C<send> or C<croak> are called. Calling C<recv> inside the callback	636	C<send> or C<croak> are called, with the only argument being the condition
521	or at any later time is guaranteed not to block.	637	variable itself. Calling C<recv> inside the callback or at any later time
		638	is guaranteed not to block.
522		639
523	=back	640	=back
524		641
525	=head1 GLOBAL VARIABLES AND FUNCTIONS	642	=head1 GLOBAL VARIABLES AND FUNCTIONS
526		643
…		…
655	=item L<AnyEvent::Util>	772	=item L<AnyEvent::Util>
656		773
657	Contains various utility functions that replace often-used but blocking	774	Contains various utility functions that replace often-used but blocking
658	functions such as C<inet_aton> by event-/callback-based versions.	775	functions such as C<inet_aton> by event-/callback-based versions.
659		776
660	=item L<AnyEvent::Handle>
661
662	Provide read and write buffers and manages watchers for reads and writes.
663
664	=item L<AnyEvent::Socket>	777	=item L<AnyEvent::Socket>
665		778
666	Provides various utility functions for (internet protocol) sockets,	779	Provides various utility functions for (internet protocol) sockets,
667	addresses and name resolution. Also functions to create non-blocking tcp	780	addresses and name resolution. Also functions to create non-blocking tcp
668	connections or tcp servers, with IPv6 and SRV record support and more.	781	connections or tcp servers, with IPv6 and SRV record support and more.
669		782
		783	=item L<AnyEvent::Handle>
		784
		785	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
		787	non-blocking SSL/TLS.
		788
670	=item L<AnyEvent::DNS>	789	=item L<AnyEvent::DNS>
671		790
672	Provides rich asynchronous DNS resolver capabilities.	791	Provides rich asynchronous DNS resolver capabilities.
673		792
		793	=item L<AnyEvent::HTTP>
		794
		795	A simple-to-use HTTP library that is capable of making a lot of concurrent
		796	HTTP requests.
		797
674	=item L<AnyEvent::HTTPD>	798	=item L<AnyEvent::HTTPD>
675		799
676	Provides a simple web application server framework.	800	Provides a simple web application server framework.
677		801
678	=item L<AnyEvent::FastPing>	802	=item L<AnyEvent::FastPing>
679		803
680	The fastest ping in the west.	804	The fastest ping in the west.
		805
		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>).
681		829
682	=item L<Net::IRC3>	830	=item L<Net::IRC3>
683		831
684	AnyEvent based IRC client module family.	832	AnyEvent based IRC client module family.
685		833
…		…
698		846
699	=item L<Coro>	847	=item L<Coro>
700		848
701	Has special support for AnyEvent via L<Coro::AnyEvent>.	849	Has special support for AnyEvent via L<Coro::AnyEvent>.
702		850
703	=item L<AnyEvent::AIO>, L<IO::AIO>
704
705	Truly asynchronous I/O, should be in the toolbox of every event
706	programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
707	together.
708
709	=item L<AnyEvent::BDB>, L<BDB>
710
711	Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
712	IO::AIO and AnyEvent together.
713
714	=item L<IO::Lambda>	851	=item L<IO::Lambda>
715		852
716	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	853	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
717		854
718	=back	855	=back
…		…
720	=cut	857	=cut
721		858
722	package AnyEvent;	859	package AnyEvent;
723		860
724	no warnings;	861	no warnings;
725	use strict;	862	use strict qw(vars subs);
726		863
727	use Carp;	864	use Carp;
728		865
729	our $VERSION = '4.03';	866	our $VERSION = 4.3;
730	our $MODEL;	867	our $MODEL;
731		868
732	our $AUTOLOAD;	869	our $AUTOLOAD;
733	our @ISA;	870	our @ISA;
734		871
		872	our @REGISTRY;
		873
		874	our $WIN32;
		875
		876	BEGIN {
		877	my $win32 = ! ! ($^O =~ /mswin32/i);
		878	eval "sub WIN32(){ $win32 }";
		879	}
		880
735	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	881	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
736		882
737	our @REGISTRY;	883	our %PROTOCOL; # (ipv4\|ipv6) => (1\|2), higher numbers are preferred
738
739	our %PROTOCOL; # (ipv4\|ipv6) => (1\|2)
740		884
741	{	885	{
742	my $idx;	886	my $idx;
743	$PROTOCOL{$_} = ++$idx	887	$PROTOCOL{$_} = ++$idx
		888	for reverse split /\s,\s/,
744	for split /\s,\s/, $ENV{PERL_ANYEVENT_PROTOCOLS} \|\| "ipv4,ipv6";	889	$ENV{PERL_ANYEVENT_PROTOCOLS} \|\| "ipv4,ipv6";
745	}	890	}
746		891
747	my @models = (	892	my @models = (
748	[EV:: => AnyEvent::Impl::EV::],	893	[EV:: => AnyEvent::Impl::EV::],
749	[Event:: => AnyEvent::Impl::Event::],	894	[Event:: => AnyEvent::Impl::Event::],
750	[Tk:: => AnyEvent::Impl::Tk::],
751	[Wx:: => AnyEvent::Impl::POE::],
752	[Prima:: => AnyEvent::Impl::POE::],
753	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	895	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
754	# everything below here will not be autoprobed as the pureperl backend should work everywhere	896	# everything below here will not be autoprobed
755	[Glib:: => AnyEvent::Impl::Glib::],	897	# as the pureperl backend should work everywhere
		898	# and is usually faster
		899	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
		900	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
756	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy	901	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
757	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	902	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
758	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	903	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
		904	[Wx:: => AnyEvent::Impl::POE::],
		905	[Prima:: => AnyEvent::Impl::POE::],
759	);	906	);
760		907
761	our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY);	908	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);
762		909
763	our @post_detect;	910	our @post_detect;
764		911
765	sub post_detect(&) {	912	sub post_detect(&) {
766	my ($cb) = @_;	913	my ($cb) = @_;
…		…
783	}	930	}
784		931
785	sub detect() {	932	sub detect() {
786	unless ($MODEL) {	933	unless ($MODEL) {
787	no strict 'refs';	934	no strict 'refs';
		935	local $SIG{__DIE__};
788		936
789	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {	937	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
790	my $model = "AnyEvent::Impl::$1";	938	my $model = "AnyEvent::Impl::$1";
791	if (eval "require $model") {	939	if (eval "require $model") {
792	$MODEL = $model;	940	$MODEL = $model;
…		…
826	$MODEL	974	$MODEL
827	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	975	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
828	}	976	}
829	}	977	}
830		978
		979	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		980
831	unshift @ISA, $MODEL;	981	unshift @ISA, $MODEL;
832	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	982
		983	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
833		984
834	(shift @post_detect)->() while @post_detect;	985	(shift @post_detect)->() while @post_detect;
835	}	986	}
836		987
837	$MODEL	988	$MODEL
…		…
847		998
848	my $class = shift;	999	my $class = shift;
849	$class->$func (@_);	1000	$class->$func (@_);
850	}	1001	}
851		1002
		1003	# utility function to dup a filehandle. this is used by many backends
		1004	# 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).
		1006	sub _dupfh($$$$) {
		1007	my ($poll, $fh, $r, $w) = @_;
		1008
		1009	require Fcntl;
		1010
		1011	# cygwin requires the fh mode to be matching, unix doesn't
		1012	my ($rw, $mode) = $poll eq "r" ? ($r, "<")
		1013	: $poll eq "w" ? ($w, ">")
		1014	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
		1015
		1016	open my $fh2, "$mode&" . fileno $fh
		1017	or die "cannot dup() filehandle: $!";
		1018
		1019	# we assume CLOEXEC is already set by perl in all important cases
		1020
		1021	($fh2, $rw)
		1022	}
		1023
852	package AnyEvent::Base;	1024	package AnyEvent::Base;
		1025
		1026	# default implementation for now and time
		1027
		1028	BEGIN {
		1029	if (eval "use Time::HiRes (); time (); 1") {
		1030	*_time = \&Time::HiRes::time;
		1031	# if (eval "use POSIX (); (POSIX::times())...
		1032	} else {
		1033	*_time = sub { time }; # epic fail
		1034	}
		1035	}
		1036
		1037	sub time { _time }
		1038	sub now { _time }
853		1039
854	# default implementation for ->condvar	1040	# default implementation for ->condvar
855		1041
856	sub condvar {	1042	sub condvar {
857	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1043	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
…		…
878	sub AnyEvent::Base::Signal::DESTROY {	1064	sub AnyEvent::Base::Signal::DESTROY {
879	my ($signal, $cb) = @{$_[0]};	1065	my ($signal, $cb) = @{$_[0]};
880		1066
881	delete $SIG_CB{$signal}{$cb};	1067	delete $SIG_CB{$signal}{$cb};
882		1068
883	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1069	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
884	}	1070	}
885		1071
886	# default implementation for ->child	1072	# default implementation for ->child
887		1073
888	our %PID_CB;	1074	our %PID_CB;
…		…
915	or Carp::croak "required option 'pid' is missing";	1101	or Carp::croak "required option 'pid' is missing";
916		1102
917	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1103	$PID_CB{$pid}{$arg{cb}} = $arg{cb};
918		1104
919	unless ($WNOHANG) {	1105	unless ($WNOHANG) {
920	$WNOHANG = eval { require POSIX; &POSIX::WNOHANG } \|\| 1;	1106	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } \|\| 1;
921	}	1107	}
922		1108
923	unless ($CHLD_W) {	1109	unless ($CHLD_W) {
924	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1110	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
925	# child could be a zombie already, so make at least one round	1111	# child could be a zombie already, so make at least one round
…		…
995	}	1181	}
996		1182
997	# undocumented/compatibility with pre-3.4	1183	# undocumented/compatibility with pre-3.4
998	*broadcast = \&send;	1184	*broadcast = \&send;
999	*wait = \&_wait;	1185	*wait = \&_wait;
		1186
		1187	=head1 ERROR AND EXCEPTION HANDLING
		1188
		1189	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
		1191	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1192	checking of all AnyEvent methods, however, which is highly useful during
		1193	development.
		1194
		1195	As for exception handling (i.e. runtime errors and exceptions thrown while
		1196	executing a callback), this is not only highly event-loop specific, but
		1197	also not in any way wrapped by this module, as this is the job of the main
		1198	program.
		1199
		1200	The pure perl event loop simply re-throws the exception (usually
		1201	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1202	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1203	so on.
		1204
		1205	=head1 ENVIRONMENT VARIABLES
		1206
		1207	The following environment variables are used by this module or its
		1208	submodules:
		1209
		1210	=over 4
		1211
		1212	=item C<PERL_ANYEVENT_VERBOSE>
		1213
		1214	By default, AnyEvent will be completely silent except in fatal
		1215	conditions. You can set this environment variable to make AnyEvent more
		1216	talkative.
		1217
		1218	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		1219	conditions, such as not being able to load the event model specified by
		1220	C<PERL_ANYEVENT_MODEL>.
		1221
		1222	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		1223	model it chooses.
		1224
		1225	=item C<PERL_ANYEVENT_STRICT>
		1226
		1227	AnyEvent does not do much argument checking by default, as thorough
		1228	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
		1230	check the arguments passed to most method calls. If it finds any problems
		1231	it will croak.
		1232
		1233	In other words, enables "strict" mode.
		1234
		1235	Unlike C<use strict>, it is definitely recommended ot keep it off in
		1236	production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while
		1237	developing programs can be very useful, however.
		1238
		1239	=item C<PERL_ANYEVENT_MODEL>
		1240
		1241	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
		1243	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		1244	and the resulting module name is loaded and if the load was successful,
		1245	used as event model. If it fails to load AnyEvent will proceed with
		1246	auto detection and -probing.
		1247
		1248	This functionality might change in future versions.
		1249
		1250	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		1251	could start your program like this:
		1252
		1253	PERL_ANYEVENT_MODEL=Perl perl ...
		1254
		1255	=item C<PERL_ANYEVENT_PROTOCOLS>
		1256
		1257	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
		1259	of auto probing).
		1260
		1261	Must be set to a comma-separated list of protocols or address families,
		1262	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		1263	used, and preference will be given to protocols mentioned earlier in the
		1264	list.
		1265
		1266	This variable can effectively be used for denial-of-service attacks
		1267	against local programs (e.g. when setuid), although the impact is likely
		1268	small, as the program has to handle connection errors already-
		1269
		1270	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>
		1272	- only support IPv4, never try to resolve or contact IPv6
		1273	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		1274	IPv6, but prefer IPv6 over IPv4.
		1275
		1276	=item C<PERL_ANYEVENT_EDNS0>
		1277
		1278	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
		1279	for DNS. This extension is generally useful to reduce DNS traffic, but
		1280	some (broken) firewalls drop such DNS packets, which is why it is off by
		1281	default.
		1282
		1283	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		1284	EDNS0 in its DNS requests.
		1285
		1286	=item C<PERL_ANYEVENT_MAX_FORKS>
		1287
		1288	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1289	will create in parallel.
		1290
		1291	=back
1000		1292
1001	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	1293	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1002		1294
1003	This is an advanced topic that you do not normally need to use AnyEvent in	1295	This is an advanced topic that you do not normally need to use AnyEvent in
1004	a module. This section is only of use to event loop authors who want to	1296	a module. This section is only of use to event loop authors who want to
…		…
1038		1330
1039	I<rxvt-unicode> also cheats a bit by not providing blocking access to	1331	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1040	condition variables: code blocking while waiting for a condition will	1332	condition variables: code blocking while waiting for a condition will
1041	C<die>. This still works with most modules/usages, and blocking calls must	1333	C<die>. This still works with most modules/usages, and blocking calls must
1042	not be done in an interactive application, so it makes sense.	1334	not be done in an interactive application, so it makes sense.
1043
1044	=head1 ENVIRONMENT VARIABLES
1045
1046	The following environment variables are used by this module:
1047
1048	=over 4
1049
1050	=item C<PERL_ANYEVENT_VERBOSE>
1051
1052	By default, AnyEvent will be completely silent except in fatal
1053	conditions. You can set this environment variable to make AnyEvent more
1054	talkative.
1055
1056	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1057	conditions, such as not being able to load the event model specified by
1058	C<PERL_ANYEVENT_MODEL>.
1059
1060	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1061	model it chooses.
1062
1063	=item C<PERL_ANYEVENT_MODEL>
1064
1065	This can be used to specify the event model to be used by AnyEvent, before
1066	auto detection and -probing kicks in. It must be a string consisting
1067	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1068	and the resulting module name is loaded and if the load was successful,
1069	used as event model. If it fails to load AnyEvent will proceed with
1070	auto detection and -probing.
1071
1072	This functionality might change in future versions.
1073
1074	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1075	could start your program like this:
1076
1077	PERL_ANYEVENT_MODEL=Perl perl ...
1078
1079	=item C<PERL_ANYEVENT_PROTOCOLS>
1080
1081	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1082	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1083	of auto probing).
1084
1085	Must be set to a comma-separated list of protocols or address families,
1086	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1087	used, and preference will be given to protocols mentioned earlier in the
1088	list.
1089
1090	This variable can effectively be used for denial-of-service attacks
1091	against local programs (e.g. when setuid), although the impact is likely
1092	small, as the program has to handle connection errors already-
1093
1094	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1095	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1096	- only support IPv4, never try to resolve or contact IPv6
1097	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1098	IPv6, but prefer IPv6 over IPv4.
1099
1100	=item C<PERL_ANYEVENT_EDNS0>
1101
1102	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1103	for DNS. This extension is generally useful to reduce DNS traffic, but
1104	some (broken) firewalls drop such DNS packets, which is why it is off by
1105	default.
1106
1107	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1108	EDNS0 in its DNS requests.
1109
1110	=back
1111		1335
1112	=head1 EXAMPLE PROGRAM	1336	=head1 EXAMPLE PROGRAM
1113		1337
1114	The following program uses an I/O watcher to read data from STDIN, a timer	1338	The following program uses an I/O watcher to read data from STDIN, a timer
1115	to display a message once per second, and a condition variable to quit the	1339	to display a message once per second, and a condition variable to quit the
…		…
1552	specified in the variable.	1776	specified in the variable.
1553		1777
1554	You can make AnyEvent completely ignore this variable by deleting it	1778	You can make AnyEvent completely ignore this variable by deleting it
1555	before the first watcher gets created, e.g. with a C<BEGIN> block:	1779	before the first watcher gets created, e.g. with a C<BEGIN> block:
1556		1780
1557	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1781	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1558		1782
1559	use AnyEvent;	1783	use AnyEvent;
1560		1784
1561	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	1785	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1562	be used to probe what backend is used and gain other information (which is	1786	be used to probe what backend is used and gain other information (which is
1563	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	1787	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		1788	$ENV{PERL_ANYEGENT_STRICT}.
		1789
		1790
		1791	=head1 BUGS
		1792
		1793	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		1794	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		1795	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		1796	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
		1797	pronounced).
1564		1798
1565		1799
1566	=head1 SEE ALSO	1800	=head1 SEE ALSO
1567		1801
1568	Utility functions: L<AnyEvent::Util>.	1802	Utility functions: L<AnyEvent::Util>.
…		…
1585	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	1819	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1586		1820
1587		1821
1588	=head1 AUTHOR	1822	=head1 AUTHOR
1589		1823
1590	Marc Lehmann <schmorp@schmorp.de>	1824	Marc Lehmann <schmorp@schmorp.de>
1591	http://home.schmorp.de/	1825	http://home.schmorp.de/
1592		1826
1593	=cut	1827	=cut
1594		1828
1595	1	1829	1
1596		1830

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.134 by root, Sun May 25 04:44:04 2008 UTC vs. Revision 1.183 by root, Wed Oct 1 07:40:39 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.134 by root, Sun May 25 04:44:04 2008 UTC vs.
Revision 1.183 by root, Wed Oct 1 07:40:39 2008 UTC