ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.194 by root, Mon Oct 20 16:08:36 2008 UTC vs.
Revision 1.286 by root, Tue Mar 16 00:26:41 2010 UTC

…		…
9	=head2 EXAMPLE PROGRAM	9	=head2 EXAMPLE PROGRAM
10		10
11	// a single header file is required	11	// a single header file is required
12	#include <ev.h>	12	#include <ev.h>
13		13
		14	#include <stdio.h> // for puts
		15
14	// every watcher type has its own typedef'd struct	16	// every watcher type has its own typedef'd struct
15	// with the name ev_<type>	17	// with the name ev_TYPE
16	ev_io stdin_watcher;	18	ev_io stdin_watcher;
17	ev_timer timeout_watcher;	19	ev_timer timeout_watcher;
18		20
19	// all watcher callbacks have a similar signature	21	// all watcher callbacks have a similar signature
20	// this callback is called when data is readable on stdin	22	// this callback is called when data is readable on stdin
21	static void	23	static void
22	stdin_cb (EV_P_ struct ev_io *w, int revents)	24	stdin_cb (EV_P_ ev_io *w, int revents)
23	{	25	{
24	puts ("stdin ready");	26	puts ("stdin ready");
25	// for one-shot events, one must manually stop the watcher	27	// for one-shot events, one must manually stop the watcher
26	// with its corresponding stop function.	28	// with its corresponding stop function.
27	ev_io_stop (EV_A_ w);	29	ev_io_stop (EV_A_ w);
…		…
30	ev_unloop (EV_A_ EVUNLOOP_ALL);	32	ev_unloop (EV_A_ EVUNLOOP_ALL);
31	}	33	}
32		34
33	// another callback, this time for a time-out	35	// another callback, this time for a time-out
34	static void	36	static void
35	timeout_cb (EV_P_ struct ev_timer *w, int revents)	37	timeout_cb (EV_P_ ev_timer *w, int revents)
36	{	38	{
37	puts ("timeout");	39	puts ("timeout");
38	// this causes the innermost ev_loop to stop iterating	40	// this causes the innermost ev_loop to stop iterating
39	ev_unloop (EV_A_ EVUNLOOP_ONE);	41	ev_unloop (EV_A_ EVUNLOOP_ONE);
40	}	42	}
…		…
60		62
61	// unloop was called, so exit	63	// unloop was called, so exit
62	return 0;	64	return 0;
63	}	65	}
64		66
65	=head1 DESCRIPTION	67	=head1 ABOUT THIS DOCUMENT
		68
		69	This document documents the libev software package.
66		70
67	The newest version of this document is also available as an html-formatted	71	The newest version of this document is also available as an html-formatted
68	web page you might find easier to navigate when reading it for the first	72	web page you might find easier to navigate when reading it for the first
69	time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>.	73	time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>.
		74
		75	While this document tries to be as complete as possible in documenting
		76	libev, its usage and the rationale behind its design, it is not a tutorial
		77	on event-based programming, nor will it introduce event-based programming
		78	with libev.
		79
		80	Familarity with event based programming techniques in general is assumed
		81	throughout this document.
		82
		83	=head1 ABOUT LIBEV
70		84
71	Libev is an event loop: you register interest in certain events (such as a	85	Libev is an event loop: you register interest in certain events (such as a
72	file descriptor being readable or a timeout occurring), and it will manage	86	file descriptor being readable or a timeout occurring), and it will manage
73	these event sources and provide your program with events.	87	these event sources and provide your program with events.
74		88
…		…
84	=head2 FEATURES	98	=head2 FEATURES
85		99
86	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the	100	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
87	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms	101	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
88	for file descriptor events (C<ev_io>), the Linux C<inotify> interface	102	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
89	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers	103	(for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner
90	with customised rescheduling (C<ev_periodic>), synchronous signals	104	inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative
91	(C<ev_signal>), process status change events (C<ev_child>), and event	105	timers (C<ev_timer>), absolute timers with customised rescheduling
92	watchers dealing with the event loop mechanism itself (C<ev_idle>,	106	(C<ev_periodic>), synchronous signals (C<ev_signal>), process status
93	C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as	107	change events (C<ev_child>), and event watchers dealing with the event
94	file watchers (C<ev_stat>) and even limited support for fork events	108	loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and
95	(C<ev_fork>).	109	C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even
		110	limited support for fork events (C<ev_fork>).
96		111
97	It also is quite fast (see this	112	It also is quite fast (see this
98	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent	113	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent
99	for example).	114	for example).
100		115
…		…
108	name C<loop> (which is always of type C<struct ev_loop *>) will not have	123	name C<loop> (which is always of type C<struct ev_loop *>) will not have
109	this argument.	124	this argument.
110		125
111	=head2 TIME REPRESENTATION	126	=head2 TIME REPRESENTATION
112		127
113	Libev represents time as a single floating point number, representing the	128	Libev represents time as a single floating point number, representing
114	(fractional) number of seconds since the (POSIX) epoch (somewhere near	129	the (fractional) number of seconds since the (POSIX) epoch (somewhere
115	the beginning of 1970, details are complicated, don't ask). This type is	130	near the beginning of 1970, details are complicated, don't ask). This
116	called C<ev_tstamp>, which is what you should use too. It usually aliases	131	type is called C<ev_tstamp>, which is what you should use too. It usually
117	to the C<double> type in C, and when you need to do any calculations on	132	aliases to the C<double> type in C. When you need to do any calculations
118	it, you should treat it as some floating point value. Unlike the name	133	on it, you should treat it as some floating point value. Unlike the name
119	component C<stamp> might indicate, it is also used for time differences	134	component C<stamp> might indicate, it is also used for time differences
120	throughout libev.	135	throughout libev.
121		136
122	=head1 ERROR HANDLING	137	=head1 ERROR HANDLING
123		138
…		…
276		291
277	=back	292	=back
278		293
279	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	294	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP
280		295
281	An event loop is described by a C<struct ev_loop *>. The library knows two	296	An event loop is described by a C<struct ev_loop *> (the C<struct>
282	types of such loops, the I<default> loop, which supports signals and child	297	is I<not> optional in this case, as there is also an C<ev_loop>
283	events, and dynamically created loops which do not.	298	I<function>).
		299
		300	The library knows two types of such loops, the I<default> loop, which
		301	supports signals and child events, and dynamically created loops which do
		302	not.
284		303
285	=over 4	304	=over 4
286		305
287	=item struct ev_loop *ev_default_loop (unsigned int flags)	306	=item struct ev_loop *ev_default_loop (unsigned int flags)
288		307
…		…
294	If you don't know what event loop to use, use the one returned from this	313	If you don't know what event loop to use, use the one returned from this
295	function.	314	function.
296		315
297	Note that this function is I<not> thread-safe, so if you want to use it	316	Note that this function is I<not> thread-safe, so if you want to use it
298	from multiple threads, you have to lock (note also that this is unlikely,	317	from multiple threads, you have to lock (note also that this is unlikely,
299	as loops cannot bes hared easily between threads anyway).	318	as loops cannot be shared easily between threads anyway).
300		319
301	The default loop is the only loop that can handle C<ev_signal> and	320	The default loop is the only loop that can handle C<ev_signal> and
302	C<ev_child> watchers, and to do this, it always registers a handler	321	C<ev_child> watchers, and to do this, it always registers a handler
303	for C<SIGCHLD>. If this is a problem for your application you can either	322	for C<SIGCHLD>. If this is a problem for your application you can either
304	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	323	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
…		…
344	flag.	363	flag.
345		364
346	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>	365	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
347	environment variable.	366	environment variable.
348		367
		368	=item C<EVFLAG_NOINOTIFY>
		369
		370	When this flag is specified, then libev will not attempt to use the
		371	I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and
		372	testing, this flag can be useful to conserve inotify file descriptors, as
		373	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
		374
		375	=item C<EVFLAG_SIGNALFD>
		376
		377	When this flag is specified, then libev will attempt to use the
		378	I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API
		379	delivers signals synchronously, which makes it both faster and might make
		380	it possible to get the queued signal data. It can also simplify signal
		381	handling with threads, as long as you properly block signals in your
		382	threads that are not interested in handling them.
		383
		384	Signalfd will not be used by default as this changes your signal mask, and
		385	there are a lot of shoddy libraries and programs (glib's threadpool for
		386	example) that can't properly initialise their signal masks.
		387
349	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	388	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
350		389
351	This is your standard select(2) backend. Not I<completely> standard, as	390	This is your standard select(2) backend. Not I<completely> standard, as
352	libev tries to roll its own fd_set with no limits on the number of fds,	391	libev tries to roll its own fd_set with no limits on the number of fds,
353	but if that fails, expect a fairly low limit on the number of fds when	392	but if that fails, expect a fairly low limit on the number of fds when
…		…
377	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and	416	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and
378	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.	417	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.
379		418
380	=item C<EVBACKEND_EPOLL> (value 4, Linux)	419	=item C<EVBACKEND_EPOLL> (value 4, Linux)
381		420
		421	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
		422	kernels).
		423
382	For few fds, this backend is a bit little slower than poll and select,	424	For few fds, this backend is a bit little slower than poll and select,
383	but it scales phenomenally better. While poll and select usually scale	425	but it scales phenomenally better. While poll and select usually scale
384	like O(total_fds) where n is the total number of fds (or the highest fd),	426	like O(total_fds) where n is the total number of fds (or the highest fd),
385	epoll scales either O(1) or O(active_fds). The epoll design has a number	427	epoll scales either O(1) or O(active_fds).
386	of shortcomings, such as silently dropping events in some hard-to-detect	428
387	cases and requiring a system call per fd change, no fork support and bad	429	The epoll mechanism deserves honorable mention as the most misdesigned
388	support for dup.	430	of the more advanced event mechanisms: mere annoyances include silently
		431	dropping file descriptors, requiring a system call per change per file
		432	descriptor (and unnecessary guessing of parameters), problems with dup and
		433	so on. The biggest issue is fork races, however - if a program forks then
		434	I<both> parent and child process have to recreate the epoll set, which can
		435	take considerable time (one syscall per file descriptor) and is of course
		436	hard to detect.
		437
		438	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
		439	of course I<doesn't>, and epoll just loves to report events for totally
		440	I<different> file descriptors (even already closed ones, so one cannot
		441	even remove them from the set) than registered in the set (especially
		442	on SMP systems). Libev tries to counter these spurious notifications by
		443	employing an additional generation counter and comparing that against the
		444	events to filter out spurious ones, recreating the set when required.
389		445
390	While stopping, setting and starting an I/O watcher in the same iteration	446	While stopping, setting and starting an I/O watcher in the same iteration
391	will result in some caching, there is still a system call per such incident	447	will result in some caching, there is still a system call per such
392	(because the fd could point to a different file description now), so its	448	incident (because the same I<file descriptor> could point to a different
393	best to avoid that. Also, C<dup ()>'ed file descriptors might not work	449	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
394	very well if you register events for both fds.	450	file descriptors might not work very well if you register events for both
395		451	file descriptors.
396	Please note that epoll sometimes generates spurious notifications, so you
397	need to use non-blocking I/O or other means to avoid blocking when no data
398	(or space) is available.
399		452
400	Best performance from this backend is achieved by not unregistering all	453	Best performance from this backend is achieved by not unregistering all
401	watchers for a file descriptor until it has been closed, if possible,	454	watchers for a file descriptor until it has been closed, if possible,
402	i.e. keep at least one watcher active per fd at all times. Stopping and	455	i.e. keep at least one watcher active per fd at all times. Stopping and
403	starting a watcher (without re-setting it) also usually doesn't cause	456	starting a watcher (without re-setting it) also usually doesn't cause
404	extra overhead.	457	extra overhead. A fork can both result in spurious notifications as well
		458	as in libev having to destroy and recreate the epoll object, which can
		459	take considerable time and thus should be avoided.
		460
		461	All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or
		462	faster than epoll for maybe up to a hundred file descriptors, depending on
		463	the usage. So sad.
405		464
406	While nominally embeddable in other event loops, this feature is broken in	465	While nominally embeddable in other event loops, this feature is broken in
407	all kernel versions tested so far.	466	all kernel versions tested so far.
408		467
409	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	468	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
410	C<EVBACKEND_POLL>.	469	C<EVBACKEND_POLL>.
411		470
412	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	471	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
413		472
414	Kqueue deserves special mention, as at the time of this writing, it was	473	Kqueue deserves special mention, as at the time of this writing, it
415	broken on all BSDs except NetBSD (usually it doesn't work reliably with	474	was broken on all BSDs except NetBSD (usually it doesn't work reliably
416	anything but sockets and pipes, except on Darwin, where of course it's	475	with anything but sockets and pipes, except on Darwin, where of course
417	completely useless). For this reason it's not being "auto-detected" unless	476	it's completely useless). Unlike epoll, however, whose brokenness
418	you explicitly specify it in the flags (i.e. using C<EVBACKEND_KQUEUE>) or	477	is by design, these kqueue bugs can (and eventually will) be fixed
419	libev was compiled on a known-to-be-good (-enough) system like NetBSD.	478	without API changes to existing programs. For this reason it's not being
		479	"auto-detected" unless you explicitly specify it in the flags (i.e. using
		480	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
		481	system like NetBSD.
420		482
421	You still can embed kqueue into a normal poll or select backend and use it	483	You still can embed kqueue into a normal poll or select backend and use it
422	only for sockets (after having made sure that sockets work with kqueue on	484	only for sockets (after having made sure that sockets work with kqueue on
423	the target platform). See C<ev_embed> watchers for more info.	485	the target platform). See C<ev_embed> watchers for more info.
424		486
425	It scales in the same way as the epoll backend, but the interface to the	487	It scales in the same way as the epoll backend, but the interface to the
426	kernel is more efficient (which says nothing about its actual speed, of	488	kernel is more efficient (which says nothing about its actual speed, of
427	course). While stopping, setting and starting an I/O watcher does never	489	course). While stopping, setting and starting an I/O watcher does never
428	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to	490	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to
429	two event changes per incident. Support for C<fork ()> is very bad and it	491	two event changes per incident. Support for C<fork ()> is very bad (but
430	drops fds silently in similarly hard-to-detect cases.	492	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect
		493	cases
431		494
432	This backend usually performs well under most conditions.	495	This backend usually performs well under most conditions.
433		496
434	While nominally embeddable in other event loops, this doesn't work	497	While nominally embeddable in other event loops, this doesn't work
435	everywhere, so you might need to test for this. And since it is broken	498	everywhere, so you might need to test for this. And since it is broken
436	almost everywhere, you should only use it when you have a lot of sockets	499	almost everywhere, you should only use it when you have a lot of sockets
437	(for which it usually works), by embedding it into another event loop	500	(for which it usually works), by embedding it into another event loop
438	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and, did I mention it,	501	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course
439	using it only for sockets.	502	also broken on OS X)) and, did I mention it, using it only for sockets.
440		503
441	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with	504	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with
442	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with	505	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with
443	C<NOTE_EOF>.	506	C<NOTE_EOF>.
444		507
…		…
464	might perform better.	527	might perform better.
465		528
466	On the positive side, with the exception of the spurious readiness	529	On the positive side, with the exception of the spurious readiness
467	notifications, this backend actually performed fully to specification	530	notifications, this backend actually performed fully to specification
468	in all tests and is fully embeddable, which is a rare feat among the	531	in all tests and is fully embeddable, which is a rare feat among the
469	OS-specific backends.	532	OS-specific backends (I vastly prefer correctness over speed hacks).
470		533
471	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	534	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
472	C<EVBACKEND_POLL>.	535	C<EVBACKEND_POLL>.
473		536
474	=item C<EVBACKEND_ALL>	537	=item C<EVBACKEND_ALL>
…		…
479		542
480	It is definitely not recommended to use this flag.	543	It is definitely not recommended to use this flag.
481		544
482	=back	545	=back
483		546
484	If one or more of these are or'ed into the flags value, then only these	547	If one or more of the backend flags are or'ed into the flags value,
485	backends will be tried (in the reverse order as listed here). If none are	548	then only these backends will be tried (in the reverse order as listed
486	specified, all backends in C<ev_recommended_backends ()> will be tried.	549	here). If none are specified, all backends in C<ev_recommended_backends
		550	()> will be tried.
487		551
488	Example: This is the most typical usage.	552	Example: This is the most typical usage.
489		553
490	if (!ev_default_loop (0))	554	if (!ev_default_loop (0))
491	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");	555	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
…		…
527	responsibility to either stop all watchers cleanly yourself I<before>	591	responsibility to either stop all watchers cleanly yourself I<before>
528	calling this function, or cope with the fact afterwards (which is usually	592	calling this function, or cope with the fact afterwards (which is usually
529	the easiest thing, you can just ignore the watchers and/or C<free ()> them	593	the easiest thing, you can just ignore the watchers and/or C<free ()> them
530	for example).	594	for example).
531		595
532	Note that certain global state, such as signal state, will not be freed by	596	Note that certain global state, such as signal state (and installed signal
533	this function, and related watchers (such as signal and child watchers)	597	handlers), will not be freed by this function, and related watchers (such
534	would need to be stopped manually.	598	as signal and child watchers) would need to be stopped manually.
535		599
536	In general it is not advisable to call this function except in the	600	In general it is not advisable to call this function except in the
537	rare occasion where you really need to free e.g. the signal handling	601	rare occasion where you really need to free e.g. the signal handling
538	pipe fds. If you need dynamically allocated loops it is better to use	602	pipe fds. If you need dynamically allocated loops it is better to use
539	C<ev_loop_new> and C<ev_loop_destroy>).	603	C<ev_loop_new> and C<ev_loop_destroy>.
540		604
541	=item ev_loop_destroy (loop)	605	=item ev_loop_destroy (loop)
542		606
543	Like C<ev_default_destroy>, but destroys an event loop created by an	607	Like C<ev_default_destroy>, but destroys an event loop created by an
544	earlier call to C<ev_loop_new>.	608	earlier call to C<ev_loop_new>.
…		…
582		646
583	This value can sometimes be useful as a generation counter of sorts (it	647	This value can sometimes be useful as a generation counter of sorts (it
584	"ticks" the number of loop iterations), as it roughly corresponds with	648	"ticks" the number of loop iterations), as it roughly corresponds with
585	C<ev_prepare> and C<ev_check> calls.	649	C<ev_prepare> and C<ev_check> calls.
586		650
		651	=item unsigned int ev_loop_depth (loop)
		652
		653	Returns the number of times C<ev_loop> was entered minus the number of
		654	times C<ev_loop> was exited, in other words, the recursion depth.
		655
		656	Outside C<ev_loop>, this number is zero. In a callback, this number is
		657	C<1>, unless C<ev_loop> was invoked recursively (or from another thread),
		658	in which case it is higher.
		659
		660	Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread
		661	etc.), doesn't count as exit.
		662
587	=item unsigned int ev_backend (loop)	663	=item unsigned int ev_backend (loop)
588		664
589	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	665	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
590	use.	666	use.
591		667
…		…
605		681
606	This function is rarely useful, but when some event callback runs for a	682	This function is rarely useful, but when some event callback runs for a
607	very long time without entering the event loop, updating libev's idea of	683	very long time without entering the event loop, updating libev's idea of
608	the current time is a good idea.	684	the current time is a good idea.
609		685
610	See also "The special problem of time updates" in the C<ev_timer> section.	686	See also L<The special problem of time updates> in the C<ev_timer> section.
		687
		688	=item ev_suspend (loop)
		689
		690	=item ev_resume (loop)
		691
		692	These two functions suspend and resume a loop, for use when the loop is
		693	not used for a while and timeouts should not be processed.
		694
		695	A typical use case would be an interactive program such as a game: When
		696	the user presses C<^Z> to suspend the game and resumes it an hour later it
		697	would be best to handle timeouts as if no time had actually passed while
		698	the program was suspended. This can be achieved by calling C<ev_suspend>
		699	in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
		700	C<ev_resume> directly afterwards to resume timer processing.
		701
		702	Effectively, all C<ev_timer> watchers will be delayed by the time spend
		703	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers
		704	will be rescheduled (that is, they will lose any events that would have
		705	occured while suspended).
		706
		707	After calling C<ev_suspend> you B<must not> call I<any> function on the
		708	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>
		709	without a previous call to C<ev_suspend>.
		710
		711	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
		712	event loop time (see C<ev_now_update>).
611		713
612	=item ev_loop (loop, int flags)	714	=item ev_loop (loop, int flags)
613		715
614	Finally, this is it, the event handler. This function usually is called	716	Finally, this is it, the event handler. This function usually is called
615	after you initialised all your watchers and you want to start handling	717	after you have initialised all your watchers and you want to start
616	events.	718	handling events.
617		719
618	If the flags argument is specified as C<0>, it will not return until	720	If the flags argument is specified as C<0>, it will not return until
619	either no event watchers are active anymore or C<ev_unloop> was called.	721	either no event watchers are active anymore or C<ev_unloop> was called.
620		722
621	Please note that an explicit C<ev_unloop> is usually better than	723	Please note that an explicit C<ev_unloop> is usually better than
…		…
631	the loop.	733	the loop.
632		734
633	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	735	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
634	necessary) and will handle those and any already outstanding ones. It	736	necessary) and will handle those and any already outstanding ones. It
635	will block your process until at least one new event arrives (which could	737	will block your process until at least one new event arrives (which could
636	be an event internal to libev itself, so there is no guarentee that a	738	be an event internal to libev itself, so there is no guarantee that a
637	user-registered callback will be called), and will return after one	739	user-registered callback will be called), and will return after one
638	iteration of the loop.	740	iteration of the loop.
639		741
640	This is useful if you are waiting for some external event in conjunction	742	This is useful if you are waiting for some external event in conjunction
641	with something not expressible using other libev watchers (i.e. "roll your	743	with something not expressible using other libev watchers (i.e. "roll your
…		…
695		797
696	Ref/unref can be used to add or remove a reference count on the event	798	Ref/unref can be used to add or remove a reference count on the event
697	loop: Every watcher keeps one reference, and as long as the reference	799	loop: Every watcher keeps one reference, and as long as the reference
698	count is nonzero, C<ev_loop> will not return on its own.	800	count is nonzero, C<ev_loop> will not return on its own.
699		801
700	If you have a watcher you never unregister that should not keep C<ev_loop>	802	This is useful when you have a watcher that you never intend to
701	from returning, call ev_unref() after starting, and ev_ref() before	803	unregister, but that nevertheless should not keep C<ev_loop> from
		804	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
702	stopping it.	805	before stopping it.
703		806
704	As an example, libev itself uses this for its internal signal pipe: It is	807	As an example, libev itself uses this for its internal signal pipe: It
705	not visible to the libev user and should not keep C<ev_loop> from exiting	808	is not visible to the libev user and should not keep C<ev_loop> from
706	if no event watchers registered by it are active. It is also an excellent	809	exiting if no event watchers registered by it are active. It is also an
707	way to do this for generic recurring timers or from within third-party	810	excellent way to do this for generic recurring timers or from within
708	libraries. Just remember to I<unref after start> and I<ref before stop>	811	third-party libraries. Just remember to I<unref after start> and I<ref
709	(but only if the watcher wasn't active before, or was active before,	812	before stop> (but only if the watcher wasn't active before, or was active
710	respectively).	813	before, respectively. Note also that libev might stop watchers itself
		814	(e.g. non-repeating timers) in which case you have to C<ev_ref>
		815	in the callback).
711		816
712	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	817	Example: Create a signal watcher, but keep it from keeping C<ev_loop>
713	running when nothing else is active.	818	running when nothing else is active.
714		819
715	struct ev_signal exitsig;	820	ev_signal exitsig;
716	ev_signal_init (&exitsig, sig_cb, SIGINT);	821	ev_signal_init (&exitsig, sig_cb, SIGINT);
717	ev_signal_start (loop, &exitsig);	822	ev_signal_start (loop, &exitsig);
718	evf_unref (loop);	823	evf_unref (loop);
719		824
720	Example: For some weird reason, unregister the above signal handler again.	825	Example: For some weird reason, unregister the above signal handler again.
…		…
744		849
745	By setting a higher I<io collect interval> you allow libev to spend more	850	By setting a higher I<io collect interval> you allow libev to spend more
746	time collecting I/O events, so you can handle more events per iteration,	851	time collecting I/O events, so you can handle more events per iteration,
747	at the cost of increasing latency. Timeouts (both C<ev_periodic> and	852	at the cost of increasing latency. Timeouts (both C<ev_periodic> and
748	C<ev_timer>) will be not affected. Setting this to a non-null value will	853	C<ev_timer>) will be not affected. Setting this to a non-null value will
749	introduce an additional C<ev_sleep ()> call into most loop iterations.	854	introduce an additional C<ev_sleep ()> call into most loop iterations. The
		855	sleep time ensures that libev will not poll for I/O events more often then
		856	once per this interval, on average.
750		857
751	Likewise, by setting a higher I<timeout collect interval> you allow libev	858	Likewise, by setting a higher I<timeout collect interval> you allow libev
752	to spend more time collecting timeouts, at the expense of increased	859	to spend more time collecting timeouts, at the expense of increased
753	latency/jitter/inexactness (the watcher callback will be called	860	latency/jitter/inexactness (the watcher callback will be called
754	later). C<ev_io> watchers will not be affected. Setting this to a non-null	861	later). C<ev_io> watchers will not be affected. Setting this to a non-null
…		…
756		863
757	Many (busy) programs can usually benefit by setting the I/O collect	864	Many (busy) programs can usually benefit by setting the I/O collect
758	interval to a value near C<0.1> or so, which is often enough for	865	interval to a value near C<0.1> or so, which is often enough for
759	interactive servers (of course not for games), likewise for timeouts. It	866	interactive servers (of course not for games), likewise for timeouts. It
760	usually doesn't make much sense to set it to a lower value than C<0.01>,	867	usually doesn't make much sense to set it to a lower value than C<0.01>,
761	as this approaches the timing granularity of most systems.	868	as this approaches the timing granularity of most systems. Note that if
		869	you do transactions with the outside world and you can't increase the
		870	parallelity, then this setting will limit your transaction rate (if you
		871	need to poll once per transaction and the I/O collect interval is 0.01,
		872	then you can't do more than 100 transations per second).
762		873
763	Setting the I<timeout collect interval> can improve the opportunity for	874	Setting the I<timeout collect interval> can improve the opportunity for
764	saving power, as the program will "bundle" timer callback invocations that	875	saving power, as the program will "bundle" timer callback invocations that
765	are "near" in time together, by delaying some, thus reducing the number of	876	are "near" in time together, by delaying some, thus reducing the number of
766	times the process sleeps and wakes up again. Another useful technique to	877	times the process sleeps and wakes up again. Another useful technique to
767	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure	878	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure
768	they fire on, say, one-second boundaries only.	879	they fire on, say, one-second boundaries only.
769		880
		881	Example: we only need 0.1s timeout granularity, and we wish not to poll
		882	more often than 100 times per second:
		883
		884	ev_set_timeout_collect_interval (EV_DEFAULT_UC_ 0.1);
		885	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
		886
		887	=item ev_invoke_pending (loop)
		888
		889	This call will simply invoke all pending watchers while resetting their
		890	pending state. Normally, C<ev_loop> does this automatically when required,
		891	but when overriding the invoke callback this call comes handy.
		892
		893	=item int ev_pending_count (loop)
		894
		895	Returns the number of pending watchers - zero indicates that no watchers
		896	are pending.
		897
		898	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
		899
		900	This overrides the invoke pending functionality of the loop: Instead of
		901	invoking all pending watchers when there are any, C<ev_loop> will call
		902	this callback instead. This is useful, for example, when you want to
		903	invoke the actual watchers inside another context (another thread etc.).
		904
		905	If you want to reset the callback, use C<ev_invoke_pending> as new
		906	callback.
		907
		908	=item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))
		909
		910	Sometimes you want to share the same loop between multiple threads. This
		911	can be done relatively simply by putting mutex_lock/unlock calls around
		912	each call to a libev function.
		913
		914	However, C<ev_loop> can run an indefinite time, so it is not feasible to
		915	wait for it to return. One way around this is to wake up the loop via
		916	C<ev_unloop> and C<av_async_send>, another way is to set these I<release>
		917	and I<acquire> callbacks on the loop.
		918
		919	When set, then C<release> will be called just before the thread is
		920	suspended waiting for new events, and C<acquire> is called just
		921	afterwards.
		922
		923	Ideally, C<release> will just call your mutex_unlock function, and
		924	C<acquire> will just call the mutex_lock function again.
		925
		926	While event loop modifications are allowed between invocations of
		927	C<release> and C<acquire> (that's their only purpose after all), no
		928	modifications done will affect the event loop, i.e. adding watchers will
		929	have no effect on the set of file descriptors being watched, or the time
		930	waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it
		931	to take note of any changes you made.
		932
		933	In theory, threads executing C<ev_loop> will be async-cancel safe between
		934	invocations of C<release> and C<acquire>.
		935
		936	See also the locking example in the C<THREADS> section later in this
		937	document.
		938
		939	=item ev_set_userdata (loop, void *data)
		940
		941	=item ev_userdata (loop)
		942
		943	Set and retrieve a single C<void *> associated with a loop. When
		944	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
		945	C<0.>
		946
		947	These two functions can be used to associate arbitrary data with a loop,
		948	and are intended solely for the C<invoke_pending_cb>, C<release> and
		949	C<acquire> callbacks described above, but of course can be (ab-)used for
		950	any other purpose as well.
		951
770	=item ev_loop_verify (loop)	952	=item ev_loop_verify (loop)
771		953
772	This function only does something when C<EV_VERIFY> support has been	954	This function only does something when C<EV_VERIFY> support has been
773	compiled in. which is the default for non-minimal builds. It tries to go	955	compiled in, which is the default for non-minimal builds. It tries to go
774	through all internal structures and checks them for validity. If anything	956	through all internal structures and checks them for validity. If anything
775	is found to be inconsistent, it will print an error message to standard	957	is found to be inconsistent, it will print an error message to standard
776	error and call C<abort ()>.	958	error and call C<abort ()>.
777		959
778	This can be used to catch bugs inside libev itself: under normal	960	This can be used to catch bugs inside libev itself: under normal
…		…
782	=back	964	=back
783		965
784		966
785	=head1 ANATOMY OF A WATCHER	967	=head1 ANATOMY OF A WATCHER
786		968
		969	In the following description, uppercase C<TYPE> in names stands for the
		970	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
		971	watchers and C<ev_io_start> for I/O watchers.
		972
787	A watcher is a structure that you create and register to record your	973	A watcher is a structure that you create and register to record your
788	interest in some event. For instance, if you want to wait for STDIN to	974	interest in some event. For instance, if you want to wait for STDIN to
789	become readable, you would create an C<ev_io> watcher for that:	975	become readable, you would create an C<ev_io> watcher for that:
790		976
791	static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)	977	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
792	{	978	{
793	ev_io_stop (w);	979	ev_io_stop (w);
794	ev_unloop (loop, EVUNLOOP_ALL);	980	ev_unloop (loop, EVUNLOOP_ALL);
795	}	981	}
796		982
797	struct ev_loop *loop = ev_default_loop (0);	983	struct ev_loop *loop = ev_default_loop (0);
		984
798	struct ev_io stdin_watcher;	985	ev_io stdin_watcher;
		986
799	ev_init (&stdin_watcher, my_cb);	987	ev_init (&stdin_watcher, my_cb);
800	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	988	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
801	ev_io_start (loop, &stdin_watcher);	989	ev_io_start (loop, &stdin_watcher);
		990
802	ev_loop (loop, 0);	991	ev_loop (loop, 0);
803		992
804	As you can see, you are responsible for allocating the memory for your	993	As you can see, you are responsible for allocating the memory for your
805	watcher structures (and it is usually a bad idea to do this on the stack,	994	watcher structures (and it is I<usually> a bad idea to do this on the
806	although this can sometimes be quite valid).	995	stack).
		996
		997	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
		998	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
807		999
808	Each watcher structure must be initialised by a call to C<ev_init	1000	Each watcher structure must be initialised by a call to C<ev_init
809	(watcher *, callback)>, which expects a callback to be provided. This	1001	(watcher *, callback)>, which expects a callback to be provided. This
810	callback gets invoked each time the event occurs (or, in the case of I/O	1002	callback gets invoked each time the event occurs (or, in the case of I/O
811	watchers, each time the event loop detects that the file descriptor given	1003	watchers, each time the event loop detects that the file descriptor given
812	is readable and/or writable).	1004	is readable and/or writable).
813		1005
814	Each watcher type has its own C<< ev_<type>_set (watcher *, ...) >> macro	1006	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
815	with arguments specific to this watcher type. There is also a macro	1007	macro to configure it, with arguments specific to the watcher type. There
816	to combine initialisation and setting in one call: C<< ev_<type>_init	1008	is also a macro to combine initialisation and setting in one call: C<<
817	(watcher *, callback, ...) >>.	1009	ev_TYPE_init (watcher *, callback, ...) >>.
818		1010
819	To make the watcher actually watch out for events, you have to start it	1011	To make the watcher actually watch out for events, you have to start it
820	with a watcher-specific start function (C<< ev_<type>_start (loop, watcher	1012	with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher
821	*) >>), and you can stop watching for events at any time by calling the	1013	*) >>), and you can stop watching for events at any time by calling the
822	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	1014	corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>.
823		1015
824	As long as your watcher is active (has been started but not stopped) you	1016	As long as your watcher is active (has been started but not stopped) you
825	must not touch the values stored in it. Most specifically you must never	1017	must not touch the values stored in it. Most specifically you must never
826	reinitialise it or call its C<set> macro.	1018	reinitialise it or call its C<ev_TYPE_set> macro.
827		1019
828	Each and every callback receives the event loop pointer as first, the	1020	Each and every callback receives the event loop pointer as first, the
829	registered watcher structure as second, and a bitset of received events as	1021	registered watcher structure as second, and a bitset of received events as
830	third argument.	1022	third argument.
831		1023
…		…
889		1081
890	=item C<EV_ASYNC>	1082	=item C<EV_ASYNC>
891		1083
892	The given async watcher has been asynchronously notified (see C<ev_async>).	1084	The given async watcher has been asynchronously notified (see C<ev_async>).
893		1085
		1086	=item C<EV_CUSTOM>
		1087
		1088	Not ever sent (or otherwise used) by libev itself, but can be freely used
		1089	by libev users to signal watchers (e.g. via C<ev_feed_event>).
		1090
894	=item C<EV_ERROR>	1091	=item C<EV_ERROR>
895		1092
896	An unspecified error has occurred, the watcher has been stopped. This might	1093	An unspecified error has occurred, the watcher has been stopped. This might
897	happen because the watcher could not be properly started because libev	1094	happen because the watcher could not be properly started because libev
898	ran out of memory, a file descriptor was found to be closed or any other	1095	ran out of memory, a file descriptor was found to be closed or any other
		1096	problem. Libev considers these application bugs.
		1097
899	problem. You best act on it by reporting the problem and somehow coping	1098	You best act on it by reporting the problem and somehow coping with the
900	with the watcher being stopped.	1099	watcher being stopped. Note that well-written programs should not receive
		1100	an error ever, so when your watcher receives it, this usually indicates a
		1101	bug in your program.
901		1102
902	Libev will usually signal a few "dummy" events together with an error, for	1103	Libev will usually signal a few "dummy" events together with an error, for
903	example it might indicate that a fd is readable or writable, and if your	1104	example it might indicate that a fd is readable or writable, and if your
904	callbacks is well-written it can just attempt the operation and cope with	1105	callbacks is well-written it can just attempt the operation and cope with
905	the error from read() or write(). This will not work in multi-threaded	1106	the error from read() or write(). This will not work in multi-threaded
…		…
908		1109
909	=back	1110	=back
910		1111
911	=head2 GENERIC WATCHER FUNCTIONS	1112	=head2 GENERIC WATCHER FUNCTIONS
912		1113
913	In the following description, C<TYPE> stands for the watcher type,
914	e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.
915
916	=over 4	1114	=over 4
917		1115
918	=item C<ev_init> (ev_TYPE *watcher, callback)	1116	=item C<ev_init> (ev_TYPE *watcher, callback)
919		1117
920	This macro initialises the generic portion of a watcher. The contents	1118	This macro initialises the generic portion of a watcher. The contents
…		…
925	which rolls both calls into one.	1123	which rolls both calls into one.
926		1124
927	You can reinitialise a watcher at any time as long as it has been stopped	1125	You can reinitialise a watcher at any time as long as it has been stopped
928	(or never started) and there are no pending events outstanding.	1126	(or never started) and there are no pending events outstanding.
929		1127
930	The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,	1128	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
931	int revents)>.	1129	int revents)>.
932		1130
933	Example: Initialise an C<ev_io> watcher in two steps.	1131	Example: Initialise an C<ev_io> watcher in two steps.
934		1132
935	ev_io w;	1133	ev_io w;
936	ev_init (&w, my_cb);	1134	ev_init (&w, my_cb);
937	ev_io_set (&w, STDIN_FILENO, EV_READ);	1135	ev_io_set (&w, STDIN_FILENO, EV_READ);
938		1136
939	=item C<ev_TYPE_set> (ev_TYPE *, [args])	1137	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
940		1138
941	This macro initialises the type-specific parts of a watcher. You need to	1139	This macro initialises the type-specific parts of a watcher. You need to
942	call C<ev_init> at least once before you call this macro, but you can	1140	call C<ev_init> at least once before you call this macro, but you can
943	call C<ev_TYPE_set> any number of times. You must not, however, call this	1141	call C<ev_TYPE_set> any number of times. You must not, however, call this
944	macro on a watcher that is active (it can be pending, however, which is a	1142	macro on a watcher that is active (it can be pending, however, which is a
…		…
957		1155
958	Example: Initialise and set an C<ev_io> watcher in one step.	1156	Example: Initialise and set an C<ev_io> watcher in one step.
959		1157
960	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);	1158	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
961		1159
962	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)	1160	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
963		1161
964	Starts (activates) the given watcher. Only active watchers will receive	1162	Starts (activates) the given watcher. Only active watchers will receive
965	events. If the watcher is already active nothing will happen.	1163	events. If the watcher is already active nothing will happen.
966		1164
967	Example: Start the C<ev_io> watcher that is being abused as example in this	1165	Example: Start the C<ev_io> watcher that is being abused as example in this
968	whole section.	1166	whole section.
969		1167
970	ev_io_start (EV_DEFAULT_UC, &w);	1168	ev_io_start (EV_DEFAULT_UC, &w);
971		1169
972	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)	1170	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
973		1171
974	Stops the given watcher again (if active) and clears the pending	1172	Stops the given watcher if active, and clears the pending status (whether
		1173	the watcher was active or not).
		1174
975	status. It is possible that stopped watchers are pending (for example,	1175	It is possible that stopped watchers are pending - for example,
976	non-repeating timers are being stopped when they become pending), but	1176	non-repeating timers are being stopped when they become pending - but
977	C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If	1177	calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
978	you want to free or reuse the memory used by the watcher it is therefore a	1178	pending. If you want to free or reuse the memory used by the watcher it is
979	good idea to always call its C<ev_TYPE_stop> function.	1179	therefore a good idea to always call its C<ev_TYPE_stop> function.
980		1180
981	=item bool ev_is_active (ev_TYPE *watcher)	1181	=item bool ev_is_active (ev_TYPE *watcher)
982		1182
983	Returns a true value iff the watcher is active (i.e. it has been started	1183	Returns a true value iff the watcher is active (i.e. it has been started
984	and not yet been stopped). As long as a watcher is active you must not modify	1184	and not yet been stopped). As long as a watcher is active you must not modify
…		…
1000	=item ev_cb_set (ev_TYPE *watcher, callback)	1200	=item ev_cb_set (ev_TYPE *watcher, callback)
1001		1201
1002	Change the callback. You can change the callback at virtually any time	1202	Change the callback. You can change the callback at virtually any time
1003	(modulo threads).	1203	(modulo threads).
1004		1204
1005	=item ev_set_priority (ev_TYPE *watcher, priority)	1205	=item ev_set_priority (ev_TYPE *watcher, int priority)
1006		1206
1007	=item int ev_priority (ev_TYPE *watcher)	1207	=item int ev_priority (ev_TYPE *watcher)
1008		1208
1009	Set and query the priority of the watcher. The priority is a small	1209	Set and query the priority of the watcher. The priority is a small
1010	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>	1210	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
1011	(default: C<-2>). Pending watchers with higher priority will be invoked	1211	(default: C<-2>). Pending watchers with higher priority will be invoked
1012	before watchers with lower priority, but priority will not keep watchers	1212	before watchers with lower priority, but priority will not keep watchers
1013	from being executed (except for C<ev_idle> watchers).	1213	from being executed (except for C<ev_idle> watchers).
1014		1214
1015	This means that priorities are I<only> used for ordering callback
1016	invocation after new events have been received. This is useful, for
1017	example, to reduce latency after idling, or more often, to bind two
1018	watchers on the same event and make sure one is called first.
1019
1020	If you need to suppress invocation when higher priority events are pending	1215	If you need to suppress invocation when higher priority events are pending
1021	you need to look at C<ev_idle> watchers, which provide this functionality.	1216	you need to look at C<ev_idle> watchers, which provide this functionality.
1022		1217
1023	You I<must not> change the priority of a watcher as long as it is active or	1218	You I<must not> change the priority of a watcher as long as it is active or
1024	pending.	1219	pending.
1025		1220
		1221	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
		1222	fine, as long as you do not mind that the priority value you query might
		1223	or might not have been clamped to the valid range.
		1224
1026	The default priority used by watchers when no priority has been set is	1225	The default priority used by watchers when no priority has been set is
1027	always C<0>, which is supposed to not be too high and not be too low :).	1226	always C<0>, which is supposed to not be too high and not be too low :).
1028		1227
1029	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1228	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
1030	fine, as long as you do not mind that the priority value you query might	1229	priorities.
1031	or might not have been adjusted to be within valid range.
1032		1230
1033	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1231	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
1034		1232
1035	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1233	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
1036	C<loop> nor C<revents> need to be valid as long as the watcher callback	1234	C<loop> nor C<revents> need to be valid as long as the watcher callback
…		…
1043	returns its C<revents> bitset (as if its callback was invoked). If the	1241	returns its C<revents> bitset (as if its callback was invoked). If the
1044	watcher isn't pending it does nothing and returns C<0>.	1242	watcher isn't pending it does nothing and returns C<0>.
1045		1243
1046	Sometimes it can be useful to "poll" a watcher instead of waiting for its	1244	Sometimes it can be useful to "poll" a watcher instead of waiting for its
1047	callback to be invoked, which can be accomplished with this function.	1245	callback to be invoked, which can be accomplished with this function.
		1246
		1247	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
		1248
		1249	Feeds the given event set into the event loop, as if the specified event
		1250	had happened for the specified watcher (which must be a pointer to an
		1251	initialised but not necessarily started event watcher). Obviously you must
		1252	not free the watcher as long as it has pending events.
		1253
		1254	Stopping the watcher, letting libev invoke it, or calling
		1255	C<ev_clear_pending> will clear the pending event, even if the watcher was
		1256	not started in the first place.
		1257
		1258	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
		1259	functions that do not need a watcher.
1048		1260
1049	=back	1261	=back
1050		1262
1051		1263
1052	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1264	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
…		…
1058	member, you can also "subclass" the watcher type and provide your own	1270	member, you can also "subclass" the watcher type and provide your own
1059	data:	1271	data:
1060		1272
1061	struct my_io	1273	struct my_io
1062	{	1274	{
1063	struct ev_io io;	1275	ev_io io;
1064	int otherfd;	1276	int otherfd;
1065	void *somedata;	1277	void *somedata;
1066	struct whatever *mostinteresting;	1278	struct whatever *mostinteresting;
1067	};	1279	};
1068		1280
…		…
1071	ev_io_init (&w.io, my_cb, fd, EV_READ);	1283	ev_io_init (&w.io, my_cb, fd, EV_READ);
1072		1284
1073	And since your callback will be called with a pointer to the watcher, you	1285	And since your callback will be called with a pointer to the watcher, you
1074	can cast it back to your own type:	1286	can cast it back to your own type:
1075		1287
1076	static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents)	1288	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1077	{	1289	{
1078	struct my_io *w = (struct my_io *)w_;	1290	struct my_io *w = (struct my_io *)w_;
1079	...	1291	...
1080	}	1292	}
1081		1293
…		…
1099	programmers):	1311	programmers):
1100		1312
1101	#include <stddef.h>	1313	#include <stddef.h>
1102		1314
1103	static void	1315	static void
1104	t1_cb (EV_P_ struct ev_timer *w, int revents)	1316	t1_cb (EV_P_ ev_timer *w, int revents)
1105	{	1317	{
1106	struct my_biggy big = (struct my_biggy *	1318	struct my_biggy big = (struct my_biggy *)
1107	(((char *)w) - offsetof (struct my_biggy, t1));	1319	(((char *)w) - offsetof (struct my_biggy, t1));
1108	}	1320	}
1109		1321
1110	static void	1322	static void
1111	t2_cb (EV_P_ struct ev_timer *w, int revents)	1323	t2_cb (EV_P_ ev_timer *w, int revents)
1112	{	1324	{
1113	struct my_biggy big = (struct my_biggy *	1325	struct my_biggy big = (struct my_biggy *)
1114	(((char *)w) - offsetof (struct my_biggy, t2));	1326	(((char *)w) - offsetof (struct my_biggy, t2));
1115	}	1327	}
		1328
		1329	=head2 WATCHER PRIORITY MODELS
		1330
		1331	Many event loops support I<watcher priorities>, which are usually small
		1332	integers that influence the ordering of event callback invocation
		1333	between watchers in some way, all else being equal.
		1334
		1335	In libev, Watcher priorities can be set using C<ev_set_priority>. See its
		1336	description for the more technical details such as the actual priority
		1337	range.
		1338
		1339	There are two common ways how these these priorities are being interpreted
		1340	by event loops:
		1341
		1342	In the more common lock-out model, higher priorities "lock out" invocation
		1343	of lower priority watchers, which means as long as higher priority
		1344	watchers receive events, lower priority watchers are not being invoked.
		1345
		1346	The less common only-for-ordering model uses priorities solely to order
		1347	callback invocation within a single event loop iteration: Higher priority
		1348	watchers are invoked before lower priority ones, but they all get invoked
		1349	before polling for new events.
		1350
		1351	Libev uses the second (only-for-ordering) model for all its watchers
		1352	except for idle watchers (which use the lock-out model).
		1353
		1354	The rationale behind this is that implementing the lock-out model for
		1355	watchers is not well supported by most kernel interfaces, and most event
		1356	libraries will just poll for the same events again and again as long as
		1357	their callbacks have not been executed, which is very inefficient in the
		1358	common case of one high-priority watcher locking out a mass of lower
		1359	priority ones.
		1360
		1361	Static (ordering) priorities are most useful when you have two or more
		1362	watchers handling the same resource: a typical usage example is having an
		1363	C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle
		1364	timeouts. Under load, data might be received while the program handles
		1365	other jobs, but since timers normally get invoked first, the timeout
		1366	handler will be executed before checking for data. In that case, giving
		1367	the timer a lower priority than the I/O watcher ensures that I/O will be
		1368	handled first even under adverse conditions (which is usually, but not
		1369	always, what you want).
		1370
		1371	Since idle watchers use the "lock-out" model, meaning that idle watchers
		1372	will only be executed when no same or higher priority watchers have
		1373	received events, they can be used to implement the "lock-out" model when
		1374	required.
		1375
		1376	For example, to emulate how many other event libraries handle priorities,
		1377	you can associate an C<ev_idle> watcher to each such watcher, and in
		1378	the normal watcher callback, you just start the idle watcher. The real
		1379	processing is done in the idle watcher callback. This causes libev to
		1380	continously poll and process kernel event data for the watcher, but when
		1381	the lock-out case is known to be rare (which in turn is rare :), this is
		1382	workable.
		1383
		1384	Usually, however, the lock-out model implemented that way will perform
		1385	miserably under the type of load it was designed to handle. In that case,
		1386	it might be preferable to stop the real watcher before starting the
		1387	idle watcher, so the kernel will not have to process the event in case
		1388	the actual processing will be delayed for considerable time.
		1389
		1390	Here is an example of an I/O watcher that should run at a strictly lower
		1391	priority than the default, and which should only process data when no
		1392	other events are pending:
		1393
		1394	ev_idle idle; // actual processing watcher
		1395	ev_io io; // actual event watcher
		1396
		1397	static void
		1398	io_cb (EV_P_ ev_io *w, int revents)
		1399	{
		1400	// stop the I/O watcher, we received the event, but
		1401	// are not yet ready to handle it.
		1402	ev_io_stop (EV_A_ w);
		1403
		1404	// start the idle watcher to ahndle the actual event.
		1405	// it will not be executed as long as other watchers
		1406	// with the default priority are receiving events.
		1407	ev_idle_start (EV_A_ &idle);
		1408	}
		1409
		1410	static void
		1411	idle_cb (EV_P_ ev_idle *w, int revents)
		1412	{
		1413	// actual processing
		1414	read (STDIN_FILENO, ...);
		1415
		1416	// have to start the I/O watcher again, as
		1417	// we have handled the event
		1418	ev_io_start (EV_P_ &io);
		1419	}
		1420
		1421	// initialisation
		1422	ev_idle_init (&idle, idle_cb);
		1423	ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ);
		1424	ev_io_start (EV_DEFAULT_ &io);
		1425
		1426	In the "real" world, it might also be beneficial to start a timer, so that
		1427	low-priority connections can not be locked out forever under load. This
		1428	enables your program to keep a lower latency for important connections
		1429	during short periods of high load, while not completely locking out less
		1430	important ones.
1116		1431
1117		1432
1118	=head1 WATCHER TYPES	1433	=head1 WATCHER TYPES
1119		1434
1120	This section describes each watcher in detail, but will not repeat	1435	This section describes each watcher in detail, but will not repeat
…		…
1146	descriptors to non-blocking mode is also usually a good idea (but not	1461	descriptors to non-blocking mode is also usually a good idea (but not
1147	required if you know what you are doing).	1462	required if you know what you are doing).
1148		1463
1149	If you cannot use non-blocking mode, then force the use of a	1464	If you cannot use non-blocking mode, then force the use of a
1150	known-to-be-good backend (at the time of this writing, this includes only	1465	known-to-be-good backend (at the time of this writing, this includes only
1151	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>).	1466	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
		1467	descriptors for which non-blocking operation makes no sense (such as
		1468	files) - libev doesn't guarentee any specific behaviour in that case.
1152		1469
1153	Another thing you have to watch out for is that it is quite easy to	1470	Another thing you have to watch out for is that it is quite easy to
1154	receive "spurious" readiness notifications, that is your callback might	1471	receive "spurious" readiness notifications, that is your callback might
1155	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1472	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1156	because there is no data. Not only are some backends known to create a	1473	because there is no data. Not only are some backends known to create a
…		…
1221		1538
1222	So when you encounter spurious, unexplained daemon exits, make sure you	1539	So when you encounter spurious, unexplained daemon exits, make sure you
1223	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon	1540	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1224	somewhere, as that would have given you a big clue).	1541	somewhere, as that would have given you a big clue).
1225		1542
		1543	=head3 The special problem of accept()ing when you can't
		1544
		1545	Many implementations of the POSIX C<accept> function (for example,
		1546	found in port-2004 Linux) have the peculiar behaviour of not removing a
		1547	connection from the pending queue in all error cases.
		1548
		1549	For example, larger servers often run out of file descriptors (because
		1550	of resource limits), causing C<accept> to fail with C<ENFILE> but not
		1551	rejecting the connection, leading to libev signalling readiness on
		1552	the next iteration again (the connection still exists after all), and
		1553	typically causing the program to loop at 100% CPU usage.
		1554
		1555	Unfortunately, the set of errors that cause this issue differs between
		1556	operating systems, there is usually little the app can do to remedy the
		1557	situation, and no known thread-safe method of removing the connection to
		1558	cope with overload is known (to me).
		1559
		1560	One of the easiest ways to handle this situation is to just ignore it
		1561	- when the program encounters an overload, it will just loop until the
		1562	situation is over. While this is a form of busy waiting, no OS offers an
		1563	event-based way to handle this situation, so it's the best one can do.
		1564
		1565	A better way to handle the situation is to log any errors other than
		1566	C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
		1567	messages, and continue as usual, which at least gives the user an idea of
		1568	what could be wrong ("raise the ulimit!"). For extra points one could stop
		1569	the C<ev_io> watcher on the listening fd "for a while", which reduces CPU
		1570	usage.
		1571
		1572	If your program is single-threaded, then you could also keep a dummy file
		1573	descriptor for overload situations (e.g. by opening F</dev/null>), and
		1574	when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>,
		1575	close that fd, and create a new dummy fd. This will gracefully refuse
		1576	clients under typical overload conditions.
		1577
		1578	The last way to handle it is to simply log the error and C<exit>, as
		1579	is often done with C<malloc> failures, but this results in an easy
		1580	opportunity for a DoS attack.
1226		1581
1227	=head3 Watcher-Specific Functions	1582	=head3 Watcher-Specific Functions
1228		1583
1229	=over 4	1584	=over 4
1230		1585
…		…
1251	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well	1606	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well
1252	readable, but only once. Since it is likely line-buffered, you could	1607	readable, but only once. Since it is likely line-buffered, you could
1253	attempt to read a whole line in the callback.	1608	attempt to read a whole line in the callback.
1254		1609
1255	static void	1610	static void
1256	stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1611	stdin_readable_cb (struct ev_loop *loop, ev_io *w, int revents)
1257	{	1612	{
1258	ev_io_stop (loop, w);	1613	ev_io_stop (loop, w);
1259	.. read from stdin here (or from w->fd) and handle any I/O errors	1614	.. read from stdin here (or from w->fd) and handle any I/O errors
1260	}	1615	}
1261		1616
1262	...	1617	...
1263	struct ev_loop *loop = ev_default_init (0);	1618	struct ev_loop *loop = ev_default_init (0);
1264	struct ev_io stdin_readable;	1619	ev_io stdin_readable;
1265	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1620	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1266	ev_io_start (loop, &stdin_readable);	1621	ev_io_start (loop, &stdin_readable);
1267	ev_loop (loop, 0);	1622	ev_loop (loop, 0);
1268		1623
1269		1624
…		…
1277	year, it will still time out after (roughly) one hour. "Roughly" because	1632	year, it will still time out after (roughly) one hour. "Roughly" because
1278	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1633	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1279	monotonic clock option helps a lot here).	1634	monotonic clock option helps a lot here).
1280		1635
1281	The callback is guaranteed to be invoked only I<after> its timeout has	1636	The callback is guaranteed to be invoked only I<after> its timeout has
1282	passed, but if multiple timers become ready during the same loop iteration	1637	passed (not I<at>, so on systems with very low-resolution clocks this
1283	then order of execution is undefined.	1638	might introduce a small delay). If multiple timers become ready during the
		1639	same loop iteration then the ones with earlier time-out values are invoked
		1640	before ones of the same priority with later time-out values (but this is
		1641	no longer true when a callback calls C<ev_loop> recursively).
		1642
		1643	=head3 Be smart about timeouts
		1644
		1645	Many real-world problems involve some kind of timeout, usually for error
		1646	recovery. A typical example is an HTTP request - if the other side hangs,
		1647	you want to raise some error after a while.
		1648
		1649	What follows are some ways to handle this problem, from obvious and
		1650	inefficient to smart and efficient.
		1651
		1652	In the following, a 60 second activity timeout is assumed - a timeout that
		1653	gets reset to 60 seconds each time there is activity (e.g. each time some
		1654	data or other life sign was received).
		1655
		1656	=over 4
		1657
		1658	=item 1. Use a timer and stop, reinitialise and start it on activity.
		1659
		1660	This is the most obvious, but not the most simple way: In the beginning,
		1661	start the watcher:
		1662
		1663	ev_timer_init (timer, callback, 60., 0.);
		1664	ev_timer_start (loop, timer);
		1665
		1666	Then, each time there is some activity, C<ev_timer_stop> it, initialise it
		1667	and start it again:
		1668
		1669	ev_timer_stop (loop, timer);
		1670	ev_timer_set (timer, 60., 0.);
		1671	ev_timer_start (loop, timer);
		1672
		1673	This is relatively simple to implement, but means that each time there is
		1674	some activity, libev will first have to remove the timer from its internal
		1675	data structure and then add it again. Libev tries to be fast, but it's
		1676	still not a constant-time operation.
		1677
		1678	=item 2. Use a timer and re-start it with C<ev_timer_again> inactivity.
		1679
		1680	This is the easiest way, and involves using C<ev_timer_again> instead of
		1681	C<ev_timer_start>.
		1682
		1683	To implement this, configure an C<ev_timer> with a C<repeat> value
		1684	of C<60> and then call C<ev_timer_again> at start and each time you
		1685	successfully read or write some data. If you go into an idle state where
		1686	you do not expect data to travel on the socket, you can C<ev_timer_stop>
		1687	the timer, and C<ev_timer_again> will automatically restart it if need be.
		1688
		1689	That means you can ignore both the C<ev_timer_start> function and the
		1690	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
		1691	member and C<ev_timer_again>.
		1692
		1693	At start:
		1694
		1695	ev_init (timer, callback);
		1696	timer->repeat = 60.;
		1697	ev_timer_again (loop, timer);
		1698
		1699	Each time there is some activity:
		1700
		1701	ev_timer_again (loop, timer);
		1702
		1703	It is even possible to change the time-out on the fly, regardless of
		1704	whether the watcher is active or not:
		1705
		1706	timer->repeat = 30.;
		1707	ev_timer_again (loop, timer);
		1708
		1709	This is slightly more efficient then stopping/starting the timer each time
		1710	you want to modify its timeout value, as libev does not have to completely
		1711	remove and re-insert the timer from/into its internal data structure.
		1712
		1713	It is, however, even simpler than the "obvious" way to do it.
		1714
		1715	=item 3. Let the timer time out, but then re-arm it as required.
		1716
		1717	This method is more tricky, but usually most efficient: Most timeouts are
		1718	relatively long compared to the intervals between other activity - in
		1719	our example, within 60 seconds, there are usually many I/O events with
		1720	associated activity resets.
		1721
		1722	In this case, it would be more efficient to leave the C<ev_timer> alone,
		1723	but remember the time of last activity, and check for a real timeout only
		1724	within the callback:
		1725
		1726	ev_tstamp last_activity; // time of last activity
		1727
		1728	static void
		1729	callback (EV_P_ ev_timer *w, int revents)
		1730	{
		1731	ev_tstamp now = ev_now (EV_A);
		1732	ev_tstamp timeout = last_activity + 60.;
		1733
		1734	// if last_activity + 60. is older than now, we did time out
		1735	if (timeout < now)
		1736	{
		1737	// timeout occured, take action
		1738	}
		1739	else
		1740	{
		1741	// callback was invoked, but there was some activity, re-arm
		1742	// the watcher to fire in last_activity + 60, which is
		1743	// guaranteed to be in the future, so "again" is positive:
		1744	w->repeat = timeout - now;
		1745	ev_timer_again (EV_A_ w);
		1746	}
		1747	}
		1748
		1749	To summarise the callback: first calculate the real timeout (defined
		1750	as "60 seconds after the last activity"), then check if that time has
		1751	been reached, which means something I<did>, in fact, time out. Otherwise
		1752	the callback was invoked too early (C<timeout> is in the future), so
		1753	re-schedule the timer to fire at that future time, to see if maybe we have
		1754	a timeout then.
		1755
		1756	Note how C<ev_timer_again> is used, taking advantage of the
		1757	C<ev_timer_again> optimisation when the timer is already running.
		1758
		1759	This scheme causes more callback invocations (about one every 60 seconds
		1760	minus half the average time between activity), but virtually no calls to
		1761	libev to change the timeout.
		1762
		1763	To start the timer, simply initialise the watcher and set C<last_activity>
		1764	to the current time (meaning we just have some activity :), then call the
		1765	callback, which will "do the right thing" and start the timer:
		1766
		1767	ev_init (timer, callback);
		1768	last_activity = ev_now (loop);
		1769	callback (loop, timer, EV_TIMEOUT);
		1770
		1771	And when there is some activity, simply store the current time in
		1772	C<last_activity>, no libev calls at all:
		1773
		1774	last_actiivty = ev_now (loop);
		1775
		1776	This technique is slightly more complex, but in most cases where the
		1777	time-out is unlikely to be triggered, much more efficient.
		1778
		1779	Changing the timeout is trivial as well (if it isn't hard-coded in the
		1780	callback :) - just change the timeout and invoke the callback, which will
		1781	fix things for you.
		1782
		1783	=item 4. Wee, just use a double-linked list for your timeouts.
		1784
		1785	If there is not one request, but many thousands (millions...), all
		1786	employing some kind of timeout with the same timeout value, then one can
		1787	do even better:
		1788
		1789	When starting the timeout, calculate the timeout value and put the timeout
		1790	at the I<end> of the list.
		1791
		1792	Then use an C<ev_timer> to fire when the timeout at the I<beginning> of
		1793	the list is expected to fire (for example, using the technique #3).
		1794
		1795	When there is some activity, remove the timer from the list, recalculate
		1796	the timeout, append it to the end of the list again, and make sure to
		1797	update the C<ev_timer> if it was taken from the beginning of the list.
		1798
		1799	This way, one can manage an unlimited number of timeouts in O(1) time for
		1800	starting, stopping and updating the timers, at the expense of a major
		1801	complication, and having to use a constant timeout. The constant timeout
		1802	ensures that the list stays sorted.
		1803
		1804	=back
		1805
		1806	So which method the best?
		1807
		1808	Method #2 is a simple no-brain-required solution that is adequate in most
		1809	situations. Method #3 requires a bit more thinking, but handles many cases
		1810	better, and isn't very complicated either. In most case, choosing either
		1811	one is fine, with #3 being better in typical situations.
		1812
		1813	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is
		1814	rather complicated, but extremely efficient, something that really pays
		1815	off after the first million or so of active timers, i.e. it's usually
		1816	overkill :)
1284		1817
1285	=head3 The special problem of time updates	1818	=head3 The special problem of time updates
1286		1819
1287	Establishing the current time is a costly operation (it usually takes at	1820	Establishing the current time is a costly operation (it usually takes at
1288	least two system calls): EV therefore updates its idea of the current	1821	least two system calls): EV therefore updates its idea of the current
…		…
1300		1833
1301	If the event loop is suspended for a long time, you can also force an	1834	If the event loop is suspended for a long time, you can also force an
1302	update of the time returned by C<ev_now ()> by calling C<ev_now_update	1835	update of the time returned by C<ev_now ()> by calling C<ev_now_update
1303	()>.	1836	()>.
1304		1837
		1838	=head3 The special problems of suspended animation
		1839
		1840	When you leave the server world it is quite customary to hit machines that
		1841	can suspend/hibernate - what happens to the clocks during such a suspend?
		1842
		1843	Some quick tests made with a Linux 2.6.28 indicate that a suspend freezes
		1844	all processes, while the clocks (C<times>, C<CLOCK_MONOTONIC>) continue
		1845	to run until the system is suspended, but they will not advance while the
		1846	system is suspended. That means, on resume, it will be as if the program
		1847	was frozen for a few seconds, but the suspend time will not be counted
		1848	towards C<ev_timer> when a monotonic clock source is used. The real time
		1849	clock advanced as expected, but if it is used as sole clocksource, then a
		1850	long suspend would be detected as a time jump by libev, and timers would
		1851	be adjusted accordingly.
		1852
		1853	I would not be surprised to see different behaviour in different between
		1854	operating systems, OS versions or even different hardware.
		1855
		1856	The other form of suspend (job control, or sending a SIGSTOP) will see a
		1857	time jump in the monotonic clocks and the realtime clock. If the program
		1858	is suspended for a very long time, and monotonic clock sources are in use,
		1859	then you can expect C<ev_timer>s to expire as the full suspension time
		1860	will be counted towards the timers. When no monotonic clock source is in
		1861	use, then libev will again assume a timejump and adjust accordingly.
		1862
		1863	It might be beneficial for this latter case to call C<ev_suspend>
		1864	and C<ev_resume> in code that handles C<SIGTSTP>, to at least get
		1865	deterministic behaviour in this case (you can do nothing against
		1866	C<SIGSTOP>).
		1867
1305	=head3 Watcher-Specific Functions and Data Members	1868	=head3 Watcher-Specific Functions and Data Members
1306		1869
1307	=over 4	1870	=over 4
1308		1871
1309	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	1872	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
…		…
1332	If the timer is started but non-repeating, stop it (as if it timed out).	1895	If the timer is started but non-repeating, stop it (as if it timed out).
1333		1896
1334	If the timer is repeating, either start it if necessary (with the	1897	If the timer is repeating, either start it if necessary (with the
1335	C<repeat> value), or reset the running timer to the C<repeat> value.	1898	C<repeat> value), or reset the running timer to the C<repeat> value.
1336		1899
1337	This sounds a bit complicated, but here is a useful and typical	1900	This sounds a bit complicated, see L<Be smart about timeouts>, above, for a
1338	example: Imagine you have a TCP connection and you want a so-called idle	1901	usage example.
1339	timeout, that is, you want to be called when there have been, say, 60
1340	seconds of inactivity on the socket. The easiest way to do this is to
1341	configure an C<ev_timer> with a C<repeat> value of C<60> and then call
1342	C<ev_timer_again> each time you successfully read or write some data. If
1343	you go into an idle state where you do not expect data to travel on the
1344	socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
1345	automatically restart it if need be.
1346		1902
1347	That means you can ignore the C<after> value and C<ev_timer_start>	1903	=item ev_tstamp ev_timer_remaining (loop, ev_timer *)
1348	altogether and only ever use the C<repeat> value and C<ev_timer_again>:
1349		1904
1350	ev_timer_init (timer, callback, 0., 5.);	1905	Returns the remaining time until a timer fires. If the timer is active,
1351	ev_timer_again (loop, timer);	1906	then this time is relative to the current event loop time, otherwise it's
1352	...	1907	the timeout value currently configured.
1353	timer->again = 17.;
1354	ev_timer_again (loop, timer);
1355	...
1356	timer->again = 10.;
1357	ev_timer_again (loop, timer);
1358		1908
1359	This is more slightly efficient then stopping/starting the timer each time	1909	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
1360	you want to modify its timeout value.	1910	C<5>. When the timer is started and one second passes, C<ev_timer_remaining>
1361		1911	will return C<4>. When the timer expires and is restarted, it will return
1362	Note, however, that it is often even more efficient to remember the	1912	roughly C<7> (likely slightly less as callback invocation takes some time,
1363	time of the last activity and let the timer time-out naturally. In the	1913	too), and so on.
1364	callback, you then check whether the time-out is real, or, if there was
1365	some activity, you reschedule the watcher to time-out in "last_activity +
1366	timeout - ev_now ()" seconds.
1367		1914
1368	=item ev_tstamp repeat [read-write]	1915	=item ev_tstamp repeat [read-write]
1369		1916
1370	The current C<repeat> value. Will be used each time the watcher times out	1917	The current C<repeat> value. Will be used each time the watcher times out
1371	or C<ev_timer_again> is called, and determines the next timeout (if any),	1918	or C<ev_timer_again> is called, and determines the next timeout (if any),
…		…
1376	=head3 Examples	1923	=head3 Examples
1377		1924
1378	Example: Create a timer that fires after 60 seconds.	1925	Example: Create a timer that fires after 60 seconds.
1379		1926
1380	static void	1927	static void
1381	one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1928	one_minute_cb (struct ev_loop *loop, ev_timer *w, int revents)
1382	{	1929	{
1383	.. one minute over, w is actually stopped right here	1930	.. one minute over, w is actually stopped right here
1384	}	1931	}
1385		1932
1386	struct ev_timer mytimer;	1933	ev_timer mytimer;
1387	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);	1934	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1388	ev_timer_start (loop, &mytimer);	1935	ev_timer_start (loop, &mytimer);
1389		1936
1390	Example: Create a timeout timer that times out after 10 seconds of	1937	Example: Create a timeout timer that times out after 10 seconds of
1391	inactivity.	1938	inactivity.
1392		1939
1393	static void	1940	static void
1394	timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1941	timeout_cb (struct ev_loop *loop, ev_timer *w, int revents)
1395	{	1942	{
1396	.. ten seconds without any activity	1943	.. ten seconds without any activity
1397	}	1944	}
1398		1945
1399	struct ev_timer mytimer;	1946	ev_timer mytimer;
1400	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	1947	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1401	ev_timer_again (&mytimer); /* start timer */	1948	ev_timer_again (&mytimer); /* start timer */
1402	ev_loop (loop, 0);	1949	ev_loop (loop, 0);
1403		1950
1404	// and in some piece of code that gets executed on any "activity":	1951	// and in some piece of code that gets executed on any "activity":
…		…
1409	=head2 C<ev_periodic> - to cron or not to cron?	1956	=head2 C<ev_periodic> - to cron or not to cron?
1410		1957
1411	Periodic watchers are also timers of a kind, but they are very versatile	1958	Periodic watchers are also timers of a kind, but they are very versatile
1412	(and unfortunately a bit complex).	1959	(and unfortunately a bit complex).
1413		1960
1414	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	1961	Unlike C<ev_timer>, periodic watchers are not based on real time (or
1415	but on wall clock time (absolute time). You can tell a periodic watcher	1962	relative time, the physical time that passes) but on wall clock time
1416	to trigger after some specific point in time. For example, if you tell a	1963	(absolute time, the thing you can read on your calender or clock). The
1417	periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now ()	1964	difference is that wall clock time can run faster or slower than real
1418	+ 10.>, that is, an absolute time not a delay) and then reset your system	1965	time, and time jumps are not uncommon (e.g. when you adjust your
1419	clock to January of the previous year, then it will take more than year	1966	wrist-watch).
1420	to trigger the event (unlike an C<ev_timer>, which would still trigger
1421	roughly 10 seconds later as it uses a relative timeout).
1422		1967
		1968	You can tell a periodic watcher to trigger after some specific point
		1969	in time: for example, if you tell a periodic watcher to trigger "in 10
		1970	seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time
		1971	not a delay) and then reset your system clock to January of the previous
		1972	year, then it will take a year or more to trigger the event (unlike an
		1973	C<ev_timer>, which would still trigger roughly 10 seconds after starting
		1974	it, as it uses a relative timeout).
		1975
1423	C<ev_periodic>s can also be used to implement vastly more complex timers,	1976	C<ev_periodic> watchers can also be used to implement vastly more complex
1424	such as triggering an event on each "midnight, local time", or other	1977	timers, such as triggering an event on each "midnight, local time", or
1425	complicated rules.	1978	other complicated rules. This cannot be done with C<ev_timer> watchers, as
		1979	those cannot react to time jumps.
1426		1980
1427	As with timers, the callback is guaranteed to be invoked only when the	1981	As with timers, the callback is guaranteed to be invoked only when the
1428	time (C<at>) has passed, but if multiple periodic timers become ready	1982	point in time where it is supposed to trigger has passed. If multiple
1429	during the same loop iteration, then order of execution is undefined.	1983	timers become ready during the same loop iteration then the ones with
		1984	earlier time-out values are invoked before ones with later time-out values
		1985	(but this is no longer true when a callback calls C<ev_loop> recursively).
1430		1986
1431	=head3 Watcher-Specific Functions and Data Members	1987	=head3 Watcher-Specific Functions and Data Members
1432		1988
1433	=over 4	1989	=over 4
1434		1990
1435	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	1991	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1436		1992
1437	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	1993	=item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1438		1994
1439	Lots of arguments, lets sort it out... There are basically three modes of	1995	Lots of arguments, let's sort it out... There are basically three modes of
1440	operation, and we will explain them from simplest to most complex:	1996	operation, and we will explain them from simplest to most complex:
1441		1997
1442	=over 4	1998	=over 4
1443		1999
1444	=item * absolute timer (at = time, interval = reschedule_cb = 0)	2000	=item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0)
1445		2001
1446	In this configuration the watcher triggers an event after the wall clock	2002	In this configuration the watcher triggers an event after the wall clock
1447	time C<at> has passed. It will not repeat and will not adjust when a time	2003	time C<offset> has passed. It will not repeat and will not adjust when a
1448	jump occurs, that is, if it is to be run at January 1st 2011 then it will	2004	time jump occurs, that is, if it is to be run at January 1st 2011 then it
1449	only run when the system clock reaches or surpasses this time.	2005	will be stopped and invoked when the system clock reaches or surpasses
		2006	this point in time.
1450		2007
1451	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)	2008	=item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0)
1452		2009
1453	In this mode the watcher will always be scheduled to time out at the next	2010	In this mode the watcher will always be scheduled to time out at the next
1454	C<at + N * interval> time (for some integer N, which can also be negative)	2011	C<offset + N * interval> time (for some integer N, which can also be
1455	and then repeat, regardless of any time jumps.	2012	negative) and then repeat, regardless of any time jumps. The C<offset>
		2013	argument is merely an offset into the C<interval> periods.
1456		2014
1457	This can be used to create timers that do not drift with respect to the	2015	This can be used to create timers that do not drift with respect to the
1458	system clock, for example, here is a C<ev_periodic> that triggers each	2016	system clock, for example, here is an C<ev_periodic> that triggers each
1459	hour, on the hour:	2017	hour, on the hour (with respect to UTC):
1460		2018
1461	ev_periodic_set (&periodic, 0., 3600., 0);	2019	ev_periodic_set (&periodic, 0., 3600., 0);
1462		2020
1463	This doesn't mean there will always be 3600 seconds in between triggers,	2021	This doesn't mean there will always be 3600 seconds in between triggers,
1464	but only that the callback will be called when the system time shows a	2022	but only that the callback will be called when the system time shows a
1465	full hour (UTC), or more correctly, when the system time is evenly divisible	2023	full hour (UTC), or more correctly, when the system time is evenly divisible
1466	by 3600.	2024	by 3600.
1467		2025
1468	Another way to think about it (for the mathematically inclined) is that	2026	Another way to think about it (for the mathematically inclined) is that
1469	C<ev_periodic> will try to run the callback in this mode at the next possible	2027	C<ev_periodic> will try to run the callback in this mode at the next possible
1470	time where C<time = at (mod interval)>, regardless of any time jumps.	2028	time where C<time = offset (mod interval)>, regardless of any time jumps.
1471		2029
1472	For numerical stability it is preferable that the C<at> value is near	2030	For numerical stability it is preferable that the C<offset> value is near
1473	C<ev_now ()> (the current time), but there is no range requirement for	2031	C<ev_now ()> (the current time), but there is no range requirement for
1474	this value, and in fact is often specified as zero.	2032	this value, and in fact is often specified as zero.
1475		2033
1476	Note also that there is an upper limit to how often a timer can fire (CPU	2034	Note also that there is an upper limit to how often a timer can fire (CPU
1477	speed for example), so if C<interval> is very small then timing stability	2035	speed for example), so if C<interval> is very small then timing stability
1478	will of course deteriorate. Libev itself tries to be exact to be about one	2036	will of course deteriorate. Libev itself tries to be exact to be about one
1479	millisecond (if the OS supports it and the machine is fast enough).	2037	millisecond (if the OS supports it and the machine is fast enough).
1480		2038
1481	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)	2039	=item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback)
1482		2040
1483	In this mode the values for C<interval> and C<at> are both being	2041	In this mode the values for C<interval> and C<offset> are both being
1484	ignored. Instead, each time the periodic watcher gets scheduled, the	2042	ignored. Instead, each time the periodic watcher gets scheduled, the
1485	reschedule callback will be called with the watcher as first, and the	2043	reschedule callback will be called with the watcher as first, and the
1486	current time as second argument.	2044	current time as second argument.
1487		2045
1488	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,	2046	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever,
1489	ever, or make ANY event loop modifications whatsoever>.	2047	or make ANY other event loop modifications whatsoever, unless explicitly
		2048	allowed by documentation here>.
1490		2049
1491	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop	2050	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop
1492	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the	2051	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
1493	only event loop modification you are allowed to do).	2052	only event loop modification you are allowed to do).
1494		2053
1495	The callback prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic	2054	The callback prototype is C<ev_tstamp (*reschedule_cb)(ev_periodic
1496	*w, ev_tstamp now)>, e.g.:	2055	*w, ev_tstamp now)>, e.g.:
1497		2056
		2057	static ev_tstamp
1498	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	2058	my_rescheduler (ev_periodic *w, ev_tstamp now)
1499	{	2059	{
1500	return now + 60.;	2060	return now + 60.;
1501	}	2061	}
1502		2062
1503	It must return the next time to trigger, based on the passed time value	2063	It must return the next time to trigger, based on the passed time value
…		…
1523	a different time than the last time it was called (e.g. in a crond like	2083	a different time than the last time it was called (e.g. in a crond like
1524	program when the crontabs have changed).	2084	program when the crontabs have changed).
1525		2085
1526	=item ev_tstamp ev_periodic_at (ev_periodic *)	2086	=item ev_tstamp ev_periodic_at (ev_periodic *)
1527		2087
1528	When active, returns the absolute time that the watcher is supposed to	2088	When active, returns the absolute time that the watcher is supposed
1529	trigger next.	2089	to trigger next. This is not the same as the C<offset> argument to
		2090	C<ev_periodic_set>, but indeed works even in interval and manual
		2091	rescheduling modes.
1530		2092
1531	=item ev_tstamp offset [read-write]	2093	=item ev_tstamp offset [read-write]
1532		2094
1533	When repeating, this contains the offset value, otherwise this is the	2095	When repeating, this contains the offset value, otherwise this is the
1534	absolute point in time (the C<at> value passed to C<ev_periodic_set>).	2096	absolute point in time (the C<offset> value passed to C<ev_periodic_set>,
		2097	although libev might modify this value for better numerical stability).
1535		2098
1536	Can be modified any time, but changes only take effect when the periodic	2099	Can be modified any time, but changes only take effect when the periodic
1537	timer fires or C<ev_periodic_again> is being called.	2100	timer fires or C<ev_periodic_again> is being called.
1538		2101
1539	=item ev_tstamp interval [read-write]	2102	=item ev_tstamp interval [read-write]
1540		2103
1541	The current interval value. Can be modified any time, but changes only	2104	The current interval value. Can be modified any time, but changes only
1542	take effect when the periodic timer fires or C<ev_periodic_again> is being	2105	take effect when the periodic timer fires or C<ev_periodic_again> is being
1543	called.	2106	called.
1544		2107
1545	=item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]	2108	=item ev_tstamp (*reschedule_cb)(ev_periodic *w, ev_tstamp now) [read-write]
1546		2109
1547	The current reschedule callback, or C<0>, if this functionality is	2110	The current reschedule callback, or C<0>, if this functionality is
1548	switched off. Can be changed any time, but changes only take effect when	2111	switched off. Can be changed any time, but changes only take effect when
1549	the periodic timer fires or C<ev_periodic_again> is being called.	2112	the periodic timer fires or C<ev_periodic_again> is being called.
1550		2113
…		…
1555	Example: Call a callback every hour, or, more precisely, whenever the	2118	Example: Call a callback every hour, or, more precisely, whenever the
1556	system time is divisible by 3600. The callback invocation times have	2119	system time is divisible by 3600. The callback invocation times have
1557	potentially a lot of jitter, but good long-term stability.	2120	potentially a lot of jitter, but good long-term stability.
1558		2121
1559	static void	2122	static void
1560	clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)	2123	clock_cb (struct ev_loop *loop, ev_io *w, int revents)
1561	{	2124	{
1562	... its now a full hour (UTC, or TAI or whatever your clock follows)	2125	... its now a full hour (UTC, or TAI or whatever your clock follows)
1563	}	2126	}
1564		2127
1565	struct ev_periodic hourly_tick;	2128	ev_periodic hourly_tick;
1566	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);	2129	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1567	ev_periodic_start (loop, &hourly_tick);	2130	ev_periodic_start (loop, &hourly_tick);
1568		2131
1569	Example: The same as above, but use a reschedule callback to do it:	2132	Example: The same as above, but use a reschedule callback to do it:
1570		2133
1571	#include <math.h>	2134	#include <math.h>
1572		2135
1573	static ev_tstamp	2136	static ev_tstamp
1574	my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)	2137	my_scheduler_cb (ev_periodic *w, ev_tstamp now)
1575	{	2138	{
1576	return now + (3600. - fmod (now, 3600.));	2139	return now + (3600. - fmod (now, 3600.));
1577	}	2140	}
1578		2141
1579	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);	2142	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1580		2143
1581	Example: Call a callback every hour, starting now:	2144	Example: Call a callback every hour, starting now:
1582		2145
1583	struct ev_periodic hourly_tick;	2146	ev_periodic hourly_tick;
1584	ev_periodic_init (&hourly_tick, clock_cb,	2147	ev_periodic_init (&hourly_tick, clock_cb,
1585	fmod (ev_now (loop), 3600.), 3600., 0);	2148	fmod (ev_now (loop), 3600.), 3600., 0);
1586	ev_periodic_start (loop, &hourly_tick);	2149	ev_periodic_start (loop, &hourly_tick);
1587		2150
1588		2151
…		…
1591	Signal watchers will trigger an event when the process receives a specific	2154	Signal watchers will trigger an event when the process receives a specific
1592	signal one or more times. Even though signals are very asynchronous, libev	2155	signal one or more times. Even though signals are very asynchronous, libev
1593	will try it's best to deliver signals synchronously, i.e. as part of the	2156	will try it's best to deliver signals synchronously, i.e. as part of the
1594	normal event processing, like any other event.	2157	normal event processing, like any other event.
1595		2158
1596	If you want signals asynchronously, just use C<sigaction> as you would	2159	If you want signals to be delivered truly asynchronously, just use
1597	do without libev and forget about sharing the signal. You can even use	2160	C<sigaction> as you would do without libev and forget about sharing
1598	C<ev_async> from a signal handler to synchronously wake up an event loop.	2161	the signal. You can even use C<ev_async> from a signal handler to
		2162	synchronously wake up an event loop.
1599		2163
1600	You can configure as many watchers as you like per signal. Only when the	2164	You can configure as many watchers as you like for the same signal, but
		2165	only within the same loop, i.e. you can watch for C<SIGINT> in your
		2166	default loop and for C<SIGIO> in another loop, but you cannot watch for
		2167	C<SIGINT> in both the default loop and another loop at the same time. At
		2168	the moment, C<SIGCHLD> is permanently tied to the default loop.
		2169
1601	first watcher gets started will libev actually register a signal handler	2170	When the first watcher gets started will libev actually register something
1602	with the kernel (thus it coexists with your own signal handlers as long as	2171	with the kernel (thus it coexists with your own signal handlers as long as
1603	you don't register any with libev for the same signal). Similarly, when	2172	you don't register any with libev for the same signal).
1604	the last signal watcher for a signal is stopped, libev will reset the
1605	signal handler to SIG_DFL (regardless of what it was set to before).
1606		2173
1607	If possible and supported, libev will install its handlers with	2174	If possible and supported, libev will install its handlers with
1608	C<SA_RESTART> behaviour enabled, so system calls should not be unduly	2175	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
1609	interrupted. If you have a problem with system calls getting interrupted by	2176	not be unduly interrupted. If you have a problem with system calls getting
1610	signals you can block all signals in an C<ev_check> watcher and unblock	2177	interrupted by signals you can block all signals in an C<ev_check> watcher
1611	them in an C<ev_prepare> watcher.	2178	and unblock them in an C<ev_prepare> watcher.
		2179
		2180	=head3 The special problem of inheritance over fork/execve/pthread_create
		2181
		2182	Both the signal mask (C<sigprocmask>) and the signal disposition
		2183	(C<sigaction>) are unspecified after starting a signal watcher (and after
		2184	stopping it again), that is, libev might or might not block the signal,
		2185	and might or might not set or restore the installed signal handler.
		2186
		2187	While this does not matter for the signal disposition (libev never
		2188	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
		2189	C<execve>), this matters for the signal mask: many programs do not expect
		2190	certain signals to be blocked.
		2191
		2192	This means that before calling C<exec> (from the child) you should reset
		2193	the signal mask to whatever "default" you expect (all clear is a good
		2194	choice usually).
		2195
		2196	The simplest way to ensure that the signal mask is reset in the child is
		2197	to install a fork handler with C<pthread_atfork> that resets it. That will
		2198	catch fork calls done by libraries (such as the libc) as well.
		2199
		2200	In current versions of libev, the signal will not be blocked indefinitely
		2201	unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces
		2202	the window of opportunity for problems, it will not go away, as libev
		2203	I<has> to modify the signal mask, at least temporarily.
		2204
		2205	So I can't stress this enough: I<If you do not reset your signal mask when
		2206	you expect it to be empty, you have a race condition in your code>. This
		2207	is not a libev-specific thing, this is true for most event libraries.
1612		2208
1613	=head3 Watcher-Specific Functions and Data Members	2209	=head3 Watcher-Specific Functions and Data Members
1614		2210
1615	=over 4	2211	=over 4
1616		2212
…		…
1630	=head3 Examples	2226	=head3 Examples
1631		2227
1632	Example: Try to exit cleanly on SIGINT.	2228	Example: Try to exit cleanly on SIGINT.
1633		2229
1634	static void	2230	static void
1635	sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)	2231	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
1636	{	2232	{
1637	ev_unloop (loop, EVUNLOOP_ALL);	2233	ev_unloop (loop, EVUNLOOP_ALL);
1638	}	2234	}
1639		2235
1640	struct ev_signal signal_watcher;	2236	ev_signal signal_watcher;
1641	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2237	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1642	ev_signal_start (loop, &signal_watcher);	2238	ev_signal_start (loop, &signal_watcher);
1643		2239
1644		2240
1645	=head2 C<ev_child> - watch out for process status changes	2241	=head2 C<ev_child> - watch out for process status changes
…		…
1648	some child status changes (most typically when a child of yours dies or	2244	some child status changes (most typically when a child of yours dies or
1649	exits). It is permissible to install a child watcher I<after> the child	2245	exits). It is permissible to install a child watcher I<after> the child
1650	has been forked (which implies it might have already exited), as long	2246	has been forked (which implies it might have already exited), as long
1651	as the event loop isn't entered (or is continued from a watcher), i.e.,	2247	as the event loop isn't entered (or is continued from a watcher), i.e.,
1652	forking and then immediately registering a watcher for the child is fine,	2248	forking and then immediately registering a watcher for the child is fine,
1653	but forking and registering a watcher a few event loop iterations later is	2249	but forking and registering a watcher a few event loop iterations later or
1654	not.	2250	in the next callback invocation is not.
1655		2251
1656	Only the default event loop is capable of handling signals, and therefore	2252	Only the default event loop is capable of handling signals, and therefore
1657	you can only register child watchers in the default event loop.	2253	you can only register child watchers in the default event loop.
1658		2254
		2255	Due to some design glitches inside libev, child watchers will always be
		2256	handled at maximum priority (their priority is set to C<EV_MAXPRI> by
		2257	libev)
		2258
1659	=head3 Process Interaction	2259	=head3 Process Interaction
1660		2260
1661	Libev grabs C<SIGCHLD> as soon as the default event loop is	2261	Libev grabs C<SIGCHLD> as soon as the default event loop is
1662	initialised. This is necessary to guarantee proper behaviour even if	2262	initialised. This is necessary to guarantee proper behaviour even if the
1663	the first child watcher is started after the child exits. The occurrence	2263	first child watcher is started after the child exits. The occurrence
1664	of C<SIGCHLD> is recorded asynchronously, but child reaping is done	2264	of C<SIGCHLD> is recorded asynchronously, but child reaping is done
1665	synchronously as part of the event loop processing. Libev always reaps all	2265	synchronously as part of the event loop processing. Libev always reaps all
1666	children, even ones not watched.	2266	children, even ones not watched.
1667		2267
1668	=head3 Overriding the Built-In Processing	2268	=head3 Overriding the Built-In Processing
…		…
1678	=head3 Stopping the Child Watcher	2278	=head3 Stopping the Child Watcher
1679		2279
1680	Currently, the child watcher never gets stopped, even when the	2280	Currently, the child watcher never gets stopped, even when the
1681	child terminates, so normally one needs to stop the watcher in the	2281	child terminates, so normally one needs to stop the watcher in the
1682	callback. Future versions of libev might stop the watcher automatically	2282	callback. Future versions of libev might stop the watcher automatically
1683	when a child exit is detected.	2283	when a child exit is detected (calling C<ev_child_stop> twice is not a
		2284	problem).
1684		2285
1685	=head3 Watcher-Specific Functions and Data Members	2286	=head3 Watcher-Specific Functions and Data Members
1686		2287
1687	=over 4	2288	=over 4
1688		2289
…		…
1720	its completion.	2321	its completion.
1721		2322
1722	ev_child cw;	2323	ev_child cw;
1723		2324
1724	static void	2325	static void
1725	child_cb (EV_P_ struct ev_child *w, int revents)	2326	child_cb (EV_P_ ev_child *w, int revents)
1726	{	2327	{
1727	ev_child_stop (EV_A_ w);	2328	ev_child_stop (EV_A_ w);
1728	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);	2329	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);
1729	}	2330	}
1730		2331
…		…
1745		2346
1746		2347
1747	=head2 C<ev_stat> - did the file attributes just change?	2348	=head2 C<ev_stat> - did the file attributes just change?
1748		2349
1749	This watches a file system path for attribute changes. That is, it calls	2350	This watches a file system path for attribute changes. That is, it calls
1750	C<stat> regularly (or when the OS says it changed) and sees if it changed	2351	C<stat> on that path in regular intervals (or when the OS says it changed)
1751	compared to the last time, invoking the callback if it did.	2352	and sees if it changed compared to the last time, invoking the callback if
		2353	it did.
1752		2354
1753	The path does not need to exist: changing from "path exists" to "path does	2355	The path does not need to exist: changing from "path exists" to "path does
1754	not exist" is a status change like any other. The condition "path does	2356	not exist" is a status change like any other. The condition "path does not
1755	not exist" is signified by the C<st_nlink> field being zero (which is	2357	exist" (or more correctly "path cannot be stat'ed") is signified by the
1756	otherwise always forced to be at least one) and all the other fields of	2358	C<st_nlink> field being zero (which is otherwise always forced to be at
1757	the stat buffer having unspecified contents.	2359	least one) and all the other fields of the stat buffer having unspecified
		2360	contents.
1758		2361
1759	The path I<should> be absolute and I<must not> end in a slash. If it is	2362	The path I<must not> end in a slash or contain special components such as
		2363	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1760	relative and your working directory changes, the behaviour is undefined.	2364	your working directory changes, then the behaviour is undefined.
1761		2365
1762	Since there is no standard kernel interface to do this, the portable	2366	Since there is no portable change notification interface available, the
1763	implementation simply calls C<stat (2)> regularly on the path to see if	2367	portable implementation simply calls C<stat(2)> regularly on the path
1764	it changed somehow. You can specify a recommended polling interval for	2368	to see if it changed somehow. You can specify a recommended polling
1765	this case. If you specify a polling interval of C<0> (highly recommended!)	2369	interval for this case. If you specify a polling interval of C<0> (highly
1766	then a I<suitable, unspecified default> value will be used (which	2370	recommended!) then a I<suitable, unspecified default> value will be used
1767	you can expect to be around five seconds, although this might change	2371	(which you can expect to be around five seconds, although this might
1768	dynamically). Libev will also impose a minimum interval which is currently	2372	change dynamically). Libev will also impose a minimum interval which is
1769	around C<0.1>, but thats usually overkill.	2373	currently around C<0.1>, but that's usually overkill.
1770		2374
1771	This watcher type is not meant for massive numbers of stat watchers,	2375	This watcher type is not meant for massive numbers of stat watchers,
1772	as even with OS-supported change notifications, this can be	2376	as even with OS-supported change notifications, this can be
1773	resource-intensive.	2377	resource-intensive.
1774		2378
1775	At the time of this writing, the only OS-specific interface implemented	2379	At the time of this writing, the only OS-specific interface implemented
1776	is the Linux inotify interface (implementing kqueue support is left as	2380	is the Linux inotify interface (implementing kqueue support is left as an
1777	an exercise for the reader. Note, however, that the author sees no way	2381	exercise for the reader. Note, however, that the author sees no way of
1778	of implementing C<ev_stat> semantics with kqueue).	2382	implementing C<ev_stat> semantics with kqueue, except as a hint).
1779		2383
1780	=head3 ABI Issues (Largefile Support)	2384	=head3 ABI Issues (Largefile Support)
1781		2385
1782	Libev by default (unless the user overrides this) uses the default	2386	Libev by default (unless the user overrides this) uses the default
1783	compilation environment, which means that on systems with large file	2387	compilation environment, which means that on systems with large file
1784	support disabled by default, you get the 32 bit version of the stat	2388	support disabled by default, you get the 32 bit version of the stat
1785	structure. When using the library from programs that change the ABI to	2389	structure. When using the library from programs that change the ABI to
1786	use 64 bit file offsets the programs will fail. In that case you have to	2390	use 64 bit file offsets the programs will fail. In that case you have to
1787	compile libev with the same flags to get binary compatibility. This is	2391	compile libev with the same flags to get binary compatibility. This is
1788	obviously the case with any flags that change the ABI, but the problem is	2392	obviously the case with any flags that change the ABI, but the problem is
1789	most noticeably disabled with ev_stat and large file support.	2393	most noticeably displayed with ev_stat and large file support.
1790		2394
1791	The solution for this is to lobby your distribution maker to make large	2395	The solution for this is to lobby your distribution maker to make large
1792	file interfaces available by default (as e.g. FreeBSD does) and not	2396	file interfaces available by default (as e.g. FreeBSD does) and not
1793	optional. Libev cannot simply switch on large file support because it has	2397	optional. Libev cannot simply switch on large file support because it has
1794	to exchange stat structures with application programs compiled using the	2398	to exchange stat structures with application programs compiled using the
1795	default compilation environment.	2399	default compilation environment.
1796		2400
1797	=head3 Inotify and Kqueue	2401	=head3 Inotify and Kqueue
1798		2402
1799	When C<inotify (7)> support has been compiled into libev (generally only	2403	When C<inotify (7)> support has been compiled into libev and present at
1800	available with Linux) and present at runtime, it will be used to speed up	2404	runtime, it will be used to speed up change detection where possible. The
1801	change detection where possible. The inotify descriptor will be created lazily	2405	inotify descriptor will be created lazily when the first C<ev_stat>
1802	when the first C<ev_stat> watcher is being started.	2406	watcher is being started.
1803		2407
1804	Inotify presence does not change the semantics of C<ev_stat> watchers	2408	Inotify presence does not change the semantics of C<ev_stat> watchers
1805	except that changes might be detected earlier, and in some cases, to avoid	2409	except that changes might be detected earlier, and in some cases, to avoid
1806	making regular C<stat> calls. Even in the presence of inotify support	2410	making regular C<stat> calls. Even in the presence of inotify support
1807	there are many cases where libev has to resort to regular C<stat> polling,	2411	there are many cases where libev has to resort to regular C<stat> polling,
1808	but as long as the path exists, libev usually gets away without polling.	2412	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		2413	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		2414	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		2415	xfs are fully working) libev usually gets away without polling.
1809		2416
1810	There is no support for kqueue, as apparently it cannot be used to	2417	There is no support for kqueue, as apparently it cannot be used to
1811	implement this functionality, due to the requirement of having a file	2418	implement this functionality, due to the requirement of having a file
1812	descriptor open on the object at all times, and detecting renames, unlinks	2419	descriptor open on the object at all times, and detecting renames, unlinks
1813	etc. is difficult.	2420	etc. is difficult.
1814		2421
		2422	=head3 C<stat ()> is a synchronous operation
		2423
		2424	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2425	the process. The exception are C<ev_stat> watchers - those call C<stat
		2426	()>, which is a synchronous operation.
		2427
		2428	For local paths, this usually doesn't matter: unless the system is very
		2429	busy or the intervals between stat's are large, a stat call will be fast,
		2430	as the path data is usually in memory already (except when starting the
		2431	watcher).
		2432
		2433	For networked file systems, calling C<stat ()> can block an indefinite
		2434	time due to network issues, and even under good conditions, a stat call
		2435	often takes multiple milliseconds.
		2436
		2437	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2438	paths, although this is fully supported by libev.
		2439
1815	=head3 The special problem of stat time resolution	2440	=head3 The special problem of stat time resolution
1816		2441
1817	The C<stat ()> system call only supports full-second resolution portably, and	2442	The C<stat ()> system call only supports full-second resolution portably,
1818	even on systems where the resolution is higher, most file systems still	2443	and even on systems where the resolution is higher, most file systems
1819	only support whole seconds.	2444	still only support whole seconds.
1820		2445
1821	That means that, if the time is the only thing that changes, you can	2446	That means that, if the time is the only thing that changes, you can
1822	easily miss updates: on the first update, C<ev_stat> detects a change and	2447	easily miss updates: on the first update, C<ev_stat> detects a change and
1823	calls your callback, which does something. When there is another update	2448	calls your callback, which does something. When there is another update
1824	within the same second, C<ev_stat> will be unable to detect unless the	2449	within the same second, C<ev_stat> will be unable to detect unless the
…		…
1967		2592
1968	=head3 Watcher-Specific Functions and Data Members	2593	=head3 Watcher-Specific Functions and Data Members
1969		2594
1970	=over 4	2595	=over 4
1971		2596
1972	=item ev_idle_init (ev_signal *, callback)	2597	=item ev_idle_init (ev_idle *, callback)
1973		2598
1974	Initialises and configures the idle watcher - it has no parameters of any	2599	Initialises and configures the idle watcher - it has no parameters of any
1975	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	2600	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
1976	believe me.	2601	believe me.
1977		2602
…		…
1981		2606
1982	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the	2607	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
1983	callback, free it. Also, use no error checking, as usual.	2608	callback, free it. Also, use no error checking, as usual.
1984		2609
1985	static void	2610	static void
1986	idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)	2611	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)
1987	{	2612	{
1988	free (w);	2613	free (w);
1989	// now do something you wanted to do when the program has	2614	// now do something you wanted to do when the program has
1990	// no longer anything immediate to do.	2615	// no longer anything immediate to do.
1991	}	2616	}
1992		2617
1993	struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));	2618	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
1994	ev_idle_init (idle_watcher, idle_cb);	2619	ev_idle_init (idle_watcher, idle_cb);
1995	ev_idle_start (loop, idle_cb);	2620	ev_idle_start (loop, idle_watcher);
1996		2621
1997		2622
1998	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2623	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
1999		2624
2000	Prepare and check watchers are usually (but not always) used in pairs:	2625	Prepare and check watchers are usually (but not always) used in pairs:
…		…
2079		2704
2080	static ev_io iow [nfd];	2705	static ev_io iow [nfd];
2081	static ev_timer tw;	2706	static ev_timer tw;
2082		2707
2083	static void	2708	static void
2084	io_cb (ev_loop *loop, ev_io *w, int revents)	2709	io_cb (struct ev_loop *loop, ev_io *w, int revents)
2085	{	2710	{
2086	}	2711	}
2087		2712
2088	// create io watchers for each fd and a timer before blocking	2713	// create io watchers for each fd and a timer before blocking
2089	static void	2714	static void
2090	adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)	2715	adns_prepare_cb (struct ev_loop *loop, ev_prepare *w, int revents)
2091	{	2716	{
2092	int timeout = 3600000;	2717	int timeout = 3600000;
2093	struct pollfd fds [nfd];	2718	struct pollfd fds [nfd];
2094	// actual code will need to loop here and realloc etc.	2719	// actual code will need to loop here and realloc etc.
2095	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	2720	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
2096		2721
2097	/* the callback is illegal, but won't be called as we stop during check */	2722	/* the callback is illegal, but won't be called as we stop during check */
2098	ev_timer_init (&tw, 0, timeout * 1e-3);	2723	ev_timer_init (&tw, 0, timeout * 1e-3, 0.);
2099	ev_timer_start (loop, &tw);	2724	ev_timer_start (loop, &tw);
2100		2725
2101	// create one ev_io per pollfd	2726	// create one ev_io per pollfd
2102	for (int i = 0; i < nfd; ++i)	2727	for (int i = 0; i < nfd; ++i)
2103	{	2728	{
…		…
2110	}	2735	}
2111	}	2736	}
2112		2737
2113	// stop all watchers after blocking	2738	// stop all watchers after blocking
2114	static void	2739	static void
2115	adns_check_cb (ev_loop *loop, ev_check *w, int revents)	2740	adns_check_cb (struct ev_loop *loop, ev_check *w, int revents)
2116	{	2741	{
2117	ev_timer_stop (loop, &tw);	2742	ev_timer_stop (loop, &tw);
2118		2743
2119	for (int i = 0; i < nfd; ++i)	2744	for (int i = 0; i < nfd; ++i)
2120	{	2745	{
…		…
2216	some fds have to be watched and handled very quickly (with low latency),	2841	some fds have to be watched and handled very quickly (with low latency),
2217	and even priorities and idle watchers might have too much overhead. In	2842	and even priorities and idle watchers might have too much overhead. In
2218	this case you would put all the high priority stuff in one loop and all	2843	this case you would put all the high priority stuff in one loop and all
2219	the rest in a second one, and embed the second one in the first.	2844	the rest in a second one, and embed the second one in the first.
2220		2845
2221	As long as the watcher is active, the callback will be invoked every time	2846	As long as the watcher is active, the callback will be invoked every
2222	there might be events pending in the embedded loop. The callback must then	2847	time there might be events pending in the embedded loop. The callback
2223	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke	2848	must then call C<ev_embed_sweep (mainloop, watcher)> to make a single
2224	their callbacks (you could also start an idle watcher to give the embedded	2849	sweep and invoke their callbacks (the callback doesn't need to invoke the
2225	loop strictly lower priority for example). You can also set the callback	2850	C<ev_embed_sweep> function directly, it could also start an idle watcher
2226	to C<0>, in which case the embed watcher will automatically execute the	2851	to give the embedded loop strictly lower priority for example).
2227	embedded loop sweep.
2228		2852
2229	As long as the watcher is started it will automatically handle events. The	2853	You can also set the callback to C<0>, in which case the embed watcher
2230	callback will be invoked whenever some events have been handled. You can	2854	will automatically execute the embedded loop sweep whenever necessary.
2231	set the callback to C<0> to avoid having to specify one if you are not
2232	interested in that.
2233		2855
2234	Also, there have not currently been made special provisions for forking:	2856	Fork detection will be handled transparently while the C<ev_embed> watcher
2235	when you fork, you not only have to call C<ev_loop_fork> on both loops,	2857	is active, i.e., the embedded loop will automatically be forked when the
2236	but you will also have to stop and restart any C<ev_embed> watchers	2858	embedding loop forks. In other cases, the user is responsible for calling
2237	yourself - but you can use a fork watcher to handle this automatically,	2859	C<ev_loop_fork> on the embedded loop.
2238	and future versions of libev might do just that.
2239		2860
2240	Unfortunately, not all backends are embeddable: only the ones returned by	2861	Unfortunately, not all backends are embeddable: only the ones returned by
2241	C<ev_embeddable_backends> are, which, unfortunately, does not include any	2862	C<ev_embeddable_backends> are, which, unfortunately, does not include any
2242	portable one.	2863	portable one.
2243		2864
…		…
2288	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be	2909	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be
2289	used).	2910	used).
2290		2911
2291	struct ev_loop *loop_hi = ev_default_init (0);	2912	struct ev_loop *loop_hi = ev_default_init (0);
2292	struct ev_loop *loop_lo = 0;	2913	struct ev_loop *loop_lo = 0;
2293	struct ev_embed embed;	2914	ev_embed embed;
2294		2915
2295	// see if there is a chance of getting one that works	2916	// see if there is a chance of getting one that works
2296	// (remember that a flags value of 0 means autodetection)	2917	// (remember that a flags value of 0 means autodetection)
2297	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()	2918	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
2298	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())	2919	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
…		…
2312	kqueue implementation). Store the kqueue/socket-only event loop in	2933	kqueue implementation). Store the kqueue/socket-only event loop in
2313	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).	2934	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
2314		2935
2315	struct ev_loop *loop = ev_default_init (0);	2936	struct ev_loop *loop = ev_default_init (0);
2316	struct ev_loop *loop_socket = 0;	2937	struct ev_loop *loop_socket = 0;
2317	struct ev_embed embed;	2938	ev_embed embed;
2318		2939
2319	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)	2940	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
2320	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))	2941	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
2321	{	2942	{
2322	ev_embed_init (&embed, 0, loop_socket);	2943	ev_embed_init (&embed, 0, loop_socket);
…		…
2337	event loop blocks next and before C<ev_check> watchers are being called,	2958	event loop blocks next and before C<ev_check> watchers are being called,
2338	and only in the child after the fork. If whoever good citizen calling	2959	and only in the child after the fork. If whoever good citizen calling
2339	C<ev_default_fork> cheats and calls it in the wrong process, the fork	2960	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2340	handlers will be invoked, too, of course.	2961	handlers will be invoked, too, of course.
2341		2962
		2963	=head3 The special problem of life after fork - how is it possible?
		2964
		2965	Most uses of C<fork()> consist of forking, then some simple calls to ste
		2966	up/change the process environment, followed by a call to C<exec()>. This
		2967	sequence should be handled by libev without any problems.
		2968
		2969	This changes when the application actually wants to do event handling
		2970	in the child, or both parent in child, in effect "continuing" after the
		2971	fork.
		2972
		2973	The default mode of operation (for libev, with application help to detect
		2974	forks) is to duplicate all the state in the child, as would be expected
		2975	when I<either> the parent I<or> the child process continues.
		2976
		2977	When both processes want to continue using libev, then this is usually the
		2978	wrong result. In that case, usually one process (typically the parent) is
		2979	supposed to continue with all watchers in place as before, while the other
		2980	process typically wants to start fresh, i.e. without any active watchers.
		2981
		2982	The cleanest and most efficient way to achieve that with libev is to
		2983	simply create a new event loop, which of course will be "empty", and
		2984	use that for new watchers. This has the advantage of not touching more
		2985	memory than necessary, and thus avoiding the copy-on-write, and the
		2986	disadvantage of having to use multiple event loops (which do not support
		2987	signal watchers).
		2988
		2989	When this is not possible, or you want to use the default loop for
		2990	other reasons, then in the process that wants to start "fresh", call
		2991	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying
		2992	the default loop will "orphan" (not stop) all registered watchers, so you
		2993	have to be careful not to execute code that modifies those watchers. Note
		2994	also that in that case, you have to re-register any signal watchers.
		2995
2342	=head3 Watcher-Specific Functions and Data Members	2996	=head3 Watcher-Specific Functions and Data Members
2343		2997
2344	=over 4	2998	=over 4
2345		2999
2346	=item ev_fork_init (ev_signal *, callback)	3000	=item ev_fork_init (ev_signal *, callback)
…		…
2375	=head3 Queueing	3029	=head3 Queueing
2376		3030
2377	C<ev_async> does not support queueing of data in any way. The reason	3031	C<ev_async> does not support queueing of data in any way. The reason
2378	is that the author does not know of a simple (or any) algorithm for a	3032	is that the author does not know of a simple (or any) algorithm for a
2379	multiple-writer-single-reader queue that works in all cases and doesn't	3033	multiple-writer-single-reader queue that works in all cases and doesn't
2380	need elaborate support such as pthreads.	3034	need elaborate support such as pthreads or unportable memory access
		3035	semantics.
2381		3036
2382	That means that if you want to queue data, you have to provide your own	3037	That means that if you want to queue data, you have to provide your own
2383	queue. But at least I can tell you how to implement locking around your	3038	queue. But at least I can tell you how to implement locking around your
2384	queue:	3039	queue:
2385		3040
…		…
2463	=over 4	3118	=over 4
2464		3119
2465	=item ev_async_init (ev_async *, callback)	3120	=item ev_async_init (ev_async *, callback)
2466		3121
2467	Initialises and configures the async watcher - it has no parameters of any	3122	Initialises and configures the async watcher - it has no parameters of any
2468	kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless,	3123	kind. There is a C<ev_async_set> macro, but using it is utterly pointless,
2469	trust me.	3124	trust me.
2470		3125
2471	=item ev_async_send (loop, ev_async *)	3126	=item ev_async_send (loop, ev_async *)
2472		3127
2473	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3128	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
2474	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3129	an C<EV_ASYNC> event on the watcher into the event loop. Unlike
2475	C<ev_feed_event>, this call is safe to do from other threads, signal or	3130	C<ev_feed_event>, this call is safe to do from other threads, signal or
2476	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3131	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding
2477	section below on what exactly this means).	3132	section below on what exactly this means).
2478		3133
		3134	Note that, as with other watchers in libev, multiple events might get
		3135	compressed into a single callback invocation (another way to look at this
		3136	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,
		3137	reset when the event loop detects that).
		3138
2479	This call incurs the overhead of a system call only once per loop iteration,	3139	This call incurs the overhead of a system call only once per event loop
2480	so while the overhead might be noticeable, it doesn't apply to repeated	3140	iteration, so while the overhead might be noticeable, it doesn't apply to
2481	calls to C<ev_async_send>.	3141	repeated calls to C<ev_async_send> for the same event loop.
2482		3142
2483	=item bool = ev_async_pending (ev_async *)	3143	=item bool = ev_async_pending (ev_async *)
2484		3144
2485	Returns a non-zero value when C<ev_async_send> has been called on the	3145	Returns a non-zero value when C<ev_async_send> has been called on the
2486	watcher but the event has not yet been processed (or even noted) by the	3146	watcher but the event has not yet been processed (or even noted) by the
…		…
2489	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When	3149	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When
2490	the loop iterates next and checks for the watcher to have become active,	3150	the loop iterates next and checks for the watcher to have become active,
2491	it will reset the flag again. C<ev_async_pending> can be used to very	3151	it will reset the flag again. C<ev_async_pending> can be used to very
2492	quickly check whether invoking the loop might be a good idea.	3152	quickly check whether invoking the loop might be a good idea.
2493		3153
2494	Not that this does I<not> check whether the watcher itself is pending, only	3154	Not that this does I<not> check whether the watcher itself is pending,
2495	whether it has been requested to make this watcher pending.	3155	only whether it has been requested to make this watcher pending: there
		3156	is a time window between the event loop checking and resetting the async
		3157	notification, and the callback being invoked.
2496		3158
2497	=back	3159	=back
2498		3160
2499		3161
2500	=head1 OTHER FUNCTIONS	3162	=head1 OTHER FUNCTIONS
…		…
2536	/* doh, nothing entered */;	3198	/* doh, nothing entered */;
2537	}	3199	}
2538		3200
2539	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3201	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
2540		3202
2541	=item ev_feed_event (ev_loop *, watcher *, int revents)
2542
2543	Feeds the given event set into the event loop, as if the specified event
2544	had happened for the specified watcher (which must be a pointer to an
2545	initialised but not necessarily started event watcher).
2546
2547	=item ev_feed_fd_event (ev_loop *, int fd, int revents)	3203	=item ev_feed_fd_event (loop, int fd, int revents)
2548		3204
2549	Feed an event on the given fd, as if a file descriptor backend detected	3205	Feed an event on the given fd, as if a file descriptor backend detected
2550	the given events it.	3206	the given events it.
2551		3207
2552	=item ev_feed_signal_event (ev_loop *loop, int signum)	3208	=item ev_feed_signal_event (loop, int signum)
2553		3209
2554	Feed an event as if the given signal occurred (C<loop> must be the default	3210	Feed an event as if the given signal occurred (C<loop> must be the default
2555	loop!).	3211	loop!).
2556		3212
2557	=back	3213	=back
…		…
2637		3293
2638	=over 4	3294	=over 4
2639		3295
2640	=item ev::TYPE::TYPE ()	3296	=item ev::TYPE::TYPE ()
2641		3297
2642	=item ev::TYPE::TYPE (struct ev_loop *)	3298	=item ev::TYPE::TYPE (loop)
2643		3299
2644	=item ev::TYPE::~TYPE	3300	=item ev::TYPE::~TYPE
2645		3301
2646	The constructor (optionally) takes an event loop to associate the watcher	3302	The constructor (optionally) takes an event loop to associate the watcher
2647	with. If it is omitted, it will use C<EV_DEFAULT>.	3303	with. If it is omitted, it will use C<EV_DEFAULT>.
…		…
2679		3335
2680	myclass obj;	3336	myclass obj;
2681	ev::io iow;	3337	ev::io iow;
2682	iow.set <myclass, &myclass::io_cb> (&obj);	3338	iow.set <myclass, &myclass::io_cb> (&obj);
2683		3339
		3340	=item w->set (object *)
		3341
		3342	This is an B<experimental> feature that might go away in a future version.
		3343
		3344	This is a variation of a method callback - leaving out the method to call
		3345	will default the method to C<operator ()>, which makes it possible to use
		3346	functor objects without having to manually specify the C<operator ()> all
		3347	the time. Incidentally, you can then also leave out the template argument
		3348	list.
		3349
		3350	The C<operator ()> method prototype must be C<void operator ()(watcher &w,
		3351	int revents)>.
		3352
		3353	See the method-C<set> above for more details.
		3354
		3355	Example: use a functor object as callback.
		3356
		3357	struct myfunctor
		3358	{
		3359	void operator() (ev::io &w, int revents)
		3360	{
		3361	...
		3362	}
		3363	}
		3364
		3365	myfunctor f;
		3366
		3367	ev::io w;
		3368	w.set (&f);
		3369
2684	=item w->set<function> (void *data = 0)	3370	=item w->set<function> (void *data = 0)
2685		3371
2686	Also sets a callback, but uses a static method or plain function as	3372	Also sets a callback, but uses a static method or plain function as
2687	callback. The optional C<data> argument will be stored in the watcher's	3373	callback. The optional C<data> argument will be stored in the watcher's
2688	C<data> member and is free for you to use.	3374	C<data> member and is free for you to use.
…		…
2694	Example: Use a plain function as callback.	3380	Example: Use a plain function as callback.
2695		3381
2696	static void io_cb (ev::io &w, int revents) { }	3382	static void io_cb (ev::io &w, int revents) { }
2697	iow.set <io_cb> ();	3383	iow.set <io_cb> ();
2698		3384
2699	=item w->set (struct ev_loop *)	3385	=item w->set (loop)
2700		3386
2701	Associates a different C<struct ev_loop> with this watcher. You can only	3387	Associates a different C<struct ev_loop> with this watcher. You can only
2702	do this when the watcher is inactive (and not pending either).	3388	do this when the watcher is inactive (and not pending either).
2703		3389
2704	=item w->set ([arguments])	3390	=item w->set ([arguments])
…		…
2774	L<http://software.schmorp.de/pkg/EV>.	3460	L<http://software.schmorp.de/pkg/EV>.
2775		3461
2776	=item Python	3462	=item Python
2777		3463
2778	Python bindings can be found at L<http://code.google.com/p/pyev/>. It	3464	Python bindings can be found at L<http://code.google.com/p/pyev/>. It
2779	seems to be quite complete and well-documented. Note, however, that the	3465	seems to be quite complete and well-documented.
2780	patch they require for libev is outright dangerous as it breaks the ABI
2781	for everybody else, and therefore, should never be applied in an installed
2782	libev (if python requires an incompatible ABI then it needs to embed
2783	libev).
2784		3466
2785	=item Ruby	3467	=item Ruby
2786		3468
2787	Tony Arcieri has written a ruby extension that offers access to a subset	3469	Tony Arcieri has written a ruby extension that offers access to a subset
2788	of the libev API and adds file handle abstractions, asynchronous DNS and	3470	of the libev API and adds file handle abstractions, asynchronous DNS and
2789	more on top of it. It can be found via gem servers. Its homepage is at	3471	more on top of it. It can be found via gem servers. Its homepage is at
2790	L<http://rev.rubyforge.org/>.	3472	L<http://rev.rubyforge.org/>.
2791		3473
		3474	Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190>
		3475	makes rev work even on mingw.
		3476
		3477	=item Haskell
		3478
		3479	A haskell binding to libev is available at
		3480	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.
		3481
2792	=item D	3482	=item D
2793		3483
2794	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3484	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2795	be found at L<http://proj.llucax.com.ar/wiki/evd>.	3485	be found at L<http://proj.llucax.com.ar/wiki/evd>.
		3486
		3487	=item Ocaml
		3488
		3489	Erkki Seppala has written Ocaml bindings for libev, to be found at
		3490	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
		3491
		3492	=item Lua
		3493
		3494	Brian Maher has written a partial interface to libev for lua (at the
		3495	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
		3496	L<http://github.com/brimworks/lua-ev>.
2796		3497
2797	=back	3498	=back
2798		3499
2799		3500
2800	=head1 MACRO MAGIC	3501	=head1 MACRO MAGIC
…		…
2901		3602
2902	#define EV_STANDALONE 1	3603	#define EV_STANDALONE 1
2903	#include "ev.h"	3604	#include "ev.h"
2904		3605
2905	Both header files and implementation files can be compiled with a C++	3606	Both header files and implementation files can be compiled with a C++
2906	compiler (at least, thats a stated goal, and breakage will be treated	3607	compiler (at least, that's a stated goal, and breakage will be treated
2907	as a bug).	3608	as a bug).
2908		3609
2909	You need the following files in your source tree, or in a directory	3610	You need the following files in your source tree, or in a directory
2910	in your include path (e.g. in libev/ when using -Ilibev):	3611	in your include path (e.g. in libev/ when using -Ilibev):
2911		3612
…		…
2954	libev.m4	3655	libev.m4
2955		3656
2956	=head2 PREPROCESSOR SYMBOLS/MACROS	3657	=head2 PREPROCESSOR SYMBOLS/MACROS
2957		3658
2958	Libev can be configured via a variety of preprocessor symbols you have to	3659	Libev can be configured via a variety of preprocessor symbols you have to
2959	define before including any of its files. The default in the absence of	3660	define before including (or compiling) any of its files. The default in
2960	autoconf is documented for every option.	3661	the absence of autoconf is documented for every option.
		3662
		3663	Symbols marked with "(h)" do not change the ABI, and can have different
		3664	values when compiling libev vs. including F<ev.h>, so it is permissible
		3665	to redefine them before including F<ev.h> without breakign compatibility
		3666	to a compiled library. All other symbols change the ABI, which means all
		3667	users of libev and the libev code itself must be compiled with compatible
		3668	settings.
2961		3669
2962	=over 4	3670	=over 4
2963		3671
2964	=item EV_STANDALONE	3672	=item EV_STANDALONE (h)
2965		3673
2966	Must always be C<1> if you do not use autoconf configuration, which	3674	Must always be C<1> if you do not use autoconf configuration, which
2967	keeps libev from including F<config.h>, and it also defines dummy	3675	keeps libev from including F<config.h>, and it also defines dummy
2968	implementations for some libevent functions (such as logging, which is not	3676	implementations for some libevent functions (such as logging, which is not
2969	supported). It will also not define any of the structs usually found in	3677	supported). It will also not define any of the structs usually found in
2970	F<event.h> that are not directly supported by the libev core alone.	3678	F<event.h> that are not directly supported by the libev core alone.
2971		3679
		3680	In standalone mode, libev will still try to automatically deduce the
		3681	configuration, but has to be more conservative.
		3682
2972	=item EV_USE_MONOTONIC	3683	=item EV_USE_MONOTONIC
2973		3684
2974	If defined to be C<1>, libev will try to detect the availability of the	3685	If defined to be C<1>, libev will try to detect the availability of the
2975	monotonic clock option at both compile time and runtime. Otherwise no use	3686	monotonic clock option at both compile time and runtime. Otherwise no
2976	of the monotonic clock option will be attempted. If you enable this, you	3687	use of the monotonic clock option will be attempted. If you enable this,
2977	usually have to link against librt or something similar. Enabling it when	3688	you usually have to link against librt or something similar. Enabling it
2978	the functionality isn't available is safe, though, although you have	3689	when the functionality isn't available is safe, though, although you have
2979	to make sure you link against any libraries where the C<clock_gettime>	3690	to make sure you link against any libraries where the C<clock_gettime>
2980	function is hiding in (often F<-lrt>).	3691	function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>.
2981		3692
2982	=item EV_USE_REALTIME	3693	=item EV_USE_REALTIME
2983		3694
2984	If defined to be C<1>, libev will try to detect the availability of the	3695	If defined to be C<1>, libev will try to detect the availability of the
2985	real-time clock option at compile time (and assume its availability at	3696	real-time clock option at compile time (and assume its availability
2986	runtime if successful). Otherwise no use of the real-time clock option will	3697	at runtime if successful). Otherwise no use of the real-time clock
2987	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	3698	option will be attempted. This effectively replaces C<gettimeofday>
2988	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	3699	by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect
2989	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	3700	correctness. See the note about libraries in the description of
		3701	C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of
		3702	C<EV_USE_CLOCK_SYSCALL>.
		3703
		3704	=item EV_USE_CLOCK_SYSCALL
		3705
		3706	If defined to be C<1>, libev will try to use a direct syscall instead
		3707	of calling the system-provided C<clock_gettime> function. This option
		3708	exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt>
		3709	unconditionally pulls in C<libpthread>, slowing down single-threaded
		3710	programs needlessly. Using a direct syscall is slightly slower (in
		3711	theory), because no optimised vdso implementation can be used, but avoids
		3712	the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or
		3713	higher, as it simplifies linking (no need for C<-lrt>).
2990		3714
2991	=item EV_USE_NANOSLEEP	3715	=item EV_USE_NANOSLEEP
2992		3716
2993	If defined to be C<1>, libev will assume that C<nanosleep ()> is available	3717	If defined to be C<1>, libev will assume that C<nanosleep ()> is available
2994	and will use it for delays. Otherwise it will use C<select ()>.	3718	and will use it for delays. Otherwise it will use C<select ()>.
…		…
3010		3734
3011	=item EV_SELECT_USE_FD_SET	3735	=item EV_SELECT_USE_FD_SET
3012		3736
3013	If defined to C<1>, then the select backend will use the system C<fd_set>	3737	If defined to C<1>, then the select backend will use the system C<fd_set>
3014	structure. This is useful if libev doesn't compile due to a missing	3738	structure. This is useful if libev doesn't compile due to a missing
3015	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on	3739	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout
3016	exotic systems. This usually limits the range of file descriptors to some	3740	on exotic systems. This usually limits the range of file descriptors to
3017	low limit such as 1024 or might have other limitations (winsocket only	3741	some low limit such as 1024 or might have other limitations (winsocket
3018	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	3742	only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
3019	influence the size of the C<fd_set> used.	3743	configures the maximum size of the C<fd_set>.
3020		3744
3021	=item EV_SELECT_IS_WINSOCKET	3745	=item EV_SELECT_IS_WINSOCKET
3022		3746
3023	When defined to C<1>, the select backend will assume that	3747	When defined to C<1>, the select backend will assume that
3024	select/socket/connect etc. don't understand file descriptors but	3748	select/socket/connect etc. don't understand file descriptors but
…		…
3026	be used is the winsock select). This means that it will call	3750	be used is the winsock select). This means that it will call
3027	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,	3751	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
3028	it is assumed that all these functions actually work on fds, even	3752	it is assumed that all these functions actually work on fds, even
3029	on win32. Should not be defined on non-win32 platforms.	3753	on win32. Should not be defined on non-win32 platforms.
3030		3754
3031	=item EV_FD_TO_WIN32_HANDLE	3755	=item EV_FD_TO_WIN32_HANDLE(fd)
3032		3756
3033	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map	3757	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map
3034	file descriptors to socket handles. When not defining this symbol (the	3758	file descriptors to socket handles. When not defining this symbol (the
3035	default), then libev will call C<_get_osfhandle>, which is usually	3759	default), then libev will call C<_get_osfhandle>, which is usually
3036	correct. In some cases, programs use their own file descriptor management,	3760	correct. In some cases, programs use their own file descriptor management,
3037	in which case they can provide this function to map fds to socket handles.	3761	in which case they can provide this function to map fds to socket handles.
		3762
		3763	=item EV_WIN32_HANDLE_TO_FD(handle)
		3764
		3765	If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors
		3766	using the standard C<_open_osfhandle> function. For programs implementing
		3767	their own fd to handle mapping, overwriting this function makes it easier
		3768	to do so. This can be done by defining this macro to an appropriate value.
		3769
		3770	=item EV_WIN32_CLOSE_FD(fd)
		3771
		3772	If programs implement their own fd to handle mapping on win32, then this
		3773	macro can be used to override the C<close> function, useful to unregister
		3774	file descriptors again. Note that the replacement function has to close
		3775	the underlying OS handle.
3038		3776
3039	=item EV_USE_POLL	3777	=item EV_USE_POLL
3040		3778
3041	If defined to be C<1>, libev will compile in support for the C<poll>(2)	3779	If defined to be C<1>, libev will compile in support for the C<poll>(2)
3042	backend. Otherwise it will be enabled on non-win32 platforms. It	3780	backend. Otherwise it will be enabled on non-win32 platforms. It
…		…
3089	as well as for signal and thread safety in C<ev_async> watchers.	3827	as well as for signal and thread safety in C<ev_async> watchers.
3090		3828
3091	In the absence of this define, libev will use C<sig_atomic_t volatile>	3829	In the absence of this define, libev will use C<sig_atomic_t volatile>
3092	(from F<signal.h>), which is usually good enough on most platforms.	3830	(from F<signal.h>), which is usually good enough on most platforms.
3093		3831
3094	=item EV_H	3832	=item EV_H (h)
3095		3833
3096	The name of the F<ev.h> header file used to include it. The default if	3834	The name of the F<ev.h> header file used to include it. The default if
3097	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be	3835	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
3098	used to virtually rename the F<ev.h> header file in case of conflicts.	3836	used to virtually rename the F<ev.h> header file in case of conflicts.
3099		3837
3100	=item EV_CONFIG_H	3838	=item EV_CONFIG_H (h)
3101		3839
3102	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override	3840	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
3103	F<ev.c>'s idea of where to find the F<config.h> file, similarly to	3841	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
3104	C<EV_H>, above.	3842	C<EV_H>, above.
3105		3843
3106	=item EV_EVENT_H	3844	=item EV_EVENT_H (h)
3107		3845
3108	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea	3846	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
3109	of how the F<event.h> header can be found, the default is C<"event.h">.	3847	of how the F<event.h> header can be found, the default is C<"event.h">.
3110		3848
3111	=item EV_PROTOTYPES	3849	=item EV_PROTOTYPES (h)
3112		3850
3113	If defined to be C<0>, then F<ev.h> will not define any function	3851	If defined to be C<0>, then F<ev.h> will not define any function
3114	prototypes, but still define all the structs and other symbols. This is	3852	prototypes, but still define all the structs and other symbols. This is
3115	occasionally useful if you want to provide your own wrapper functions	3853	occasionally useful if you want to provide your own wrapper functions
3116	around libev functions.	3854	around libev functions.
…		…
3138	fine.	3876	fine.
3139		3877
3140	If your embedding application does not need any priorities, defining these	3878	If your embedding application does not need any priorities, defining these
3141	both to C<0> will save some memory and CPU.	3879	both to C<0> will save some memory and CPU.
3142		3880
3143	=item EV_PERIODIC_ENABLE	3881	=item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE,
		3882	EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE,
		3883	EV_ASYNC_ENABLE, EV_CHILD_ENABLE.
3144		3884
3145	If undefined or defined to be C<1>, then periodic timers are supported. If	3885	If undefined or defined to be C<1> (and the platform supports it), then
3146	defined to be C<0>, then they are not. Disabling them saves a few kB of	3886	the respective watcher type is supported. If defined to be C<0>, then it
3147	code.	3887	is not. Disabling watcher types mainly saves codesize.
3148		3888
3149	=item EV_IDLE_ENABLE	3889	=item EV_FEATURES
3150
3151	If undefined or defined to be C<1>, then idle watchers are supported. If
3152	defined to be C<0>, then they are not. Disabling them saves a few kB of
3153	code.
3154
3155	=item EV_EMBED_ENABLE
3156
3157	If undefined or defined to be C<1>, then embed watchers are supported. If
3158	defined to be C<0>, then they are not. Embed watchers rely on most other
3159	watcher types, which therefore must not be disabled.
3160
3161	=item EV_STAT_ENABLE
3162
3163	If undefined or defined to be C<1>, then stat watchers are supported. If
3164	defined to be C<0>, then they are not.
3165
3166	=item EV_FORK_ENABLE
3167
3168	If undefined or defined to be C<1>, then fork watchers are supported. If
3169	defined to be C<0>, then they are not.
3170
3171	=item EV_ASYNC_ENABLE
3172
3173	If undefined or defined to be C<1>, then async watchers are supported. If
3174	defined to be C<0>, then they are not.
3175
3176	=item EV_MINIMAL
3177		3890
3178	If you need to shave off some kilobytes of code at the expense of some	3891	If you need to shave off some kilobytes of code at the expense of some
3179	speed, define this symbol to C<1>. Currently this is used to override some	3892	speed (but with the full API), you can define this symbol to request
3180	inlining decisions, saves roughly 30% code size on amd64. It also selects a	3893	certain subsets of functionality. The default is to enable all features
3181	much smaller 2-heap for timer management over the default 4-heap.	3894	that can be enabled on the platform.
		3895
		3896	Note that using autoconf will usually override most of the features, so
		3897	using this symbol makes sense mostly when embedding libev.
		3898
		3899	A typical way to use this symbol is to define it to C<0> (or to a bitset
		3900	with some broad features you want) and then selectively re-enable
		3901	additional parts you want, for example if you want everything minimal,
		3902	but multiple event loop support, async and child watchers and the poll
		3903	backend, use this:
		3904
		3905	#define EV_FEATURES 0
		3906	#define EV_MULTIPLICITY 1
		3907	#define EV_USE_POLL 1
		3908	#define EV_CHILD_ENABLE 1
		3909	#define EV_ASYNC_ENABLE 1
		3910
		3911	The actual value is a bitset, it can be a combination of the following
		3912	values:
		3913
		3914	=over 4
		3915
		3916	=item C<1> - faster/larger code
		3917
		3918	Use larger code to speed up some operations.
		3919
		3920	Currently this is used to override some inlining decisions (enlarging the roughly
		3921	30% code size on amd64.
		3922
		3923	When optimising for size, use of compiler flags such as C<-Os> with
		3924	gcc recommended, as well as C<-DNDEBUG>, as libev contains a number of
		3925	assertions.
		3926
		3927	=item C<2> - faster/larger data structures
		3928
		3929	Replaces the small 2-heap for timer management by a faster 4-heap, larger
		3930	hash table sizes and so on. This will usually further increase codesize
		3931	and can additionally have an effect on the size of data structures at
		3932	runtime.
		3933
		3934	=item C<4> - full API configuration
		3935
		3936	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
		3937	enables multiplicity (C<EV_MULTIPLICITY>=1).
		3938
		3939	It also enables a lot of the "lesser used" core API functions. See C<ev.h>
		3940	for details on which parts of the API are still available without this
		3941	feature, and do not complain if this subset changes over time.
		3942
		3943	=item C<8> - enable all optional watcher types
		3944
		3945	Enables all optional watcher types. If you want to selectively enable
		3946	only some watcher types other than I/O and timers (e.g. prepare,
		3947	embed, async, child...) you can enable them manually by defining
		3948	C<EV_watchertype_ENABLE> to C<1> instead.
		3949
		3950	=item C<16> - enable all backends
		3951
		3952	This enables all backends - without this feature, you need to enable at
		3953	least one backend manually (C<EV_USE_SELECT> is a good choice).
		3954
		3955	=item C<32> - enable OS-specific "helper" APIs
		3956
		3957	Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by
		3958	default.
		3959
		3960	=back
		3961
		3962	Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0>
		3963	reduces the compiled size of libev from 24.7Kb to 6.5Kb on my GNU/Linux
		3964	amd64 system, while still giving you I/O watchers, timers and monotonic
		3965	clock support.
		3966
		3967	With an intelligent-enough linker (gcc+binutils are intelligent enough
		3968	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
		3969	your program might be left out as well - a binary starting a timer and an
		3970	I/O watcher then might come out at only 5Kb.
		3971
		3972	=item EV_AVOID_STDIO
		3973
		3974	If this is set to C<1> at compiletime, then libev will avoid using stdio
		3975	functions (printf, scanf, perror etc.). This will increase the codesize
		3976	somewhat, but if your program doesn't otherwise depend on stdio and your
		3977	libc allows it, this avoids linking in the stdio library which is quite
		3978	big.
		3979
		3980	Note that error messages might become less precise when this option is
		3981	enabled.
		3982
		3983	=item EV_NSIG
		3984
		3985	The highest supported signal number, +1 (or, the number of
		3986	signals): Normally, libev tries to deduce the maximum number of signals
		3987	automatically, but sometimes this fails, in which case it can be
		3988	specified. Also, using a lower number than detected (C<32> should be
		3989	good for about any system in existance) can save some memory, as libev
		3990	statically allocates some 12-24 bytes per signal number.
3182		3991
3183	=item EV_PID_HASHSIZE	3992	=item EV_PID_HASHSIZE
3184		3993
3185	C<ev_child> watchers use a small hash table to distribute workload by	3994	C<ev_child> watchers use a small hash table to distribute workload by
3186	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	3995	pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled),
3187	than enough. If you need to manage thousands of children you might want to	3996	usually more than enough. If you need to manage thousands of children you
3188	increase this value (I<must> be a power of two).	3997	might want to increase this value (I<must> be a power of two).
3189		3998
3190	=item EV_INOTIFY_HASHSIZE	3999	=item EV_INOTIFY_HASHSIZE
3191		4000
3192	C<ev_stat> watchers use a small hash table to distribute workload by	4001	C<ev_stat> watchers use a small hash table to distribute workload by
3193	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	4002	inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES>
3194	usually more than enough. If you need to manage thousands of C<ev_stat>	4003	disabled), usually more than enough. If you need to manage thousands of
3195	watchers you might want to increase this value (I<must> be a power of	4004	C<ev_stat> watchers you might want to increase this value (I<must> be a
3196	two).	4005	power of two).
3197		4006
3198	=item EV_USE_4HEAP	4007	=item EV_USE_4HEAP
3199		4008
3200	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4009	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3201	timer and periodics heaps, libev uses a 4-heap when this symbol is defined	4010	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
3202	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably	4011	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
3203	faster performance with many (thousands) of watchers.	4012	faster performance with many (thousands) of watchers.
3204		4013
3205	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4014	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3206	(disabled).	4015	will be C<0>.
3207		4016
3208	=item EV_HEAP_CACHE_AT	4017	=item EV_HEAP_CACHE_AT
3209		4018
3210	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4019	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3211	timer and periodics heaps, libev can cache the timestamp (I<at>) within	4020	timer and periodics heaps, libev can cache the timestamp (I<at>) within
3212	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),	4021	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
3213	which uses 8-12 bytes more per watcher and a few hundred bytes more code,	4022	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
3214	but avoids random read accesses on heap changes. This improves performance	4023	but avoids random read accesses on heap changes. This improves performance
3215	noticeably with many (hundreds) of watchers.	4024	noticeably with many (hundreds) of watchers.
3216		4025
3217	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4026	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3218	(disabled).	4027	will be C<0>.
3219		4028
3220	=item EV_VERIFY	4029	=item EV_VERIFY
3221		4030
3222	Controls how much internal verification (see C<ev_loop_verify ()>) will	4031	Controls how much internal verification (see C<ev_loop_verify ()>) will
3223	be done: If set to C<0>, no internal verification code will be compiled	4032	be done: If set to C<0>, no internal verification code will be compiled
…		…
3225	called. If set to C<2>, then the internal verification code will be	4034	called. If set to C<2>, then the internal verification code will be
3226	called once per loop, which can slow down libev. If set to C<3>, then the	4035	called once per loop, which can slow down libev. If set to C<3>, then the
3227	verification code will be called very frequently, which will slow down	4036	verification code will be called very frequently, which will slow down
3228	libev considerably.	4037	libev considerably.
3229		4038
3230	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be	4039	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3231	C<0>.	4040	will be C<0>.
3232		4041
3233	=item EV_COMMON	4042	=item EV_COMMON
3234		4043
3235	By default, all watchers have a C<void *data> member. By redefining	4044	By default, all watchers have a C<void *data> member. By redefining
3236	this macro to a something else you can include more and other types of	4045	this macro to a something else you can include more and other types of
…		…
3294	file.	4103	file.
3295		4104
3296	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	4105	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
3297	that everybody includes and which overrides some configure choices:	4106	that everybody includes and which overrides some configure choices:
3298		4107
3299	#define EV_MINIMAL 1	4108	#define EV_FEATURES 0
3300	#define EV_USE_POLL 0	4109	#define EV_USE_SELECT 1
3301	#define EV_MULTIPLICITY 0
3302	#define EV_PERIODIC_ENABLE 0
3303	#define EV_STAT_ENABLE 0
3304	#define EV_FORK_ENABLE 0
3305	#define EV_CONFIG_H <config.h>	4110	#define EV_CONFIG_H <config.h>
3306	#define EV_MINPRI 0
3307	#define EV_MAXPRI 0
3308		4111
3309	#include "ev++.h"	4112	#include "ev++.h"
3310		4113
3311	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4114	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
3312		4115
…		…
3372	default loop and triggering an C<ev_async> watcher from the default loop	4175	default loop and triggering an C<ev_async> watcher from the default loop
3373	watcher callback into the event loop interested in the signal.	4176	watcher callback into the event loop interested in the signal.
3374		4177
3375	=back	4178	=back
3376		4179
		4180	=head4 THREAD LOCKING EXAMPLE
		4181
		4182	Here is a fictitious example of how to run an event loop in a different
		4183	thread than where callbacks are being invoked and watchers are
		4184	created/added/removed.
		4185
		4186	For a real-world example, see the C<EV::Loop::Async> perl module,
		4187	which uses exactly this technique (which is suited for many high-level
		4188	languages).
		4189
		4190	The example uses a pthread mutex to protect the loop data, a condition
		4191	variable to wait for callback invocations, an async watcher to notify the
		4192	event loop thread and an unspecified mechanism to wake up the main thread.
		4193
		4194	First, you need to associate some data with the event loop:
		4195
		4196	typedef struct {
		4197	mutex_t lock; /* global loop lock */
		4198	ev_async async_w;
		4199	thread_t tid;
		4200	cond_t invoke_cv;
		4201	} userdata;
		4202
		4203	void prepare_loop (EV_P)
		4204	{
		4205	// for simplicity, we use a static userdata struct.
		4206	static userdata u;
		4207
		4208	ev_async_init (&u->async_w, async_cb);
		4209	ev_async_start (EV_A_ &u->async_w);
		4210
		4211	pthread_mutex_init (&u->lock, 0);
		4212	pthread_cond_init (&u->invoke_cv, 0);
		4213
		4214	// now associate this with the loop
		4215	ev_set_userdata (EV_A_ u);
		4216	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		4217	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		4218
		4219	// then create the thread running ev_loop
		4220	pthread_create (&u->tid, 0, l_run, EV_A);
		4221	}
		4222
		4223	The callback for the C<ev_async> watcher does nothing: the watcher is used
		4224	solely to wake up the event loop so it takes notice of any new watchers
		4225	that might have been added:
		4226
		4227	static void
		4228	async_cb (EV_P_ ev_async *w, int revents)
		4229	{
		4230	// just used for the side effects
		4231	}
		4232
		4233	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		4234	protecting the loop data, respectively.
		4235
		4236	static void
		4237	l_release (EV_P)
		4238	{
		4239	userdata *u = ev_userdata (EV_A);
		4240	pthread_mutex_unlock (&u->lock);
		4241	}
		4242
		4243	static void
		4244	l_acquire (EV_P)
		4245	{
		4246	userdata *u = ev_userdata (EV_A);
		4247	pthread_mutex_lock (&u->lock);
		4248	}
		4249
		4250	The event loop thread first acquires the mutex, and then jumps straight
		4251	into C<ev_loop>:
		4252
		4253	void *
		4254	l_run (void *thr_arg)
		4255	{
		4256	struct ev_loop *loop = (struct ev_loop *)thr_arg;
		4257
		4258	l_acquire (EV_A);
		4259	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		4260	ev_loop (EV_A_ 0);
		4261	l_release (EV_A);
		4262
		4263	return 0;
		4264	}
		4265
		4266	Instead of invoking all pending watchers, the C<l_invoke> callback will
		4267	signal the main thread via some unspecified mechanism (signals? pipe
		4268	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		4269	have been called (in a while loop because a) spurious wakeups are possible
		4270	and b) skipping inter-thread-communication when there are no pending
		4271	watchers is very beneficial):
		4272
		4273	static void
		4274	l_invoke (EV_P)
		4275	{
		4276	userdata *u = ev_userdata (EV_A);
		4277
		4278	while (ev_pending_count (EV_A))
		4279	{
		4280	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		4281	pthread_cond_wait (&u->invoke_cv, &u->lock);
		4282	}
		4283	}
		4284
		4285	Now, whenever the main thread gets told to invoke pending watchers, it
		4286	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		4287	thread to continue:
		4288
		4289	static void
		4290	real_invoke_pending (EV_P)
		4291	{
		4292	userdata *u = ev_userdata (EV_A);
		4293
		4294	pthread_mutex_lock (&u->lock);
		4295	ev_invoke_pending (EV_A);
		4296	pthread_cond_signal (&u->invoke_cv);
		4297	pthread_mutex_unlock (&u->lock);
		4298	}
		4299
		4300	Whenever you want to start/stop a watcher or do other modifications to an
		4301	event loop, you will now have to lock:
		4302
		4303	ev_timer timeout_watcher;
		4304	userdata *u = ev_userdata (EV_A);
		4305
		4306	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		4307
		4308	pthread_mutex_lock (&u->lock);
		4309	ev_timer_start (EV_A_ &timeout_watcher);
		4310	ev_async_send (EV_A_ &u->async_w);
		4311	pthread_mutex_unlock (&u->lock);
		4312
		4313	Note that sending the C<ev_async> watcher is required because otherwise
		4314	an event loop currently blocking in the kernel will have no knowledge
		4315	about the newly added timer. By waking up the loop it will pick up any new
		4316	watchers in the next event loop iteration.
		4317
3377	=head3 COROUTINES	4318	=head3 COROUTINES
3378		4319
3379	Libev is very accommodating to coroutines ("cooperative threads"):	4320	Libev is very accommodating to coroutines ("cooperative threads"):
3380	libev fully supports nesting calls to its functions from different	4321	libev fully supports nesting calls to its functions from different
3381	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4322	coroutines (e.g. you can call C<ev_loop> on the same loop from two
3382	different coroutines, and switch freely between both coroutines running the	4323	different coroutines, and switch freely between both coroutines running
3383	loop, as long as you don't confuse yourself). The only exception is that	4324	the loop, as long as you don't confuse yourself). The only exception is
3384	you must not do this from C<ev_periodic> reschedule callbacks.	4325	that you must not do this from C<ev_periodic> reschedule callbacks.
3385		4326
3386	Care has been taken to ensure that libev does not keep local state inside	4327	Care has been taken to ensure that libev does not keep local state inside
3387	C<ev_loop>, and other calls do not usually allow for coroutine switches as	4328	C<ev_loop>, and other calls do not usually allow for coroutine switches as
3388	they do not clal any callbacks.	4329	they do not call any callbacks.
3389		4330
3390	=head2 COMPILER WARNINGS	4331	=head2 COMPILER WARNINGS
3391		4332
3392	Depending on your compiler and compiler settings, you might get no or a	4333	Depending on your compiler and compiler settings, you might get no or a
3393	lot of warnings when compiling libev code. Some people are apparently	4334	lot of warnings when compiling libev code. Some people are apparently
…		…
3427	==2274== definitely lost: 0 bytes in 0 blocks.	4368	==2274== definitely lost: 0 bytes in 0 blocks.
3428	==2274== possibly lost: 0 bytes in 0 blocks.	4369	==2274== possibly lost: 0 bytes in 0 blocks.
3429	==2274== still reachable: 256 bytes in 1 blocks.	4370	==2274== still reachable: 256 bytes in 1 blocks.
3430		4371
3431	Then there is no memory leak, just as memory accounted to global variables	4372	Then there is no memory leak, just as memory accounted to global variables
3432	is not a memleak - the memory is still being refernced, and didn't leak.	4373	is not a memleak - the memory is still being referenced, and didn't leak.
3433		4374
3434	Similarly, under some circumstances, valgrind might report kernel bugs	4375	Similarly, under some circumstances, valgrind might report kernel bugs
3435	as if it were a bug in libev (e.g. in realloc or in the poll backend,	4376	as if it were a bug in libev (e.g. in realloc or in the poll backend,
3436	although an acceptable workaround has been found here), or it might be	4377	although an acceptable workaround has been found here), or it might be
3437	confused.	4378	confused.
…		…
3466	way (note also that glib is the slowest event library known to man).	4407	way (note also that glib is the slowest event library known to man).
3467		4408
3468	There is no supported compilation method available on windows except	4409	There is no supported compilation method available on windows except
3469	embedding it into other applications.	4410	embedding it into other applications.
3470		4411
		4412	Sensible signal handling is officially unsupported by Microsoft - libev
		4413	tries its best, but under most conditions, signals will simply not work.
		4414
3471	Not a libev limitation but worth mentioning: windows apparently doesn't	4415	Not a libev limitation but worth mentioning: windows apparently doesn't
3472	accept large writes: instead of resulting in a partial write, windows will	4416	accept large writes: instead of resulting in a partial write, windows will
3473	either accept everything or return C<ENOBUFS> if the buffer is too large,	4417	either accept everything or return C<ENOBUFS> if the buffer is too large,
3474	so make sure you only write small amounts into your sockets (less than a	4418	so make sure you only write small amounts into your sockets (less than a
3475	megabyte seems safe, but this apparently depends on the amount of memory	4419	megabyte seems safe, but this apparently depends on the amount of memory
…		…
3479	the abysmal performance of winsockets, using a large number of sockets	4423	the abysmal performance of winsockets, using a large number of sockets
3480	is not recommended (and not reasonable). If your program needs to use	4424	is not recommended (and not reasonable). If your program needs to use
3481	more than a hundred or so sockets, then likely it needs to use a totally	4425	more than a hundred or so sockets, then likely it needs to use a totally
3482	different implementation for windows, as libev offers the POSIX readiness	4426	different implementation for windows, as libev offers the POSIX readiness
3483	notification model, which cannot be implemented efficiently on windows	4427	notification model, which cannot be implemented efficiently on windows
3484	(Microsoft monopoly games).	4428	(due to Microsoft monopoly games).
3485		4429
3486	A typical way to use libev under windows is to embed it (see the embedding	4430	A typical way to use libev under windows is to embed it (see the embedding
3487	section for details) and use the following F<evwrap.h> header file instead	4431	section for details) and use the following F<evwrap.h> header file instead
3488	of F<ev.h>:	4432	of F<ev.h>:
3489		4433
…		…
3525		4469
3526	Early versions of winsocket's select only supported waiting for a maximum	4470	Early versions of winsocket's select only supported waiting for a maximum
3527	of C<64> handles (probably owning to the fact that all windows kernels	4471	of C<64> handles (probably owning to the fact that all windows kernels
3528	can only wait for C<64> things at the same time internally; Microsoft	4472	can only wait for C<64> things at the same time internally; Microsoft
3529	recommends spawning a chain of threads and wait for 63 handles and the	4473	recommends spawning a chain of threads and wait for 63 handles and the
3530	previous thread in each. Great).	4474	previous thread in each. Sounds great!).
3531		4475
3532	Newer versions support more handles, but you need to define C<FD_SETSIZE>	4476	Newer versions support more handles, but you need to define C<FD_SETSIZE>
3533	to some high number (e.g. C<2048>) before compiling the winsocket select	4477	to some high number (e.g. C<2048>) before compiling the winsocket select
3534	call (which might be in libev or elsewhere, for example, perl does its own	4478	call (which might be in libev or elsewhere, for example, perl and many
3535	select emulation on windows).	4479	other interpreters do their own select emulation on windows).
3536		4480
3537	Another limit is the number of file descriptors in the Microsoft runtime	4481	Another limit is the number of file descriptors in the Microsoft runtime
3538	libraries, which by default is C<64> (there must be a hidden I<64> fetish	4482	libraries, which by default is C<64> (there must be a hidden I<64>
3539	or something like this inside Microsoft). You can increase this by calling	4483	fetish or something like this inside Microsoft). You can increase this
3540	C<_setmaxstdio>, which can increase this limit to C<2048> (another	4484	by calling C<_setmaxstdio>, which can increase this limit to C<2048>
3541	arbitrary limit), but is broken in many versions of the Microsoft runtime	4485	(another arbitrary limit), but is broken in many versions of the Microsoft
3542	libraries.
3543
3544	This might get you to about C<512> or C<2048> sockets (depending on	4486	runtime libraries. This might get you to about C<512> or C<2048> sockets
3545	windows version and/or the phase of the moon). To get more, you need to	4487	(depending on windows version and/or the phase of the moon). To get more,
3546	wrap all I/O functions and provide your own fd management, but the cost of	4488	you need to wrap all I/O functions and provide your own fd management, but
3547	calling select (O(n²)) will likely make this unworkable.	4489	the cost of calling select (O(n²)) will likely make this unworkable.
3548		4490
3549	=back	4491	=back
3550		4492
3551	=head2 PORTABILITY REQUIREMENTS	4493	=head2 PORTABILITY REQUIREMENTS
3552		4494
…		…
3595	=item C<double> must hold a time value in seconds with enough accuracy	4537	=item C<double> must hold a time value in seconds with enough accuracy
3596		4538
3597	The type C<double> is used to represent timestamps. It is required to	4539	The type C<double> is used to represent timestamps. It is required to
3598	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	4540	have at least 51 bits of mantissa (and 9 bits of exponent), which is good
3599	enough for at least into the year 4000. This requirement is fulfilled by	4541	enough for at least into the year 4000. This requirement is fulfilled by
3600	implementations implementing IEEE 754 (basically all existing ones).	4542	implementations implementing IEEE 754, which is basically all existing
		4543	ones. With IEEE 754 doubles, you get microsecond accuracy until at least
		4544	2200.
3601		4545
3602	=back	4546	=back
3603		4547
3604	If you know of other additional requirements drop me a note.	4548	If you know of other additional requirements drop me a note.
3605		4549
…		…
3673	involves iterating over all running async watchers or all signal numbers.	4617	involves iterating over all running async watchers or all signal numbers.
3674		4618
3675	=back	4619	=back
3676		4620
3677		4621
		4622	=head1 GLOSSARY
		4623
		4624	=over 4
		4625
		4626	=item active
		4627
		4628	A watcher is active as long as it has been started (has been attached to
		4629	an event loop) but not yet stopped (disassociated from the event loop).
		4630
		4631	=item application
		4632
		4633	In this document, an application is whatever is using libev.
		4634
		4635	=item callback
		4636
		4637	The address of a function that is called when some event has been
		4638	detected. Callbacks are being passed the event loop, the watcher that
		4639	received the event, and the actual event bitset.
		4640
		4641	=item callback invocation
		4642
		4643	The act of calling the callback associated with a watcher.
		4644
		4645	=item event
		4646
		4647	A change of state of some external event, such as data now being available
		4648	for reading on a file descriptor, time having passed or simply not having
		4649	any other events happening anymore.
		4650
		4651	In libev, events are represented as single bits (such as C<EV_READ> or
		4652	C<EV_TIMEOUT>).
		4653
		4654	=item event library
		4655
		4656	A software package implementing an event model and loop.
		4657
		4658	=item event loop
		4659
		4660	An entity that handles and processes external events and converts them
		4661	into callback invocations.
		4662
		4663	=item event model
		4664
		4665	The model used to describe how an event loop handles and processes
		4666	watchers and events.
		4667
		4668	=item pending
		4669
		4670	A watcher is pending as soon as the corresponding event has been detected,
		4671	and stops being pending as soon as the watcher will be invoked or its
		4672	pending status is explicitly cleared by the application.
		4673
		4674	A watcher can be pending, but not active. Stopping a watcher also clears
		4675	its pending status.
		4676
		4677	=item real time
		4678
		4679	The physical time that is observed. It is apparently strictly monotonic :)
		4680
		4681	=item wall-clock time
		4682
		4683	The time and date as shown on clocks. Unlike real time, it can actually
		4684	be wrong and jump forwards and backwards, e.g. when the you adjust your
		4685	clock.
		4686
		4687	=item watcher
		4688
		4689	A data structure that describes interest in certain events. Watchers need
		4690	to be started (attached to an event loop) before they can receive events.
		4691
		4692	=item watcher invocation
		4693
		4694	The act of calling the callback associated with a watcher.
		4695
		4696	=back
		4697
3678	=head1 AUTHOR	4698	=head1 AUTHOR
3679		4699
3680	Marc Lehmann <libev@schmorp.de>.	4700	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.
3681		4701

Diff Legend

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