ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.355 by root, Tue Jan 11 01:41:56 2011 UTC vs.
Revision 1.432 by root, Sat Apr 26 14:28:48 2014 UTC

		1	=encoding utf-8
		2
1	=head1 NAME	3	=head1 NAME
2		4
3	libev - a high performance full-featured event loop written in C	5	libev - a high performance full-featured event loop written in C
4		6
5	=head1 SYNOPSIS	7	=head1 SYNOPSIS
…		…
58	ev_timer_start (loop, &timeout_watcher);	60	ev_timer_start (loop, &timeout_watcher);
59		61
60	// now wait for events to arrive	62	// now wait for events to arrive
61	ev_run (loop, 0);	63	ev_run (loop, 0);
62		64
63	// unloop was called, so exit	65	// break was called, so exit
64	return 0;	66	return 0;
65	}	67	}
66		68
67	=head1 ABOUT THIS DOCUMENT	69	=head1 ABOUT THIS DOCUMENT
68		70
…		…
82		84
83	=head1 WHAT TO READ WHEN IN A HURRY	85	=head1 WHAT TO READ WHEN IN A HURRY
84		86
85	This manual tries to be very detailed, but unfortunately, this also makes	87	This manual tries to be very detailed, but unfortunately, this also makes
86	it very long. If you just want to know the basics of libev, I suggest	88	it very long. If you just want to know the basics of libev, I suggest
87	reading L<ANATOMY OF A WATCHER>, then the L<EXAMPLE PROGRAM> above and	89	reading L</ANATOMY OF A WATCHER>, then the L</EXAMPLE PROGRAM> above and
88	look up the missing functions in L<GLOBAL FUNCTIONS> and the C<ev_io> and	90	look up the missing functions in L</GLOBAL FUNCTIONS> and the C<ev_io> and
89	C<ev_timer> sections in L<WATCHER TYPES>.	91	C<ev_timer> sections in L</WATCHER TYPES>.
90		92
91	=head1 ABOUT LIBEV	93	=head1 ABOUT LIBEV
92		94
93	Libev is an event loop: you register interest in certain events (such as a	95	Libev is an event loop: you register interest in certain events (such as a
94	file descriptor being readable or a timeout occurring), and it will manage	96	file descriptor being readable or a timeout occurring), and it will manage
…		…
174	=item ev_tstamp ev_time ()	176	=item ev_tstamp ev_time ()
175		177
176	Returns the current time as libev would use it. Please note that the	178	Returns the current time as libev would use it. Please note that the
177	C<ev_now> function is usually faster and also often returns the timestamp	179	C<ev_now> function is usually faster and also often returns the timestamp
178	you actually want to know. Also interesting is the combination of	180	you actually want to know. Also interesting is the combination of
179	C<ev_update_now> and C<ev_now>.	181	C<ev_now_update> and C<ev_now>.
180		182
181	=item ev_sleep (ev_tstamp interval)	183	=item ev_sleep (ev_tstamp interval)
182		184
183	Sleep for the given interval: The current thread will be blocked until	185	Sleep for the given interval: The current thread will be blocked
184	either it is interrupted or the given time interval has passed. Basically	186	until either it is interrupted or the given time interval has
		187	passed (approximately - it might return a bit earlier even if not
		188	interrupted). Returns immediately if C<< interval <= 0 >>.
		189
185	this is a sub-second-resolution C<sleep ()>.	190	Basically this is a sub-second-resolution C<sleep ()>.
		191
		192	The range of the C<interval> is limited - libev only guarantees to work
		193	with sleep times of up to one day (C<< interval <= 86400 >>).
186		194
187	=item int ev_version_major ()	195	=item int ev_version_major ()
188		196
189	=item int ev_version_minor ()	197	=item int ev_version_minor ()
190		198
…		…
241	the current system, you would need to look at C<ev_embeddable_backends ()	249	the current system, you would need to look at C<ev_embeddable_backends ()
242	& ev_supported_backends ()>, likewise for recommended ones.	250	& ev_supported_backends ()>, likewise for recommended ones.
243		251
244	See the description of C<ev_embed> watchers for more info.	252	See the description of C<ev_embed> watchers for more info.
245		253
246	=item ev_set_allocator (void *(*cb)(void *ptr, long size))	254	=item ev_set_allocator (void *(*cb)(void *ptr, long size) throw ())
247		255
248	Sets the allocation function to use (the prototype is similar - the	256	Sets the allocation function to use (the prototype is similar - the
249	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is	257	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is
250	used to allocate and free memory (no surprises here). If it returns zero	258	used to allocate and free memory (no surprises here). If it returns zero
251	when memory needs to be allocated (C<size != 0>), the library might abort	259	when memory needs to be allocated (C<size != 0>), the library might abort
…		…
277	}	285	}
278		286
279	...	287	...
280	ev_set_allocator (persistent_realloc);	288	ev_set_allocator (persistent_realloc);
281		289
282	=item ev_set_syserr_cb (void (*cb)(const char *msg))	290	=item ev_set_syserr_cb (void (*cb)(const char *msg) throw ())
283		291
284	Set the callback function to call on a retryable system call error (such	292	Set the callback function to call on a retryable system call error (such
285	as failed select, poll, epoll_wait). The message is a printable string	293	as failed select, poll, epoll_wait). The message is a printable string
286	indicating the system call or subsystem causing the problem. If this	294	indicating the system call or subsystem causing the problem. If this
287	callback is set, then libev will expect it to remedy the situation, no	295	callback is set, then libev will expect it to remedy the situation, no
…		…
390		398
391	If this flag bit is or'ed into the flag value (or the program runs setuid	399	If this flag bit is or'ed into the flag value (or the program runs setuid
392	or setgid) then libev will I<not> look at the environment variable	400	or setgid) then libev will I<not> look at the environment variable
393	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will	401	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
394	override the flags completely if it is found in the environment. This is	402	override the flags completely if it is found in the environment. This is
395	useful to try out specific backends to test their performance, or to work	403	useful to try out specific backends to test their performance, to work
396	around bugs.	404	around bugs, or to make libev threadsafe (accessing environment variables
		405	cannot be done in a threadsafe way, but usually it works if no other
		406	thread modifies them).
397		407
398	=item C<EVFLAG_FORKCHECK>	408	=item C<EVFLAG_FORKCHECK>
399		409
400	Instead of calling C<ev_loop_fork> manually after a fork, you can also	410	Instead of calling C<ev_loop_fork> manually after a fork, you can also
401	make libev check for a fork in each iteration by enabling this flag.	411	make libev check for a fork in each iteration by enabling this flag.
…		…
435	example) that can't properly initialise their signal masks.	445	example) that can't properly initialise their signal masks.
436		446
437	=item C<EVFLAG_NOSIGMASK>	447	=item C<EVFLAG_NOSIGMASK>
438		448
439	When this flag is specified, then libev will avoid to modify the signal	449	When this flag is specified, then libev will avoid to modify the signal
440	mask. Specifically, this means you ahve to make sure signals are unblocked	450	mask. Specifically, this means you have to make sure signals are unblocked
441	when you want to receive them.	451	when you want to receive them.
442		452
443	This behaviour is useful when you want to do your own signal handling, or	453	This behaviour is useful when you want to do your own signal handling, or
444	want to handle signals only in specific threads and want to avoid libev	454	want to handle signals only in specific threads and want to avoid libev
445	unblocking the signals.	455	unblocking the signals.
		456
		457	It's also required by POSIX in a threaded program, as libev calls
		458	C<sigprocmask>, whose behaviour is officially unspecified.
446		459
447	This flag's behaviour will become the default in future versions of libev.	460	This flag's behaviour will become the default in future versions of libev.
448		461
449	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	462	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
450		463
…		…
480	=item C<EVBACKEND_EPOLL> (value 4, Linux)	493	=item C<EVBACKEND_EPOLL> (value 4, Linux)
481		494
482	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9	495	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
483	kernels).	496	kernels).
484		497
485	For few fds, this backend is a bit little slower than poll and select,	498	For few fds, this backend is a bit little slower than poll and select, but
486	but it scales phenomenally better. While poll and select usually scale	499	it scales phenomenally better. While poll and select usually scale like
487	like O(total_fds) where n is the total number of fds (or the highest fd),	500	O(total_fds) where total_fds is the total number of fds (or the highest
488	epoll scales either O(1) or O(active_fds).	501	fd), epoll scales either O(1) or O(active_fds).
489		502
490	The epoll mechanism deserves honorable mention as the most misdesigned	503	The epoll mechanism deserves honorable mention as the most misdesigned
491	of the more advanced event mechanisms: mere annoyances include silently	504	of the more advanced event mechanisms: mere annoyances include silently
492	dropping file descriptors, requiring a system call per change per file	505	dropping file descriptors, requiring a system call per change per file
493	descriptor (and unnecessary guessing of parameters), problems with dup,	506	descriptor (and unnecessary guessing of parameters), problems with dup,
…		…
496	0.1ms) and so on. The biggest issue is fork races, however - if a program	509	0.1ms) and so on. The biggest issue is fork races, however - if a program
497	forks then I<both> parent and child process have to recreate the epoll	510	forks then I<both> parent and child process have to recreate the epoll
498	set, which can take considerable time (one syscall per file descriptor)	511	set, which can take considerable time (one syscall per file descriptor)
499	and is of course hard to detect.	512	and is of course hard to detect.
500		513
501	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but	514	Epoll is also notoriously buggy - embedding epoll fds I<should> work,
502	of course I<doesn't>, and epoll just loves to report events for totally	515	but of course I<doesn't>, and epoll just loves to report events for
503	I<different> file descriptors (even already closed ones, so one cannot	516	totally I<different> file descriptors (even already closed ones, so
504	even remove them from the set) than registered in the set (especially	517	one cannot even remove them from the set) than registered in the set
505	on SMP systems). Libev tries to counter these spurious notifications by	518	(especially on SMP systems). Libev tries to counter these spurious
506	employing an additional generation counter and comparing that against the	519	notifications by employing an additional generation counter and comparing
507	events to filter out spurious ones, recreating the set when required. Last	520	that against the events to filter out spurious ones, recreating the set
		521	when required. Epoll also erroneously rounds down timeouts, but gives you
		522	no way to know when and by how much, so sometimes you have to busy-wait
		523	because epoll returns immediately despite a nonzero timeout. And last
508	not least, it also refuses to work with some file descriptors which work	524	not least, it also refuses to work with some file descriptors which work
509	perfectly fine with C<select> (files, many character devices...).	525	perfectly fine with C<select> (files, many character devices...).
510		526
511	Epoll is truly the train wreck analog among event poll mechanisms,	527	Epoll is truly the train wreck among event poll mechanisms, a frankenpoll,
512	a frankenpoll, cobbled together in a hurry, no thought to design or	528	cobbled together in a hurry, no thought to design or interaction with
513	interaction with others.	529	others. Oh, the pain, will it ever stop...
514		530
515	While stopping, setting and starting an I/O watcher in the same iteration	531	While stopping, setting and starting an I/O watcher in the same iteration
516	will result in some caching, there is still a system call per such	532	will result in some caching, there is still a system call per such
517	incident (because the same I<file descriptor> could point to a different	533	incident (because the same I<file descriptor> could point to a different
518	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed	534	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
…		…
555		571
556	It scales in the same way as the epoll backend, but the interface to the	572	It scales in the same way as the epoll backend, but the interface to the
557	kernel is more efficient (which says nothing about its actual speed, of	573	kernel is more efficient (which says nothing about its actual speed, of
558	course). While stopping, setting and starting an I/O watcher does never	574	course). While stopping, setting and starting an I/O watcher does never
559	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to	575	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to
560	two event changes per incident. Support for C<fork ()> is very bad (but	576	two event changes per incident. Support for C<fork ()> is very bad (you
561	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect	577	might have to leak fd's on fork, but it's more sane than epoll) and it
562	cases	578	drops fds silently in similarly hard-to-detect cases.
563		579
564	This backend usually performs well under most conditions.	580	This backend usually performs well under most conditions.
565		581
566	While nominally embeddable in other event loops, this doesn't work	582	While nominally embeddable in other event loops, this doesn't work
567	everywhere, so you might need to test for this. And since it is broken	583	everywhere, so you might need to test for this. And since it is broken
…		…
596	among the OS-specific backends (I vastly prefer correctness over speed	612	among the OS-specific backends (I vastly prefer correctness over speed
597	hacks).	613	hacks).
598		614
599	On the negative side, the interface is I<bizarre> - so bizarre that	615	On the negative side, the interface is I<bizarre> - so bizarre that
600	even sun itself gets it wrong in their code examples: The event polling	616	even sun itself gets it wrong in their code examples: The event polling
601	function sometimes returning events to the caller even though an error	617	function sometimes returns events to the caller even though an error
602	occurred, but with no indication whether it has done so or not (yes, it's	618	occurred, but with no indication whether it has done so or not (yes, it's
603	even documented that way) - deadly for edge-triggered interfaces where	619	even documented that way) - deadly for edge-triggered interfaces where you
604	you absolutely have to know whether an event occurred or not because you	620	absolutely have to know whether an event occurred or not because you have
605	have to re-arm the watcher.	621	to re-arm the watcher.
606		622
607	Fortunately libev seems to be able to work around these idiocies.	623	Fortunately libev seems to be able to work around these idiocies.
608		624
609	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	625	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
610	C<EVBACKEND_POLL>.	626	C<EVBACKEND_POLL>.
…		…
672	reinitialise the kernel state for backends that have one. Despite the	688	reinitialise the kernel state for backends that have one. Despite the
673	name, you can call it anytime, but it makes most sense after forking, in	689	name, you can call it anytime, but it makes most sense after forking, in
674	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the	690	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
675	child before resuming or calling C<ev_run>.	691	child before resuming or calling C<ev_run>.
676		692
677	Again, you I<have> to call it on I<any> loop that you want to re-use after	693	Again, you I<have> to call it on I<any> loop that you want to re-use after
678	a fork, I<even if you do not plan to use the loop in the parent>. This is	694	a fork, I<even if you do not plan to use the loop in the parent>. This is
679	because some kernel interfaces *cough* I<kqueue> *cough* do funny things	695	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
680	during fork.	696	during fork.
681		697
682	On the other hand, you only need to call this function in the child	698	On the other hand, you only need to call this function in the child
…		…
752		768
753	This function is rarely useful, but when some event callback runs for a	769	This function is rarely useful, but when some event callback runs for a
754	very long time without entering the event loop, updating libev's idea of	770	very long time without entering the event loop, updating libev's idea of
755	the current time is a good idea.	771	the current time is a good idea.
756		772
757	See also L<The special problem of time updates> in the C<ev_timer> section.	773	See also L</The special problem of time updates> in the C<ev_timer> section.
758		774
759	=item ev_suspend (loop)	775	=item ev_suspend (loop)
760		776
761	=item ev_resume (loop)	777	=item ev_resume (loop)
762		778
…		…
780	without a previous call to C<ev_suspend>.	796	without a previous call to C<ev_suspend>.
781		797
782	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the	798	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
783	event loop time (see C<ev_now_update>).	799	event loop time (see C<ev_now_update>).
784		800
785	=item ev_run (loop, int flags)	801	=item bool ev_run (loop, int flags)
786		802
787	Finally, this is it, the event handler. This function usually is called	803	Finally, this is it, the event handler. This function usually is called
788	after you have initialised all your watchers and you want to start	804	after you have initialised all your watchers and you want to start
789	handling events. It will ask the operating system for any new events, call	805	handling events. It will ask the operating system for any new events, call
790	the watcher callbacks, an then repeat the whole process indefinitely: This	806	the watcher callbacks, and then repeat the whole process indefinitely: This
791	is why event loops are called I<loops>.	807	is why event loops are called I<loops>.
792		808
793	If the flags argument is specified as C<0>, it will keep handling events	809	If the flags argument is specified as C<0>, it will keep handling events
794	until either no event watchers are active anymore or C<ev_break> was	810	until either no event watchers are active anymore or C<ev_break> was
795	called.	811	called.
		812
		813	The return value is false if there are no more active watchers (which
		814	usually means "all jobs done" or "deadlock"), and true in all other cases
		815	(which usually means " you should call C<ev_run> again").
796		816
797	Please note that an explicit C<ev_break> is usually better than	817	Please note that an explicit C<ev_break> is usually better than
798	relying on all watchers to be stopped when deciding when a program has	818	relying on all watchers to be stopped when deciding when a program has
799	finished (especially in interactive programs), but having a program	819	finished (especially in interactive programs), but having a program
800	that automatically loops as long as it has to and no longer by virtue	820	that automatically loops as long as it has to and no longer by virtue
801	of relying on its watchers stopping correctly, that is truly a thing of	821	of relying on its watchers stopping correctly, that is truly a thing of
802	beauty.	822	beauty.
803		823
804	This function is also I<mostly> exception-safe - you can break out of	824	This function is I<mostly> exception-safe - you can break out of a
805	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++	825	C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
806	exception and so on. This does not decrement the C<ev_depth> value, nor	826	exception and so on. This does not decrement the C<ev_depth> value, nor
807	will it clear any outstanding C<EVBREAK_ONE> breaks.	827	will it clear any outstanding C<EVBREAK_ONE> breaks.
808		828
809	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle	829	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
810	those events and any already outstanding ones, but will not wait and	830	those events and any already outstanding ones, but will not wait and
…		…
822	This is useful if you are waiting for some external event in conjunction	842	This is useful if you are waiting for some external event in conjunction
823	with something not expressible using other libev watchers (i.e. "roll your	843	with something not expressible using other libev watchers (i.e. "roll your
824	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is	844	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
825	usually a better approach for this kind of thing.	845	usually a better approach for this kind of thing.
826		846
827	Here are the gory details of what C<ev_run> does:	847	Here are the gory details of what C<ev_run> does (this is for your
		848	understanding, not a guarantee that things will work exactly like this in
		849	future versions):
828		850
829	- Increment loop depth.	851	- Increment loop depth.
830	- Reset the ev_break status.	852	- Reset the ev_break status.
831	- Before the first iteration, call any pending watchers.	853	- Before the first iteration, call any pending watchers.
832	LOOP:	854	LOOP:
…		…
865	anymore.	887	anymore.
866		888
867	... queue jobs here, make sure they register event watchers as long	889	... queue jobs here, make sure they register event watchers as long
868	... as they still have work to do (even an idle watcher will do..)	890	... as they still have work to do (even an idle watcher will do..)
869	ev_run (my_loop, 0);	891	ev_run (my_loop, 0);
870	... jobs done or somebody called unloop. yeah!	892	... jobs done or somebody called break. yeah!
871		893
872	=item ev_break (loop, how)	894	=item ev_break (loop, how)
873		895
874	Can be used to make a call to C<ev_run> return early (but only after it	896	Can be used to make a call to C<ev_run> return early (but only after it
875	has processed all outstanding events). The C<how> argument must be either	897	has processed all outstanding events). The C<how> argument must be either
…		…
938	overhead for the actual polling but can deliver many events at once.	960	overhead for the actual polling but can deliver many events at once.
939		961
940	By setting a higher I<io collect interval> you allow libev to spend more	962	By setting a higher I<io collect interval> you allow libev to spend more
941	time collecting I/O events, so you can handle more events per iteration,	963	time collecting I/O events, so you can handle more events per iteration,
942	at the cost of increasing latency. Timeouts (both C<ev_periodic> and	964	at the cost of increasing latency. Timeouts (both C<ev_periodic> and
943	C<ev_timer>) will be not affected. Setting this to a non-null value will	965	C<ev_timer>) will not be affected. Setting this to a non-null value will
944	introduce an additional C<ev_sleep ()> call into most loop iterations. The	966	introduce an additional C<ev_sleep ()> call into most loop iterations. The
945	sleep time ensures that libev will not poll for I/O events more often then	967	sleep time ensures that libev will not poll for I/O events more often then
946	once per this interval, on average.	968	once per this interval, on average (as long as the host time resolution is
		969	good enough).
947		970
948	Likewise, by setting a higher I<timeout collect interval> you allow libev	971	Likewise, by setting a higher I<timeout collect interval> you allow libev
949	to spend more time collecting timeouts, at the expense of increased	972	to spend more time collecting timeouts, at the expense of increased
950	latency/jitter/inexactness (the watcher callback will be called	973	latency/jitter/inexactness (the watcher callback will be called
951	later). C<ev_io> watchers will not be affected. Setting this to a non-null	974	later). C<ev_io> watchers will not be affected. Setting this to a non-null
…		…
997	invoke the actual watchers inside another context (another thread etc.).	1020	invoke the actual watchers inside another context (another thread etc.).
998		1021
999	If you want to reset the callback, use C<ev_invoke_pending> as new	1022	If you want to reset the callback, use C<ev_invoke_pending> as new
1000	callback.	1023	callback.
1001		1024
1002	=item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))	1025	=item ev_set_loop_release_cb (loop, void (*release)(EV_P) throw (), void (*acquire)(EV_P) throw ())
1003		1026
1004	Sometimes you want to share the same loop between multiple threads. This	1027	Sometimes you want to share the same loop between multiple threads. This
1005	can be done relatively simply by putting mutex_lock/unlock calls around	1028	can be done relatively simply by putting mutex_lock/unlock calls around
1006	each call to a libev function.	1029	each call to a libev function.
1007		1030
1008	However, C<ev_run> can run an indefinite time, so it is not feasible	1031	However, C<ev_run> can run an indefinite time, so it is not feasible
1009	to wait for it to return. One way around this is to wake up the event	1032	to wait for it to return. One way around this is to wake up the event
1010	loop via C<ev_break> and C<av_async_send>, another way is to set these	1033	loop via C<ev_break> and C<ev_async_send>, another way is to set these
1011	I<release> and I<acquire> callbacks on the loop.	1034	I<release> and I<acquire> callbacks on the loop.
1012		1035
1013	When set, then C<release> will be called just before the thread is	1036	When set, then C<release> will be called just before the thread is
1014	suspended waiting for new events, and C<acquire> is called just	1037	suspended waiting for new events, and C<acquire> is called just
1015	afterwards.	1038	afterwards.
…		…
1155		1178
1156	=item C<EV_PREPARE>	1179	=item C<EV_PREPARE>
1157		1180
1158	=item C<EV_CHECK>	1181	=item C<EV_CHECK>
1159		1182
1160	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts	1183	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts to
1161	to gather new events, and all C<ev_check> watchers are invoked just after	1184	gather new events, and all C<ev_check> watchers are queued (not invoked)
1162	C<ev_run> has gathered them, but before it invokes any callbacks for any	1185	just after C<ev_run> has gathered them, but before it queues any callbacks
		1186	for any received events. That means C<ev_prepare> watchers are the last
		1187	watchers invoked before the event loop sleeps or polls for new events, and
		1188	C<ev_check> watchers will be invoked before any other watchers of the same
		1189	or lower priority within an event loop iteration.
		1190
1163	received events. Callbacks of both watcher types can start and stop as	1191	Callbacks of both watcher types can start and stop as many watchers as
1164	many watchers as they want, and all of them will be taken into account	1192	they want, and all of them will be taken into account (for example, a
1165	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	1193	C<ev_prepare> watcher might start an idle watcher to keep C<ev_run> from
1166	C<ev_run> from blocking).	1194	blocking).
1167		1195
1168	=item C<EV_EMBED>	1196	=item C<EV_EMBED>
1169		1197
1170	The embedded event loop specified in the C<ev_embed> watcher needs attention.	1198	The embedded event loop specified in the C<ev_embed> watcher needs attention.
1171		1199
…		…
1294		1322
1295	=item callback ev_cb (ev_TYPE *watcher)	1323	=item callback ev_cb (ev_TYPE *watcher)
1296		1324
1297	Returns the callback currently set on the watcher.	1325	Returns the callback currently set on the watcher.
1298		1326
1299	=item ev_cb_set (ev_TYPE *watcher, callback)	1327	=item ev_set_cb (ev_TYPE *watcher, callback)
1300		1328
1301	Change the callback. You can change the callback at virtually any time	1329	Change the callback. You can change the callback at virtually any time
1302	(modulo threads).	1330	(modulo threads).
1303		1331
1304	=item ev_set_priority (ev_TYPE *watcher, int priority)	1332	=item ev_set_priority (ev_TYPE *watcher, int priority)
…		…
1322	or might not have been clamped to the valid range.	1350	or might not have been clamped to the valid range.
1323		1351
1324	The default priority used by watchers when no priority has been set is	1352	The default priority used by watchers when no priority has been set is
1325	always C<0>, which is supposed to not be too high and not be too low :).	1353	always C<0>, which is supposed to not be too high and not be too low :).
1326		1354
1327	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of	1355	See L</WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
1328	priorities.	1356	priorities.
1329		1357
1330	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1358	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
1331		1359
1332	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1360	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
…		…
1357	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related	1385	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
1358	functions that do not need a watcher.	1386	functions that do not need a watcher.
1359		1387
1360	=back	1388	=back
1361		1389
1362	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1390	See also the L</ASSOCIATING CUSTOM DATA WITH A WATCHER> and L</BUILDING YOUR
1363		1391	OWN COMPOSITE WATCHERS> idioms.
1364	Each watcher has, by default, a member C<void *data> that you can change
1365	and read at any time: libev will completely ignore it. This can be used
1366	to associate arbitrary data with your watcher. If you need more data and
1367	don't want to allocate memory and store a pointer to it in that data
1368	member, you can also "subclass" the watcher type and provide your own
1369	data:
1370
1371	struct my_io
1372	{
1373	ev_io io;
1374	int otherfd;
1375	void *somedata;
1376	struct whatever *mostinteresting;
1377	};
1378
1379	...
1380	struct my_io w;
1381	ev_io_init (&w.io, my_cb, fd, EV_READ);
1382
1383	And since your callback will be called with a pointer to the watcher, you
1384	can cast it back to your own type:
1385
1386	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1387	{
1388	struct my_io *w = (struct my_io *)w_;
1389	...
1390	}
1391
1392	More interesting and less C-conformant ways of casting your callback type
1393	instead have been omitted.
1394
1395	Another common scenario is to use some data structure with multiple
1396	embedded watchers:
1397
1398	struct my_biggy
1399	{
1400	int some_data;
1401	ev_timer t1;
1402	ev_timer t2;
1403	}
1404
1405	In this case getting the pointer to C<my_biggy> is a bit more
1406	complicated: Either you store the address of your C<my_biggy> struct
1407	in the C<data> member of the watcher (for woozies), or you need to use
1408	some pointer arithmetic using C<offsetof> inside your watchers (for real
1409	programmers):
1410
1411	#include <stddef.h>
1412
1413	static void
1414	t1_cb (EV_P_ ev_timer *w, int revents)
1415	{
1416	struct my_biggy big = (struct my_biggy *)
1417	(((char *)w) - offsetof (struct my_biggy, t1));
1418	}
1419
1420	static void
1421	t2_cb (EV_P_ ev_timer *w, int revents)
1422	{
1423	struct my_biggy big = (struct my_biggy *)
1424	(((char *)w) - offsetof (struct my_biggy, t2));
1425	}
1426		1392
1427	=head2 WATCHER STATES	1393	=head2 WATCHER STATES
1428		1394
1429	There are various watcher states mentioned throughout this manual -	1395	There are various watcher states mentioned throughout this manual -
1430	active, pending and so on. In this section these states and the rules to	1396	active, pending and so on. In this section these states and the rules to
1431	transition between them will be described in more detail - and while these	1397	transition between them will be described in more detail - and while these
1432	rules might look complicated, they usually do "the right thing".	1398	rules might look complicated, they usually do "the right thing".
1433		1399
1434	=over 4	1400	=over 4
1435		1401
1436	=item initialiased	1402	=item initialised
1437		1403
1438	Before a watcher can be registered with the event looop it has to be	1404	Before a watcher can be registered with the event loop it has to be
1439	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to	1405	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
1440	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.	1406	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
1441		1407
1442	In this state it is simply some block of memory that is suitable for use	1408	In this state it is simply some block of memory that is suitable for
1443	in an event loop. It can be moved around, freed, reused etc. at will.	1409	use in an event loop. It can be moved around, freed, reused etc. at
		1410	will - as long as you either keep the memory contents intact, or call
		1411	C<ev_TYPE_init> again.
1444		1412
1445	=item started/running/active	1413	=item started/running/active
1446		1414
1447	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes	1415	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
1448	property of the event loop, and is actively waiting for events. While in	1416	property of the event loop, and is actively waiting for events. While in
…		…
1476	latter will clear any pending state the watcher might be in, regardless	1444	latter will clear any pending state the watcher might be in, regardless
1477	of whether it was active or not, so stopping a watcher explicitly before	1445	of whether it was active or not, so stopping a watcher explicitly before
1478	freeing it is often a good idea.	1446	freeing it is often a good idea.
1479		1447
1480	While stopped (and not pending) the watcher is essentially in the	1448	While stopped (and not pending) the watcher is essentially in the
1481	initialised state, that is it can be reused, moved, modified in any way	1449	initialised state, that is, it can be reused, moved, modified in any way
1482	you wish.	1450	you wish (but when you trash the memory block, you need to C<ev_TYPE_init>
		1451	it again).
1483		1452
1484	=back	1453	=back
1485		1454
1486	=head2 WATCHER PRIORITY MODELS	1455	=head2 WATCHER PRIORITY MODELS
1487		1456
…		…
1680	always get a readiness notification instantly, and your read (or possibly	1649	always get a readiness notification instantly, and your read (or possibly
1681	write) will still block on the disk I/O.	1650	write) will still block on the disk I/O.
1682		1651
1683	Another way to view it is that in the case of sockets, pipes, character	1652	Another way to view it is that in the case of sockets, pipes, character
1684	devices and so on, there is another party (the sender) that delivers data	1653	devices and so on, there is another party (the sender) that delivers data
1685	on it's own, but in the case of files, there is no such thing: the disk	1654	on its own, but in the case of files, there is no such thing: the disk
1686	will not send data on it's own, simply because it doesn't know what you	1655	will not send data on its own, simply because it doesn't know what you
1687	wish to read - you would first have to request some data.	1656	wish to read - you would first have to request some data.
1688		1657
1689	Since files are typically not-so-well supported by advanced notification	1658	Since files are typically not-so-well supported by advanced notification
1690	mechanism, libev tries hard to emulate POSIX behaviour with respect	1659	mechanism, libev tries hard to emulate POSIX behaviour with respect
1691	to files, even though you should not use it. The reason for this is	1660	to files, even though you should not use it. The reason for this is
…		…
1815	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1784	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1816	monotonic clock option helps a lot here).	1785	monotonic clock option helps a lot here).
1817		1786
1818	The callback is guaranteed to be invoked only I<after> its timeout has	1787	The callback is guaranteed to be invoked only I<after> its timeout has
1819	passed (not I<at>, so on systems with very low-resolution clocks this	1788	passed (not I<at>, so on systems with very low-resolution clocks this
1820	might introduce a small delay). If multiple timers become ready during the	1789	might introduce a small delay, see "the special problem of being too
		1790	early", below). If multiple timers become ready during the same loop
1821	same loop iteration then the ones with earlier time-out values are invoked	1791	iteration then the ones with earlier time-out values are invoked before
1822	before ones of the same priority with later time-out values (but this is	1792	ones of the same priority with later time-out values (but this is no
1823	no longer true when a callback calls C<ev_run> recursively).	1793	longer true when a callback calls C<ev_run> recursively).
1824		1794
1825	=head3 Be smart about timeouts	1795	=head3 Be smart about timeouts
1826		1796
1827	Many real-world problems involve some kind of timeout, usually for error	1797	Many real-world problems involve some kind of timeout, usually for error
1828	recovery. A typical example is an HTTP request - if the other side hangs,	1798	recovery. A typical example is an HTTP request - if the other side hangs,
…		…
1903		1873
1904	In this case, it would be more efficient to leave the C<ev_timer> alone,	1874	In this case, it would be more efficient to leave the C<ev_timer> alone,
1905	but remember the time of last activity, and check for a real timeout only	1875	but remember the time of last activity, and check for a real timeout only
1906	within the callback:	1876	within the callback:
1907		1877
		1878	ev_tstamp timeout = 60.;
1908	ev_tstamp last_activity; // time of last activity	1879	ev_tstamp last_activity; // time of last activity
		1880	ev_timer timer;
1909		1881
1910	static void	1882	static void
1911	callback (EV_P_ ev_timer *w, int revents)	1883	callback (EV_P_ ev_timer *w, int revents)
1912	{	1884	{
1913	ev_tstamp now = ev_now (EV_A);	1885	// calculate when the timeout would happen
1914	ev_tstamp timeout = last_activity + 60.;	1886	ev_tstamp after = last_activity - ev_now (EV_A) + timeout;
1915		1887
1916	// if last_activity + 60. is older than now, we did time out	1888	// if negative, it means we the timeout already occurred
1917	if (timeout < now)	1889	if (after < 0.)
1918	{	1890	{
1919	// timeout occurred, take action	1891	// timeout occurred, take action
1920	}	1892	}
1921	else	1893	else
1922	{	1894	{
1923	// callback was invoked, but there was some activity, re-arm	1895	// callback was invoked, but there was some recent
1924	// the watcher to fire in last_activity + 60, which is	1896	// activity. simply restart the timer to time out
1925	// guaranteed to be in the future, so "again" is positive:	1897	// after "after" seconds, which is the earliest time
1926	w->repeat = timeout - now;	1898	// the timeout can occur.
		1899	ev_timer_set (w, after, 0.);
1927	ev_timer_again (EV_A_ w);	1900	ev_timer_start (EV_A_ w);
1928	}	1901	}
1929	}	1902	}
1930		1903
1931	To summarise the callback: first calculate the real timeout (defined	1904	To summarise the callback: first calculate in how many seconds the
1932	as "60 seconds after the last activity"), then check if that time has	1905	timeout will occur (by calculating the absolute time when it would occur,
1933	been reached, which means something I<did>, in fact, time out. Otherwise	1906	C<last_activity + timeout>, and subtracting the current time, C<ev_now
1934	the callback was invoked too early (C<timeout> is in the future), so	1907	(EV_A)> from that).
1935	re-schedule the timer to fire at that future time, to see if maybe we have
1936	a timeout then.
1937		1908
1938	Note how C<ev_timer_again> is used, taking advantage of the	1909	If this value is negative, then we are already past the timeout, i.e. we
1939	C<ev_timer_again> optimisation when the timer is already running.	1910	timed out, and need to do whatever is needed in this case.
		1911
		1912	Otherwise, we now the earliest time at which the timeout would trigger,
		1913	and simply start the timer with this timeout value.
		1914
		1915	In other words, each time the callback is invoked it will check whether
		1916	the timeout occurred. If not, it will simply reschedule itself to check
		1917	again at the earliest time it could time out. Rinse. Repeat.
1940		1918
1941	This scheme causes more callback invocations (about one every 60 seconds	1919	This scheme causes more callback invocations (about one every 60 seconds
1942	minus half the average time between activity), but virtually no calls to	1920	minus half the average time between activity), but virtually no calls to
1943	libev to change the timeout.	1921	libev to change the timeout.
1944		1922
1945	To start the timer, simply initialise the watcher and set C<last_activity>	1923	To start the machinery, simply initialise the watcher and set
1946	to the current time (meaning we just have some activity :), then call the	1924	C<last_activity> to the current time (meaning there was some activity just
1947	callback, which will "do the right thing" and start the timer:	1925	now), then call the callback, which will "do the right thing" and start
		1926	the timer:
1948		1927
		1928	last_activity = ev_now (EV_A);
1949	ev_init (timer, callback);	1929	ev_init (&timer, callback);
1950	last_activity = ev_now (loop);	1930	callback (EV_A_ &timer, 0);
1951	callback (loop, timer, EV_TIMER);
1952		1931
1953	And when there is some activity, simply store the current time in	1932	When there is some activity, simply store the current time in
1954	C<last_activity>, no libev calls at all:	1933	C<last_activity>, no libev calls at all:
1955		1934
		1935	if (activity detected)
1956	last_activity = ev_now (loop);	1936	last_activity = ev_now (EV_A);
		1937
		1938	When your timeout value changes, then the timeout can be changed by simply
		1939	providing a new value, stopping the timer and calling the callback, which
		1940	will again do the right thing (for example, time out immediately :).
		1941
		1942	timeout = new_value;
		1943	ev_timer_stop (EV_A_ &timer);
		1944	callback (EV_A_ &timer, 0);
1957		1945
1958	This technique is slightly more complex, but in most cases where the	1946	This technique is slightly more complex, but in most cases where the
1959	time-out is unlikely to be triggered, much more efficient.	1947	time-out is unlikely to be triggered, much more efficient.
1960
1961	Changing the timeout is trivial as well (if it isn't hard-coded in the
1962	callback :) - just change the timeout and invoke the callback, which will
1963	fix things for you.
1964		1948
1965	=item 4. Wee, just use a double-linked list for your timeouts.	1949	=item 4. Wee, just use a double-linked list for your timeouts.
1966		1950
1967	If there is not one request, but many thousands (millions...), all	1951	If there is not one request, but many thousands (millions...), all
1968	employing some kind of timeout with the same timeout value, then one can	1952	employing some kind of timeout with the same timeout value, then one can
…		…
1995	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is	1979	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is
1996	rather complicated, but extremely efficient, something that really pays	1980	rather complicated, but extremely efficient, something that really pays
1997	off after the first million or so of active timers, i.e. it's usually	1981	off after the first million or so of active timers, i.e. it's usually
1998	overkill :)	1982	overkill :)
1999		1983
		1984	=head3 The special problem of being too early
		1985
		1986	If you ask a timer to call your callback after three seconds, then
		1987	you expect it to be invoked after three seconds - but of course, this
		1988	cannot be guaranteed to infinite precision. Less obviously, it cannot be
		1989	guaranteed to any precision by libev - imagine somebody suspending the
		1990	process with a STOP signal for a few hours for example.
		1991
		1992	So, libev tries to invoke your callback as soon as possible I<after> the
		1993	delay has occurred, but cannot guarantee this.
		1994
		1995	A less obvious failure mode is calling your callback too early: many event
		1996	loops compare timestamps with a "elapsed delay >= requested delay", but
		1997	this can cause your callback to be invoked much earlier than you would
		1998	expect.
		1999
		2000	To see why, imagine a system with a clock that only offers full second
		2001	resolution (think windows if you can't come up with a broken enough OS
		2002	yourself). If you schedule a one-second timer at the time 500.9, then the
		2003	event loop will schedule your timeout to elapse at a system time of 500
		2004	(500.9 truncated to the resolution) + 1, or 501.
		2005
		2006	If an event library looks at the timeout 0.1s later, it will see "501 >=
		2007	501" and invoke the callback 0.1s after it was started, even though a
		2008	one-second delay was requested - this is being "too early", despite best
		2009	intentions.
		2010
		2011	This is the reason why libev will never invoke the callback if the elapsed
		2012	delay equals the requested delay, but only when the elapsed delay is
		2013	larger than the requested delay. In the example above, libev would only invoke
		2014	the callback at system time 502, or 1.1s after the timer was started.
		2015
		2016	So, while libev cannot guarantee that your callback will be invoked
		2017	exactly when requested, it I<can> and I<does> guarantee that the requested
		2018	delay has actually elapsed, or in other words, it always errs on the "too
		2019	late" side of things.
		2020
2000	=head3 The special problem of time updates	2021	=head3 The special problem of time updates
2001		2022
2002	Establishing the current time is a costly operation (it usually takes at	2023	Establishing the current time is a costly operation (it usually takes
2003	least two system calls): EV therefore updates its idea of the current	2024	at least one system call): EV therefore updates its idea of the current
2004	time only before and after C<ev_run> collects new events, which causes a	2025	time only before and after C<ev_run> collects new events, which causes a
2005	growing difference between C<ev_now ()> and C<ev_time ()> when handling	2026	growing difference between C<ev_now ()> and C<ev_time ()> when handling
2006	lots of events in one iteration.	2027	lots of events in one iteration.
2007		2028
2008	The relative timeouts are calculated relative to the C<ev_now ()>	2029	The relative timeouts are calculated relative to the C<ev_now ()>
…		…
2014	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	2035	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
2015		2036
2016	If the event loop is suspended for a long time, you can also force an	2037	If the event loop is suspended for a long time, you can also force an
2017	update of the time returned by C<ev_now ()> by calling C<ev_now_update	2038	update of the time returned by C<ev_now ()> by calling C<ev_now_update
2018	()>.	2039	()>.
		2040
		2041	=head3 The special problem of unsynchronised clocks
		2042
		2043	Modern systems have a variety of clocks - libev itself uses the normal
		2044	"wall clock" clock and, if available, the monotonic clock (to avoid time
		2045	jumps).
		2046
		2047	Neither of these clocks is synchronised with each other or any other clock
		2048	on the system, so C<ev_time ()> might return a considerably different time
		2049	than C<gettimeofday ()> or C<time ()>. On a GNU/Linux system, for example,
		2050	a call to C<gettimeofday> might return a second count that is one higher
		2051	than a directly following call to C<time>.
		2052
		2053	The moral of this is to only compare libev-related timestamps with
		2054	C<ev_time ()> and C<ev_now ()>, at least if you want better precision than
		2055	a second or so.
		2056
		2057	One more problem arises due to this lack of synchronisation: if libev uses
		2058	the system monotonic clock and you compare timestamps from C<ev_time>
		2059	or C<ev_now> from when you started your timer and when your callback is
		2060	invoked, you will find that sometimes the callback is a bit "early".
		2061
		2062	This is because C<ev_timer>s work in real time, not wall clock time, so
		2063	libev makes sure your callback is not invoked before the delay happened,
		2064	I<measured according to the real time>, not the system clock.
		2065
		2066	If your timeouts are based on a physical timescale (e.g. "time out this
		2067	connection after 100 seconds") then this shouldn't bother you as it is
		2068	exactly the right behaviour.
		2069
		2070	If you want to compare wall clock/system timestamps to your timers, then
		2071	you need to use C<ev_periodic>s, as these are based on the wall clock
		2072	time, where your comparisons will always generate correct results.
2019		2073
2020	=head3 The special problems of suspended animation	2074	=head3 The special problems of suspended animation
2021		2075
2022	When you leave the server world it is quite customary to hit machines that	2076	When you leave the server world it is quite customary to hit machines that
2023	can suspend/hibernate - what happens to the clocks during such a suspend?	2077	can suspend/hibernate - what happens to the clocks during such a suspend?
…		…
2067	keep up with the timer (because it takes longer than those 10 seconds to	2121	keep up with the timer (because it takes longer than those 10 seconds to
2068	do stuff) the timer will not fire more than once per event loop iteration.	2122	do stuff) the timer will not fire more than once per event loop iteration.
2069		2123
2070	=item ev_timer_again (loop, ev_timer *)	2124	=item ev_timer_again (loop, ev_timer *)
2071		2125
2072	This will act as if the timer timed out and restart it again if it is	2126	This will act as if the timer timed out, and restarts it again if it is
2073	repeating. The exact semantics are:	2127	repeating. It basically works like calling C<ev_timer_stop>, updating the
		2128	timeout to the C<repeat> value and calling C<ev_timer_start>.
2074		2129
		2130	The exact semantics are as in the following rules, all of which will be
		2131	applied to the watcher:
		2132
		2133	=over 4
		2134
2075	If the timer is pending, its pending status is cleared.	2135	=item If the timer is pending, the pending status is always cleared.
2076		2136
2077	If the timer is started but non-repeating, stop it (as if it timed out).	2137	=item If the timer is started but non-repeating, stop it (as if it timed
		2138	out, without invoking it).
2078		2139
2079	If the timer is repeating, either start it if necessary (with the	2140	=item If the timer is repeating, make the C<repeat> value the new timeout
2080	C<repeat> value), or reset the running timer to the C<repeat> value.	2141	and start the timer, if necessary.
2081		2142
		2143	=back
		2144
2082	This sounds a bit complicated, see L<Be smart about timeouts>, above, for a	2145	This sounds a bit complicated, see L</Be smart about timeouts>, above, for a
2083	usage example.	2146	usage example.
2084		2147
2085	=item ev_tstamp ev_timer_remaining (loop, ev_timer *)	2148	=item ev_tstamp ev_timer_remaining (loop, ev_timer *)
2086		2149
2087	Returns the remaining time until a timer fires. If the timer is active,	2150	Returns the remaining time until a timer fires. If the timer is active,
…		…
2207		2270
2208	Another way to think about it (for the mathematically inclined) is that	2271	Another way to think about it (for the mathematically inclined) is that
2209	C<ev_periodic> will try to run the callback in this mode at the next possible	2272	C<ev_periodic> will try to run the callback in this mode at the next possible
2210	time where C<time = offset (mod interval)>, regardless of any time jumps.	2273	time where C<time = offset (mod interval)>, regardless of any time jumps.
2211		2274
2212	For numerical stability it is preferable that the C<offset> value is near	2275	The C<interval> I<MUST> be positive, and for numerical stability, the
2213	C<ev_now ()> (the current time), but there is no range requirement for	2276	interval value should be higher than C<1/8192> (which is around 100
2214	this value, and in fact is often specified as zero.	2277	microseconds) and C<offset> should be higher than C<0> and should have
		2278	at most a similar magnitude as the current time (say, within a factor of
		2279	ten). Typical values for offset are, in fact, C<0> or something between
		2280	C<0> and C<interval>, which is also the recommended range.
2215		2281
2216	Note also that there is an upper limit to how often a timer can fire (CPU	2282	Note also that there is an upper limit to how often a timer can fire (CPU
2217	speed for example), so if C<interval> is very small then timing stability	2283	speed for example), so if C<interval> is very small then timing stability
2218	will of course deteriorate. Libev itself tries to be exact to be about one	2284	will of course deteriorate. Libev itself tries to be exact to be about one
2219	millisecond (if the OS supports it and the machine is fast enough).	2285	millisecond (if the OS supports it and the machine is fast enough).
…		…
2327		2393
2328	ev_periodic hourly_tick;	2394	ev_periodic hourly_tick;
2329	ev_periodic_init (&hourly_tick, clock_cb,	2395	ev_periodic_init (&hourly_tick, clock_cb,
2330	fmod (ev_now (loop), 3600.), 3600., 0);	2396	fmod (ev_now (loop), 3600.), 3600., 0);
2331	ev_periodic_start (loop, &hourly_tick);	2397	ev_periodic_start (loop, &hourly_tick);
2332		2398
2333		2399
2334	=head2 C<ev_signal> - signal me when a signal gets signalled!	2400	=head2 C<ev_signal> - signal me when a signal gets signalled!
2335		2401
2336	Signal watchers will trigger an event when the process receives a specific	2402	Signal watchers will trigger an event when the process receives a specific
2337	signal one or more times. Even though signals are very asynchronous, libev	2403	signal one or more times. Even though signals are very asynchronous, libev
…		…
2347	only within the same loop, i.e. you can watch for C<SIGINT> in your	2413	only within the same loop, i.e. you can watch for C<SIGINT> in your
2348	default loop and for C<SIGIO> in another loop, but you cannot watch for	2414	default loop and for C<SIGIO> in another loop, but you cannot watch for
2349	C<SIGINT> in both the default loop and another loop at the same time. At	2415	C<SIGINT> in both the default loop and another loop at the same time. At
2350	the moment, C<SIGCHLD> is permanently tied to the default loop.	2416	the moment, C<SIGCHLD> is permanently tied to the default loop.
2351		2417
2352	When the first watcher gets started will libev actually register something	2418	Only after the first watcher for a signal is started will libev actually
2353	with the kernel (thus it coexists with your own signal handlers as long as	2419	register something with the kernel. It thus coexists with your own signal
2354	you don't register any with libev for the same signal).	2420	handlers as long as you don't register any with libev for the same signal.
2355		2421
2356	If possible and supported, libev will install its handlers with	2422	If possible and supported, libev will install its handlers with
2357	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should	2423	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
2358	not be unduly interrupted. If you have a problem with system calls getting	2424	not be unduly interrupted. If you have a problem with system calls getting
2359	interrupted by signals you can block all signals in an C<ev_check> watcher	2425	interrupted by signals you can block all signals in an C<ev_check> watcher
…		…
2362	=head3 The special problem of inheritance over fork/execve/pthread_create	2428	=head3 The special problem of inheritance over fork/execve/pthread_create
2363		2429
2364	Both the signal mask (C<sigprocmask>) and the signal disposition	2430	Both the signal mask (C<sigprocmask>) and the signal disposition
2365	(C<sigaction>) are unspecified after starting a signal watcher (and after	2431	(C<sigaction>) are unspecified after starting a signal watcher (and after
2366	stopping it again), that is, libev might or might not block the signal,	2432	stopping it again), that is, libev might or might not block the signal,
2367	and might or might not set or restore the installed signal handler.	2433	and might or might not set or restore the installed signal handler (but
		2434	see C<EVFLAG_NOSIGMASK>).
2368		2435
2369	While this does not matter for the signal disposition (libev never	2436	While this does not matter for the signal disposition (libev never
2370	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on	2437	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
2371	C<execve>), this matters for the signal mask: many programs do not expect	2438	C<execve>), this matters for the signal mask: many programs do not expect
2372	certain signals to be blocked.	2439	certain signals to be blocked.
…		…
2543		2610
2544	=head2 C<ev_stat> - did the file attributes just change?	2611	=head2 C<ev_stat> - did the file attributes just change?
2545		2612
2546	This watches a file system path for attribute changes. That is, it calls	2613	This watches a file system path for attribute changes. That is, it calls
2547	C<stat> on that path in regular intervals (or when the OS says it changed)	2614	C<stat> on that path in regular intervals (or when the OS says it changed)
2548	and sees if it changed compared to the last time, invoking the callback if	2615	and sees if it changed compared to the last time, invoking the callback
2549	it did.	2616	if it did. Starting the watcher C<stat>'s the file, so only changes that
		2617	happen after the watcher has been started will be reported.
2550		2618
2551	The path does not need to exist: changing from "path exists" to "path does	2619	The path does not need to exist: changing from "path exists" to "path does
2552	not exist" is a status change like any other. The condition "path does not	2620	not exist" is a status change like any other. The condition "path does not
2553	exist" (or more correctly "path cannot be stat'ed") is signified by the	2621	exist" (or more correctly "path cannot be stat'ed") is signified by the
2554	C<st_nlink> field being zero (which is otherwise always forced to be at	2622	C<st_nlink> field being zero (which is otherwise always forced to be at
…		…
2784	Apart from keeping your process non-blocking (which is a useful	2852	Apart from keeping your process non-blocking (which is a useful
2785	effect on its own sometimes), idle watchers are a good place to do	2853	effect on its own sometimes), idle watchers are a good place to do
2786	"pseudo-background processing", or delay processing stuff to after the	2854	"pseudo-background processing", or delay processing stuff to after the
2787	event loop has handled all outstanding events.	2855	event loop has handled all outstanding events.
2788		2856
		2857	=head3 Abusing an C<ev_idle> watcher for its side-effect
		2858
		2859	As long as there is at least one active idle watcher, libev will never
		2860	sleep unnecessarily. Or in other words, it will loop as fast as possible.
		2861	For this to work, the idle watcher doesn't need to be invoked at all - the
		2862	lowest priority will do.
		2863
		2864	This mode of operation can be useful together with an C<ev_check> watcher,
		2865	to do something on each event loop iteration - for example to balance load
		2866	between different connections.
		2867
		2868	See L</Abusing an ev_check watcher for its side-effect> for a longer
		2869	example.
		2870
2789	=head3 Watcher-Specific Functions and Data Members	2871	=head3 Watcher-Specific Functions and Data Members
2790		2872
2791	=over 4	2873	=over 4
2792		2874
2793	=item ev_idle_init (ev_idle *, callback)	2875	=item ev_idle_init (ev_idle *, callback)
…		…
2804	callback, free it. Also, use no error checking, as usual.	2886	callback, free it. Also, use no error checking, as usual.
2805		2887
2806	static void	2888	static void
2807	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)	2889	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)
2808	{	2890	{
		2891	// stop the watcher
		2892	ev_idle_stop (loop, w);
		2893
		2894	// now we can free it
2809	free (w);	2895	free (w);
		2896
2810	// now do something you wanted to do when the program has	2897	// now do something you wanted to do when the program has
2811	// no longer anything immediate to do.	2898	// no longer anything immediate to do.
2812	}	2899	}
2813		2900
2814	ev_idle *idle_watcher = malloc (sizeof (ev_idle));	2901	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
…		…
2816	ev_idle_start (loop, idle_watcher);	2903	ev_idle_start (loop, idle_watcher);
2817		2904
2818		2905
2819	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2906	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
2820		2907
2821	Prepare and check watchers are usually (but not always) used in pairs:	2908	Prepare and check watchers are often (but not always) used in pairs:
2822	prepare watchers get invoked before the process blocks and check watchers	2909	prepare watchers get invoked before the process blocks and check watchers
2823	afterwards.	2910	afterwards.
2824		2911
2825	You I<must not> call C<ev_run> or similar functions that enter	2912	You I<must not> call C<ev_run> or similar functions that enter
2826	the current event loop from either C<ev_prepare> or C<ev_check>	2913	the current event loop from either C<ev_prepare> or C<ev_check>
…		…
2854	with priority higher than or equal to the event loop and one coroutine	2941	with priority higher than or equal to the event loop and one coroutine
2855	of lower priority, but only once, using idle watchers to keep the event	2942	of lower priority, but only once, using idle watchers to keep the event
2856	loop from blocking if lower-priority coroutines are active, thus mapping	2943	loop from blocking if lower-priority coroutines are active, thus mapping
2857	low-priority coroutines to idle/background tasks).	2944	low-priority coroutines to idle/background tasks).
2858		2945
2859	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)	2946	When used for this purpose, it is recommended to give C<ev_check> watchers
2860	priority, to ensure that they are being run before any other watchers	2947	highest (C<EV_MAXPRI>) priority, to ensure that they are being run before
2861	after the poll (this doesn't matter for C<ev_prepare> watchers).	2948	any other watchers after the poll (this doesn't matter for C<ev_prepare>
		2949	watchers).
2862		2950
2863	Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not	2951	Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not
2864	activate ("feed") events into libev. While libev fully supports this, they	2952	activate ("feed") events into libev. While libev fully supports this, they
2865	might get executed before other C<ev_check> watchers did their job. As	2953	might get executed before other C<ev_check> watchers did their job. As
2866	C<ev_check> watchers are often used to embed other (non-libev) event	2954	C<ev_check> watchers are often used to embed other (non-libev) event
2867	loops those other event loops might be in an unusable state until their	2955	loops those other event loops might be in an unusable state until their
2868	C<ev_check> watcher ran (always remind yourself to coexist peacefully with	2956	C<ev_check> watcher ran (always remind yourself to coexist peacefully with
2869	others).	2957	others).
		2958
		2959	=head3 Abusing an C<ev_check> watcher for its side-effect
		2960
		2961	C<ev_check> (and less often also C<ev_prepare>) watchers can also be
		2962	useful because they are called once per event loop iteration. For
		2963	example, if you want to handle a large number of connections fairly, you
		2964	normally only do a bit of work for each active connection, and if there
		2965	is more work to do, you wait for the next event loop iteration, so other
		2966	connections have a chance of making progress.
		2967
		2968	Using an C<ev_check> watcher is almost enough: it will be called on the
		2969	next event loop iteration. However, that isn't as soon as possible -
		2970	without external events, your C<ev_check> watcher will not be invoked.
		2971
		2972	This is where C<ev_idle> watchers come in handy - all you need is a
		2973	single global idle watcher that is active as long as you have one active
		2974	C<ev_check> watcher. The C<ev_idle> watcher makes sure the event loop
		2975	will not sleep, and the C<ev_check> watcher makes sure a callback gets
		2976	invoked. Neither watcher alone can do that.
2870		2977
2871	=head3 Watcher-Specific Functions and Data Members	2978	=head3 Watcher-Specific Functions and Data Members
2872		2979
2873	=over 4	2980	=over 4
2874		2981
…		…
3075		3182
3076	=over 4	3183	=over 4
3077		3184
3078	=item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)	3185	=item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)
3079		3186
3080	=item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)	3187	=item ev_embed_set (ev_embed *, struct ev_loop *embedded_loop)
3081		3188
3082	Configures the watcher to embed the given loop, which must be	3189	Configures the watcher to embed the given loop, which must be
3083	embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be	3190	embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be
3084	invoked automatically, otherwise it is the responsibility of the callback	3191	invoked automatically, otherwise it is the responsibility of the callback
3085	to invoke it (it will continue to be called until the sweep has been done,	3192	to invoke it (it will continue to be called until the sweep has been done,
…		…
3106	used).	3213	used).
3107		3214
3108	struct ev_loop *loop_hi = ev_default_init (0);	3215	struct ev_loop *loop_hi = ev_default_init (0);
3109	struct ev_loop *loop_lo = 0;	3216	struct ev_loop *loop_lo = 0;
3110	ev_embed embed;	3217	ev_embed embed;
3111		3218
3112	// see if there is a chance of getting one that works	3219	// see if there is a chance of getting one that works
3113	// (remember that a flags value of 0 means autodetection)	3220	// (remember that a flags value of 0 means autodetection)
3114	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()	3221	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
3115	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())	3222	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
3116	: 0;	3223	: 0;
…		…
3130	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).	3237	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
3131		3238
3132	struct ev_loop *loop = ev_default_init (0);	3239	struct ev_loop *loop = ev_default_init (0);
3133	struct ev_loop *loop_socket = 0;	3240	struct ev_loop *loop_socket = 0;
3134	ev_embed embed;	3241	ev_embed embed;
3135		3242
3136	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)	3243	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
3137	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))	3244	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
3138	{	3245	{
3139	ev_embed_init (&embed, 0, loop_socket);	3246	ev_embed_init (&embed, 0, loop_socket);
3140	ev_embed_start (loop, &embed);	3247	ev_embed_start (loop, &embed);
…		…
3148		3255
3149	=head2 C<ev_fork> - the audacity to resume the event loop after a fork	3256	=head2 C<ev_fork> - the audacity to resume the event loop after a fork
3150		3257
3151	Fork watchers are called when a C<fork ()> was detected (usually because	3258	Fork watchers are called when a C<fork ()> was detected (usually because
3152	whoever is a good citizen cared to tell libev about it by calling	3259	whoever is a good citizen cared to tell libev about it by calling
3153	C<ev_default_fork> or C<ev_loop_fork>). The invocation is done before the	3260	C<ev_loop_fork>). The invocation is done before the event loop blocks next
3154	event loop blocks next and before C<ev_check> watchers are being called,	3261	and before C<ev_check> watchers are being called, and only in the child
3155	and only in the child after the fork. If whoever good citizen calling	3262	after the fork. If whoever good citizen calling C<ev_default_fork> cheats
3156	C<ev_default_fork> cheats and calls it in the wrong process, the fork	3263	and calls it in the wrong process, the fork handlers will be invoked, too,
3157	handlers will be invoked, too, of course.	3264	of course.
3158		3265
3159	=head3 The special problem of life after fork - how is it possible?	3266	=head3 The special problem of life after fork - how is it possible?
3160		3267
3161	Most uses of C<fork()> consist of forking, then some simple calls to set	3268	Most uses of C<fork()> consist of forking, then some simple calls to set
3162	up/change the process environment, followed by a call to C<exec()>. This	3269	up/change the process environment, followed by a call to C<exec()>. This
…		…
3243	atexit (program_exits);	3350	atexit (program_exits);
3244		3351
3245		3352
3246	=head2 C<ev_async> - how to wake up an event loop	3353	=head2 C<ev_async> - how to wake up an event loop
3247		3354
3248	In general, you cannot use an C<ev_run> from multiple threads or other	3355	In general, you cannot use an C<ev_loop> from multiple threads or other
3249	asynchronous sources such as signal handlers (as opposed to multiple event	3356	asynchronous sources such as signal handlers (as opposed to multiple event
3250	loops - those are of course safe to use in different threads).	3357	loops - those are of course safe to use in different threads).
3251		3358
3252	Sometimes, however, you need to wake up an event loop you do not control,	3359	Sometimes, however, you need to wake up an event loop you do not control,
3253	for example because it belongs to another thread. This is what C<ev_async>	3360	for example because it belongs to another thread. This is what C<ev_async>
…		…
3255	it by calling C<ev_async_send>, which is thread- and signal safe.	3362	it by calling C<ev_async_send>, which is thread- and signal safe.
3256		3363
3257	This functionality is very similar to C<ev_signal> watchers, as signals,	3364	This functionality is very similar to C<ev_signal> watchers, as signals,
3258	too, are asynchronous in nature, and signals, too, will be compressed	3365	too, are asynchronous in nature, and signals, too, will be compressed
3259	(i.e. the number of callback invocations may be less than the number of	3366	(i.e. the number of callback invocations may be less than the number of
3260	C<ev_async_sent> calls). In fact, you could use signal watchers as a kind	3367	C<ev_async_send> calls). In fact, you could use signal watchers as a kind
3261	of "global async watchers" by using a watcher on an otherwise unused	3368	of "global async watchers" by using a watcher on an otherwise unused
3262	signal, and C<ev_feed_signal> to signal this watcher from another thread,	3369	signal, and C<ev_feed_signal> to signal this watcher from another thread,
3263	even without knowing which loop owns the signal.	3370	even without knowing which loop owns the signal.
3264
3265	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not
3266	just the default loop.
3267		3371
3268	=head3 Queueing	3372	=head3 Queueing
3269		3373
3270	C<ev_async> does not support queueing of data in any way. The reason	3374	C<ev_async> does not support queueing of data in any way. The reason
3271	is that the author does not know of a simple (or any) algorithm for a	3375	is that the author does not know of a simple (or any) algorithm for a
…		…
3363	trust me.	3467	trust me.
3364		3468
3365	=item ev_async_send (loop, ev_async *)	3469	=item ev_async_send (loop, ev_async *)
3366		3470
3367	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3471	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
3368	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3472	an C<EV_ASYNC> event on the watcher into the event loop, and instantly
		3473	returns.
		3474
3369	C<ev_feed_event>, this call is safe to do from other threads, signal or	3475	Unlike C<ev_feed_event>, this call is safe to do from other threads,
3370	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3476	signal or similar contexts (see the discussion of C<EV_ATOMIC_T> in the
3371	section below on what exactly this means).	3477	embedding section below on what exactly this means).
3372		3478
3373	Note that, as with other watchers in libev, multiple events might get	3479	Note that, as with other watchers in libev, multiple events might get
3374	compressed into a single callback invocation (another way to look at this	3480	compressed into a single callback invocation (another way to look at
3375	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,	3481	this is that C<ev_async> watchers are level-triggered: they are set on
3376	reset when the event loop detects that).	3482	C<ev_async_send>, reset when the event loop detects that).
3377		3483
3378	This call incurs the overhead of a system call only once per event loop	3484	This call incurs the overhead of at most one extra system call per event
3379	iteration, so while the overhead might be noticeable, it doesn't apply to	3485	loop iteration, if the event loop is blocked, and no syscall at all if
3380	repeated calls to C<ev_async_send> for the same event loop.	3486	the event loop (or your program) is processing events. That means that
		3487	repeated calls are basically free (there is no need to avoid calls for
		3488	performance reasons) and that the overhead becomes smaller (typically
		3489	zero) under load.
3381		3490
3382	=item bool = ev_async_pending (ev_async *)	3491	=item bool = ev_async_pending (ev_async *)
3383		3492
3384	Returns a non-zero value when C<ev_async_send> has been called on the	3493	Returns a non-zero value when C<ev_async_send> has been called on the
3385	watcher but the event has not yet been processed (or even noted) by the	3494	watcher but the event has not yet been processed (or even noted) by the
…		…
3440	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3549	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
3441		3550
3442	=item ev_feed_fd_event (loop, int fd, int revents)	3551	=item ev_feed_fd_event (loop, int fd, int revents)
3443		3552
3444	Feed an event on the given fd, as if a file descriptor backend detected	3553	Feed an event on the given fd, as if a file descriptor backend detected
3445	the given events it.	3554	the given events.
3446		3555
3447	=item ev_feed_signal_event (loop, int signum)	3556	=item ev_feed_signal_event (loop, int signum)
3448		3557
3449	Feed an event as if the given signal occurred. See also C<ev_feed_signal>,	3558	Feed an event as if the given signal occurred. See also C<ev_feed_signal>,
3450	which is async-safe.	3559	which is async-safe.
…		…
3455	=head1 COMMON OR USEFUL IDIOMS (OR BOTH)	3564	=head1 COMMON OR USEFUL IDIOMS (OR BOTH)
3456		3565
3457	This section explains some common idioms that are not immediately	3566	This section explains some common idioms that are not immediately
3458	obvious. Note that examples are sprinkled over the whole manual, and this	3567	obvious. Note that examples are sprinkled over the whole manual, and this
3459	section only contains stuff that wouldn't fit anywhere else.	3568	section only contains stuff that wouldn't fit anywhere else.
		3569
		3570	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
		3571
		3572	Each watcher has, by default, a C<void *data> member that you can read
		3573	or modify at any time: libev will completely ignore it. This can be used
		3574	to associate arbitrary data with your watcher. If you need more data and
		3575	don't want to allocate memory separately and store a pointer to it in that
		3576	data member, you can also "subclass" the watcher type and provide your own
		3577	data:
		3578
		3579	struct my_io
		3580	{
		3581	ev_io io;
		3582	int otherfd;
		3583	void *somedata;
		3584	struct whatever *mostinteresting;
		3585	};
		3586
		3587	...
		3588	struct my_io w;
		3589	ev_io_init (&w.io, my_cb, fd, EV_READ);
		3590
		3591	And since your callback will be called with a pointer to the watcher, you
		3592	can cast it back to your own type:
		3593
		3594	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
		3595	{
		3596	struct my_io *w = (struct my_io *)w_;
		3597	...
		3598	}
		3599
		3600	More interesting and less C-conformant ways of casting your callback
		3601	function type instead have been omitted.
		3602
		3603	=head2 BUILDING YOUR OWN COMPOSITE WATCHERS
		3604
		3605	Another common scenario is to use some data structure with multiple
		3606	embedded watchers, in effect creating your own watcher that combines
		3607	multiple libev event sources into one "super-watcher":
		3608
		3609	struct my_biggy
		3610	{
		3611	int some_data;
		3612	ev_timer t1;
		3613	ev_timer t2;
		3614	}
		3615
		3616	In this case getting the pointer to C<my_biggy> is a bit more
		3617	complicated: Either you store the address of your C<my_biggy> struct in
		3618	the C<data> member of the watcher (for woozies or C++ coders), or you need
		3619	to use some pointer arithmetic using C<offsetof> inside your watchers (for
		3620	real programmers):
		3621
		3622	#include <stddef.h>
		3623
		3624	static void
		3625	t1_cb (EV_P_ ev_timer *w, int revents)
		3626	{
		3627	struct my_biggy big = (struct my_biggy *)
		3628	(((char *)w) - offsetof (struct my_biggy, t1));
		3629	}
		3630
		3631	static void
		3632	t2_cb (EV_P_ ev_timer *w, int revents)
		3633	{
		3634	struct my_biggy big = (struct my_biggy *)
		3635	(((char *)w) - offsetof (struct my_biggy, t2));
		3636	}
		3637
		3638	=head2 AVOIDING FINISHING BEFORE RETURNING
		3639
		3640	Often you have structures like this in event-based programs:
		3641
		3642	callback ()
		3643	{
		3644	free (request);
		3645	}
		3646
		3647	request = start_new_request (..., callback);
		3648
		3649	The intent is to start some "lengthy" operation. The C<request> could be
		3650	used to cancel the operation, or do other things with it.
		3651
		3652	It's not uncommon to have code paths in C<start_new_request> that
		3653	immediately invoke the callback, for example, to report errors. Or you add
		3654	some caching layer that finds that it can skip the lengthy aspects of the
		3655	operation and simply invoke the callback with the result.
		3656
		3657	The problem here is that this will happen I<before> C<start_new_request>
		3658	has returned, so C<request> is not set.
		3659
		3660	Even if you pass the request by some safer means to the callback, you
		3661	might want to do something to the request after starting it, such as
		3662	canceling it, which probably isn't working so well when the callback has
		3663	already been invoked.
		3664
		3665	A common way around all these issues is to make sure that
		3666	C<start_new_request> I<always> returns before the callback is invoked. If
		3667	C<start_new_request> immediately knows the result, it can artificially
		3668	delay invoking the callback by using a C<prepare> or C<idle> watcher for
		3669	example, or more sneakily, by reusing an existing (stopped) watcher and
		3670	pushing it into the pending queue:
		3671
		3672	ev_set_cb (watcher, callback);
		3673	ev_feed_event (EV_A_ watcher, 0);
		3674
		3675	This way, C<start_new_request> can safely return before the callback is
		3676	invoked, while not delaying callback invocation too much.
3460		3677
3461	=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS	3678	=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS
3462		3679
3463	Often (especially in GUI toolkits) there are places where you have	3680	Often (especially in GUI toolkits) there are places where you have
3464	I<modal> interaction, which is most easily implemented by recursively	3681	I<modal> interaction, which is most easily implemented by recursively
…		…
3466		3683
3467	This brings the problem of exiting - a callback might want to finish the	3684	This brings the problem of exiting - a callback might want to finish the
3468	main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but	3685	main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but
3469	a modal "Are you sure?" dialog is still waiting), or just the nested one	3686	a modal "Are you sure?" dialog is still waiting), or just the nested one
3470	and not the main one (e.g. user clocked "Ok" in a modal dialog), or some	3687	and not the main one (e.g. user clocked "Ok" in a modal dialog), or some
3471	other combination: In these cases, C<ev_break> will not work alone.	3688	other combination: In these cases, a simple C<ev_break> will not work.
3472		3689
3473	The solution is to maintain "break this loop" variable for each C<ev_run>	3690	The solution is to maintain "break this loop" variable for each C<ev_run>
3474	invocation, and use a loop around C<ev_run> until the condition is	3691	invocation, and use a loop around C<ev_run> until the condition is
3475	triggered, using C<EVRUN_ONCE>:	3692	triggered, using C<EVRUN_ONCE>:
3476		3693
…		…
3478	int exit_main_loop = 0;	3695	int exit_main_loop = 0;
3479		3696
3480	while (!exit_main_loop)	3697	while (!exit_main_loop)
3481	ev_run (EV_DEFAULT_ EVRUN_ONCE);	3698	ev_run (EV_DEFAULT_ EVRUN_ONCE);
3482		3699
3483	// in a model watcher	3700	// in a modal watcher
3484	int exit_nested_loop = 0;	3701	int exit_nested_loop = 0;
3485		3702
3486	while (!exit_nested_loop)	3703	while (!exit_nested_loop)
3487	ev_run (EV_A_ EVRUN_ONCE);	3704	ev_run (EV_A_ EVRUN_ONCE);
3488		3705
…		…
3498	exit_main_loop = exit_nested_loop = 1;	3715	exit_main_loop = exit_nested_loop = 1;
3499		3716
3500	=head2 THREAD LOCKING EXAMPLE	3717	=head2 THREAD LOCKING EXAMPLE
3501		3718
3502	Here is a fictitious example of how to run an event loop in a different	3719	Here is a fictitious example of how to run an event loop in a different
3503	thread than where callbacks are being invoked and watchers are	3720	thread from where callbacks are being invoked and watchers are
3504	created/added/removed.	3721	created/added/removed.
3505		3722
3506	For a real-world example, see the C<EV::Loop::Async> perl module,	3723	For a real-world example, see the C<EV::Loop::Async> perl module,
3507	which uses exactly this technique (which is suited for many high-level	3724	which uses exactly this technique (which is suited for many high-level
3508	languages).	3725	languages).
…		…
3534	// now associate this with the loop	3751	// now associate this with the loop
3535	ev_set_userdata (EV_A_ u);	3752	ev_set_userdata (EV_A_ u);
3536	ev_set_invoke_pending_cb (EV_A_ l_invoke);	3753	ev_set_invoke_pending_cb (EV_A_ l_invoke);
3537	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);	3754	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
3538		3755
3539	// then create the thread running ev_loop	3756	// then create the thread running ev_run
3540	pthread_create (&u->tid, 0, l_run, EV_A);	3757	pthread_create (&u->tid, 0, l_run, EV_A);
3541	}	3758	}
3542		3759
3543	The callback for the C<ev_async> watcher does nothing: the watcher is used	3760	The callback for the C<ev_async> watcher does nothing: the watcher is used
3544	solely to wake up the event loop so it takes notice of any new watchers	3761	solely to wake up the event loop so it takes notice of any new watchers
…		…
3633	Note that sending the C<ev_async> watcher is required because otherwise	3850	Note that sending the C<ev_async> watcher is required because otherwise
3634	an event loop currently blocking in the kernel will have no knowledge	3851	an event loop currently blocking in the kernel will have no knowledge
3635	about the newly added timer. By waking up the loop it will pick up any new	3852	about the newly added timer. By waking up the loop it will pick up any new
3636	watchers in the next event loop iteration.	3853	watchers in the next event loop iteration.
3637		3854
3638	=back	3855	=head2 THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS
		3856
		3857	While the overhead of a callback that e.g. schedules a thread is small, it
		3858	is still an overhead. If you embed libev, and your main usage is with some
		3859	kind of threads or coroutines, you might want to customise libev so that
		3860	doesn't need callbacks anymore.
		3861
		3862	Imagine you have coroutines that you can switch to using a function
		3863	C<switch_to (coro)>, that libev runs in a coroutine called C<libev_coro>
		3864	and that due to some magic, the currently active coroutine is stored in a
		3865	global called C<current_coro>. Then you can build your own "wait for libev
		3866	event" primitive by changing C<EV_CB_DECLARE> and C<EV_CB_INVOKE> (note
		3867	the differing C<;> conventions):
		3868
		3869	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3870	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb)
		3871
		3872	That means instead of having a C callback function, you store the
		3873	coroutine to switch to in each watcher, and instead of having libev call
		3874	your callback, you instead have it switch to that coroutine.
		3875
		3876	A coroutine might now wait for an event with a function called
		3877	C<wait_for_event>. (the watcher needs to be started, as always, but it doesn't
		3878	matter when, or whether the watcher is active or not when this function is
		3879	called):
		3880
		3881	void
		3882	wait_for_event (ev_watcher *w)
		3883	{
		3884	ev_set_cb (w, current_coro);
		3885	switch_to (libev_coro);
		3886	}
		3887
		3888	That basically suspends the coroutine inside C<wait_for_event> and
		3889	continues the libev coroutine, which, when appropriate, switches back to
		3890	this or any other coroutine.
		3891
		3892	You can do similar tricks if you have, say, threads with an event queue -
		3893	instead of storing a coroutine, you store the queue object and instead of
		3894	switching to a coroutine, you push the watcher onto the queue and notify
		3895	any waiters.
		3896
		3897	To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two
		3898	files, F<my_ev.h> and F<my_ev.c> that include the respective libev files:
		3899
		3900	// my_ev.h
		3901	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3902	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb);
		3903	#include "../libev/ev.h"
		3904
		3905	// my_ev.c
		3906	#define EV_H "my_ev.h"
		3907	#include "../libev/ev.c"
		3908
		3909	And then use F<my_ev.h> when you would normally use F<ev.h>, and compile
		3910	F<my_ev.c> into your project. When properly specifying include paths, you
		3911	can even use F<ev.h> as header file name directly.
3639		3912
3640		3913
3641	=head1 LIBEVENT EMULATION	3914	=head1 LIBEVENT EMULATION
3642		3915
3643	Libev offers a compatibility emulation layer for libevent. It cannot	3916	Libev offers a compatibility emulation layer for libevent. It cannot
…		…
3673		3946
3674	=back	3947	=back
3675		3948
3676	=head1 C++ SUPPORT	3949	=head1 C++ SUPPORT
3677		3950
		3951	=head2 C API
		3952
		3953	The normal C API should work fine when used from C++: both ev.h and the
		3954	libev sources can be compiled as C++. Therefore, code that uses the C API
		3955	will work fine.
		3956
		3957	Proper exception specifications might have to be added to callbacks passed
		3958	to libev: exceptions may be thrown only from watcher callbacks, all
		3959	other callbacks (allocator, syserr, loop acquire/release and periodic
		3960	reschedule callbacks) must not throw exceptions, and might need a C<throw
		3961	()> specification. If you have code that needs to be compiled as both C
		3962	and C++ you can use the C<EV_THROW> macro for this:
		3963
		3964	static void
		3965	fatal_error (const char *msg) EV_THROW
		3966	{
		3967	perror (msg);
		3968	abort ();
		3969	}
		3970
		3971	...
		3972	ev_set_syserr_cb (fatal_error);
		3973
		3974	The only API functions that can currently throw exceptions are C<ev_run>,
		3975	C<ev_invoke>, C<ev_invoke_pending> and C<ev_loop_destroy> (the latter
		3976	because it runs cleanup watchers).
		3977
		3978	Throwing exceptions in watcher callbacks is only supported if libev itself
		3979	is compiled with a C++ compiler or your C and C++ environments allow
		3980	throwing exceptions through C libraries (most do).
		3981
		3982	=head2 C++ API
		3983
3678	Libev comes with some simplistic wrapper classes for C++ that mainly allow	3984	Libev comes with some simplistic wrapper classes for C++ that mainly allow
3679	you to use some convenience methods to start/stop watchers and also change	3985	you to use some convenience methods to start/stop watchers and also change
3680	the callback model to a model using method callbacks on objects.	3986	the callback model to a model using method callbacks on objects.
3681		3987
3682	To use it,	3988	To use it,
3683		3989
3684	#include <ev++.h>	3990	#include <ev++.h>
3685		3991
3686	This automatically includes F<ev.h> and puts all of its definitions (many	3992	This automatically includes F<ev.h> and puts all of its definitions (many
3687	of them macros) into the global namespace. All C++ specific things are	3993	of them macros) into the global namespace. All C++ specific things are
3688	put into the C<ev> namespace. It should support all the same embedding	3994	put into the C<ev> namespace. It should support all the same embedding
…		…
3697	with C<operator ()> can be used as callbacks. Other types should be easy	4003	with C<operator ()> can be used as callbacks. Other types should be easy
3698	to add as long as they only need one additional pointer for context. If	4004	to add as long as they only need one additional pointer for context. If
3699	you need support for other types of functors please contact the author	4005	you need support for other types of functors please contact the author
3700	(preferably after implementing it).	4006	(preferably after implementing it).
3701		4007
		4008	For all this to work, your C++ compiler either has to use the same calling
		4009	conventions as your C compiler (for static member functions), or you have
		4010	to embed libev and compile libev itself as C++.
		4011
3702	Here is a list of things available in the C<ev> namespace:	4012	Here is a list of things available in the C<ev> namespace:
3703		4013
3704	=over 4	4014	=over 4
3705		4015
3706	=item C<ev::READ>, C<ev::WRITE> etc.	4016	=item C<ev::READ>, C<ev::WRITE> etc.
…		…
3715	=item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc.	4025	=item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc.
3716		4026
3717	For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of	4027	For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of
3718	the same name in the C<ev> namespace, with the exception of C<ev_signal>	4028	the same name in the C<ev> namespace, with the exception of C<ev_signal>
3719	which is called C<ev::sig> to avoid clashes with the C<signal> macro	4029	which is called C<ev::sig> to avoid clashes with the C<signal> macro
3720	defines by many implementations.	4030	defined by many implementations.
3721		4031
3722	All of those classes have these methods:	4032	All of those classes have these methods:
3723		4033
3724	=over 4	4034	=over 4
3725		4035
…		…
3787	void operator() (ev::io &w, int revents)	4097	void operator() (ev::io &w, int revents)
3788	{	4098	{
3789	...	4099	...
3790	}	4100	}
3791	}	4101	}
3792		4102
3793	myfunctor f;	4103	myfunctor f;
3794		4104
3795	ev::io w;	4105	ev::io w;
3796	w.set (&f);	4106	w.set (&f);
3797		4107
…		…
3815	Associates a different C<struct ev_loop> with this watcher. You can only	4125	Associates a different C<struct ev_loop> with this watcher. You can only
3816	do this when the watcher is inactive (and not pending either).	4126	do this when the watcher is inactive (and not pending either).
3817		4127
3818	=item w->set ([arguments])	4128	=item w->set ([arguments])
3819		4129
3820	Basically the same as C<ev_TYPE_set>, with the same arguments. Either this	4130	Basically the same as C<ev_TYPE_set> (except for C<ev::embed> watchers>),
3821	method or a suitable start method must be called at least once. Unlike the	4131	with the same arguments. Either this method or a suitable start method
3822	C counterpart, an active watcher gets automatically stopped and restarted	4132	must be called at least once. Unlike the C counterpart, an active watcher
3823	when reconfiguring it with this method.	4133	gets automatically stopped and restarted when reconfiguring it with this
		4134	method.
		4135
		4136	For C<ev::embed> watchers this method is called C<set_embed>, to avoid
		4137	clashing with the C<set (loop)> method.
3824		4138
3825	=item w->start ()	4139	=item w->start ()
3826		4140
3827	Starts the watcher. Note that there is no C<loop> argument, as the	4141	Starts the watcher. Note that there is no C<loop> argument, as the
3828	constructor already stores the event loop.	4142	constructor already stores the event loop.
…		…
3858	watchers in the constructor.	4172	watchers in the constructor.
3859		4173
3860	class myclass	4174	class myclass
3861	{	4175	{
3862	ev::io io ; void io_cb (ev::io &w, int revents);	4176	ev::io io ; void io_cb (ev::io &w, int revents);
3863	ev::io2 io2 ; void io2_cb (ev::io &w, int revents);	4177	ev::io io2 ; void io2_cb (ev::io &w, int revents);
3864	ev::idle idle; void idle_cb (ev::idle &w, int revents);	4178	ev::idle idle; void idle_cb (ev::idle &w, int revents);
3865		4179
3866	myclass (int fd)	4180	myclass (int fd)
3867	{	4181	{
3868	io .set <myclass, &myclass::io_cb > (this);	4182	io .set <myclass, &myclass::io_cb > (this);
…		…
3919	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.	4233	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.
3920		4234
3921	=item D	4235	=item D
3922		4236
3923	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	4237	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
3924	be found at L<http://proj.llucax.com.ar/wiki/evd>.	4238	be found at L<http://www.llucax.com.ar/proj/ev.d/index.html>.
3925		4239
3926	=item Ocaml	4240	=item Ocaml
3927		4241
3928	Erkki Seppala has written Ocaml bindings for libev, to be found at	4242	Erkki Seppala has written Ocaml bindings for libev, to be found at
3929	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.	4243	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
…		…
3932		4246
3933	Brian Maher has written a partial interface to libev for lua (at the	4247	Brian Maher has written a partial interface to libev for lua (at the
3934	time of this writing, only C<ev_io> and C<ev_timer>), to be found at	4248	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
3935	L<http://github.com/brimworks/lua-ev>.	4249	L<http://github.com/brimworks/lua-ev>.
3936		4250
		4251	=item Javascript
		4252
		4253	Node.js (L<http://nodejs.org>) uses libev as the underlying event library.
		4254
		4255	=item Others
		4256
		4257	There are others, and I stopped counting.
		4258
3937	=back	4259	=back
3938		4260
3939		4261
3940	=head1 MACRO MAGIC	4262	=head1 MACRO MAGIC
3941		4263
…		…
3977	suitable for use with C<EV_A>.	4299	suitable for use with C<EV_A>.
3978		4300
3979	=item C<EV_DEFAULT>, C<EV_DEFAULT_>	4301	=item C<EV_DEFAULT>, C<EV_DEFAULT_>
3980		4302
3981	Similar to the other two macros, this gives you the value of the default	4303	Similar to the other two macros, this gives you the value of the default
3982	loop, if multiple loops are supported ("ev loop default").	4304	loop, if multiple loops are supported ("ev loop default"). The default loop
		4305	will be initialised if it isn't already initialised.
		4306
		4307	For non-multiplicity builds, these macros do nothing, so you always have
		4308	to initialise the loop somewhere.
3983		4309
3984	=item C<EV_DEFAULT_UC>, C<EV_DEFAULT_UC_>	4310	=item C<EV_DEFAULT_UC>, C<EV_DEFAULT_UC_>
3985		4311
3986	Usage identical to C<EV_DEFAULT> and C<EV_DEFAULT_>, but requires that the	4312	Usage identical to C<EV_DEFAULT> and C<EV_DEFAULT_>, but requires that the
3987	default loop has been initialised (C<UC> == unchecked). Their behaviour	4313	default loop has been initialised (C<UC> == unchecked). Their behaviour
…		…
4132	supported). It will also not define any of the structs usually found in	4458	supported). It will also not define any of the structs usually found in
4133	F<event.h> that are not directly supported by the libev core alone.	4459	F<event.h> that are not directly supported by the libev core alone.
4134		4460
4135	In standalone mode, libev will still try to automatically deduce the	4461	In standalone mode, libev will still try to automatically deduce the
4136	configuration, but has to be more conservative.	4462	configuration, but has to be more conservative.
		4463
		4464	=item EV_USE_FLOOR
		4465
		4466	If defined to be C<1>, libev will use the C<floor ()> function for its
		4467	periodic reschedule calculations, otherwise libev will fall back on a
		4468	portable (slower) implementation. If you enable this, you usually have to
		4469	link against libm or something equivalent. Enabling this when the C<floor>
		4470	function is not available will fail, so the safe default is to not enable
		4471	this.
4137		4472
4138	=item EV_USE_MONOTONIC	4473	=item EV_USE_MONOTONIC
4139		4474
4140	If defined to be C<1>, libev will try to detect the availability of the	4475	If defined to be C<1>, libev will try to detect the availability of the
4141	monotonic clock option at both compile time and runtime. Otherwise no	4476	monotonic clock option at both compile time and runtime. Otherwise no
…		…
4226		4561
4227	If programs implement their own fd to handle mapping on win32, then this	4562	If programs implement their own fd to handle mapping on win32, then this
4228	macro can be used to override the C<close> function, useful to unregister	4563	macro can be used to override the C<close> function, useful to unregister
4229	file descriptors again. Note that the replacement function has to close	4564	file descriptors again. Note that the replacement function has to close
4230	the underlying OS handle.	4565	the underlying OS handle.
		4566
		4567	=item EV_USE_WSASOCKET
		4568
		4569	If defined to be C<1>, libev will use C<WSASocket> to create its internal
		4570	communication socket, which works better in some environments. Otherwise,
		4571	the normal C<socket> function will be used, which works better in other
		4572	environments.
4231		4573
4232	=item EV_USE_POLL	4574	=item EV_USE_POLL
4233		4575
4234	If defined to be C<1>, libev will compile in support for the C<poll>(2)	4576	If defined to be C<1>, libev will compile in support for the C<poll>(2)
4235	backend. Otherwise it will be enabled on non-win32 platforms. It	4577	backend. Otherwise it will be enabled on non-win32 platforms. It
…		…
4271	If defined to be C<1>, libev will compile in support for the Linux inotify	4613	If defined to be C<1>, libev will compile in support for the Linux inotify
4272	interface to speed up C<ev_stat> watchers. Its actual availability will	4614	interface to speed up C<ev_stat> watchers. Its actual availability will
4273	be detected at runtime. If undefined, it will be enabled if the headers	4615	be detected at runtime. If undefined, it will be enabled if the headers
4274	indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled.	4616	indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled.
4275		4617
		4618	=item EV_NO_SMP
		4619
		4620	If defined to be C<1>, libev will assume that memory is always coherent
		4621	between threads, that is, threads can be used, but threads never run on
		4622	different cpus (or different cpu cores). This reduces dependencies
		4623	and makes libev faster.
		4624
		4625	=item EV_NO_THREADS
		4626
		4627	If defined to be C<1>, libev will assume that it will never be called from
		4628	different threads (that includes signal handlers), which is a stronger
		4629	assumption than C<EV_NO_SMP>, above. This reduces dependencies and makes
		4630	libev faster.
		4631
4276	=item EV_ATOMIC_T	4632	=item EV_ATOMIC_T
4277		4633
4278	Libev requires an integer type (suitable for storing C<0> or C<1>) whose	4634	Libev requires an integer type (suitable for storing C<0> or C<1>) whose
4279	access is atomic with respect to other threads or signal contexts. No such	4635	access is atomic with respect to other threads or signal contexts. No
4280	type is easily found in the C language, so you can provide your own type	4636	such type is easily found in the C language, so you can provide your own
4281	that you know is safe for your purposes. It is used both for signal handler "locking"	4637	type that you know is safe for your purposes. It is used both for signal
4282	as well as for signal and thread safety in C<ev_async> watchers.	4638	handler "locking" as well as for signal and thread safety in C<ev_async>
		4639	watchers.
4283		4640
4284	In the absence of this define, libev will use C<sig_atomic_t volatile>	4641	In the absence of this define, libev will use C<sig_atomic_t volatile>
4285	(from F<signal.h>), which is usually good enough on most platforms.	4642	(from F<signal.h>), which is usually good enough on most platforms.
4286		4643
4287	=item EV_H (h)	4644	=item EV_H (h)
…		…
4314	will have the C<struct ev_loop *> as first argument, and you can create	4671	will have the C<struct ev_loop *> as first argument, and you can create
4315	additional independent event loops. Otherwise there will be no support	4672	additional independent event loops. Otherwise there will be no support
4316	for multiple event loops and there is no first event loop pointer	4673	for multiple event loops and there is no first event loop pointer
4317	argument. Instead, all functions act on the single default loop.	4674	argument. Instead, all functions act on the single default loop.
4318		4675
		4676	Note that C<EV_DEFAULT> and C<EV_DEFAULT_> will no longer provide a
		4677	default loop when multiplicity is switched off - you always have to
		4678	initialise the loop manually in this case.
		4679
4319	=item EV_MINPRI	4680	=item EV_MINPRI
4320		4681
4321	=item EV_MAXPRI	4682	=item EV_MAXPRI
4322		4683
4323	The range of allowed priorities. C<EV_MINPRI> must be smaller or equal to	4684	The range of allowed priorities. C<EV_MINPRI> must be smaller or equal to
…		…
4359	#define EV_USE_POLL 1	4720	#define EV_USE_POLL 1
4360	#define EV_CHILD_ENABLE 1	4721	#define EV_CHILD_ENABLE 1
4361	#define EV_ASYNC_ENABLE 1	4722	#define EV_ASYNC_ENABLE 1
4362		4723
4363	The actual value is a bitset, it can be a combination of the following	4724	The actual value is a bitset, it can be a combination of the following
4364	values:	4725	values (by default, all of these are enabled):
4365		4726
4366	=over 4	4727	=over 4
4367		4728
4368	=item C<1> - faster/larger code	4729	=item C<1> - faster/larger code
4369		4730
…		…
4373	code size by roughly 30% on amd64).	4734	code size by roughly 30% on amd64).
4374		4735
4375	When optimising for size, use of compiler flags such as C<-Os> with	4736	When optimising for size, use of compiler flags such as C<-Os> with
4376	gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of	4737	gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of
4377	assertions.	4738	assertions.
		4739
		4740	The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler
		4741	(e.g. gcc with C<-Os>).
4378		4742
4379	=item C<2> - faster/larger data structures	4743	=item C<2> - faster/larger data structures
4380		4744
4381	Replaces the small 2-heap for timer management by a faster 4-heap, larger	4745	Replaces the small 2-heap for timer management by a faster 4-heap, larger
4382	hash table sizes and so on. This will usually further increase code size	4746	hash table sizes and so on. This will usually further increase code size
4383	and can additionally have an effect on the size of data structures at	4747	and can additionally have an effect on the size of data structures at
4384	runtime.	4748	runtime.
4385		4749
		4750	The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler
		4751	(e.g. gcc with C<-Os>).
		4752
4386	=item C<4> - full API configuration	4753	=item C<4> - full API configuration
4387		4754
4388	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and	4755	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
4389	enables multiplicity (C<EV_MULTIPLICITY>=1).	4756	enables multiplicity (C<EV_MULTIPLICITY>=1).
4390		4757
…		…
4420		4787
4421	With an intelligent-enough linker (gcc+binutils are intelligent enough	4788	With an intelligent-enough linker (gcc+binutils are intelligent enough
4422	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by	4789	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
4423	your program might be left out as well - a binary starting a timer and an	4790	your program might be left out as well - a binary starting a timer and an
4424	I/O watcher then might come out at only 5Kb.	4791	I/O watcher then might come out at only 5Kb.
		4792
		4793	=item EV_API_STATIC
		4794
		4795	If this symbol is defined (by default it is not), then all identifiers
		4796	will have static linkage. This means that libev will not export any
		4797	identifiers, and you cannot link against libev anymore. This can be useful
		4798	when you embed libev, only want to use libev functions in a single file,
		4799	and do not want its identifiers to be visible.
		4800
		4801	To use this, define C<EV_API_STATIC> and include F<ev.c> in the file that
		4802	wants to use libev.
		4803
		4804	This option only works when libev is compiled with a C compiler, as C++
		4805	doesn't support the required declaration syntax.
4425		4806
4426	=item EV_AVOID_STDIO	4807	=item EV_AVOID_STDIO
4427		4808
4428	If this is set to C<1> at compiletime, then libev will avoid using stdio	4809	If this is set to C<1> at compiletime, then libev will avoid using stdio
4429	functions (printf, scanf, perror etc.). This will increase the code size	4810	functions (printf, scanf, perror etc.). This will increase the code size
…		…
4573	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4954	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
4574		4955
4575	#include "ev_cpp.h"	4956	#include "ev_cpp.h"
4576	#include "ev.c"	4957	#include "ev.c"
4577		4958
4578	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES	4959	=head1 INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT
4579		4960
4580	=head2 THREADS AND COROUTINES	4961	=head2 THREADS AND COROUTINES
4581		4962
4582	=head3 THREADS	4963	=head3 THREADS
4583		4964
…		…
4634	default loop and triggering an C<ev_async> watcher from the default loop	5015	default loop and triggering an C<ev_async> watcher from the default loop
4635	watcher callback into the event loop interested in the signal.	5016	watcher callback into the event loop interested in the signal.
4636		5017
4637	=back	5018	=back
4638		5019
4639	See also L<THREAD LOCKING EXAMPLE>.	5020	See also L</THREAD LOCKING EXAMPLE>.
4640		5021
4641	=head3 COROUTINES	5022	=head3 COROUTINES
4642		5023
4643	Libev is very accommodating to coroutines ("cooperative threads"):	5024	Libev is very accommodating to coroutines ("cooperative threads"):
4644	libev fully supports nesting calls to its functions from different	5025	libev fully supports nesting calls to its functions from different
…		…
4809	requires, and its I/O model is fundamentally incompatible with the POSIX	5190	requires, and its I/O model is fundamentally incompatible with the POSIX
4810	model. Libev still offers limited functionality on this platform in	5191	model. Libev still offers limited functionality on this platform in
4811	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	5192	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
4812	descriptors. This only applies when using Win32 natively, not when using	5193	descriptors. This only applies when using Win32 natively, not when using
4813	e.g. cygwin. Actually, it only applies to the microsofts own compilers,	5194	e.g. cygwin. Actually, it only applies to the microsofts own compilers,
4814	as every compielr comes with a slightly differently broken/incompatible	5195	as every compiler comes with a slightly differently broken/incompatible
4815	environment.	5196	environment.
4816		5197
4817	Lifting these limitations would basically require the full	5198	Lifting these limitations would basically require the full
4818	re-implementation of the I/O system. If you are into this kind of thing,	5199	re-implementation of the I/O system. If you are into this kind of thing,
4819	then note that glib does exactly that for you in a very portable way (note	5200	then note that glib does exactly that for you in a very portable way (note
…		…
4935	thread" or will block signals process-wide, both behaviours would	5316	thread" or will block signals process-wide, both behaviours would
4936	be compatible with libev. Interaction between C<sigprocmask> and	5317	be compatible with libev. Interaction between C<sigprocmask> and
4937	C<pthread_sigmask> could complicate things, however.	5318	C<pthread_sigmask> could complicate things, however.
4938		5319
4939	The most portable way to handle signals is to block signals in all threads	5320	The most portable way to handle signals is to block signals in all threads
4940	except the initial one, and run the default loop in the initial thread as	5321	except the initial one, and run the signal handling loop in the initial
4941	well.	5322	thread as well.
4942		5323
4943	=item C<long> must be large enough for common memory allocation sizes	5324	=item C<long> must be large enough for common memory allocation sizes
4944		5325
4945	To improve portability and simplify its API, libev uses C<long> internally	5326	To improve portability and simplify its API, libev uses C<long> internally
4946	instead of C<size_t> when allocating its data structures. On non-POSIX	5327	instead of C<size_t> when allocating its data structures. On non-POSIX
…		…
4952		5333
4953	The type C<double> is used to represent timestamps. It is required to	5334	The type C<double> is used to represent timestamps. It is required to
4954	have at least 51 bits of mantissa (and 9 bits of exponent), which is	5335	have at least 51 bits of mantissa (and 9 bits of exponent), which is
4955	good enough for at least into the year 4000 with millisecond accuracy	5336	good enough for at least into the year 4000 with millisecond accuracy
4956	(the design goal for libev). This requirement is overfulfilled by	5337	(the design goal for libev). This requirement is overfulfilled by
4957	implementations using IEEE 754, which is basically all existing ones. With	5338	implementations using IEEE 754, which is basically all existing ones.
		5339
4958	IEEE 754 doubles, you get microsecond accuracy until at least 2200.	5340	With IEEE 754 doubles, you get microsecond accuracy until at least the
		5341	year 2255 (and millisecond accuracy till the year 287396 - by then, libev
		5342	is either obsolete or somebody patched it to use C<long double> or
		5343	something like that, just kidding).
4959		5344
4960	=back	5345	=back
4961		5346
4962	If you know of other additional requirements drop me a note.	5347	If you know of other additional requirements drop me a note.
4963		5348
…		…
5025	=item Processing ev_async_send: O(number_of_async_watchers)	5410	=item Processing ev_async_send: O(number_of_async_watchers)
5026		5411
5027	=item Processing signals: O(max_signal_number)	5412	=item Processing signals: O(max_signal_number)
5028		5413
5029	Sending involves a system call I<iff> there were no other C<ev_async_send>	5414	Sending involves a system call I<iff> there were no other C<ev_async_send>
5030	calls in the current loop iteration. Checking for async and signal events	5415	calls in the current loop iteration and the loop is currently
		5416	blocked. Checking for async and signal events involves iterating over all
5031	involves iterating over all running async watchers or all signal numbers.	5417	running async watchers or all signal numbers.
5032		5418
5033	=back	5419	=back
5034		5420
5035		5421
5036	=head1 PORTING FROM LIBEV 3.X TO 4.X	5422	=head1 PORTING FROM LIBEV 3.X TO 4.X
…		…
5045	=over 4	5431	=over 4
5046		5432
5047	=item C<EV_COMPAT3> backwards compatibility mechanism	5433	=item C<EV_COMPAT3> backwards compatibility mechanism
5048		5434
5049	The backward compatibility mechanism can be controlled by	5435	The backward compatibility mechanism can be controlled by
5050	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>	5436	C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING>
5051	section.	5437	section.
5052		5438
5053	=item C<ev_default_destroy> and C<ev_default_fork> have been removed	5439	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
5054		5440
5055	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:	5441	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
…		…
5098	=over 4	5484	=over 4
5099		5485
5100	=item active	5486	=item active
5101		5487
5102	A watcher is active as long as it has been started and not yet stopped.	5488	A watcher is active as long as it has been started and not yet stopped.
5103	See L<WATCHER STATES> for details.	5489	See L</WATCHER STATES> for details.
5104		5490
5105	=item application	5491	=item application
5106		5492
5107	In this document, an application is whatever is using libev.	5493	In this document, an application is whatever is using libev.
5108		5494
…		…
5144	watchers and events.	5530	watchers and events.
5145		5531
5146	=item pending	5532	=item pending
5147		5533
5148	A watcher is pending as soon as the corresponding event has been	5534	A watcher is pending as soon as the corresponding event has been
5149	detected. See L<WATCHER STATES> for details.	5535	detected. See L</WATCHER STATES> for details.
5150		5536
5151	=item real time	5537	=item real time
5152		5538
5153	The physical time that is observed. It is apparently strictly monotonic :)	5539	The physical time that is observed. It is apparently strictly monotonic :)
5154		5540
5155	=item wall-clock time	5541	=item wall-clock time
5156		5542
5157	The time and date as shown on clocks. Unlike real time, it can actually	5543	The time and date as shown on clocks. Unlike real time, it can actually
5158	be wrong and jump forwards and backwards, e.g. when the you adjust your	5544	be wrong and jump forwards and backwards, e.g. when you adjust your
5159	clock.	5545	clock.
5160		5546
5161	=item watcher	5547	=item watcher
5162		5548
5163	A data structure that describes interest in certain events. Watchers need	5549	A data structure that describes interest in certain events. Watchers need
…		…
5166	=back	5552	=back
5167		5553
5168	=head1 AUTHOR	5554	=head1 AUTHOR
5169		5555
5170	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael	5556	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
5171	Magnusson and Emanuele Giaquinta.	5557	Magnusson and Emanuele Giaquinta, and minor corrections by many others.
5172		5558

Diff Legend

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