[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.196 by root, Thu Mar 26 07:47:42 2009 UTC

…		…
1	=head1 => NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, 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
121	These watchers are normal Perl objects with normal Perl lifetime. After	137	These watchers are normal Perl objects with normal Perl lifetime. After
122	creating a watcher it will immediately "watch" for events and invoke the	138	creating a watcher it will immediately "watch" for events and invoke the
123	callback when the event occurs (of course, only when the event model	139	callback when the event occurs (of course, only when the event model
124	is in control).	140	is in control).
125		141
		142	Note that B<callbacks must not permanently change global variables>
		143	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		144	callbacks must not C<die> >>. The former is good programming practise in
		145	Perl and the latter stems from the fact that exception handling differs
		146	widely between event loops.
		147
126	To disable the watcher you have to destroy it (e.g. by setting the	148	To disable the watcher you have to destroy it (e.g. by setting the
127	variable you store it in to C<undef> or otherwise deleting all references	149	variable you store it in to C<undef> or otherwise deleting all references
128	to it).	150	to it).
129		151
130	All watchers are created by calling a method on the C<AnyEvent> class.	152	All watchers are created by calling a method on the C<AnyEvent> class.
…		…
132	Many watchers either are used with "recursion" (repeating timers for	154	Many watchers either are used with "recursion" (repeating timers for
133	example), or need to refer to their watcher object in other ways.	155	example), or need to refer to their watcher object in other ways.
134		156
135	An any way to achieve that is this pattern:	157	An any way to achieve that is this pattern:
136		158
137	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	159	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
138	# you can use $w here, for example to undef it	160	# you can use $w here, for example to undef it
139	undef $w;	161	undef $w;
140	});	162	});
141		163
142	Note that C<my $w; $w => combination. This is necessary because in Perl,	164	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	165	my variables are only visible after the statement in which they are
144	declared.	166	declared.
145		167
146	=head2 I/O WATCHERS	168	=head2 I/O WATCHERS
147		169
148	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	170	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
149	with the following mandatory key-value pairs as arguments:	171	with the following mandatory key-value pairs as arguments:
150		172
151	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	173	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>,	174	(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,	175	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	176	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the
155	becomes ready.	177	callback to invoke each time the file handle becomes ready.
156		178
157	Although the callback might get passed parameters, their value and	179	Although the callback might get passed parameters, their value and
158	presence is undefined and you cannot rely on them. Portable AnyEvent	180	presence is undefined and you cannot rely on them. Portable AnyEvent
159	callbacks cannot use arguments passed to I/O watcher callbacks.	181	callbacks cannot use arguments passed to I/O watcher callbacks.
160		182
…		…
164		186
165	Some event loops issue spurious readyness notifications, so you should	187	Some event loops issue spurious readyness notifications, so you should
166	always use non-blocking calls when reading/writing from/to your file	188	always use non-blocking calls when reading/writing from/to your file
167	handles.	189	handles.
168		190
169	Example:
170
171	# wait for readability of STDIN, then read a line and disable the watcher	191	Example: wait for readability of STDIN, then read a line and disable the
		192	watcher.
		193
172	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	194	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
173	chomp (my $input = <STDIN>);	195	chomp (my $input = <STDIN>);
174	warn "read: $input\n";	196	warn "read: $input\n";
175	undef $w;	197	undef $w;
176	});	198	});
…		…
186		208
187	Although the callback might get passed parameters, their value and	209	Although the callback might get passed parameters, their value and
188	presence is undefined and you cannot rely on them. Portable AnyEvent	210	presence is undefined and you cannot rely on them. Portable AnyEvent
189	callbacks cannot use arguments passed to time watcher callbacks.	211	callbacks cannot use arguments passed to time watcher callbacks.
190		212
191	The timer callback will be invoked at most once: if you want a repeating	213	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	214	parameter, C<interval>, as a strictly positive number (> 0), then the
193	and Glib).	215	callback will be invoked regularly at that interval (in fractional
		216	seconds) after the first invocation. If C<interval> is specified with a
		217	false value, then it is treated as if it were missing.
194		218
195	Example:	219	The callback will be rescheduled before invoking the callback, but no
		220	attempt is done to avoid timer drift in most backends, so the interval is
		221	only approximate.
196		222
197	# fire an event after 7.7 seconds	223	Example: fire an event after 7.7 seconds.
		224
198	my $w = AnyEvent->timer (after => 7.7, cb => sub {	225	my $w = AnyEvent->timer (after => 7.7, cb => sub {
199	warn "timeout\n";	226	warn "timeout\n";
200	});	227	});
201		228
202	# to cancel the timer:	229	# to cancel the timer:
203	undef $w;	230	undef $w;
204		231
205	Example 2:
206
207	# fire an event after 0.5 seconds, then roughly every second	232	Example 2: fire an event after 0.5 seconds, then roughly every second.
208	my $w;
209		233
210	my $cb = sub {
211	# cancel the old timer while creating a new one
212	$w = AnyEvent->timer (after => 1, cb => $cb);	234	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
		235	warn "timeout\n";
213	};	236	};
214
215	# start the "loop" by creating the first watcher
216	$w = AnyEvent->timer (after => 0.5, cb => $cb);
217		237
218	=head3 TIMING ISSUES	238	=head3 TIMING ISSUES
219		239
220	There are two ways to handle timers: based on real time (relative, "fire	240	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	241	in 10 seconds") and based on wallclock time (absolute, "fire at 12
…		…
243		263
244	This returns the "current wallclock time" as a fractional number of	264	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>	265	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).	266	return, and the result is guaranteed to be compatible with those).
247		267
248	It progresses independently of any event loop processing.	268	It progresses independently of any event loop processing, i.e. each call
249		269	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		270
253	=item AnyEvent->now	271	=item AnyEvent->now
254		272
255	This also returns the "current wallclock time", but unlike C<time>, above,	273	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	274	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	275	the event loop (most return the same time as C<time>, above). This is the
258	time that AnyEvent timers get scheduled against.	276	time that AnyEvent's timers get scheduled against.
		277
		278	I<In almost all cases (in all cases if you don't care), this is the
		279	function to call when you want to know the current time.>
		280
		281	This function is also often faster then C<< AnyEvent->time >>, and
		282	thus the preferred method if you want some timestamp (for example,
		283	L<AnyEvent::Handle> uses this to update it's activity timeouts).
		284
		285	The rest of this section is only of relevance if you try to be very exact
		286	with your timing, you can skip it without bad conscience.
259		287
260	For a practical example of when these times differ, consider L<Event::Lib>	288	For a practical example of when these times differ, consider L<Event::Lib>
261	and L<EV> and the following set-up:	289	and L<EV> and the following set-up:
262		290
263	The event loop is running and has just invoked one of your callback at	291	The event loop is running and has just invoked one of your callback at
…		…
268		296
269	With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will	297	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	298	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>).	299	be scheduled to fire at time=504 (C<501> + C<3>).
272		300
273	With L<EV>m C<< AnyEvent->time >> returns C<501> (as that is the current	301	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	302	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	303	last event processing phase started. With L<EV>, your timer gets scheduled
276	to run at time=503 (C<500> + C<3>).	304	to run at time=503 (C<500> + C<3>).
277		305
278	In one sense, L<Event::Lib> is more exact, as it uses the current time	306	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	307	regardless of any delays introduced by event processing. However, most
280	callbacks do not expect large delays in processing, so this causes a	308	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).	309	higher drift (and a lot more system calls to get the current time).
282		310
283	In another sense, L<EV> is more exact, as your timer will be scheduled at	311	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.	312	the same time, regardless of how long event processing actually took.
285		313
286	In either case, if you care (and in most cases, you don't), then you	314	In either case, if you care (and in most cases, you don't), then you
…		…
291	=back	319	=back
292		320
293	=head2 SIGNAL WATCHERS	321	=head2 SIGNAL WATCHERS
294		322
295	You can watch for signals using a signal watcher, C<signal> is the signal	323	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	324	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
297	be invoked whenever a signal occurs.	325	callback to be invoked whenever a signal occurs.
298		326
299	Although the callback might get passed parameters, their value and	327	Although the callback might get passed parameters, their value and
300	presence is undefined and you cannot rely on them. Portable AnyEvent	328	presence is undefined and you cannot rely on them. Portable AnyEvent
301	callbacks cannot use arguments passed to signal watcher callbacks.	329	callbacks cannot use arguments passed to signal watcher callbacks.
302		330
…		…
318	=head2 CHILD PROCESS WATCHERS	346	=head2 CHILD PROCESS WATCHERS
319		347
320	You can also watch on a child process exit and catch its exit status.	348	You can also watch on a child process exit and catch its exit status.
321		349
322	The child process is specified by the C<pid> argument (if set to C<0>, it	350	The child process is specified by the C<pid> argument (if set to C<0>, it
323	watches for any child process exit). The watcher will trigger as often	351	watches for any child process exit). The watcher will triggered only when
324	as status change for the child are received. This works by installing a	352	the child process has finished and an exit status is available, not on
325	signal handler for C<SIGCHLD>. The callback will be called with the pid	353	any trace events (stopped/continued).
326	and exit status (as returned by waitpid), so unlike other watcher types,	354
327	you I<can> rely on child watcher callback arguments.	355	The callback will be called with the pid and exit status (as returned by
		356	waitpid), so unlike other watcher types, you I<can> rely on child watcher
		357	callback arguments.
		358
		359	This watcher type works by installing a signal handler for C<SIGCHLD>,
		360	and since it cannot be shared, nothing else should use SIGCHLD or reap
		361	random child processes (waiting for specific child processes, e.g. inside
		362	C<system>, is just fine).
328		363
329	There is a slight catch to child watchers, however: you usually start them	364	There is a slight catch to child watchers, however: you usually start them
330	I<after> the child process was created, and this means the process could	365	I<after> the child process was created, and this means the process could
331	have exited already (and no SIGCHLD will be sent anymore).	366	have exited already (and no SIGCHLD will be sent anymore).
332		367
…		…
338	AnyEvent program, you I<have> to create at least one watcher before you	373	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>).	374	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
340		375
341	Example: fork a process and wait for it	376	Example: fork a process and wait for it
342		377
343	my $done = AnyEvent->condvar;	378	my $done = AnyEvent->condvar;
344		379
345	my $pid = fork or exit 5;	380	my $pid = fork or exit 5;
346		381
347	my $w = AnyEvent->child (	382	my $w = AnyEvent->child (
348	pid => $pid,	383	pid => $pid,
349	cb => sub {	384	cb => sub {
350	my ($pid, $status) = @_;	385	my ($pid, $status) = @_;
351	warn "pid $pid exited with status $status";	386	warn "pid $pid exited with status $status";
352	$done->send;	387	$done->send;
353	},	388	},
354	);	389	);
355		390
356	# do something else, then wait for process exit	391	# do something else, then wait for process exit
357	$done->recv;	392	$done->recv;
358		393
359	=head2 CONDITION VARIABLES	394	=head2 CONDITION VARIABLES
360		395
361	If you are familiar with some event loops you will know that all of them	396	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	397	require you to run some blocking "loop", "run" or similar function that
…		…
368	The instrument to do that is called a "condition variable", so called	403	The instrument to do that is called a "condition variable", so called
369	because they represent a condition that must become true.	404	because they represent a condition that must become true.
370		405
371	Condition variables can be created by calling the C<< AnyEvent->condvar	406	Condition variables can be created by calling the C<< AnyEvent->condvar
372	>> method, usually without arguments. The only argument pair allowed is	407	>> method, usually without arguments. The only argument pair allowed is
		408
373	C<cb>, which specifies a callback to be called when the condition variable	409	C<cb>, which specifies a callback to be called when the condition variable
374	becomes true.	410	becomes true, with the condition variable as the first argument (but not
		411	the results).
375		412
376	After creation, the condition variable is "false" until it becomes "true"	413	After creation, the condition variable is "false" until it becomes "true"
377	by calling the C<send> method (or calling the condition variable as if it	414	by calling the C<send> method (or calling the condition variable as if it
378	were a callback, read about the caveats in the description for the C<<	415	were a callback, read about the caveats in the description for the C<<
379	->send >> method).	416	->send >> method).
…		…
435		472
436	my $done = AnyEvent->condvar;	473	my $done = AnyEvent->condvar;
437	my $delay = AnyEvent->timer (after => 5, cb => $done);	474	my $delay = AnyEvent->timer (after => 5, cb => $done);
438	$done->recv;	475	$done->recv;
439		476
		477	Example: Imagine an API that returns a condvar and doesn't support
		478	callbacks. This is how you make a synchronous call, for example from
		479	the main program:
		480
		481	use AnyEvent::CouchDB;
		482
		483	...
		484
		485	my @info = $couchdb->info->recv;
		486
		487	And this is how you would just ste a callback to be called whenever the
		488	results are available:
		489
		490	$couchdb->info->cb (sub {
		491	my @info = $_[0]->recv;
		492	});
		493
440	=head3 METHODS FOR PRODUCERS	494	=head3 METHODS FOR PRODUCERS
441		495
442	These methods should only be used by the producing side, i.e. the	496	These methods should only be used by the producing side, i.e. the
443	code/module that eventually sends the signal. Note that it is also	497	code/module that eventually sends the signal. Note that it is also
444	the producer side which creates the condvar in most cases, but it isn't	498	the producer side which creates the condvar in most cases, but it isn't
…		…
577	=item $bool = $cv->ready	631	=item $bool = $cv->ready
578		632
579	Returns true when the condition is "true", i.e. whether C<send> or	633	Returns true when the condition is "true", i.e. whether C<send> or
580	C<croak> have been called.	634	C<croak> have been called.
581		635
582	=item $cb = $cv->cb ([new callback])	636	=item $cb = $cv->cb ($cb->($cv))
583		637
584	This is a mutator function that returns the callback set and optionally	638	This is a mutator function that returns the callback set and optionally
585	replaces it before doing so.	639	replaces it before doing so.
586		640
587	The callback will be called when the condition becomes "true", i.e. when	641	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	642	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.	643	variable itself. Calling C<recv> inside the callback or at any later time
		644	is guaranteed not to block.
590		645
591	=back	646	=back
592		647
593	=head1 GLOBAL VARIABLES AND FUNCTIONS	648	=head1 GLOBAL VARIABLES AND FUNCTIONS
594		649
…		…
723	=item L<AnyEvent::Util>	778	=item L<AnyEvent::Util>
724		779
725	Contains various utility functions that replace often-used but blocking	780	Contains various utility functions that replace often-used but blocking
726	functions such as C<inet_aton> by event-/callback-based versions.	781	functions such as C<inet_aton> by event-/callback-based versions.
727		782
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>	783	=item L<AnyEvent::Socket>
733		784
734	Provides various utility functions for (internet protocol) sockets,	785	Provides various utility functions for (internet protocol) sockets,
735	addresses and name resolution. Also functions to create non-blocking tcp	786	addresses and name resolution. Also functions to create non-blocking tcp
736	connections or tcp servers, with IPv6 and SRV record support and more.	787	connections or tcp servers, with IPv6 and SRV record support and more.
737		788
		789	=item L<AnyEvent::Handle>
		790
		791	Provide read and write buffers, manages watchers for reads and writes,
		792	supports raw and formatted I/O, I/O queued and fully transparent and
		793	non-blocking SSL/TLS.
		794
738	=item L<AnyEvent::DNS>	795	=item L<AnyEvent::DNS>
739		796
740	Provides rich asynchronous DNS resolver capabilities.	797	Provides rich asynchronous DNS resolver capabilities.
741		798
		799	=item L<AnyEvent::HTTP>
		800
		801	A simple-to-use HTTP library that is capable of making a lot of concurrent
		802	HTTP requests.
		803
742	=item L<AnyEvent::HTTPD>	804	=item L<AnyEvent::HTTPD>
743		805
744	Provides a simple web application server framework.	806	Provides a simple web application server framework.
745		807
746	=item L<AnyEvent::FastPing>	808	=item L<AnyEvent::FastPing>
747		809
748	The fastest ping in the west.	810	The fastest ping in the west.
749		811
		812	=item L<AnyEvent::DBI>
		813
		814	Executes L<DBI> requests asynchronously in a proxy process.
		815
		816	=item L<AnyEvent::AIO>
		817
		818	Truly asynchronous I/O, should be in the toolbox of every event
		819	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
		820	together.
		821
		822	=item L<AnyEvent::BDB>
		823
		824	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
		825	L<BDB> and AnyEvent together.
		826
		827	=item L<AnyEvent::GPSD>
		828
		829	A non-blocking interface to gpsd, a daemon delivering GPS information.
		830
		831	=item L<AnyEvent::IGS>
		832
		833	A non-blocking interface to the Internet Go Server protocol (used by
		834	L<App::IGS>).
		835
750	=item L<Net::IRC3>	836	=item L<AnyEvent::IRC>
751		837
752	AnyEvent based IRC client module family.	838	AnyEvent based IRC client module family (replacing the older Net::IRC3).
753		839
754	=item L<Net::XMPP2>	840	=item L<Net::XMPP2>
755		841
756	AnyEvent based XMPP (Jabber protocol) module family.	842	AnyEvent based XMPP (Jabber protocol) module family.
757		843
…		…
766		852
767	=item L<Coro>	853	=item L<Coro>
768		854
769	Has special support for AnyEvent via L<Coro::AnyEvent>.	855	Has special support for AnyEvent via L<Coro::AnyEvent>.
770		856
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>	857	=item L<IO::Lambda>
783		858
784	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	859	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
785		860
786	=back	861	=back
…		…
788	=cut	863	=cut
789		864
790	package AnyEvent;	865	package AnyEvent;
791		866
792	no warnings;	867	no warnings;
793	use strict;	868	use strict qw(vars subs);
794		869
795	use Carp;	870	use Carp;
796		871
797	our $VERSION = '4.05';	872	our $VERSION = 4.341;
798	our $MODEL;	873	our $MODEL;
799		874
800	our $AUTOLOAD;	875	our $AUTOLOAD;
801	our @ISA;	876	our @ISA;
802		877
…		…
905	$MODEL	980	$MODEL
906	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	981	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
907	}	982	}
908	}	983	}
909		984
		985	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		986
910	unshift @ISA, $MODEL;	987	unshift @ISA, $MODEL;
911	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	988
		989	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
912		990
913	(shift @post_detect)->() while @post_detect;	991	(shift @post_detect)->() while @post_detect;
914	}	992	}
915		993
916	$MODEL	994	$MODEL
…		…
926		1004
927	my $class = shift;	1005	my $class = shift;
928	$class->$func (@_);	1006	$class->$func (@_);
929	}	1007	}
930		1008
		1009	# utility function to dup a filehandle. this is used by many backends
		1010	# to support binding more than one watcher per filehandle (they usually
		1011	# allow only one watcher per fd, so we dup it to get a different one).
		1012	sub _dupfh($$$$) {
		1013	my ($poll, $fh, $r, $w) = @_;
		1014
		1015	# cygwin requires the fh mode to be matching, unix doesn't
		1016	my ($rw, $mode) = $poll eq "r" ? ($r, "<")
		1017	: $poll eq "w" ? ($w, ">")
		1018	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
		1019
		1020	open my $fh2, "$mode&" . fileno $fh
		1021	or die "cannot dup() filehandle: $!";
		1022
		1023	# we assume CLOEXEC is already set by perl in all important cases
		1024
		1025	($fh2, $rw)
		1026	}
		1027
931	package AnyEvent::Base;	1028	package AnyEvent::Base;
932		1029
933	# default implementation for now and time	1030	# default implementation for now and time
934		1031
935	use Time::HiRes ();	1032	BEGIN {
		1033	if (eval "use Time::HiRes (); time (); 1") {
		1034	*_time = \&Time::HiRes::time;
		1035	# if (eval "use POSIX (); (POSIX::times())...
		1036	} else {
		1037	*_time = sub { time }; # epic fail
		1038	}
		1039	}
936		1040
937	sub time { Time::HiRes::time }	1041	sub time { _time }
938	sub now { Time::HiRes::time }	1042	sub now { _time }
939		1043
940	# default implementation for ->condvar	1044	# default implementation for ->condvar
941		1045
942	sub condvar {	1046	sub condvar {
943	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1047	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
944	}	1048	}
945		1049
946	# default implementation for ->signal	1050	# default implementation for ->signal
947		1051
948	our %SIG_CB;	1052	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1053
		1054	sub _signal_exec {
		1055	while (%SIG_EV) {
		1056	sysread $SIGPIPE_R, my $dummy, 4;
		1057	for (keys %SIG_EV) {
		1058	delete $SIG_EV{$_};
		1059	$_->() for values %{ $SIG_CB{$_} \|\| {} };
		1060	}
		1061	}
		1062	}
949		1063
950	sub signal {	1064	sub signal {
951	my (undef, %arg) = @_;	1065	my (undef, %arg) = @_;
952		1066
		1067	unless ($SIGPIPE_R) {
		1068	if (AnyEvent::WIN32) {
		1069	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1070	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R) if $SIGPIPE_R;
		1071	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W) if $SIGPIPE_W; # just in case
		1072	} else {
		1073	pipe $SIGPIPE_R, $SIGPIPE_W;
		1074	require Fcntl;
		1075	fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;
		1076	fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case
		1077	}
		1078
		1079	$SIGPIPE_R
		1080	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1081
		1082	$SIG_IO = AnyEvent->io (fh => $SIGPIPE_R, poll => "r", cb => \&_signal_exec);
		1083	}
		1084
953	my $signal = uc $arg{signal}	1085	my $signal = uc $arg{signal}
954	or Carp::croak "required option 'signal' is missing";	1086	or Carp::croak "required option 'signal' is missing";
955		1087
956	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1088	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
957	$SIG{$signal} \|\|= sub {	1089	$SIG{$signal} \|\|= sub {
958	$_->() for values %{ $SIG_CB{$signal} \|\| {} };	1090	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1091	undef $SIG_EV{$signal};
959	};	1092	};
960		1093
961	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1094	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"
962	}	1095	}
963		1096
964	sub AnyEvent::Base::Signal::DESTROY {	1097	sub AnyEvent::Base::Signal::DESTROY {
965	my ($signal, $cb) = @{$_[0]};	1098	my ($signal, $cb) = @{$_[0]};
966		1099
967	delete $SIG_CB{$signal}{$cb};	1100	delete $SIG_CB{$signal}{$cb};
968		1101
969	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1102	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
970	}	1103	}
971		1104
972	# default implementation for ->child	1105	# default implementation for ->child
973		1106
974	our %PID_CB;	1107	our %PID_CB;
…		…
1082		1215
1083	# undocumented/compatibility with pre-3.4	1216	# undocumented/compatibility with pre-3.4
1084	*broadcast = \&send;	1217	*broadcast = \&send;
1085	*wait = \&_wait;	1218	*wait = \&_wait;
1086		1219
		1220	=head1 ERROR AND EXCEPTION HANDLING
		1221
		1222	In general, AnyEvent does not do any error handling - it relies on the
		1223	caller to do that if required. The L<AnyEvent::Strict> module (see also
		1224	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1225	checking of all AnyEvent methods, however, which is highly useful during
		1226	development.
		1227
		1228	As for exception handling (i.e. runtime errors and exceptions thrown while
		1229	executing a callback), this is not only highly event-loop specific, but
		1230	also not in any way wrapped by this module, as this is the job of the main
		1231	program.
		1232
		1233	The pure perl event loop simply re-throws the exception (usually
		1234	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1235	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1236	so on.
		1237
		1238	=head1 ENVIRONMENT VARIABLES
		1239
		1240	The following environment variables are used by this module or its
		1241	submodules:
		1242
		1243	=over 4
		1244
		1245	=item C<PERL_ANYEVENT_VERBOSE>
		1246
		1247	By default, AnyEvent will be completely silent except in fatal
		1248	conditions. You can set this environment variable to make AnyEvent more
		1249	talkative.
		1250
		1251	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		1252	conditions, such as not being able to load the event model specified by
		1253	C<PERL_ANYEVENT_MODEL>.
		1254
		1255	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		1256	model it chooses.
		1257
		1258	=item C<PERL_ANYEVENT_STRICT>
		1259
		1260	AnyEvent does not do much argument checking by default, as thorough
		1261	argument checking is very costly. Setting this variable to a true value
		1262	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1263	check the arguments passed to most method calls. If it finds any problems
		1264	it will croak.
		1265
		1266	In other words, enables "strict" mode.
		1267
		1268	Unlike C<use strict>, it is definitely recommended ot keep it off in
		1269	production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while
		1270	developing programs can be very useful, however.
		1271
		1272	=item C<PERL_ANYEVENT_MODEL>
		1273
		1274	This can be used to specify the event model to be used by AnyEvent, before
		1275	auto detection and -probing kicks in. It must be a string consisting
		1276	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		1277	and the resulting module name is loaded and if the load was successful,
		1278	used as event model. If it fails to load AnyEvent will proceed with
		1279	auto detection and -probing.
		1280
		1281	This functionality might change in future versions.
		1282
		1283	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		1284	could start your program like this:
		1285
		1286	PERL_ANYEVENT_MODEL=Perl perl ...
		1287
		1288	=item C<PERL_ANYEVENT_PROTOCOLS>
		1289
		1290	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
		1291	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
		1292	of auto probing).
		1293
		1294	Must be set to a comma-separated list of protocols or address families,
		1295	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		1296	used, and preference will be given to protocols mentioned earlier in the
		1297	list.
		1298
		1299	This variable can effectively be used for denial-of-service attacks
		1300	against local programs (e.g. when setuid), although the impact is likely
		1301	small, as the program has to handle conenction and other failures anyways.
		1302
		1303	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
		1304	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
		1305	- only support IPv4, never try to resolve or contact IPv6
		1306	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		1307	IPv6, but prefer IPv6 over IPv4.
		1308
		1309	=item C<PERL_ANYEVENT_EDNS0>
		1310
		1311	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
		1312	for DNS. This extension is generally useful to reduce DNS traffic, but
		1313	some (broken) firewalls drop such DNS packets, which is why it is off by
		1314	default.
		1315
		1316	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		1317	EDNS0 in its DNS requests.
		1318
		1319	=item C<PERL_ANYEVENT_MAX_FORKS>
		1320
		1321	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1322	will create in parallel.
		1323
		1324	=back
		1325
1087	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	1326	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1088		1327
1089	This is an advanced topic that you do not normally need to use AnyEvent in	1328	This is an advanced topic that you do not normally need to use AnyEvent in
1090	a module. This section is only of use to event loop authors who want to	1329	a module. This section is only of use to event loop authors who want to
1091	provide AnyEvent compatibility.	1330	provide AnyEvent compatibility.
…		…
1124		1363
1125	I<rxvt-unicode> also cheats a bit by not providing blocking access to	1364	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1126	condition variables: code blocking while waiting for a condition will	1365	condition variables: code blocking while waiting for a condition will
1127	C<die>. This still works with most modules/usages, and blocking calls must	1366	C<die>. This still works with most modules/usages, and blocking calls must
1128	not be done in an interactive application, so it makes sense.	1367	not be done in an interactive application, so it makes sense.
1129
1130	=head1 ENVIRONMENT VARIABLES
1131
1132	The following environment variables are used by this module:
1133
1134	=over 4
1135
1136	=item C<PERL_ANYEVENT_VERBOSE>
1137
1138	By default, AnyEvent will be completely silent except in fatal
1139	conditions. You can set this environment variable to make AnyEvent more
1140	talkative.
1141
1142	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1143	conditions, such as not being able to load the event model specified by
1144	C<PERL_ANYEVENT_MODEL>.
1145
1146	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1147	model it chooses.
1148
1149	=item C<PERL_ANYEVENT_MODEL>
1150
1151	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
1153	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1154	and the resulting module name is loaded and if the load was successful,
1155	used as event model. If it fails to load AnyEvent will proceed with
1156	auto detection and -probing.
1157
1158	This functionality might change in future versions.
1159
1160	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1161	could start your program like this:
1162
1163	PERL_ANYEVENT_MODEL=Perl perl ...
1164
1165	=item C<PERL_ANYEVENT_PROTOCOLS>
1166
1167	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
1169	of auto probing).
1170
1171	Must be set to a comma-separated list of protocols or address families,
1172	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1173	used, and preference will be given to protocols mentioned earlier in the
1174	list.
1175
1176	This variable can effectively be used for denial-of-service attacks
1177	against local programs (e.g. when setuid), although the impact is likely
1178	small, as the program has to handle connection errors already-
1179
1180	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1181	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1182	- only support IPv4, never try to resolve or contact IPv6
1183	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1184	IPv6, but prefer IPv6 over IPv4.
1185
1186	=item C<PERL_ANYEVENT_EDNS0>
1187
1188	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1189	for DNS. This extension is generally useful to reduce DNS traffic, but
1190	some (broken) firewalls drop such DNS packets, which is why it is off by
1191	default.
1192
1193	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1194	EDNS0 in its DNS requests.
1195
1196	=item C<PERL_ANYEVENT_MAX_FORKS>
1197
1198	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1199	will create in parallel.
1200
1201	=back
1202		1368
1203	=head1 EXAMPLE PROGRAM	1369	=head1 EXAMPLE PROGRAM
1204		1370
1205	The following program uses an I/O watcher to read data from STDIN, a timer	1371	The following program uses an I/O watcher to read data from STDIN, a timer
1206	to display a message once per second, and a condition variable to quit the	1372	to display a message once per second, and a condition variable to quit the
…		…
1400	watcher.	1566	watcher.
1401		1567
1402	=head3 Results	1568	=head3 Results
1403		1569
1404	name watchers bytes create invoke destroy comment	1570	name watchers bytes create invoke destroy comment
1405	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	1571	EV/EV 400000 224 0.47 0.35 0.27 EV native interface
1406	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers	1572	EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers
1407	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal	1573	CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal
1408	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation	1574	Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation
1409	Event/Event 16000 516 31.88 31.30 0.85 Event native interface	1575	Event/Event 16000 517 32.20 31.80 0.81 Event native interface
1410	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers	1576	Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers
1411	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour	1577	Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour
1412	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers	1578	Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers
1413	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event	1579	POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event
1414	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select	1580	POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select
1415		1581
1416	=head3 Discussion	1582	=head3 Discussion
1417		1583
1418	The benchmark does I<not> measure scalability of the event loop very	1584	The benchmark does I<not> measure scalability of the event loop very
1419	well. For example, a select-based event loop (such as the pure perl one)	1585	well. For example, a select-based event loop (such as the pure perl one)
…		…
1621	watchers, as the management overhead dominates.	1787	watchers, as the management overhead dominates.
1622		1788
1623	=back	1789	=back
1624		1790
1625		1791
		1792	=head1 SIGNALS
		1793
		1794	AnyEvent currently installs handlers for these signals:
		1795
		1796	=over 4
		1797
		1798	=item SIGCHLD
		1799
		1800	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
		1801	emulation for event loops that do not support them natively. Also, some
		1802	event loops install a similar handler.
		1803
		1804	=item SIGPIPE
		1805
		1806	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
		1807	when AnyEvent gets loaded.
		1808
		1809	The rationale for this is that AnyEvent users usually do not really depend
		1810	on SIGPIPE delivery (which is purely an optimisation for shell use, or
		1811	badly-written programs), but C<SIGPIPE> can cause spurious and rare
		1812	program exits as a lot of people do not expect C<SIGPIPE> when writing to
		1813	some random socket.
		1814
		1815	The rationale for installing a no-op handler as opposed to ignoring it is
		1816	that this way, the handler will be restored to defaults on exec.
		1817
		1818	Feel free to install your own handler, or reset it to defaults.
		1819
		1820	=back
		1821
		1822	=cut
		1823
		1824	$SIG{PIPE} = sub { }
		1825	unless defined $SIG{PIPE};
		1826
		1827
1626	=head1 FORK	1828	=head1 FORK
1627		1829
1628	Most event libraries are not fork-safe. The ones who are usually are	1830	Most event libraries are not fork-safe. The ones who are usually are
1629	because they rely on inefficient but fork-safe C<select> or C<poll>	1831	because they rely on inefficient but fork-safe C<select> or C<poll>
1630	calls. Only L<EV> is fully fork-aware.	1832	calls. Only L<EV> is fully fork-aware.
…		…
1643	specified in the variable.	1845	specified in the variable.
1644		1846
1645	You can make AnyEvent completely ignore this variable by deleting it	1847	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:	1848	before the first watcher gets created, e.g. with a C<BEGIN> block:
1647		1849
1648	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1850	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1649		1851
1650	use AnyEvent;	1852	use AnyEvent;
1651		1853
1652	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	1854	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	1855	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).	1856	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		1857	$ENV{PERL_ANYEGENT_STRICT}.
		1858
		1859
		1860	=head1 BUGS
		1861
		1862	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		1863	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		1864	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		1865	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
		1866	pronounced).
1655		1867
1656		1868
1657	=head1 SEE ALSO	1869	=head1 SEE ALSO
1658		1870
1659	Utility functions: L<AnyEvent::Util>.	1871	Utility functions: L<AnyEvent::Util>.
…		…
1676	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	1888	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1677		1889
1678		1890
1679	=head1 AUTHOR	1891	=head1 AUTHOR
1680		1892
1681	Marc Lehmann <schmorp@schmorp.de>	1893	Marc Lehmann <schmorp@schmorp.de>
1682	http://home.schmorp.de/	1894	http://home.schmorp.de/
1683		1895
1684	=cut	1896	=cut
1685		1897
1686	1	1898	1
1687		1899

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.196 by root, Thu Mar 26 07:47:42 2009 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.196 by root, Thu Mar 26 07:47:42 2009 UTC