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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.143 by root, Wed May 28 23:57:38 2008 UTC vs.
Revision 1.172 by root, Thu Jul 17 15:21:02 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
…		…
243		248
244	This returns the "current wallclock time" as a fractional number of	249	This returns the "current wallclock time" as a fractional number of
245	seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time>	250	seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time>
246	return, and the result is guaranteed to be compatible with those).	251	return, and the result is guaranteed to be compatible with those).
247		252
248	It progresses independently of any event loop processing.	253	It progresses independently of any event loop processing, i.e. each call
249		254	will check the system clock, which usually gets updated frequently.
250	In almost all cases (in all cases if you don't care), this is the function
251	to call when you want to know the current time.
252		255
253	=item AnyEvent->now	256	=item AnyEvent->now
254		257
255	This also returns the "current wallclock time", but unlike C<time>, above,	258	This also returns the "current wallclock time", but unlike C<time>, above,
256	this value might change only once per event loop iteration, depending on	259	this value might change only once per event loop iteration, depending on
257	the event loop (most return the same time as C<time>, above). This is the	260	the event loop (most return the same time as C<time>, above). This is the
258	time that AnyEvent timers get scheduled against.	261	time that AnyEvent's timers get scheduled against.
		262
		263	I<In almost all cases (in all cases if you don't care), this is the
		264	function to call when you want to know the current time.>
		265
		266	This function is also often faster then C<< AnyEvent->time >>, and
		267	thus the preferred method if you want some timestamp (for example,
		268	L<AnyEvent::Handle> uses this to update it's activity timeouts).
		269
		270	The rest of this section is only of relevance if you try to be very exact
		271	with your timing, you can skip it without bad conscience.
259		272
260	For a practical example of when these times differ, consider L<Event::Lib>	273	For a practical example of when these times differ, consider L<Event::Lib>
261	and L<EV> and the following set-up:	274	and L<EV> and the following set-up:
262		275
263	The event loop is running and has just invoked one of your callback at	276	The event loop is running and has just invoked one of your callback at
…		…
268		281
269	With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will	282	With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will
270	both return C<501>, because that is the current time, and the timer will	283	both return C<501>, because that is the current time, and the timer will
271	be scheduled to fire at time=504 (C<501> + C<3>).	284	be scheduled to fire at time=504 (C<501> + C<3>).
272		285
273	With L<EV>m C<< AnyEvent->time >> returns C<501> (as that is the current	286	With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current
274	time), but C<< AnyEvent->now >> returns C<500>, as that is the time the	287	time), but C<< AnyEvent->now >> returns C<500>, as that is the time the
275	last event processing phase started. With L<EV>, your timer gets scheduled	288	last event processing phase started. With L<EV>, your timer gets scheduled
276	to run at time=503 (C<500> + C<3>).	289	to run at time=503 (C<500> + C<3>).
277		290
278	In one sense, L<Event::Lib> is more exact, as it uses the current time	291	In one sense, L<Event::Lib> is more exact, as it uses the current time
279	regardless of any delays introduced by event processing. However, most	292	regardless of any delays introduced by event processing. However, most
280	callbacks do not expect large delays in processing, so this causes a	293	callbacks do not expect large delays in processing, so this causes a
281	higher drift (and a lot more syscalls to get the current time).	294	higher drift (and a lot more system calls to get the current time).
282		295
283	In another sense, L<EV> is more exact, as your timer will be scheduled at	296	In another sense, L<EV> is more exact, as your timer will be scheduled at
284	the same time, regardless of how long event processing actually took.	297	the same time, regardless of how long event processing actually took.
285		298
286	In either case, if you care (and in most cases, you don't), then you	299	In either case, if you care (and in most cases, you don't), then you
…		…
291	=back	304	=back
292		305
293	=head2 SIGNAL WATCHERS	306	=head2 SIGNAL WATCHERS
294		307
295	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
296	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
297	be invoked whenever a signal occurs.	310	callback to be invoked whenever a signal occurs.
298		311
299	Although the callback might get passed parameters, their value and	312	Although the callback might get passed parameters, their value and
300	presence is undefined and you cannot rely on them. Portable AnyEvent	313	presence is undefined and you cannot rely on them. Portable AnyEvent
301	callbacks cannot use arguments passed to signal watcher callbacks.	314	callbacks cannot use arguments passed to signal watcher callbacks.
302		315
…		…
338	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
339	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	352	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
340		353
341	Example: fork a process and wait for it	354	Example: fork a process and wait for it
342		355
343	my $done = AnyEvent->condvar;	356	my $done = AnyEvent->condvar;
344		357
345	my $pid = fork or exit 5;	358	my $pid = fork or exit 5;
346		359
347	my $w = AnyEvent->child (	360	my $w = AnyEvent->child (
348	pid => $pid,	361	pid => $pid,
349	cb => sub {	362	cb => sub {
350	my ($pid, $status) = @_;	363	my ($pid, $status) = @_;
351	warn "pid $pid exited with status $status";	364	warn "pid $pid exited with status $status";
352	$done->send;	365	$done->send;
353	},	366	},
354	);	367	);
355		368
356	# do something else, then wait for process exit	369	# do something else, then wait for process exit
357	$done->recv;	370	$done->recv;
358		371
359	=head2 CONDITION VARIABLES	372	=head2 CONDITION VARIABLES
360		373
361	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
362	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
…		…
583		596
584	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
585	replaces it before doing so.	598	replaces it before doing so.
586		599
587	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
588	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
589	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.
590		604
591	=back	605	=back
592		606
593	=head1 GLOBAL VARIABLES AND FUNCTIONS	607	=head1 GLOBAL VARIABLES AND FUNCTIONS
594		608
…		…
723	=item L<AnyEvent::Util>	737	=item L<AnyEvent::Util>
724		738
725	Contains various utility functions that replace often-used but blocking	739	Contains various utility functions that replace often-used but blocking
726	functions such as C<inet_aton> by event-/callback-based versions.	740	functions such as C<inet_aton> by event-/callback-based versions.
727		741
728	=item L<AnyEvent::Handle>
729
730	Provide read and write buffers and manages watchers for reads and writes.
731
732	=item L<AnyEvent::Socket>	742	=item L<AnyEvent::Socket>
733		743
734	Provides various utility functions for (internet protocol) sockets,	744	Provides various utility functions for (internet protocol) sockets,
735	addresses and name resolution. Also functions to create non-blocking tcp	745	addresses and name resolution. Also functions to create non-blocking tcp
736	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.
737		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
738	=item L<AnyEvent::DNS>	754	=item L<AnyEvent::DNS>
739		755
740	Provides rich asynchronous DNS resolver capabilities.	756	Provides rich asynchronous DNS resolver capabilities.
741		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
742	=item L<AnyEvent::HTTPD>	763	=item L<AnyEvent::HTTPD>
743		764
744	Provides a simple web application server framework.	765	Provides a simple web application server framework.
745		766
746	=item L<AnyEvent::FastPing>	767	=item L<AnyEvent::FastPing>
747		768
748	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>).
749		794
750	=item L<Net::IRC3>	795	=item L<Net::IRC3>
751		796
752	AnyEvent based IRC client module family.	797	AnyEvent based IRC client module family.
753		798
…		…
766		811
767	=item L<Coro>	812	=item L<Coro>
768		813
769	Has special support for AnyEvent via L<Coro::AnyEvent>.	814	Has special support for AnyEvent via L<Coro::AnyEvent>.
770		815
771	=item L<AnyEvent::AIO>, L<IO::AIO>
772
773	Truly asynchronous I/O, should be in the toolbox of every event
774	programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
775	together.
776
777	=item L<AnyEvent::BDB>, L<BDB>
778
779	Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
780	IO::AIO and AnyEvent together.
781
782	=item L<IO::Lambda>	816	=item L<IO::Lambda>
783		817
784	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.
785		819
786	=back	820	=back
…		…
792	no warnings;	826	no warnings;
793	use strict;	827	use strict;
794		828
795	use Carp;	829	use Carp;
796		830
797	our $VERSION = '4.05';	831	our $VERSION = 4.22;
798	our $MODEL;	832	our $MODEL;
799		833
800	our $AUTOLOAD;	834	our $AUTOLOAD;
801	our @ISA;	835	our @ISA;
802		836
…		…
905	$MODEL	939	$MODEL
906	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.";
907	}	941	}
908	}	942	}
909		943
		944	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		945
910	unshift @ISA, $MODEL;	946	unshift @ISA, $MODEL;
911	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	947
		948	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
912		949
913	(shift @post_detect)->() while @post_detect;	950	(shift @post_detect)->() while @post_detect;
914	}	951	}
915		952
916	$MODEL	953	$MODEL
…		…
924		961
925	detect unless $MODEL;	962	detect unless $MODEL;
926		963
927	my $class = shift;	964	my $class = shift;
928	$class->$func (@_);	965	$class->$func (@_);
		966	}
		967
		968	# utility function to dup a filehandle. this is used by many backends
		969	# to support binding more than one watcher per filehandle (they usually
		970	# allow only one watcher per fd, so we dup it to get a different one).
		971	sub _dupfh($$$$) {
		972	my ($poll, $fh, $r, $w) = @_;
		973
		974	require Fcntl;
		975
		976	# cygwin requires the fh mode to be matching, unix doesn't
		977	my ($rw, $mode) = $poll eq "r" ? ($r, "<")
		978	: $poll eq "w" ? ($w, ">")
		979	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
		980
		981	open my $fh2, "$mode&" . fileno $fh
		982	or die "cannot dup() filehandle: $!";
		983
		984	# we assume CLOEXEC is already set by perl in all important cases
		985
		986	($fh2, $rw)
929	}	987	}
930		988
931	package AnyEvent::Base;	989	package AnyEvent::Base;
932		990
933	# default implementation for now and time	991	# default implementation for now and time
…		…
964	sub AnyEvent::Base::Signal::DESTROY {	1022	sub AnyEvent::Base::Signal::DESTROY {
965	my ($signal, $cb) = @{$_[0]};	1023	my ($signal, $cb) = @{$_[0]};
966		1024
967	delete $SIG_CB{$signal}{$cb};	1025	delete $SIG_CB{$signal}{$cb};
968		1026
969	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1027	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
970	}	1028	}
971		1029
972	# default implementation for ->child	1030	# default implementation for ->child
973		1031
974	our %PID_CB;	1032	our %PID_CB;
…		…
1144	C<PERL_ANYEVENT_MODEL>.	1202	C<PERL_ANYEVENT_MODEL>.
1145		1203
1146	When set to C<2> or higher, cause AnyEvent to report to STDERR which event	1204	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1147	model it chooses.	1205	model it chooses.
1148		1206
		1207	=item C<PERL_ANYEVENT_STRICT>
		1208
		1209	AnyEvent does not do much argument checking by default, as thorough
		1210	argument checking is very costly. Setting this variable to a true value
		1211	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1212	check the arguments passed to most method calls. If it finds any problems
		1213	it will croak.
		1214
		1215	In other words, enables "strict" mode.
		1216
		1217	Unlike C<use strict> it is definitely recommended ot keep it off in
		1218	production.
		1219
1149	=item C<PERL_ANYEVENT_MODEL>	1220	=item C<PERL_ANYEVENT_MODEL>
1150		1221
1151	This can be used to specify the event model to be used by AnyEvent, before	1222	This can be used to specify the event model to be used by AnyEvent, before
1152	auto detection and -probing kicks in. It must be a string consisting	1223	auto detection and -probing kicks in. It must be a string consisting
1153	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended	1224	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
…		…
1158	This functionality might change in future versions.	1229	This functionality might change in future versions.
1159		1230
1160	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you	1231	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1161	could start your program like this:	1232	could start your program like this:
1162		1233
1163	PERL_ANYEVENT_MODEL=Perl perl ...	1234	PERL_ANYEVENT_MODEL=Perl perl ...
1164		1235
1165	=item C<PERL_ANYEVENT_PROTOCOLS>	1236	=item C<PERL_ANYEVENT_PROTOCOLS>
1166		1237
1167	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences	1238	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1168	for IPv4 or IPv6. The default is unspecified (and might change, or be the result	1239	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
…		…
1643	specified in the variable.	1714	specified in the variable.
1644		1715
1645	You can make AnyEvent completely ignore this variable by deleting it	1716	You can make AnyEvent completely ignore this variable by deleting it
1646	before the first watcher gets created, e.g. with a C<BEGIN> block:	1717	before the first watcher gets created, e.g. with a C<BEGIN> block:
1647		1718
1648	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1719	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1649		1720
1650	use AnyEvent;	1721	use AnyEvent;
1651		1722
1652	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	1723	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1653	be used to probe what backend is used and gain other information (which is	1724	be used to probe what backend is used and gain other information (which is
1654	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	1725	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		1726	$ENV{PERL_ANYEGENT_STRICT}.
		1727
		1728
		1729	=head1 BUGS
		1730
		1731	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		1732	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		1733	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		1734	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
		1735	pronounced).
1655		1736
1656		1737
1657	=head1 SEE ALSO	1738	=head1 SEE ALSO
1658		1739
1659	Utility functions: L<AnyEvent::Util>.	1740	Utility functions: L<AnyEvent::Util>.
…		…
1676	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	1757	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1677		1758
1678		1759
1679	=head1 AUTHOR	1760	=head1 AUTHOR
1680		1761
1681	Marc Lehmann <schmorp@schmorp.de>	1762	Marc Lehmann <schmorp@schmorp.de>
1682	http://home.schmorp.de/	1763	http://home.schmorp.de/
1683		1764
1684	=cut	1765	=cut
1685		1766
1686	1	1767	1
1687		1768

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.143 by root, Wed May 28 23:57:38 2008 UTC vs. Revision 1.172 by root, Thu Jul 17 15:21:02 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.143 by root, Wed May 28 23:57:38 2008 UTC vs.
Revision 1.172 by root, Thu Jul 17 15:21:02 2008 UTC