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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.144 by root, Thu May 29 00:14:35 2008 UTC vs.
Revision 1.168 by root, Tue Jul 8 23:53:37 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
18		18
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	19	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	20	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	21	$w->recv; # enters "main loop" till $condvar gets ->send
22		22
		23	=head1 INTRODUCTION/TUTORIAL
		24
		25	This manpage is mainly a reference manual. If you are interested
		26	in a tutorial or some gentle introduction, have a look at the
		27	L<AnyEvent::Intro> manpage.
		28
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	29	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		30
25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	31	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26	nowadays. So what is different about AnyEvent?	32	nowadays. So what is different about AnyEvent?
27		33
28	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	34	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
29	policy> and AnyEvent is I<small and efficient>.	35	policy> and AnyEvent is I<small and efficient>.
30		36
31	First and foremost, I<AnyEvent is not an event model> itself, it only	37	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	38	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,	39	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,	40	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	41	only one event loop can be active at the same time in a process. AnyEvent
36	helps hiding the differences between those event loops.	42	cannot change this, but it can hide the differences between those event
		43	loops.
37		44
38	The goal of AnyEvent is to offer module authors the ability to do event	45	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	46	programming (waiting for I/O or timer events) without subscribing to a
40	religion, a way of living, and most importantly: without forcing your	47	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	48	module users into the same thing by forcing them to use the same event
42	model you use.	49	model you use.
43		50
44	For modules like POE or IO::Async (which is a total misnomer as it is	51	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	52	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	53	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	54	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	55	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.	56	module are I<also> forced to use the same event loop you use.
50		57
51	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	58	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
52	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	59	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	60	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,	61	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	62	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	63	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	64	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).	65	to AnyEvent, too, so it is future-proof).
59		66
60	In addition to being free of having to use I<the one and only true event	67	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	68	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	69	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	70	follow. AnyEvent, on the other hand, is lean and up to the point, by only
…		…
132	Many watchers either are used with "recursion" (repeating timers for	139	Many watchers either are used with "recursion" (repeating timers for
133	example), or need to refer to their watcher object in other ways.	140	example), or need to refer to their watcher object in other ways.
134		141
135	An any way to achieve that is this pattern:	142	An any way to achieve that is this pattern:
136		143
137	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	144	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
138	# you can use $w here, for example to undef it	145	# you can use $w here, for example to undef it
139	undef $w;	146	undef $w;
140	});	147	});
141		148
142	Note that C<my $w; $w => combination. This is necessary because in Perl,	149	Note that C<my $w; $w => combination. This is necessary because in Perl,
143	my variables are only visible after the statement in which they are	150	my variables are only visible after the statement in which they are
144	declared.	151	declared.
145		152
146	=head2 I/O WATCHERS	153	=head2 I/O WATCHERS
147		154
148	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	155	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
149	with the following mandatory key-value pairs as arguments:	156	with the following mandatory key-value pairs as arguments:
150		157
151	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	158	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events
152	for events. C<poll> must be a string that is either C<r> or C<w>,	159	(AnyEvent might or might not keep a reference to this file handle). C<poll>
153	which creates a watcher waiting for "r"eadable or "w"ritable events,	160	must be a string that is either C<r> or C<w>, which creates a watcher
154	respectively. C<cb> is the callback to invoke each time the file handle	161	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the
155	becomes ready.	162	callback to invoke each time the file handle becomes ready.
156		163
157	Although the callback might get passed parameters, their value and	164	Although the callback might get passed parameters, their value and
158	presence is undefined and you cannot rely on them. Portable AnyEvent	165	presence is undefined and you cannot rely on them. Portable AnyEvent
159	callbacks cannot use arguments passed to I/O watcher callbacks.	166	callbacks cannot use arguments passed to I/O watcher callbacks.
160		167
…		…
164		171
165	Some event loops issue spurious readyness notifications, so you should	172	Some event loops issue spurious readyness notifications, so you should
166	always use non-blocking calls when reading/writing from/to your file	173	always use non-blocking calls when reading/writing from/to your file
167	handles.	174	handles.
168		175
169	Example:
170
171	# wait for readability of STDIN, then read a line and disable the watcher	176	Example: wait for readability of STDIN, then read a line and disable the
		177	watcher.
		178
172	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	179	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
173	chomp (my $input = <STDIN>);	180	chomp (my $input = <STDIN>);
174	warn "read: $input\n";	181	warn "read: $input\n";
175	undef $w;	182	undef $w;
176	});	183	});
…		…
186		193
187	Although the callback might get passed parameters, their value and	194	Although the callback might get passed parameters, their value and
188	presence is undefined and you cannot rely on them. Portable AnyEvent	195	presence is undefined and you cannot rely on them. Portable AnyEvent
189	callbacks cannot use arguments passed to time watcher callbacks.	196	callbacks cannot use arguments passed to time watcher callbacks.
190		197
191	The timer callback will be invoked at most once: if you want a repeating	198	The callback will normally be invoked once only. If you specify another
192	timer you have to create a new watcher (this is a limitation by both Tk	199	parameter, C<interval>, as a strictly positive number (> 0), then the
193	and Glib).	200	callback will be invoked regularly at that interval (in fractional
		201	seconds) after the first invocation. If C<interval> is specified with a
		202	false value, then it is treated as if it were missing.
194		203
195	Example:	204	The callback will be rescheduled before invoking the callback, but no
		205	attempt is done to avoid timer drift in most backends, so the interval is
		206	only approximate.
196		207
197	# fire an event after 7.7 seconds	208	Example: fire an event after 7.7 seconds.
		209
198	my $w = AnyEvent->timer (after => 7.7, cb => sub {	210	my $w = AnyEvent->timer (after => 7.7, cb => sub {
199	warn "timeout\n";	211	warn "timeout\n";
200	});	212	});
201		213
202	# to cancel the timer:	214	# to cancel the timer:
203	undef $w;	215	undef $w;
204		216
205	Example 2:
206
207	# fire an event after 0.5 seconds, then roughly every second	217	Example 2: fire an event after 0.5 seconds, then roughly every second.
208	my $w;
209		218
210	my $cb = sub {
211	# cancel the old timer while creating a new one
212	$w = AnyEvent->timer (after => 1, cb => $cb);	219	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
		220	warn "timeout\n";
213	};	221	};
214
215	# start the "loop" by creating the first watcher
216	$w = AnyEvent->timer (after => 0.5, cb => $cb);
217		222
218	=head3 TIMING ISSUES	223	=head3 TIMING ISSUES
219		224
220	There are two ways to handle timers: based on real time (relative, "fire	225	There are two ways to handle timers: based on real time (relative, "fire
221	in 10 seconds") and based on wallclock time (absolute, "fire at 12	226	in 10 seconds") and based on wallclock time (absolute, "fire at 12
…		…
299	=back	304	=back
300		305
301	=head2 SIGNAL WATCHERS	306	=head2 SIGNAL WATCHERS
302		307
303	You can watch for signals using a signal watcher, C<signal> is the signal	308	You can watch for signals using a signal watcher, C<signal> is the signal
304	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	309	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
305	be invoked whenever a signal occurs.	310	callback to be invoked whenever a signal occurs.
306		311
307	Although the callback might get passed parameters, their value and	312	Although the callback might get passed parameters, their value and
308	presence is undefined and you cannot rely on them. Portable AnyEvent	313	presence is undefined and you cannot rely on them. Portable AnyEvent
309	callbacks cannot use arguments passed to signal watcher callbacks.	314	callbacks cannot use arguments passed to signal watcher callbacks.
310		315
…		…
346	AnyEvent program, you I<have> to create at least one watcher before you	351	AnyEvent program, you I<have> to create at least one watcher before you
347	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	352	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
348		353
349	Example: fork a process and wait for it	354	Example: fork a process and wait for it
350		355
351	my $done = AnyEvent->condvar;	356	my $done = AnyEvent->condvar;
352		357
353	my $pid = fork or exit 5;	358	my $pid = fork or exit 5;
354		359
355	my $w = AnyEvent->child (	360	my $w = AnyEvent->child (
356	pid => $pid,	361	pid => $pid,
357	cb => sub {	362	cb => sub {
358	my ($pid, $status) = @_;	363	my ($pid, $status) = @_;
359	warn "pid $pid exited with status $status";	364	warn "pid $pid exited with status $status";
360	$done->send;	365	$done->send;
361	},	366	},
362	);	367	);
363		368
364	# do something else, then wait for process exit	369	# do something else, then wait for process exit
365	$done->recv;	370	$done->recv;
366		371
367	=head2 CONDITION VARIABLES	372	=head2 CONDITION VARIABLES
368		373
369	If you are familiar with some event loops you will know that all of them	374	If you are familiar with some event loops you will know that all of them
370	require you to run some blocking "loop", "run" or similar function that	375	require you to run some blocking "loop", "run" or similar function that
…		…
591		596
592	This is a mutator function that returns the callback set and optionally	597	This is a mutator function that returns the callback set and optionally
593	replaces it before doing so.	598	replaces it before doing so.
594		599
595	The callback will be called when the condition becomes "true", i.e. when	600	The callback will be called when the condition becomes "true", i.e. when
596	C<send> or C<croak> are called. Calling C<recv> inside the callback	601	C<send> or C<croak> are called, with the only argument being the condition
597	or at any later time is guaranteed not to block.	602	variable itself. Calling C<recv> inside the callback or at any later time
		603	is guaranteed not to block.
598		604
599	=back	605	=back
600		606
601	=head1 GLOBAL VARIABLES AND FUNCTIONS	607	=head1 GLOBAL VARIABLES AND FUNCTIONS
602		608
…		…
731	=item L<AnyEvent::Util>	737	=item L<AnyEvent::Util>
732		738
733	Contains various utility functions that replace often-used but blocking	739	Contains various utility functions that replace often-used but blocking
734	functions such as C<inet_aton> by event-/callback-based versions.	740	functions such as C<inet_aton> by event-/callback-based versions.
735		741
736	=item L<AnyEvent::Handle>
737
738	Provide read and write buffers and manages watchers for reads and writes.
739
740	=item L<AnyEvent::Socket>	742	=item L<AnyEvent::Socket>
741		743
742	Provides various utility functions for (internet protocol) sockets,	744	Provides various utility functions for (internet protocol) sockets,
743	addresses and name resolution. Also functions to create non-blocking tcp	745	addresses and name resolution. Also functions to create non-blocking tcp
744	connections or tcp servers, with IPv6 and SRV record support and more.	746	connections or tcp servers, with IPv6 and SRV record support and more.
745		747
		748	=item L<AnyEvent::Handle>
		749
		750	Provide read and write buffers, manages watchers for reads and writes,
		751	supports raw and formatted I/O, I/O queued and fully transparent and
		752	non-blocking SSL/TLS.
		753
746	=item L<AnyEvent::DNS>	754	=item L<AnyEvent::DNS>
747		755
748	Provides rich asynchronous DNS resolver capabilities.	756	Provides rich asynchronous DNS resolver capabilities.
749		757
		758	=item L<AnyEvent::HTTP>
		759
		760	A simple-to-use HTTP library that is capable of making a lot of concurrent
		761	HTTP requests.
		762
750	=item L<AnyEvent::HTTPD>	763	=item L<AnyEvent::HTTPD>
751		764
752	Provides a simple web application server framework.	765	Provides a simple web application server framework.
753		766
754	=item L<AnyEvent::FastPing>	767	=item L<AnyEvent::FastPing>
755		768
756	The fastest ping in the west.	769	The fastest ping in the west.
		770
		771	=item L<AnyEvent::DBI>
		772
		773	Executes L<DBI> requests asynchronously in a proxy process.
		774
		775	=item L<AnyEvent::AIO>
		776
		777	Truly asynchronous I/O, should be in the toolbox of every event
		778	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
		779	together.
		780
		781	=item L<AnyEvent::BDB>
		782
		783	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
		784	L<BDB> and AnyEvent together.
		785
		786	=item L<AnyEvent::GPSD>
		787
		788	A non-blocking interface to gpsd, a daemon delivering GPS information.
		789
		790	=item L<AnyEvent::IGS>
		791
		792	A non-blocking interface to the Internet Go Server protocol (used by
		793	L<App::IGS>).
757		794
758	=item L<Net::IRC3>	795	=item L<Net::IRC3>
759		796
760	AnyEvent based IRC client module family.	797	AnyEvent based IRC client module family.
761		798
…		…
774		811
775	=item L<Coro>	812	=item L<Coro>
776		813
777	Has special support for AnyEvent via L<Coro::AnyEvent>.	814	Has special support for AnyEvent via L<Coro::AnyEvent>.
778		815
779	=item L<AnyEvent::AIO>, L<IO::AIO>
780
781	Truly asynchronous I/O, should be in the toolbox of every event
782	programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
783	together.
784
785	=item L<AnyEvent::BDB>, L<BDB>
786
787	Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
788	IO::AIO and AnyEvent together.
789
790	=item L<IO::Lambda>	816	=item L<IO::Lambda>
791		817
792	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	818	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
793		819
794	=back	820	=back
…		…
800	no warnings;	826	no warnings;
801	use strict;	827	use strict;
802		828
803	use Carp;	829	use Carp;
804		830
805	our $VERSION = '4.05';	831	our $VERSION = 4.2;
806	our $MODEL;	832	our $MODEL;
807		833
808	our $AUTOLOAD;	834	our $AUTOLOAD;
809	our @ISA;	835	our @ISA;
810		836
…		…
913	$MODEL	939	$MODEL
914	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	940	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
915	}	941	}
916	}	942	}
917		943
		944	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		945
918	unshift @ISA, $MODEL;	946	unshift @ISA, $MODEL;
919	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	947
		948	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
920		949
921	(shift @post_detect)->() while @post_detect;	950	(shift @post_detect)->() while @post_detect;
922	}	951	}
923		952
924	$MODEL	953	$MODEL
…		…
972	sub AnyEvent::Base::Signal::DESTROY {	1001	sub AnyEvent::Base::Signal::DESTROY {
973	my ($signal, $cb) = @{$_[0]};	1002	my ($signal, $cb) = @{$_[0]};
974		1003
975	delete $SIG_CB{$signal}{$cb};	1004	delete $SIG_CB{$signal}{$cb};
976		1005
977	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1006	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
978	}	1007	}
979		1008
980	# default implementation for ->child	1009	# default implementation for ->child
981		1010
982	our %PID_CB;	1011	our %PID_CB;
…		…
1152	C<PERL_ANYEVENT_MODEL>.	1181	C<PERL_ANYEVENT_MODEL>.
1153		1182
1154	When set to C<2> or higher, cause AnyEvent to report to STDERR which event	1183	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1155	model it chooses.	1184	model it chooses.
1156		1185
		1186	=item C<PERL_ANYEVENT_STRICT>
		1187
		1188	AnyEvent does not do much argument checking by default, as thorough
		1189	argument checking is very costly. Setting this variable to a true value
		1190	will cause AnyEvent to thoroughly check the arguments passed to most
		1191	method calls and croaks if it finds any problems. In other words, enables
		1192	"strict" mode. Unlike C<use strict> it is definitely recommended ot keep
		1193	it off in production.
		1194
1157	=item C<PERL_ANYEVENT_MODEL>	1195	=item C<PERL_ANYEVENT_MODEL>
1158		1196
1159	This can be used to specify the event model to be used by AnyEvent, before	1197	This can be used to specify the event model to be used by AnyEvent, before
1160	auto detection and -probing kicks in. It must be a string consisting	1198	auto detection and -probing kicks in. It must be a string consisting
1161	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended	1199	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
…		…
1166	This functionality might change in future versions.	1204	This functionality might change in future versions.
1167		1205
1168	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you	1206	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1169	could start your program like this:	1207	could start your program like this:
1170		1208
1171	PERL_ANYEVENT_MODEL=Perl perl ...	1209	PERL_ANYEVENT_MODEL=Perl perl ...
1172		1210
1173	=item C<PERL_ANYEVENT_PROTOCOLS>	1211	=item C<PERL_ANYEVENT_PROTOCOLS>
1174		1212
1175	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences	1213	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1176	for IPv4 or IPv6. The default is unspecified (and might change, or be the result	1214	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
…		…
1651	specified in the variable.	1689	specified in the variable.
1652		1690
1653	You can make AnyEvent completely ignore this variable by deleting it	1691	You can make AnyEvent completely ignore this variable by deleting it
1654	before the first watcher gets created, e.g. with a C<BEGIN> block:	1692	before the first watcher gets created, e.g. with a C<BEGIN> block:
1655		1693
1656	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1694	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1657		1695
1658	use AnyEvent;	1696	use AnyEvent;
1659		1697
1660	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	1698	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1661	be used to probe what backend is used and gain other information (which is	1699	be used to probe what backend is used and gain other information (which is
1662	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	1700	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		1701	$ENV{PERL_ANYEGENT_STRICT}.
		1702
		1703
		1704	=head1 BUGS
		1705
		1706	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		1707	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		1708	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		1709	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
		1710	pronounced).
1663		1711
1664		1712
1665	=head1 SEE ALSO	1713	=head1 SEE ALSO
1666		1714
1667	Utility functions: L<AnyEvent::Util>.	1715	Utility functions: L<AnyEvent::Util>.
…		…
1684	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	1732	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1685		1733
1686		1734
1687	=head1 AUTHOR	1735	=head1 AUTHOR
1688		1736
1689	Marc Lehmann <schmorp@schmorp.de>	1737	Marc Lehmann <schmorp@schmorp.de>
1690	http://home.schmorp.de/	1738	http://home.schmorp.de/
1691		1739
1692	=cut	1740	=cut
1693		1741
1694	1	1742	1
1695		1743

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.144 by root, Thu May 29 00:14:35 2008 UTC vs. Revision 1.168 by root, Tue Jul 8 23:53:37 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.144 by root, Thu May 29 00:14:35 2008 UTC vs.
Revision 1.168 by root, Tue Jul 8 23:53:37 2008 UTC