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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.105 by root, Thu May 1 12:35:54 2008 UTC vs.
Revision 1.112 by root, Sat May 10 01:04:42 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, Coro::EV, Coro::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
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	15	my $w = AnyEvent->timer (after => $seconds, cb => sub {
16	...	16	...
17	});	17	});
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->wait; # enters "main loop" till $condvar gets ->broadcast	20	$w->wait; # enters "main loop" till $condvar gets ->send
21	$w->broadcast; # wake up current and all future wait's	21	$w->send; # wake up current and all future wait's
22		22
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		24
25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26	nowadays. So what is different about AnyEvent?	26	nowadays. So what is different about AnyEvent?
…		…
78	The interface itself is vaguely similar, but not identical to the L<Event>	78	The interface itself is vaguely similar, but not identical to the L<Event>
79	module.	79	module.
80		80
81	During the first call of any watcher-creation method, the module tries	81	During the first call of any watcher-creation method, the module tries
82	to detect the currently loaded event loop by probing whether one of the	82	to detect the currently loaded event loop by probing whether one of the
83	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,	83	following modules is already loaded: L<EV>,
84	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,	84	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
85	L<POE>. The first one found is used. If none are found, the module tries	85	L<POE>. The first one found is used. If none are found, the module tries
86	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl	86	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
87	adaptor should always succeed) in the order given. The first one that can	87	adaptor should always succeed) in the order given. The first one that can
88	be successfully loaded will be used. If, after this, still none could be	88	be successfully loaded will be used. If, after this, still none could be
…		…
288	my $w = AnyEvent->child (	288	my $w = AnyEvent->child (
289	pid => $pid,	289	pid => $pid,
290	cb => sub {	290	cb => sub {
291	my ($pid, $status) = @_;	291	my ($pid, $status) = @_;
292	warn "pid $pid exited with status $status";	292	warn "pid $pid exited with status $status";
293	$done->broadcast;	293	$done->send;
294	},	294	},
295	);	295	);
296		296
297	# do something else, then wait for process exit	297	# do something else, then wait for process exit
298	$done->wait;	298	$done->wait;
…		…
313	>> method, usually without arguments. The only argument pair allowed is	313	>> method, usually without arguments. The only argument pair allowed is
314	C<cb>, which specifies a callback to be called when the condition variable	314	C<cb>, which specifies a callback to be called when the condition variable
315	becomes true.	315	becomes true.
316		316
317	After creation, the conditon variable is "false" until it becomes "true"	317	After creation, the conditon variable is "false" until it becomes "true"
318	by calling the C<broadcast> method.	318	by calling the C<send> method.
319		319
320	Condition variables are similar to callbacks, except that you can	320	Condition variables are similar to callbacks, except that you can
321	optionally wait for them. They can also be called merge points - points	321	optionally wait for them. They can also be called merge points - points
322	in time where multiple outstandign events have been processed. And yet	322	in time where multiple outstandign events have been processed. And yet
323	another way to call them is transations - each condition variable can be	323	another way to call them is transations - each condition variable can be
…		…
331	called or can synchronously C<< ->wait >> for the results.	331	called or can synchronously C<< ->wait >> for the results.
332		332
333	You can also use them to simulate traditional event loops - for example,	333	You can also use them to simulate traditional event loops - for example,
334	you can block your main program until an event occurs - for example, you	334	you can block your main program until an event occurs - for example, you
335	could C<< ->wait >> in your main program until the user clicks the Quit	335	could C<< ->wait >> in your main program until the user clicks the Quit
336	button of your app, which would C<< ->broadcast >> the "quit" event.	336	button of your app, which would C<< ->send >> the "quit" event.
337		337
338	Note that condition variables recurse into the event loop - if you have	338	Note that condition variables recurse into the event loop - if you have
339	two pieces of code that call C<< ->wait >> in a round-robbin fashion, you	339	two pieces of code that call C<< ->wait >> in a round-robbin fashion, you
340	lose. Therefore, condition variables are good to export to your caller, but	340	lose. Therefore, condition variables are good to export to your caller, but
341	you should avoid making a blocking wait yourself, at least in callbacks,	341	you should avoid making a blocking wait yourself, at least in callbacks,
…		…
346	easy (it is often useful to build your own transaction class on top of	346	easy (it is often useful to build your own transaction class on top of
347	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call	347	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
348	it's C<new> method in your own C<new> method.	348	it's C<new> method in your own C<new> method.
349		349
350	There are two "sides" to a condition variable - the "producer side" which	350	There are two "sides" to a condition variable - the "producer side" which
351	eventually calls C<< -> broadcast >>, and the "consumer side", which waits	351	eventually calls C<< -> send >>, and the "consumer side", which waits
352	for the broadcast to occur.	352	for the send to occur.
353		353
354	Example:	354	Example:
355		355
356	# wait till the result is ready	356	# wait till the result is ready
357	my $result_ready = AnyEvent->condvar;	357	my $result_ready = AnyEvent->condvar;
358		358
359	# do something such as adding a timer	359	# do something such as adding a timer
360	# or socket watcher the calls $result_ready->broadcast	360	# or socket watcher the calls $result_ready->send
361	# when the "result" is ready.	361	# when the "result" is ready.
362	# in this case, we simply use a timer:	362	# in this case, we simply use a timer:
363	my $w = AnyEvent->timer (	363	my $w = AnyEvent->timer (
364	after => 1,	364	after => 1,
365	cb => sub { $result_ready->broadcast },	365	cb => sub { $result_ready->send },
366	);	366	);
367		367
368	# this "blocks" (while handling events) till the callback	368	# this "blocks" (while handling events) till the callback
369	# calls broadcast	369	# calls send
370	$result_ready->wait;	370	$result_ready->wait;
371		371
372	=head3 METHODS FOR PRODUCERS	372	=head3 METHODS FOR PRODUCERS
373		373
374	These methods should only be used by the producing side, i.e. the	374	These methods should only be used by the producing side, i.e. the
375	code/module that eventually broadcasts the signal. Note that it is also	375	code/module that eventually sends the signal. Note that it is also
376	the producer side which creates the condvar in most cases, but it isn't	376	the producer side which creates the condvar in most cases, but it isn't
377	uncommon for the consumer to create it as well.	377	uncommon for the consumer to create it as well.
378		378
379	=over 4	379	=over 4
380		380
381	=item $cv->broadcast (...)	381	=item $cv->send (...)
382		382
383	Flag the condition as ready - a running C<< ->wait >> and all further	383	Flag the condition as ready - a running C<< ->wait >> and all further
384	calls to C<wait> will (eventually) return after this method has been	384	calls to C<wait> will (eventually) return after this method has been
385	called. If nobody is waiting the broadcast will be remembered.	385	called. If nobody is waiting the send will be remembered.
386		386
387	If a callback has been set on the condition variable, it is called	387	If a callback has been set on the condition variable, it is called
388	immediately from within broadcast.	388	immediately from within send.
389		389
390	Any arguments passed to the C<broadcast> call will be returned by all	390	Any arguments passed to the C<send> call will be returned by all
391	future C<< ->wait >> calls.	391	future C<< ->wait >> calls.
392		392
393	=item $cv->croak ($error)	393	=item $cv->croak ($error)
394		394
395	Similar to broadcast, but causes all call's wait C<< ->wait >> to invoke	395	Similar to send, but causes all call's wait C<< ->wait >> to invoke
396	C<Carp::croak> with the given error message/object/scalar.	396	C<Carp::croak> with the given error message/object/scalar.
397		397
398	This can be used to signal any errors to the condition variable	398	This can be used to signal any errors to the condition variable
399	user/consumer.	399	user/consumer.
400		400
…		…
407	to use a condition variable for the whole process.	407	to use a condition variable for the whole process.
408		408
409	Every call to C<< ->begin >> will increment a counter, and every call to	409	Every call to C<< ->begin >> will increment a counter, and every call to
410	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end	410	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
411	>>, the (last) callback passed to C<begin> will be executed. That callback	411	>>, the (last) callback passed to C<begin> will be executed. That callback
412	is I<supposed> to call C<< ->broadcast >>, but that is not required. If no	412	is I<supposed> to call C<< ->send >>, but that is not required. If no
413	callback was set, C<broadcast> will be called without any arguments.	413	callback was set, C<send> will be called without any arguments.
414		414
415	Let's clarify this with the ping example:	415	Let's clarify this with the ping example:
416		416
417	my $cv = AnyEvent->condvar;	417	my $cv = AnyEvent->condvar;
418		418
419	my %result;	419	my %result;
420	$cv->begin (sub { $cv->broadcast (\%result) });	420	$cv->begin (sub { $cv->send (\%result) });
421		421
422	for my $host (@list_of_hosts) {	422	for my $host (@list_of_hosts) {
423	$cv->begin;	423	$cv->begin;
424	ping_host_then_call_callback $host, sub {	424	ping_host_then_call_callback $host, sub {
425	$result{$host} = ...;	425	$result{$host} = ...;
…		…
428	}	428	}
429		429
430	$cv->end;	430	$cv->end;
431		431
432	This code fragment supposedly pings a number of hosts and calls	432	This code fragment supposedly pings a number of hosts and calls
433	C<broadcast> after results for all then have have been gathered - in any	433	C<send> after results for all then have have been gathered - in any
434	order. To achieve this, the code issues a call to C<begin> when it starts	434	order. To achieve this, the code issues a call to C<begin> when it starts
435	each ping request and calls C<end> when it has received some result for	435	each ping request and calls C<end> when it has received some result for
436	it. Since C<begin> and C<end> only maintain a counter, the order in which	436	it. Since C<begin> and C<end> only maintain a counter, the order in which
437	results arrive is not relevant.	437	results arrive is not relevant.
438		438
439	There is an additional bracketing call to C<begin> and C<end> outside the	439	There is an additional bracketing call to C<begin> and C<end> outside the
440	loop, which serves two important purposes: first, it sets the callback	440	loop, which serves two important purposes: first, it sets the callback
441	to be called once the counter reaches C<0>, and second, it ensures that	441	to be called once the counter reaches C<0>, and second, it ensures that
442	broadcast is called even when C<no> hosts are being pinged (the loop	442	C<send> is called even when C<no> hosts are being pinged (the loop
443	doesn't execute once).	443	doesn't execute once).
444		444
445	This is the general pattern when you "fan out" into multiple subrequests:	445	This is the general pattern when you "fan out" into multiple subrequests:
446	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>	446	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>
447	is called at least once, and then, for each subrequest you start, call	447	is called at least once, and then, for each subrequest you start, call
…		…
452	=head3 METHODS FOR CONSUMERS	452	=head3 METHODS FOR CONSUMERS
453		453
454	These methods should only be used by the consuming side, i.e. the	454	These methods should only be used by the consuming side, i.e. the
455	code awaits the condition.	455	code awaits the condition.
456		456
		457	=over 4
		458
457	=item $cv->wait	459	=item $cv->wait
458		460
459	Wait (blocking if necessary) until the C<< ->broadcast >> or C<< ->croak	461	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
460	>> methods have been called on c<$cv>, while servicing other watchers	462	>> methods have been called on c<$cv>, while servicing other watchers
461	normally.	463	normally.
462		464
463	You can only wait once on a condition - additional calls are valid but	465	You can only wait once on a condition - additional calls are valid but
464	will return immediately.	466	will return immediately.
465		467
466	If an error condition has been set by calling C<< ->croak >>, then this	468	If an error condition has been set by calling C<< ->croak >>, then this
467	function will call C<croak>.	469	function will call C<croak>.
468		470
469	In list context, all parameters passed to C<broadcast> will be returned,	471	In list context, all parameters passed to C<send> will be returned,
470	in scalar context only the first one will be returned.	472	in scalar context only the first one will be returned.
471		473
472	Not all event models support a blocking wait - some die in that case	474	Not all event models support a blocking wait - some die in that case
473	(programs might want to do that to stay interactive), so I<if you are	475	(programs might want to do that to stay interactive), so I<if you are
474	using this from a module, never require a blocking wait>, but let the	476	using this from a module, never require a blocking wait>, but let the
…		…
478	while still suppporting blocking waits if the caller so desires).	480	while still suppporting blocking waits if the caller so desires).
479		481
480	Another reason I<never> to C<< ->wait >> in a module is that you cannot	482	Another reason I<never> to C<< ->wait >> in a module is that you cannot
481	sensibly have two C<< ->wait >>'s in parallel, as that would require	483	sensibly have two C<< ->wait >>'s in parallel, as that would require
482	multiple interpreters or coroutines/threads, none of which C<AnyEvent>	484	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
483	can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and	485	can supply.
484	L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s	486
485	from different coroutines, however).	487	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
		488	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
		489	versions and also integrates coroutines into AnyEvent, making blocking
		490	C<< ->wait >> calls perfectly safe as long as they are done from another
		491	coroutine (one that doesn't run the event loop).
486		492
487	You can ensure that C<< -wait >> never blocks by setting a callback and	493	You can ensure that C<< -wait >> never blocks by setting a callback and
488	only calling C<< ->wait >> from within that callback (or at a later	494	only calling C<< ->wait >> from within that callback (or at a later
489	time). This will work even when the event loop does not support blocking	495	time). This will work even when the event loop does not support blocking
490	waits otherwise.	496	waits otherwise.
		497
		498	=item $bool = $cv->ready
		499
		500	Returns true when the condition is "true", i.e. whether C<send> or
		501	C<croak> have been called.
		502
		503	=item $cb = $cv->cb ([new callback])
		504
		505	This is a mutator function that returns the callback set and optionally
		506	replaces it before doing so.
		507
		508	The callback will be called when the condition becomes "true", i.e. when
		509	C<send> or C<croak> are called. Calling C<wait> inside the callback
		510	or at any later time is guaranteed not to block.
491		511
492	=back	512	=back
493		513
494	=head1 GLOBAL VARIABLES AND FUNCTIONS	514	=head1 GLOBAL VARIABLES AND FUNCTIONS
495		515
…		…
503	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	523	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case
504	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	524	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
505		525
506	The known classes so far are:	526	The known classes so far are:
507		527
508	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
509	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
510	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).	528	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
511	AnyEvent::Impl::Event based on Event, second best choice.	529	AnyEvent::Impl::Event based on Event, second best choice.
512	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.	530	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
513	AnyEvent::Impl::Glib based on Glib, third-best choice.	531	AnyEvent::Impl::Glib based on Glib, third-best choice.
514	AnyEvent::Impl::Tk based on Tk, very bad choice.	532	AnyEvent::Impl::Tk based on Tk, very bad choice.
…		…
531	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	549	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
532	if necessary. You should only call this function right before you would	550	if necessary. You should only call this function right before you would
533	have created an AnyEvent watcher anyway, that is, as late as possible at	551	have created an AnyEvent watcher anyway, that is, as late as possible at
534	runtime.	552	runtime.
535		553
		554	=item $guard = AnyEvent::post_detect { BLOCK }
		555
		556	Arranges for the code block to be executed as soon as the event model is
		557	autodetected (or immediately if this has already happened).
		558
		559	If called in scalar or list context, then it creates and returns an object
		560	that automatically removes the callback again when it is destroyed. See
		561	L<Coro::BDB> for a case where this is useful.
		562
		563	=item @AnyEvent::post_detect
		564
		565	If there are any code references in this array (you can C<push> to it
		566	before or after loading AnyEvent), then they will called directly after
		567	the event loop has been chosen.
		568
		569	You should check C<$AnyEvent::MODEL> before adding to this array, though:
		570	if it contains a true value then the event loop has already been detected,
		571	and the array will be ignored.
		572
		573	Best use C<AnyEvent::post_detect { BLOCK }> instead.
		574
536	=back	575	=back
537		576
538	=head1 WHAT TO DO IN A MODULE	577	=head1 WHAT TO DO IN A MODULE
539		578
540	As a module author, you should C<use AnyEvent> and call AnyEvent methods	579	As a module author, you should C<use AnyEvent> and call AnyEvent methods
…		…
544	decide which event module to use as soon as the first method is called, so	583	decide which event module to use as soon as the first method is called, so
545	by calling AnyEvent in your module body you force the user of your module	584	by calling AnyEvent in your module body you force the user of your module
546	to load the event module first.	585	to load the event module first.
547		586
548	Never call C<< ->wait >> on a condition variable unless you I<know> that	587	Never call C<< ->wait >> on a condition variable unless you I<know> that
549	the C<< ->broadcast >> method has been called on it already. This is	588	the C<< ->send >> method has been called on it already. This is
550	because it will stall the whole program, and the whole point of using	589	because it will stall the whole program, and the whole point of using
551	events is to stay interactive.	590	events is to stay interactive.
552		591
553	It is fine, however, to call C<< ->wait >> when the user of your module	592	It is fine, however, to call C<< ->wait >> when the user of your module
554	requests it (i.e. if you create a http request object ad have a method	593	requests it (i.e. if you create a http request object ad have a method
…		…
628		667
629	High level API for event-based execution flow control.	668	High level API for event-based execution flow control.
630		669
631	=item L<Coro>	670	=item L<Coro>
632		671
633	Has special support for AnyEvent.	672	Has special support for AnyEvent via L<Coro::AnyEvent>.
634		673
635	=item L<IO::Lambda>	674	=item L<IO::Lambda>
636		675
637	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	676	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
638		677
…		…
655	no warnings;	694	no warnings;
656	use strict;	695	use strict;
657		696
658	use Carp;	697	use Carp;
659		698
660	our $VERSION = '3.3';	699	our $VERSION = '3.4';
661	our $MODEL;	700	our $MODEL;
662		701
663	our $AUTOLOAD;	702	our $AUTOLOAD;
664	our @ISA;	703	our @ISA;
665		704
666	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	705	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
667		706
668	our @REGISTRY;	707	our @REGISTRY;
669		708
670	my @models = (	709	my @models = (
671	[Coro::EV:: => AnyEvent::Impl::CoroEV::],
672	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
673	[EV:: => AnyEvent::Impl::EV::],	710	[EV:: => AnyEvent::Impl::EV::],
674	[Event:: => AnyEvent::Impl::Event::],	711	[Event:: => AnyEvent::Impl::Event::],
675	[Tk:: => AnyEvent::Impl::Tk::],	712	[Tk:: => AnyEvent::Impl::Tk::],
676	[Wx:: => AnyEvent::Impl::POE::],	713	[Wx:: => AnyEvent::Impl::POE::],
677	[Prima:: => AnyEvent::Impl::POE::],	714	[Prima:: => AnyEvent::Impl::POE::],
…		…
681	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy	718	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
682	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	719	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
683	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	720	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
684	);	721	);
685		722
686	our %method = map +($_ => 1), qw(io timer signal child condvar broadcast wait one_event DESTROY);	723	our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY);
		724
		725	our @post_detect;
		726
		727	sub post_detect(&) {
		728	my ($cb) = @_;
		729
		730	if ($MODEL) {
		731	$cb->();
		732
		733	1
		734	} else {
		735	push @post_detect, $cb;
		736
		737	defined wantarray
		738	? bless \$cb, "AnyEvent::Util::Guard"
		739	: ()
		740	}
		741	}
		742
		743	sub AnyEvent::Util::Guard::DESTROY {
		744	@post_detect = grep $_ != ${$_[0]}, @post_detect;
		745	}
687		746
688	sub detect() {	747	sub detect() {
689	unless ($MODEL) {	748	unless ($MODEL) {
690	no strict 'refs';	749	no strict 'refs';
691		750
…		…
725	last;	784	last;
726	}	785	}
727	}	786	}
728		787
729	$MODEL	788	$MODEL
730	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event) or Glib.";	789	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
731	}	790	}
732	}	791	}
733		792
734	unshift @ISA, $MODEL;	793	unshift @ISA, $MODEL;
735	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	794	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		795
		796	(shift @post_detect)->() while @post_detect;
736	}	797	}
737		798
738	$MODEL	799	$MODEL
739	}	800	}
740		801
…		…
1374		1435
1375	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1436	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1376		1437
1377	use AnyEvent;	1438	use AnyEvent;
1378		1439
		1440	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
		1441	be used to probe what backend is used and gain other information (which is
		1442	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).
		1443
1379		1444
1380	=head1 SEE ALSO	1445	=head1 SEE ALSO
1381		1446
1382	Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>,	1447	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,
1383	L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>,
1384	L<Event::Lib>, L<Qt>, L<POE>.	1448	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1385		1449
1386	Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>,	1450	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1387	L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>,	1451	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1388	L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>,	1452	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1389	L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>.	1453	L<AnyEvent::Impl::POE>.
		1454
		1455	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,
1390		1456
1391	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.	1457	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.
1392		1458
1393		1459
1394	=head1 AUTHOR	1460	=head1 AUTHOR

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.105 by root, Thu May 1 12:35:54 2008 UTC vs. Revision 1.112 by root, Sat May 10 01:04:42 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.105 by root, Thu May 1 12:35:54 2008 UTC vs.
Revision 1.112 by root, Sat May 10 01:04:42 2008 UTC