ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.209 by root, Wed Oct 29 14:12:34 2008 UTC vs.
Revision 1.366 by sf-exg, Thu Feb 3 16:21:08 2011 UTC

…		…
8		8
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
		14	#include <stdio.h> // for puts
13		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;
…		…
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);
28		30
29	// this causes all nested ev_loop's to stop iterating	31	// this causes all nested ev_run's to stop iterating
30	ev_unloop (EV_A_ EVUNLOOP_ALL);	32	ev_break (EV_A_ EVBREAK_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_ 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_run to stop iterating
39	ev_unloop (EV_A_ EVUNLOOP_ONE);	41	ev_break (EV_A_ EVBREAK_ONE);
40	}	42	}
41		43
42	int	44	int
43	main (void)	45	main (void)
44	{	46	{
45	// use the default event loop unless you have special needs	47	// use the default event loop unless you have special needs
46	ev_loop *loop = ev_default_loop (0);	48	struct ev_loop *loop = EV_DEFAULT;
47		49
48	// initialise an io watcher, then start it	50	// initialise an io watcher, then start it
49	// this one will watch for stdin to become readable	51	// this one will watch for stdin to become readable
50	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);	52	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
51	ev_io_start (loop, &stdin_watcher);	53	ev_io_start (loop, &stdin_watcher);
…		…
54	// simple non-repeating 5.5 second timeout	56	// simple non-repeating 5.5 second timeout
55	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);	57	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
56	ev_timer_start (loop, &timeout_watcher);	58	ev_timer_start (loop, &timeout_watcher);
57		59
58	// now wait for events to arrive	60	// now wait for events to arrive
59	ev_loop (loop, 0);	61	ev_run (loop, 0);
60		62
61	// unloop was called, so exit	63	// break 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	Familiarity with event based programming techniques in general is assumed
		81	throughout this document.
		82
		83	=head1 WHAT TO READ WHEN IN A HURRY
		84
		85	This manual tries to be very detailed, but unfortunately, this also makes
		86	it very long. If you just want to know the basics of libev, I suggest
		87	reading L<ANATOMY OF A WATCHER>, then the L<EXAMPLE PROGRAM> above and
		88	look up the missing functions in L<GLOBAL FUNCTIONS> and the C<ev_io> and
		89	C<ev_timer> sections in L<WATCHER TYPES>.
		90
		91	=head1 ABOUT LIBEV
70		92
71	Libev is an event loop: you register interest in certain events (such as a	93	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	94	file descriptor being readable or a timeout occurring), and it will manage
73	these event sources and provide your program with events.	95	these event sources and provide your program with events.
74		96
…		…
84	=head2 FEATURES	106	=head2 FEATURES
85		107
86	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the	108	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
87	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms	109	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
88	for file descriptor events (C<ev_io>), the Linux C<inotify> interface	110	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
89	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers	111	(for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner
90	with customised rescheduling (C<ev_periodic>), synchronous signals	112	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	113	timers (C<ev_timer>), absolute timers with customised rescheduling
92	watchers dealing with the event loop mechanism itself (C<ev_idle>,	114	(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	115	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	116	loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and
95	(C<ev_fork>).	117	C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even
		118	limited support for fork events (C<ev_fork>).
96		119
97	It also is quite fast (see this	120	It also is quite fast (see this
98	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent	121	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent
99	for example).	122	for example).
100		123
…		…
103	Libev is very configurable. In this manual the default (and most common)	126	Libev is very configurable. In this manual the default (and most common)
104	configuration will be described, which supports multiple event loops. For	127	configuration will be described, which supports multiple event loops. For
105	more info about various configuration options please have a look at	128	more info about various configuration options please have a look at
106	B<EMBED> section in this manual. If libev was configured without support	129	B<EMBED> section in this manual. If libev was configured without support
107	for multiple event loops, then all functions taking an initial argument of	130	for multiple event loops, then all functions taking an initial argument of
108	name C<loop> (which is always of type C<ev_loop *>) will not have	131	name C<loop> (which is always of type C<struct ev_loop *>) will not have
109	this argument.	132	this argument.
110		133
111	=head2 TIME REPRESENTATION	134	=head2 TIME REPRESENTATION
112		135
113	Libev represents time as a single floating point number, representing the	136	Libev represents time as a single floating point number, representing
114	(fractional) number of seconds since the (POSIX) epoch (somewhere near	137	the (fractional) number of seconds since the (POSIX) epoch (in practice
115	the beginning of 1970, details are complicated, don't ask). This type is	138	somewhere near the beginning of 1970, details are complicated, don't
116	called C<ev_tstamp>, which is what you should use too. It usually aliases	139	ask). This type is called C<ev_tstamp>, which is what you should use
117	to the C<double> type in C, and when you need to do any calculations on	140	too. It usually aliases to the C<double> type in C. When you need to do
118	it, you should treat it as some floating point value. Unlike the name	141	any calculations on it, you should treat it as some floating point value.
		142
119	component C<stamp> might indicate, it is also used for time differences	143	Unlike the name component C<stamp> might indicate, it is also used for
120	throughout libev.	144	time differences (e.g. delays) throughout libev.
121		145
122	=head1 ERROR HANDLING	146	=head1 ERROR HANDLING
123		147
124	Libev knows three classes of errors: operating system errors, usage errors	148	Libev knows three classes of errors: operating system errors, usage errors
125	and internal errors (bugs).	149	and internal errors (bugs).
…		…
149		173
150	=item ev_tstamp ev_time ()	174	=item ev_tstamp ev_time ()
151		175
152	Returns the current time as libev would use it. Please note that the	176	Returns the current time as libev would use it. Please note that the
153	C<ev_now> function is usually faster and also often returns the timestamp	177	C<ev_now> function is usually faster and also often returns the timestamp
154	you actually want to know.	178	you actually want to know. Also interesting is the combination of
		179	C<ev_update_now> and C<ev_now>.
155		180
156	=item ev_sleep (ev_tstamp interval)	181	=item ev_sleep (ev_tstamp interval)
157		182
158	Sleep for the given interval: The current thread will be blocked until	183	Sleep for the given interval: The current thread will be blocked until
159	either it is interrupted or the given time interval has passed. Basically	184	either it is interrupted or the given time interval has passed. Basically
…		…
176	as this indicates an incompatible change. Minor versions are usually	201	as this indicates an incompatible change. Minor versions are usually
177	compatible to older versions, so a larger minor version alone is usually	202	compatible to older versions, so a larger minor version alone is usually
178	not a problem.	203	not a problem.
179		204
180	Example: Make sure we haven't accidentally been linked against the wrong	205	Example: Make sure we haven't accidentally been linked against the wrong
181	version.	206	version (note, however, that this will not detect other ABI mismatches,
		207	such as LFS or reentrancy).
182		208
183	assert (("libev version mismatch",	209	assert (("libev version mismatch",
184	ev_version_major () == EV_VERSION_MAJOR	210	ev_version_major () == EV_VERSION_MAJOR
185	&& ev_version_minor () >= EV_VERSION_MINOR));	211	&& ev_version_minor () >= EV_VERSION_MINOR));
186		212
…		…
197	assert (("sorry, no epoll, no sex",	223	assert (("sorry, no epoll, no sex",
198	ev_supported_backends () & EVBACKEND_EPOLL));	224	ev_supported_backends () & EVBACKEND_EPOLL));
199		225
200	=item unsigned int ev_recommended_backends ()	226	=item unsigned int ev_recommended_backends ()
201		227
202	Return the set of all backends compiled into this binary of libev and also	228	Return the set of all backends compiled into this binary of libev and
203	recommended for this platform. This set is often smaller than the one	229	also recommended for this platform, meaning it will work for most file
		230	descriptor types. This set is often smaller than the one returned by
204	returned by C<ev_supported_backends>, as for example kqueue is broken on	231	C<ev_supported_backends>, as for example kqueue is broken on most BSDs
205	most BSDs and will not be auto-detected unless you explicitly request it	232	and will not be auto-detected unless you explicitly request it (assuming
206	(assuming you know what you are doing). This is the set of backends that	233	you know what you are doing). This is the set of backends that libev will
207	libev will probe for if you specify no backends explicitly.	234	probe for if you specify no backends explicitly.
208		235
209	=item unsigned int ev_embeddable_backends ()	236	=item unsigned int ev_embeddable_backends ()
210		237
211	Returns the set of backends that are embeddable in other event loops. This	238	Returns the set of backends that are embeddable in other event loops. This
212	is the theoretical, all-platform, value. To find which backends	239	value is platform-specific but can include backends not available on the
213	might be supported on the current system, you would need to look at	240	current system. To find which embeddable backends might be supported on
214	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	241	the current system, you would need to look at C<ev_embeddable_backends ()
215	recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
216		243
217	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
218		245
219	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]	246	=item ev_set_allocator (void *(*cb)(void *ptr, long size))
220		247
221	Sets the allocation function to use (the prototype is similar - the	248	Sets the allocation function to use (the prototype is similar - the
222	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is	249	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is
223	used to allocate and free memory (no surprises here). If it returns zero	250	used to allocate and free memory (no surprises here). If it returns zero
224	when memory needs to be allocated (C<size != 0>), the library might abort	251	when memory needs to be allocated (C<size != 0>), the library might abort
…		…
250	}	277	}
251		278
252	...	279	...
253	ev_set_allocator (persistent_realloc);	280	ev_set_allocator (persistent_realloc);
254		281
255	=item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]	282	=item ev_set_syserr_cb (void (*cb)(const char *msg))
256		283
257	Set the callback function to call on a retryable system call error (such	284	Set the callback function to call on a retryable system call error (such
258	as failed select, poll, epoll_wait). The message is a printable string	285	as failed select, poll, epoll_wait). The message is a printable string
259	indicating the system call or subsystem causing the problem. If this	286	indicating the system call or subsystem causing the problem. If this
260	callback is set, then libev will expect it to remedy the situation, no	287	callback is set, then libev will expect it to remedy the situation, no
…		…
272	}	299	}
273		300
274	...	301	...
275	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
276		303
		304	=item ev_feed_signal (int signum)
		305
		306	This function can be used to "simulate" a signal receive. It is completely
		307	safe to call this function at any time, from any context, including signal
		308	handlers or random threads.
		309
		310	Its main use is to customise signal handling in your process, especially
		311	in the presence of threads. For example, you could block signals
		312	by default in all threads (and specifying C<EVFLAG_NOSIGMASK> when
		313	creating any loops), and in one thread, use C<sigwait> or any other
		314	mechanism to wait for signals, then "deliver" them to libev by calling
		315	C<ev_feed_signal>.
		316
277	=back	317	=back
278		318
279	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	319	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
280		320
281	An event loop is described by a C<struct ev_loop *> (the C<struct>	321	An event loop is described by a C<struct ev_loop *> (the C<struct> is
282	is I<not> optional in this case, as there is also an C<ev_loop>	322	I<not> optional in this case unless libev 3 compatibility is disabled, as
283	I<function>).	323	libev 3 had an C<ev_loop> function colliding with the struct name).
284		324
285	The library knows two types of such loops, the I<default> loop, which	325	The library knows two types of such loops, the I<default> loop, which
286	supports signals and child events, and dynamically created loops which do	326	supports child process events, and dynamically created event loops which
287	not.	327	do not.
288		328
289	=over 4	329	=over 4
290		330
291	=item struct ev_loop *ev_default_loop (unsigned int flags)	331	=item struct ev_loop *ev_default_loop (unsigned int flags)
292		332
293	This will initialise the default event loop if it hasn't been initialised	333	This returns the "default" event loop object, which is what you should
294	yet and return it. If the default loop could not be initialised, returns	334	normally use when you just need "the event loop". Event loop objects and
295	false. If it already was initialised it simply returns it (and ignores the	335	the C<flags> parameter are described in more detail in the entry for
296	flags. If that is troubling you, check C<ev_backend ()> afterwards).	336	C<ev_loop_new>.
		337
		338	If the default loop is already initialised then this function simply
		339	returns it (and ignores the flags. If that is troubling you, check
		340	C<ev_backend ()> afterwards). Otherwise it will create it with the given
		341	flags, which should almost always be C<0>, unless the caller is also the
		342	one calling C<ev_run> or otherwise qualifies as "the main program".
297		343
298	If you don't know what event loop to use, use the one returned from this	344	If you don't know what event loop to use, use the one returned from this
299	function.	345	function (or via the C<EV_DEFAULT> macro).
300		346
301	Note that this function is I<not> thread-safe, so if you want to use it	347	Note that this function is I<not> thread-safe, so if you want to use it
302	from multiple threads, you have to lock (note also that this is unlikely,	348	from multiple threads, you have to employ some kind of mutex (note also
303	as loops cannot be shared easily between threads anyway).	349	that this case is unlikely, as loops cannot be shared easily between
		350	threads anyway).
304		351
305	The default loop is the only loop that can handle C<ev_signal> and	352	The default loop is the only loop that can handle C<ev_child> watchers,
306	C<ev_child> watchers, and to do this, it always registers a handler	353	and to do this, it always registers a handler for C<SIGCHLD>. If this is
307	for C<SIGCHLD>. If this is a problem for your application you can either	354	a problem for your application you can either create a dynamic loop with
308	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	355	C<ev_loop_new> which doesn't do that, or you can simply overwrite the
309	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	356	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
310	C<ev_default_init>.	357
		358	Example: This is the most typical usage.
		359
		360	if (!ev_default_loop (0))
		361	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
		362
		363	Example: Restrict libev to the select and poll backends, and do not allow
		364	environment settings to be taken into account:
		365
		366	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
		367
		368	=item struct ev_loop *ev_loop_new (unsigned int flags)
		369
		370	This will create and initialise a new event loop object. If the loop
		371	could not be initialised, returns false.
		372
		373	This function is thread-safe, and one common way to use libev with
		374	threads is indeed to create one loop per thread, and using the default
		375	loop in the "main" or "initial" thread.
311		376
312	The flags argument can be used to specify special behaviour or specific	377	The flags argument can be used to specify special behaviour or specific
313	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).	378	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
314		379
315	The following flags are supported:	380	The following flags are supported:
…		…
330	useful to try out specific backends to test their performance, or to work	395	useful to try out specific backends to test their performance, or to work
331	around bugs.	396	around bugs.
332		397
333	=item C<EVFLAG_FORKCHECK>	398	=item C<EVFLAG_FORKCHECK>
334		399
335	Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after	400	Instead of calling C<ev_loop_fork> manually after a fork, you can also
336	a fork, you can also make libev check for a fork in each iteration by	401	make libev check for a fork in each iteration by enabling this flag.
337	enabling this flag.
338		402
339	This works by calling C<getpid ()> on every iteration of the loop,	403	This works by calling C<getpid ()> on every iteration of the loop,
340	and thus this might slow down your event loop if you do a lot of loop	404	and thus this might slow down your event loop if you do a lot of loop
341	iterations and little real work, but is usually not noticeable (on my	405	iterations and little real work, but is usually not noticeable (on my
342	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence	406	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence
…		…
348	flag.	412	flag.
349		413
350	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>	414	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
351	environment variable.	415	environment variable.
352		416
		417	=item C<EVFLAG_NOINOTIFY>
		418
		419	When this flag is specified, then libev will not attempt to use the
		420	I<inotify> API for its C<ev_stat> watchers. Apart from debugging and
		421	testing, this flag can be useful to conserve inotify file descriptors, as
		422	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
		423
		424	=item C<EVFLAG_SIGNALFD>
		425
		426	When this flag is specified, then libev will attempt to use the
		427	I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API
		428	delivers signals synchronously, which makes it both faster and might make
		429	it possible to get the queued signal data. It can also simplify signal
		430	handling with threads, as long as you properly block signals in your
		431	threads that are not interested in handling them.
		432
		433	Signalfd will not be used by default as this changes your signal mask, and
		434	there are a lot of shoddy libraries and programs (glib's threadpool for
		435	example) that can't properly initialise their signal masks.
		436
		437	=item C<EVFLAG_NOSIGMASK>
		438
		439	When this flag is specified, then libev will avoid to modify the signal
		440	mask. Specifically, this means you ahve to make sure signals are unblocked
		441	when you want to receive them.
		442
		443	This behaviour is useful when you want to do your own signal handling, or
		444	want to handle signals only in specific threads and want to avoid libev
		445	unblocking the signals.
		446
		447	It's also required by POSIX in a threaded program, as libev calls
		448	C<sigprocmask>, whose behaviour is officially unspecified.
		449
		450	This flag's behaviour will become the default in future versions of libev.
		451
353	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	452	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
354		453
355	This is your standard select(2) backend. Not I<completely> standard, as	454	This is your standard select(2) backend. Not I<completely> standard, as
356	libev tries to roll its own fd_set with no limits on the number of fds,	455	libev tries to roll its own fd_set with no limits on the number of fds,
357	but if that fails, expect a fairly low limit on the number of fds when	456	but if that fails, expect a fairly low limit on the number of fds when
…		…
381	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and	480	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and
382	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.	481	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.
383		482
384	=item C<EVBACKEND_EPOLL> (value 4, Linux)	483	=item C<EVBACKEND_EPOLL> (value 4, Linux)
385		484
		485	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
		486	kernels).
		487
386	For few fds, this backend is a bit little slower than poll and select,	488	For few fds, this backend is a bit little slower than poll and select,
387	but it scales phenomenally better. While poll and select usually scale	489	but it scales phenomenally better. While poll and select usually scale
388	like O(total_fds) where n is the total number of fds (or the highest fd),	490	like O(total_fds) where n is the total number of fds (or the highest fd),
389	epoll scales either O(1) or O(active_fds).	491	epoll scales either O(1) or O(active_fds).
390		492
391	The epoll syscalls are the most misdesigned of the more advanced event	493	The epoll mechanism deserves honorable mention as the most misdesigned
392	mechanisms: problems include silently dropping fds, requiring a system	494	of the more advanced event mechanisms: mere annoyances include silently
		495	dropping file descriptors, requiring a system call per change per file
393	call per change per fd (and unnecessary guessing of parameters), problems	496	descriptor (and unnecessary guessing of parameters), problems with dup,
		497	returning before the timeout value, resulting in additional iterations
		498	(and only giving 5ms accuracy while select on the same platform gives
394	with dup and so on. The biggest issue is fork races, however - if a	499	0.1ms) and so on. The biggest issue is fork races, however - if a program
395	program forks then I<both> parent and child process have to recreate the	500	forks then I<both> parent and child process have to recreate the epoll
396	epoll set, which can take considerable time (one syscall per fd) and is of	501	set, which can take considerable time (one syscall per file descriptor)
397	course hard to detect.	502	and is of course hard to detect.
398		503
399	Epoll is also notoriously buggy - embedding epoll fds should work, but	504	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
400	of course doesn't, and epoll just loves to report events for totally	505	of course I<doesn't>, and epoll just loves to report events for totally
401	I<different> file descriptors (even already closed ones, so one cannot	506	I<different> file descriptors (even already closed ones, so one cannot
402	even remove them from the set) than registered in the set (especially	507	even remove them from the set) than registered in the set (especially
403	on SMP systems). Libev tries to counter these spurious notifications by	508	on SMP systems). Libev tries to counter these spurious notifications by
404	employing an additional generation counter and comparing that against the	509	employing an additional generation counter and comparing that against the
405	events to filter out spurious ones.	510	events to filter out spurious ones, recreating the set when required. Last
		511	not least, it also refuses to work with some file descriptors which work
		512	perfectly fine with C<select> (files, many character devices...).
		513
		514	Epoll is truly the train wreck analog among event poll mechanisms,
		515	a frankenpoll, cobbled together in a hurry, no thought to design or
		516	interaction with others.
406		517
407	While stopping, setting and starting an I/O watcher in the same iteration	518	While stopping, setting and starting an I/O watcher in the same iteration
408	will result in some caching, there is still a system call per such incident	519	will result in some caching, there is still a system call per such
409	(because the fd could point to a different file description now), so its	520	incident (because the same I<file descriptor> could point to a different
410	best to avoid that. Also, C<dup ()>'ed file descriptors might not work	521	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
411	very well if you register events for both fds.	522	file descriptors might not work very well if you register events for both
		523	file descriptors.
412		524
413	Best performance from this backend is achieved by not unregistering all	525	Best performance from this backend is achieved by not unregistering all
414	watchers for a file descriptor until it has been closed, if possible,	526	watchers for a file descriptor until it has been closed, if possible,
415	i.e. keep at least one watcher active per fd at all times. Stopping and	527	i.e. keep at least one watcher active per fd at all times. Stopping and
416	starting a watcher (without re-setting it) also usually doesn't cause	528	starting a watcher (without re-setting it) also usually doesn't cause
417	extra overhead. A fork can both result in spurious notifications as well	529	extra overhead. A fork can both result in spurious notifications as well
418	as in libev having to destroy and recreate the epoll object, which can	530	as in libev having to destroy and recreate the epoll object, which can
419	take considerable time and thus should be avoided.	531	take considerable time and thus should be avoided.
420		532
		533	All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or
		534	faster than epoll for maybe up to a hundred file descriptors, depending on
		535	the usage. So sad.
		536
421	While nominally embeddable in other event loops, this feature is broken in	537	While nominally embeddable in other event loops, this feature is broken in
422	all kernel versions tested so far.	538	all kernel versions tested so far.
423		539
424	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	540	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
425	C<EVBACKEND_POLL>.	541	C<EVBACKEND_POLL>.
426		542
427	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	543	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
428		544
429	Kqueue deserves special mention, as at the time of this writing, it was	545	Kqueue deserves special mention, as at the time of this writing, it
430	broken on all BSDs except NetBSD (usually it doesn't work reliably with	546	was broken on all BSDs except NetBSD (usually it doesn't work reliably
431	anything but sockets and pipes, except on Darwin, where of course it's	547	with anything but sockets and pipes, except on Darwin, where of course
432	completely useless). For this reason it's not being "auto-detected" unless	548	it's completely useless). Unlike epoll, however, whose brokenness
433	you explicitly specify it in the flags (i.e. using C<EVBACKEND_KQUEUE>) or	549	is by design, these kqueue bugs can (and eventually will) be fixed
434	libev was compiled on a known-to-be-good (-enough) system like NetBSD.	550	without API changes to existing programs. For this reason it's not being
		551	"auto-detected" unless you explicitly specify it in the flags (i.e. using
		552	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
		553	system like NetBSD.
435		554
436	You still can embed kqueue into a normal poll or select backend and use it	555	You still can embed kqueue into a normal poll or select backend and use it
437	only for sockets (after having made sure that sockets work with kqueue on	556	only for sockets (after having made sure that sockets work with kqueue on
438	the target platform). See C<ev_embed> watchers for more info.	557	the target platform). See C<ev_embed> watchers for more info.
439		558
…		…
449		568
450	While nominally embeddable in other event loops, this doesn't work	569	While nominally embeddable in other event loops, this doesn't work
451	everywhere, so you might need to test for this. And since it is broken	570	everywhere, so you might need to test for this. And since it is broken
452	almost everywhere, you should only use it when you have a lot of sockets	571	almost everywhere, you should only use it when you have a lot of sockets
453	(for which it usually works), by embedding it into another event loop	572	(for which it usually works), by embedding it into another event loop
454	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and, did I mention it,	573	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course
455	using it only for sockets.	574	also broken on OS X)) and, did I mention it, using it only for sockets.
456		575
457	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with	576	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with
458	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with	577	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with
459	C<NOTE_EOF>.	578	C<NOTE_EOF>.
460		579
…		…
468	=item C<EVBACKEND_PORT> (value 32, Solaris 10)	587	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
469		588
470	This uses the Solaris 10 event port mechanism. As with everything on Solaris,	589	This uses the Solaris 10 event port mechanism. As with everything on Solaris,
471	it's really slow, but it still scales very well (O(active_fds)).	590	it's really slow, but it still scales very well (O(active_fds)).
472		591
473	Please note that Solaris event ports can deliver a lot of spurious
474	notifications, so you need to use non-blocking I/O or other means to avoid
475	blocking when no data (or space) is available.
476
477	While this backend scales well, it requires one system call per active	592	While this backend scales well, it requires one system call per active
478	file descriptor per loop iteration. For small and medium numbers of file	593	file descriptor per loop iteration. For small and medium numbers of file
479	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	594	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
480	might perform better.	595	might perform better.
481		596
482	On the positive side, with the exception of the spurious readiness	597	On the positive side, this backend actually performed fully to
483	notifications, this backend actually performed fully to specification
484	in all tests and is fully embeddable, which is a rare feat among the	598	specification in all tests and is fully embeddable, which is a rare feat
485	OS-specific backends (I vastly prefer correctness over speed hacks).	599	among the OS-specific backends (I vastly prefer correctness over speed
		600	hacks).
		601
		602	On the negative side, the interface is I<bizarre> - so bizarre that
		603	even sun itself gets it wrong in their code examples: The event polling
		604	function sometimes returning events to the caller even though an error
		605	occurred, but with no indication whether it has done so or not (yes, it's
		606	even documented that way) - deadly for edge-triggered interfaces where
		607	you absolutely have to know whether an event occurred or not because you
		608	have to re-arm the watcher.
		609
		610	Fortunately libev seems to be able to work around these idiocies.
486		611
487	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	612	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
488	C<EVBACKEND_POLL>.	613	C<EVBACKEND_POLL>.
489		614
490	=item C<EVBACKEND_ALL>	615	=item C<EVBACKEND_ALL>
491		616
492	Try all backends (even potentially broken ones that wouldn't be tried	617	Try all backends (even potentially broken ones that wouldn't be tried
493	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as	618	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
494	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.	619	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
495		620
496	It is definitely not recommended to use this flag.	621	It is definitely not recommended to use this flag, use whatever
		622	C<ev_recommended_backends ()> returns, or simply do not specify a backend
		623	at all.
		624
		625	=item C<EVBACKEND_MASK>
		626
		627	Not a backend at all, but a mask to select all backend bits from a
		628	C<flags> value, in case you want to mask out any backends from a flags
		629	value (e.g. when modifying the C<LIBEV_FLAGS> environment variable).
497		630
498	=back	631	=back
499		632
500	If one or more of these are or'ed into the flags value, then only these	633	If one or more of the backend flags are or'ed into the flags value,
501	backends will be tried (in the reverse order as listed here). If none are	634	then only these backends will be tried (in the reverse order as listed
502	specified, all backends in C<ev_recommended_backends ()> will be tried.	635	here). If none are specified, all backends in C<ev_recommended_backends
503		636	()> will be tried.
504	Example: This is the most typical usage.
505
506	if (!ev_default_loop (0))
507	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
508
509	Example: Restrict libev to the select and poll backends, and do not allow
510	environment settings to be taken into account:
511
512	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
513
514	Example: Use whatever libev has to offer, but make sure that kqueue is
515	used if available (warning, breaks stuff, best use only with your own
516	private event loop and only if you know the OS supports your types of
517	fds):
518
519	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
520
521	=item struct ev_loop *ev_loop_new (unsigned int flags)
522
523	Similar to C<ev_default_loop>, but always creates a new event loop that is
524	always distinct from the default loop. Unlike the default loop, it cannot
525	handle signal and child watchers, and attempts to do so will be greeted by
526	undefined behaviour (or a failed assertion if assertions are enabled).
527
528	Note that this function I<is> thread-safe, and the recommended way to use
529	libev with threads is indeed to create one loop per thread, and using the
530	default loop in the "main" or "initial" thread.
531		637
532	Example: Try to create a event loop that uses epoll and nothing else.	638	Example: Try to create a event loop that uses epoll and nothing else.
533		639
534	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	640	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
535	if (!epoller)	641	if (!epoller)
536	fatal ("no epoll found here, maybe it hides under your chair");	642	fatal ("no epoll found here, maybe it hides under your chair");
537		643
		644	Example: Use whatever libev has to offer, but make sure that kqueue is
		645	used if available.
		646
		647	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE);
		648
538	=item ev_default_destroy ()	649	=item ev_loop_destroy (loop)
539		650
540	Destroys the default loop again (frees all memory and kernel state	651	Destroys an event loop object (frees all memory and kernel state
541	etc.). None of the active event watchers will be stopped in the normal	652	etc.). None of the active event watchers will be stopped in the normal
542	sense, so e.g. C<ev_is_active> might still return true. It is your	653	sense, so e.g. C<ev_is_active> might still return true. It is your
543	responsibility to either stop all watchers cleanly yourself I<before>	654	responsibility to either stop all watchers cleanly yourself I<before>
544	calling this function, or cope with the fact afterwards (which is usually	655	calling this function, or cope with the fact afterwards (which is usually
545	the easiest thing, you can just ignore the watchers and/or C<free ()> them	656	the easiest thing, you can just ignore the watchers and/or C<free ()> them
…		…
547		658
548	Note that certain global state, such as signal state (and installed signal	659	Note that certain global state, such as signal state (and installed signal
549	handlers), will not be freed by this function, and related watchers (such	660	handlers), will not be freed by this function, and related watchers (such
550	as signal and child watchers) would need to be stopped manually.	661	as signal and child watchers) would need to be stopped manually.
551		662
552	In general it is not advisable to call this function except in the	663	This function is normally used on loop objects allocated by
553	rare occasion where you really need to free e.g. the signal handling	664	C<ev_loop_new>, but it can also be used on the default loop returned by
		665	C<ev_default_loop>, in which case it is not thread-safe.
		666
		667	Note that it is not advisable to call this function on the default loop
		668	except in the rare occasion where you really need to free its resources.
554	pipe fds. If you need dynamically allocated loops it is better to use	669	If you need dynamically allocated loops it is better to use C<ev_loop_new>
555	C<ev_loop_new> and C<ev_loop_destroy>).	670	and C<ev_loop_destroy>.
556		671
557	=item ev_loop_destroy (loop)	672	=item ev_loop_fork (loop)
558		673
559	Like C<ev_default_destroy>, but destroys an event loop created by an
560	earlier call to C<ev_loop_new>.
561
562	=item ev_default_fork ()
563
564	This function sets a flag that causes subsequent C<ev_loop> iterations	674	This function sets a flag that causes subsequent C<ev_run> iterations to
565	to reinitialise the kernel state for backends that have one. Despite the	675	reinitialise the kernel state for backends that have one. Despite the
566	name, you can call it anytime, but it makes most sense after forking, in	676	name, you can call it anytime, but it makes most sense after forking, in
567	the child process (or both child and parent, but that again makes little	677	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
568	sense). You I<must> call it in the child before using any of the libev	678	child before resuming or calling C<ev_run>.
569	functions, and it will only take effect at the next C<ev_loop> iteration.	679
		680	Again, you I<have> to call it on I<any> loop that you want to re-use after
		681	a fork, I<even if you do not plan to use the loop in the parent>. This is
		682	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
		683	during fork.
570		684
571	On the other hand, you only need to call this function in the child	685	On the other hand, you only need to call this function in the child
572	process if and only if you want to use the event library in the child. If	686	process if and only if you want to use the event loop in the child. If
573	you just fork+exec, you don't have to call it at all.	687	you just fork+exec or create a new loop in the child, you don't have to
		688	call it at all (in fact, C<epoll> is so badly broken that it makes a
		689	difference, but libev will usually detect this case on its own and do a
		690	costly reset of the backend).
574		691
575	The function itself is quite fast and it's usually not a problem to call	692	The function itself is quite fast and it's usually not a problem to call
576	it just in case after a fork. To make this easy, the function will fit in	693	it just in case after a fork.
577	quite nicely into a call to C<pthread_atfork>:
578		694
		695	Example: Automate calling C<ev_loop_fork> on the default loop when
		696	using pthreads.
		697
		698	static void
		699	post_fork_child (void)
		700	{
		701	ev_loop_fork (EV_DEFAULT);
		702	}
		703
		704	...
579	pthread_atfork (0, 0, ev_default_fork);	705	pthread_atfork (0, 0, post_fork_child);
580
581	=item ev_loop_fork (loop)
582
583	Like C<ev_default_fork>, but acts on an event loop created by
584	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
585	after fork that you want to re-use in the child, and how you do this is
586	entirely your own problem.
587		706
588	=item int ev_is_default_loop (loop)	707	=item int ev_is_default_loop (loop)
589		708
590	Returns true when the given loop is, in fact, the default loop, and false	709	Returns true when the given loop is, in fact, the default loop, and false
591	otherwise.	710	otherwise.
592		711
593	=item unsigned int ev_loop_count (loop)	712	=item unsigned int ev_iteration (loop)
594		713
595	Returns the count of loop iterations for the loop, which is identical to	714	Returns the current iteration count for the event loop, which is identical
596	the number of times libev did poll for new events. It starts at C<0> and	715	to the number of times libev did poll for new events. It starts at C<0>
597	happily wraps around with enough iterations.	716	and happily wraps around with enough iterations.
598		717
599	This value can sometimes be useful as a generation counter of sorts (it	718	This value can sometimes be useful as a generation counter of sorts (it
600	"ticks" the number of loop iterations), as it roughly corresponds with	719	"ticks" the number of loop iterations), as it roughly corresponds with
601	C<ev_prepare> and C<ev_check> calls.	720	C<ev_prepare> and C<ev_check> calls - and is incremented between the
		721	prepare and check phases.
		722
		723	=item unsigned int ev_depth (loop)
		724
		725	Returns the number of times C<ev_run> was entered minus the number of
		726	times C<ev_run> was exited normally, in other words, the recursion depth.
		727
		728	Outside C<ev_run>, this number is zero. In a callback, this number is
		729	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
		730	in which case it is higher.
		731
		732	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread,
		733	throwing an exception etc.), doesn't count as "exit" - consider this
		734	as a hint to avoid such ungentleman-like behaviour unless it's really
		735	convenient, in which case it is fully supported.
602		736
603	=item unsigned int ev_backend (loop)	737	=item unsigned int ev_backend (loop)
604		738
605	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	739	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
606	use.	740	use.
…		…
615		749
616	=item ev_now_update (loop)	750	=item ev_now_update (loop)
617		751
618	Establishes the current time by querying the kernel, updating the time	752	Establishes the current time by querying the kernel, updating the time
619	returned by C<ev_now ()> in the progress. This is a costly operation and	753	returned by C<ev_now ()> in the progress. This is a costly operation and
620	is usually done automatically within C<ev_loop ()>.	754	is usually done automatically within C<ev_run ()>.
621		755
622	This function is rarely useful, but when some event callback runs for a	756	This function is rarely useful, but when some event callback runs for a
623	very long time without entering the event loop, updating libev's idea of	757	very long time without entering the event loop, updating libev's idea of
624	the current time is a good idea.	758	the current time is a good idea.
625		759
626	See also "The special problem of time updates" in the C<ev_timer> section.	760	See also L<The special problem of time updates> in the C<ev_timer> section.
627		761
		762	=item ev_suspend (loop)
		763
		764	=item ev_resume (loop)
		765
		766	These two functions suspend and resume an event loop, for use when the
		767	loop is not used for a while and timeouts should not be processed.
		768
		769	A typical use case would be an interactive program such as a game: When
		770	the user presses C<^Z> to suspend the game and resumes it an hour later it
		771	would be best to handle timeouts as if no time had actually passed while
		772	the program was suspended. This can be achieved by calling C<ev_suspend>
		773	in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
		774	C<ev_resume> directly afterwards to resume timer processing.
		775
		776	Effectively, all C<ev_timer> watchers will be delayed by the time spend
		777	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers
		778	will be rescheduled (that is, they will lose any events that would have
		779	occurred while suspended).
		780
		781	After calling C<ev_suspend> you B<must not> call I<any> function on the
		782	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>
		783	without a previous call to C<ev_suspend>.
		784
		785	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
		786	event loop time (see C<ev_now_update>).
		787
628	=item ev_loop (loop, int flags)	788	=item ev_run (loop, int flags)
629		789
630	Finally, this is it, the event handler. This function usually is called	790	Finally, this is it, the event handler. This function usually is called
631	after you initialised all your watchers and you want to start handling	791	after you have initialised all your watchers and you want to start
632	events.	792	handling events. It will ask the operating system for any new events, call
		793	the watcher callbacks, an then repeat the whole process indefinitely: This
		794	is why event loops are called I<loops>.
633		795
634	If the flags argument is specified as C<0>, it will not return until	796	If the flags argument is specified as C<0>, it will keep handling events
635	either no event watchers are active anymore or C<ev_unloop> was called.	797	until either no event watchers are active anymore or C<ev_break> was
		798	called.
636		799
637	Please note that an explicit C<ev_unloop> is usually better than	800	Please note that an explicit C<ev_break> is usually better than
638	relying on all watchers to be stopped when deciding when a program has	801	relying on all watchers to be stopped when deciding when a program has
639	finished (especially in interactive programs), but having a program	802	finished (especially in interactive programs), but having a program
640	that automatically loops as long as it has to and no longer by virtue	803	that automatically loops as long as it has to and no longer by virtue
641	of relying on its watchers stopping correctly, that is truly a thing of	804	of relying on its watchers stopping correctly, that is truly a thing of
642	beauty.	805	beauty.
643		806
		807	This function is also I<mostly> exception-safe - you can break out of
		808	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
		809	exception and so on. This does not decrement the C<ev_depth> value, nor
		810	will it clear any outstanding C<EVBREAK_ONE> breaks.
		811
644	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	812	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
645	those events and any already outstanding ones, but will not block your	813	those events and any already outstanding ones, but will not wait and
646	process in case there are no events and will return after one iteration of	814	block your process in case there are no events and will return after one
647	the loop.	815	iteration of the loop. This is sometimes useful to poll and handle new
		816	events while doing lengthy calculations, to keep the program responsive.
648		817
649	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	818	A flags value of C<EVRUN_ONCE> will look for new events (waiting if
650	necessary) and will handle those and any already outstanding ones. It	819	necessary) and will handle those and any already outstanding ones. It
651	will block your process until at least one new event arrives (which could	820	will block your process until at least one new event arrives (which could
652	be an event internal to libev itself, so there is no guarantee that a	821	be an event internal to libev itself, so there is no guarantee that a
653	user-registered callback will be called), and will return after one	822	user-registered callback will be called), and will return after one
654	iteration of the loop.	823	iteration of the loop.
655		824
656	This is useful if you are waiting for some external event in conjunction	825	This is useful if you are waiting for some external event in conjunction
657	with something not expressible using other libev watchers (i.e. "roll your	826	with something not expressible using other libev watchers (i.e. "roll your
658	own C<ev_loop>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is	827	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
659	usually a better approach for this kind of thing.	828	usually a better approach for this kind of thing.
660		829
661	Here are the gory details of what C<ev_loop> does:	830	Here are the gory details of what C<ev_run> does:
662		831
		832	- Increment loop depth.
		833	- Reset the ev_break status.
663	- Before the first iteration, call any pending watchers.	834	- Before the first iteration, call any pending watchers.
		835	LOOP:
664	* If EVFLAG_FORKCHECK was used, check for a fork.	836	- If EVFLAG_FORKCHECK was used, check for a fork.
665	- If a fork was detected (by any means), queue and call all fork watchers.	837	- If a fork was detected (by any means), queue and call all fork watchers.
666	- Queue and call all prepare watchers.	838	- Queue and call all prepare watchers.
		839	- If ev_break was called, goto FINISH.
667	- If we have been forked, detach and recreate the kernel state	840	- If we have been forked, detach and recreate the kernel state
668	as to not disturb the other process.	841	as to not disturb the other process.
669	- Update the kernel state with all outstanding changes.	842	- Update the kernel state with all outstanding changes.
670	- Update the "event loop time" (ev_now ()).	843	- Update the "event loop time" (ev_now ()).
671	- Calculate for how long to sleep or block, if at all	844	- Calculate for how long to sleep or block, if at all
672	(active idle watchers, EVLOOP_NONBLOCK or not having	845	(active idle watchers, EVRUN_NOWAIT or not having
673	any active watchers at all will result in not sleeping).	846	any active watchers at all will result in not sleeping).
674	- Sleep if the I/O and timer collect interval say so.	847	- Sleep if the I/O and timer collect interval say so.
		848	- Increment loop iteration counter.
675	- Block the process, waiting for any events.	849	- Block the process, waiting for any events.
676	- Queue all outstanding I/O (fd) events.	850	- Queue all outstanding I/O (fd) events.
677	- Update the "event loop time" (ev_now ()), and do time jump adjustments.	851	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
678	- Queue all expired timers.	852	- Queue all expired timers.
679	- Queue all expired periodics.	853	- Queue all expired periodics.
680	- Unless any events are pending now, queue all idle watchers.	854	- Queue all idle watchers with priority higher than that of pending events.
681	- Queue all check watchers.	855	- Queue all check watchers.
682	- Call all queued watchers in reverse order (i.e. check watchers first).	856	- Call all queued watchers in reverse order (i.e. check watchers first).
683	Signals and child watchers are implemented as I/O watchers, and will	857	Signals and child watchers are implemented as I/O watchers, and will
684	be handled here by queueing them when their watcher gets executed.	858	be handled here by queueing them when their watcher gets executed.
685	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	859	- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT
686	were used, or there are no active watchers, return, otherwise	860	were used, or there are no active watchers, goto FINISH, otherwise
687	continue with step *.	861	continue with step LOOP.
		862	FINISH:
		863	- Reset the ev_break status iff it was EVBREAK_ONE.
		864	- Decrement the loop depth.
		865	- Return.
688		866
689	Example: Queue some jobs and then loop until no events are outstanding	867	Example: Queue some jobs and then loop until no events are outstanding
690	anymore.	868	anymore.
691		869
692	... queue jobs here, make sure they register event watchers as long	870	... queue jobs here, make sure they register event watchers as long
693	... as they still have work to do (even an idle watcher will do..)	871	... as they still have work to do (even an idle watcher will do..)
694	ev_loop (my_loop, 0);	872	ev_run (my_loop, 0);
695	... jobs done or somebody called unloop. yeah!	873	... jobs done or somebody called break. yeah!
696		874
697	=item ev_unloop (loop, how)	875	=item ev_break (loop, how)
698		876
699	Can be used to make a call to C<ev_loop> return early (but only after it	877	Can be used to make a call to C<ev_run> return early (but only after it
700	has processed all outstanding events). The C<how> argument must be either	878	has processed all outstanding events). The C<how> argument must be either
701	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	879	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
702	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	880	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
703		881
704	This "unloop state" will be cleared when entering C<ev_loop> again.	882	This "break state" will be cleared on the next call to C<ev_run>.
705		883
706	It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls.	884	It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in
		885	which case it will have no effect.
707		886
708	=item ev_ref (loop)	887	=item ev_ref (loop)
709		888
710	=item ev_unref (loop)	889	=item ev_unref (loop)
711		890
712	Ref/unref can be used to add or remove a reference count on the event	891	Ref/unref can be used to add or remove a reference count on the event
713	loop: Every watcher keeps one reference, and as long as the reference	892	loop: Every watcher keeps one reference, and as long as the reference
714	count is nonzero, C<ev_loop> will not return on its own.	893	count is nonzero, C<ev_run> will not return on its own.
715		894
716	If you have a watcher you never unregister that should not keep C<ev_loop>	895	This is useful when you have a watcher that you never intend to
717	from returning, call ev_unref() after starting, and ev_ref() before	896	unregister, but that nevertheless should not keep C<ev_run> from
		897	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
718	stopping it.	898	before stopping it.
719		899
720	As an example, libev itself uses this for its internal signal pipe: It is	900	As an example, libev itself uses this for its internal signal pipe: It
721	not visible to the libev user and should not keep C<ev_loop> from exiting	901	is not visible to the libev user and should not keep C<ev_run> from
722	if no event watchers registered by it are active. It is also an excellent	902	exiting if no event watchers registered by it are active. It is also an
723	way to do this for generic recurring timers or from within third-party	903	excellent way to do this for generic recurring timers or from within
724	libraries. Just remember to I<unref after start> and I<ref before stop>	904	third-party libraries. Just remember to I<unref after start> and I<ref
725	(but only if the watcher wasn't active before, or was active before,	905	before stop> (but only if the watcher wasn't active before, or was active
726	respectively).	906	before, respectively. Note also that libev might stop watchers itself
		907	(e.g. non-repeating timers) in which case you have to C<ev_ref>
		908	in the callback).
727		909
728	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	910	Example: Create a signal watcher, but keep it from keeping C<ev_run>
729	running when nothing else is active.	911	running when nothing else is active.
730		912
731	ev_signal exitsig;	913	ev_signal exitsig;
732	ev_signal_init (&exitsig, sig_cb, SIGINT);	914	ev_signal_init (&exitsig, sig_cb, SIGINT);
733	ev_signal_start (loop, &exitsig);	915	ev_signal_start (loop, &exitsig);
734	evf_unref (loop);	916	ev_unref (loop);
735		917
736	Example: For some weird reason, unregister the above signal handler again.	918	Example: For some weird reason, unregister the above signal handler again.
737		919
738	ev_ref (loop);	920	ev_ref (loop);
739	ev_signal_stop (loop, &exitsig);	921	ev_signal_stop (loop, &exitsig);
…		…
760		942
761	By setting a higher I<io collect interval> you allow libev to spend more	943	By setting a higher I<io collect interval> you allow libev to spend more
762	time collecting I/O events, so you can handle more events per iteration,	944	time collecting I/O events, so you can handle more events per iteration,
763	at the cost of increasing latency. Timeouts (both C<ev_periodic> and	945	at the cost of increasing latency. Timeouts (both C<ev_periodic> and
764	C<ev_timer>) will be not affected. Setting this to a non-null value will	946	C<ev_timer>) will be not affected. Setting this to a non-null value will
765	introduce an additional C<ev_sleep ()> call into most loop iterations.	947	introduce an additional C<ev_sleep ()> call into most loop iterations. The
		948	sleep time ensures that libev will not poll for I/O events more often then
		949	once per this interval, on average.
766		950
767	Likewise, by setting a higher I<timeout collect interval> you allow libev	951	Likewise, by setting a higher I<timeout collect interval> you allow libev
768	to spend more time collecting timeouts, at the expense of increased	952	to spend more time collecting timeouts, at the expense of increased
769	latency/jitter/inexactness (the watcher callback will be called	953	latency/jitter/inexactness (the watcher callback will be called
770	later). C<ev_io> watchers will not be affected. Setting this to a non-null	954	later). C<ev_io> watchers will not be affected. Setting this to a non-null
…		…
772		956
773	Many (busy) programs can usually benefit by setting the I/O collect	957	Many (busy) programs can usually benefit by setting the I/O collect
774	interval to a value near C<0.1> or so, which is often enough for	958	interval to a value near C<0.1> or so, which is often enough for
775	interactive servers (of course not for games), likewise for timeouts. It	959	interactive servers (of course not for games), likewise for timeouts. It
776	usually doesn't make much sense to set it to a lower value than C<0.01>,	960	usually doesn't make much sense to set it to a lower value than C<0.01>,
777	as this approaches the timing granularity of most systems.	961	as this approaches the timing granularity of most systems. Note that if
		962	you do transactions with the outside world and you can't increase the
		963	parallelity, then this setting will limit your transaction rate (if you
		964	need to poll once per transaction and the I/O collect interval is 0.01,
		965	then you can't do more than 100 transactions per second).
778		966
779	Setting the I<timeout collect interval> can improve the opportunity for	967	Setting the I<timeout collect interval> can improve the opportunity for
780	saving power, as the program will "bundle" timer callback invocations that	968	saving power, as the program will "bundle" timer callback invocations that
781	are "near" in time together, by delaying some, thus reducing the number of	969	are "near" in time together, by delaying some, thus reducing the number of
782	times the process sleeps and wakes up again. Another useful technique to	970	times the process sleeps and wakes up again. Another useful technique to
783	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure	971	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure
784	they fire on, say, one-second boundaries only.	972	they fire on, say, one-second boundaries only.
785		973
		974	Example: we only need 0.1s timeout granularity, and we wish not to poll
		975	more often than 100 times per second:
		976
		977	ev_set_timeout_collect_interval (EV_DEFAULT_UC_ 0.1);
		978	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
		979
		980	=item ev_invoke_pending (loop)
		981
		982	This call will simply invoke all pending watchers while resetting their
		983	pending state. Normally, C<ev_run> does this automatically when required,
		984	but when overriding the invoke callback this call comes handy. This
		985	function can be invoked from a watcher - this can be useful for example
		986	when you want to do some lengthy calculation and want to pass further
		987	event handling to another thread (you still have to make sure only one
		988	thread executes within C<ev_invoke_pending> or C<ev_run> of course).
		989
		990	=item int ev_pending_count (loop)
		991
		992	Returns the number of pending watchers - zero indicates that no watchers
		993	are pending.
		994
		995	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
		996
		997	This overrides the invoke pending functionality of the loop: Instead of
		998	invoking all pending watchers when there are any, C<ev_run> will call
		999	this callback instead. This is useful, for example, when you want to
		1000	invoke the actual watchers inside another context (another thread etc.).
		1001
		1002	If you want to reset the callback, use C<ev_invoke_pending> as new
		1003	callback.
		1004
		1005	=item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))
		1006
		1007	Sometimes you want to share the same loop between multiple threads. This
		1008	can be done relatively simply by putting mutex_lock/unlock calls around
		1009	each call to a libev function.
		1010
		1011	However, C<ev_run> can run an indefinite time, so it is not feasible
		1012	to wait for it to return. One way around this is to wake up the event
		1013	loop via C<ev_break> and C<av_async_send>, another way is to set these
		1014	I<release> and I<acquire> callbacks on the loop.
		1015
		1016	When set, then C<release> will be called just before the thread is
		1017	suspended waiting for new events, and C<acquire> is called just
		1018	afterwards.
		1019
		1020	Ideally, C<release> will just call your mutex_unlock function, and
		1021	C<acquire> will just call the mutex_lock function again.
		1022
		1023	While event loop modifications are allowed between invocations of
		1024	C<release> and C<acquire> (that's their only purpose after all), no
		1025	modifications done will affect the event loop, i.e. adding watchers will
		1026	have no effect on the set of file descriptors being watched, or the time
		1027	waited. Use an C<ev_async> watcher to wake up C<ev_run> when you want it
		1028	to take note of any changes you made.
		1029
		1030	In theory, threads executing C<ev_run> will be async-cancel safe between
		1031	invocations of C<release> and C<acquire>.
		1032
		1033	See also the locking example in the C<THREADS> section later in this
		1034	document.
		1035
		1036	=item ev_set_userdata (loop, void *data)
		1037
		1038	=item void *ev_userdata (loop)
		1039
		1040	Set and retrieve a single C<void *> associated with a loop. When
		1041	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
		1042	C<0>.
		1043
		1044	These two functions can be used to associate arbitrary data with a loop,
		1045	and are intended solely for the C<invoke_pending_cb>, C<release> and
		1046	C<acquire> callbacks described above, but of course can be (ab-)used for
		1047	any other purpose as well.
		1048
786	=item ev_loop_verify (loop)	1049	=item ev_verify (loop)
787		1050
788	This function only does something when C<EV_VERIFY> support has been	1051	This function only does something when C<EV_VERIFY> support has been
789	compiled in, which is the default for non-minimal builds. It tries to go	1052	compiled in, which is the default for non-minimal builds. It tries to go
790	through all internal structures and checks them for validity. If anything	1053	through all internal structures and checks them for validity. If anything
791	is found to be inconsistent, it will print an error message to standard	1054	is found to be inconsistent, it will print an error message to standard
…		…
802		1065
803	In the following description, uppercase C<TYPE> in names stands for the	1066	In the following description, uppercase C<TYPE> in names stands for the
804	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer	1067	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
805	watchers and C<ev_io_start> for I/O watchers.	1068	watchers and C<ev_io_start> for I/O watchers.
806		1069
807	A watcher is a structure that you create and register to record your	1070	A watcher is an opaque structure that you allocate and register to record
808	interest in some event. For instance, if you want to wait for STDIN to	1071	your interest in some event. To make a concrete example, imagine you want
809	become readable, you would create an C<ev_io> watcher for that:	1072	to wait for STDIN to become readable, you would create an C<ev_io> watcher
		1073	for that:
810		1074
811	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)	1075	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
812	{	1076	{
813	ev_io_stop (w);	1077	ev_io_stop (w);
814	ev_unloop (loop, EVUNLOOP_ALL);	1078	ev_break (loop, EVBREAK_ALL);
815	}	1079	}
816		1080
817	struct ev_loop *loop = ev_default_loop (0);	1081	struct ev_loop *loop = ev_default_loop (0);
818		1082
819	ev_io stdin_watcher;	1083	ev_io stdin_watcher;
820		1084
821	ev_init (&stdin_watcher, my_cb);	1085	ev_init (&stdin_watcher, my_cb);
822	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	1086	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
823	ev_io_start (loop, &stdin_watcher);	1087	ev_io_start (loop, &stdin_watcher);
824		1088
825	ev_loop (loop, 0);	1089	ev_run (loop, 0);
826		1090
827	As you can see, you are responsible for allocating the memory for your	1091	As you can see, you are responsible for allocating the memory for your
828	watcher structures (and it is I<usually> a bad idea to do this on the	1092	watcher structures (and it is I<usually> a bad idea to do this on the
829	stack).	1093	stack).
830		1094
831	Each watcher has an associated watcher structure (called C<struct ev_TYPE>	1095	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
832	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).	1096	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
833		1097
834	Each watcher structure must be initialised by a call to C<ev_init	1098	Each watcher structure must be initialised by a call to C<ev_init (watcher
835	(watcher *, callback)>, which expects a callback to be provided. This	1099	*, callback)>, which expects a callback to be provided. This callback is
836	callback gets invoked each time the event occurs (or, in the case of I/O	1100	invoked each time the event occurs (or, in the case of I/O watchers, each
837	watchers, each time the event loop detects that the file descriptor given	1101	time the event loop detects that the file descriptor given is readable
838	is readable and/or writable).	1102	and/or writable).
839		1103
840	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>	1104	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
841	macro to configure it, with arguments specific to the watcher type. There	1105	macro to configure it, with arguments specific to the watcher type. There
842	is also a macro to combine initialisation and setting in one call: C<<	1106	is also a macro to combine initialisation and setting in one call: C<<
843	ev_TYPE_init (watcher *, callback, ...) >>.	1107	ev_TYPE_init (watcher *, callback, ...) >>.
…		…
866	=item C<EV_WRITE>	1130	=item C<EV_WRITE>
867		1131
868	The file descriptor in the C<ev_io> watcher has become readable and/or	1132	The file descriptor in the C<ev_io> watcher has become readable and/or
869	writable.	1133	writable.
870		1134
871	=item C<EV_TIMEOUT>	1135	=item C<EV_TIMER>
872		1136
873	The C<ev_timer> watcher has timed out.	1137	The C<ev_timer> watcher has timed out.
874		1138
875	=item C<EV_PERIODIC>	1139	=item C<EV_PERIODIC>
876		1140
…		…
894		1158
895	=item C<EV_PREPARE>	1159	=item C<EV_PREPARE>
896		1160
897	=item C<EV_CHECK>	1161	=item C<EV_CHECK>
898		1162
899	All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts	1163	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts
900	to gather new events, and all C<ev_check> watchers are invoked just after	1164	to gather new events, and all C<ev_check> watchers are invoked just after
901	C<ev_loop> has gathered them, but before it invokes any callbacks for any	1165	C<ev_run> has gathered them, but before it invokes any callbacks for any
902	received events. Callbacks of both watcher types can start and stop as	1166	received events. Callbacks of both watcher types can start and stop as
903	many watchers as they want, and all of them will be taken into account	1167	many watchers as they want, and all of them will be taken into account
904	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	1168	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
905	C<ev_loop> from blocking).	1169	C<ev_run> from blocking).
906		1170
907	=item C<EV_EMBED>	1171	=item C<EV_EMBED>
908		1172
909	The embedded event loop specified in the C<ev_embed> watcher needs attention.	1173	The embedded event loop specified in the C<ev_embed> watcher needs attention.
910		1174
911	=item C<EV_FORK>	1175	=item C<EV_FORK>
912		1176
913	The event loop has been resumed in the child process after fork (see	1177	The event loop has been resumed in the child process after fork (see
914	C<ev_fork>).	1178	C<ev_fork>).
915		1179
		1180	=item C<EV_CLEANUP>
		1181
		1182	The event loop is about to be destroyed (see C<ev_cleanup>).
		1183
916	=item C<EV_ASYNC>	1184	=item C<EV_ASYNC>
917		1185
918	The given async watcher has been asynchronously notified (see C<ev_async>).	1186	The given async watcher has been asynchronously notified (see C<ev_async>).
		1187
		1188	=item C<EV_CUSTOM>
		1189
		1190	Not ever sent (or otherwise used) by libev itself, but can be freely used
		1191	by libev users to signal watchers (e.g. via C<ev_feed_event>).
919		1192
920	=item C<EV_ERROR>	1193	=item C<EV_ERROR>
921		1194
922	An unspecified error has occurred, the watcher has been stopped. This might	1195	An unspecified error has occurred, the watcher has been stopped. This might
923	happen because the watcher could not be properly started because libev	1196	happen because the watcher could not be properly started because libev
…		…
961		1234
962	ev_io w;	1235	ev_io w;
963	ev_init (&w, my_cb);	1236	ev_init (&w, my_cb);
964	ev_io_set (&w, STDIN_FILENO, EV_READ);	1237	ev_io_set (&w, STDIN_FILENO, EV_READ);
965		1238
966	=item C<ev_TYPE_set> (ev_TYPE *, [args])	1239	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
967		1240
968	This macro initialises the type-specific parts of a watcher. You need to	1241	This macro initialises the type-specific parts of a watcher. You need to
969	call C<ev_init> at least once before you call this macro, but you can	1242	call C<ev_init> at least once before you call this macro, but you can
970	call C<ev_TYPE_set> any number of times. You must not, however, call this	1243	call C<ev_TYPE_set> any number of times. You must not, however, call this
971	macro on a watcher that is active (it can be pending, however, which is a	1244	macro on a watcher that is active (it can be pending, however, which is a
…		…
984		1257
985	Example: Initialise and set an C<ev_io> watcher in one step.	1258	Example: Initialise and set an C<ev_io> watcher in one step.
986		1259
987	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);	1260	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
988		1261
989	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)	1262	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
990		1263
991	Starts (activates) the given watcher. Only active watchers will receive	1264	Starts (activates) the given watcher. Only active watchers will receive
992	events. If the watcher is already active nothing will happen.	1265	events. If the watcher is already active nothing will happen.
993		1266
994	Example: Start the C<ev_io> watcher that is being abused as example in this	1267	Example: Start the C<ev_io> watcher that is being abused as example in this
995	whole section.	1268	whole section.
996		1269
997	ev_io_start (EV_DEFAULT_UC, &w);	1270	ev_io_start (EV_DEFAULT_UC, &w);
998		1271
999	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)	1272	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
1000		1273
1001	Stops the given watcher if active, and clears the pending status (whether	1274	Stops the given watcher if active, and clears the pending status (whether
1002	the watcher was active or not).	1275	the watcher was active or not).
1003		1276
1004	It is possible that stopped watchers are pending - for example,	1277	It is possible that stopped watchers are pending - for example,
…		…
1029	=item ev_cb_set (ev_TYPE *watcher, callback)	1302	=item ev_cb_set (ev_TYPE *watcher, callback)
1030		1303
1031	Change the callback. You can change the callback at virtually any time	1304	Change the callback. You can change the callback at virtually any time
1032	(modulo threads).	1305	(modulo threads).
1033		1306
1034	=item ev_set_priority (ev_TYPE *watcher, priority)	1307	=item ev_set_priority (ev_TYPE *watcher, int priority)
1035		1308
1036	=item int ev_priority (ev_TYPE *watcher)	1309	=item int ev_priority (ev_TYPE *watcher)
1037		1310
1038	Set and query the priority of the watcher. The priority is a small	1311	Set and query the priority of the watcher. The priority is a small
1039	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>	1312	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
1040	(default: C<-2>). Pending watchers with higher priority will be invoked	1313	(default: C<-2>). Pending watchers with higher priority will be invoked
1041	before watchers with lower priority, but priority will not keep watchers	1314	before watchers with lower priority, but priority will not keep watchers
1042	from being executed (except for C<ev_idle> watchers).	1315	from being executed (except for C<ev_idle> watchers).
1043		1316
1044	This means that priorities are I<only> used for ordering callback
1045	invocation after new events have been received. This is useful, for
1046	example, to reduce latency after idling, or more often, to bind two
1047	watchers on the same event and make sure one is called first.
1048
1049	If you need to suppress invocation when higher priority events are pending	1317	If you need to suppress invocation when higher priority events are pending
1050	you need to look at C<ev_idle> watchers, which provide this functionality.	1318	you need to look at C<ev_idle> watchers, which provide this functionality.
1051		1319
1052	You I<must not> change the priority of a watcher as long as it is active or	1320	You I<must not> change the priority of a watcher as long as it is active or
1053	pending.	1321	pending.
1054
1055	The default priority used by watchers when no priority has been set is
1056	always C<0>, which is supposed to not be too high and not be too low :).
1057		1322
1058	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1323	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
1059	fine, as long as you do not mind that the priority value you query might	1324	fine, as long as you do not mind that the priority value you query might
1060	or might not have been clamped to the valid range.	1325	or might not have been clamped to the valid range.
		1326
		1327	The default priority used by watchers when no priority has been set is
		1328	always C<0>, which is supposed to not be too high and not be too low :).
		1329
		1330	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
		1331	priorities.
1061		1332
1062	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1333	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
1063		1334
1064	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1335	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
1065	C<loop> nor C<revents> need to be valid as long as the watcher callback	1336	C<loop> nor C<revents> need to be valid as long as the watcher callback
…		…
1073	watcher isn't pending it does nothing and returns C<0>.	1344	watcher isn't pending it does nothing and returns C<0>.
1074		1345
1075	Sometimes it can be useful to "poll" a watcher instead of waiting for its	1346	Sometimes it can be useful to "poll" a watcher instead of waiting for its
1076	callback to be invoked, which can be accomplished with this function.	1347	callback to be invoked, which can be accomplished with this function.
1077		1348
		1349	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
		1350
		1351	Feeds the given event set into the event loop, as if the specified event
		1352	had happened for the specified watcher (which must be a pointer to an
		1353	initialised but not necessarily started event watcher). Obviously you must
		1354	not free the watcher as long as it has pending events.
		1355
		1356	Stopping the watcher, letting libev invoke it, or calling
		1357	C<ev_clear_pending> will clear the pending event, even if the watcher was
		1358	not started in the first place.
		1359
		1360	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
		1361	functions that do not need a watcher.
		1362
1078	=back	1363	=back
1079		1364
		1365	See also the L<ASSOCIATING CUSTOM DATA WITH A WATCHER> and L<BUILDING YOUR
		1366	OWN COMPOSITE WATCHERS> idioms.
1080		1367
1081	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1368	=head2 WATCHER STATES
1082		1369
1083	Each watcher has, by default, a member C<void *data> that you can change	1370	There are various watcher states mentioned throughout this manual -
1084	and read at any time: libev will completely ignore it. This can be used	1371	active, pending and so on. In this section these states and the rules to
1085	to associate arbitrary data with your watcher. If you need more data and	1372	transition between them will be described in more detail - and while these
1086	don't want to allocate memory and store a pointer to it in that data	1373	rules might look complicated, they usually do "the right thing".
1087	member, you can also "subclass" the watcher type and provide your own
1088	data:
1089		1374
1090	struct my_io	1375	=over 4
		1376
		1377	=item initialiased
		1378
		1379	Before a watcher can be registered with the event looop it has to be
		1380	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
		1381	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
		1382
		1383	In this state it is simply some block of memory that is suitable for
		1384	use in an event loop. It can be moved around, freed, reused etc. at
		1385	will - as long as you either keep the memory contents intact, or call
		1386	C<ev_TYPE_init> again.
		1387
		1388	=item started/running/active
		1389
		1390	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
		1391	property of the event loop, and is actively waiting for events. While in
		1392	this state it cannot be accessed (except in a few documented ways), moved,
		1393	freed or anything else - the only legal thing is to keep a pointer to it,
		1394	and call libev functions on it that are documented to work on active watchers.
		1395
		1396	=item pending
		1397
		1398	If a watcher is active and libev determines that an event it is interested
		1399	in has occurred (such as a timer expiring), it will become pending. It will
		1400	stay in this pending state until either it is stopped or its callback is
		1401	about to be invoked, so it is not normally pending inside the watcher
		1402	callback.
		1403
		1404	The watcher might or might not be active while it is pending (for example,
		1405	an expired non-repeating timer can be pending but no longer active). If it
		1406	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
		1407	but it is still property of the event loop at this time, so cannot be
		1408	moved, freed or reused. And if it is active the rules described in the
		1409	previous item still apply.
		1410
		1411	It is also possible to feed an event on a watcher that is not active (e.g.
		1412	via C<ev_feed_event>), in which case it becomes pending without being
		1413	active.
		1414
		1415	=item stopped
		1416
		1417	A watcher can be stopped implicitly by libev (in which case it might still
		1418	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
		1419	latter will clear any pending state the watcher might be in, regardless
		1420	of whether it was active or not, so stopping a watcher explicitly before
		1421	freeing it is often a good idea.
		1422
		1423	While stopped (and not pending) the watcher is essentially in the
		1424	initialised state, that is, it can be reused, moved, modified in any way
		1425	you wish (but when you trash the memory block, you need to C<ev_TYPE_init>
		1426	it again).
		1427
		1428	=back
		1429
		1430	=head2 WATCHER PRIORITY MODELS
		1431
		1432	Many event loops support I<watcher priorities>, which are usually small
		1433	integers that influence the ordering of event callback invocation
		1434	between watchers in some way, all else being equal.
		1435
		1436	In libev, Watcher priorities can be set using C<ev_set_priority>. See its
		1437	description for the more technical details such as the actual priority
		1438	range.
		1439
		1440	There are two common ways how these these priorities are being interpreted
		1441	by event loops:
		1442
		1443	In the more common lock-out model, higher priorities "lock out" invocation
		1444	of lower priority watchers, which means as long as higher priority
		1445	watchers receive events, lower priority watchers are not being invoked.
		1446
		1447	The less common only-for-ordering model uses priorities solely to order
		1448	callback invocation within a single event loop iteration: Higher priority
		1449	watchers are invoked before lower priority ones, but they all get invoked
		1450	before polling for new events.
		1451
		1452	Libev uses the second (only-for-ordering) model for all its watchers
		1453	except for idle watchers (which use the lock-out model).
		1454
		1455	The rationale behind this is that implementing the lock-out model for
		1456	watchers is not well supported by most kernel interfaces, and most event
		1457	libraries will just poll for the same events again and again as long as
		1458	their callbacks have not been executed, which is very inefficient in the
		1459	common case of one high-priority watcher locking out a mass of lower
		1460	priority ones.
		1461
		1462	Static (ordering) priorities are most useful when you have two or more
		1463	watchers handling the same resource: a typical usage example is having an
		1464	C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle
		1465	timeouts. Under load, data might be received while the program handles
		1466	other jobs, but since timers normally get invoked first, the timeout
		1467	handler will be executed before checking for data. In that case, giving
		1468	the timer a lower priority than the I/O watcher ensures that I/O will be
		1469	handled first even under adverse conditions (which is usually, but not
		1470	always, what you want).
		1471
		1472	Since idle watchers use the "lock-out" model, meaning that idle watchers
		1473	will only be executed when no same or higher priority watchers have
		1474	received events, they can be used to implement the "lock-out" model when
		1475	required.
		1476
		1477	For example, to emulate how many other event libraries handle priorities,
		1478	you can associate an C<ev_idle> watcher to each such watcher, and in
		1479	the normal watcher callback, you just start the idle watcher. The real
		1480	processing is done in the idle watcher callback. This causes libev to
		1481	continuously poll and process kernel event data for the watcher, but when
		1482	the lock-out case is known to be rare (which in turn is rare :), this is
		1483	workable.
		1484
		1485	Usually, however, the lock-out model implemented that way will perform
		1486	miserably under the type of load it was designed to handle. In that case,
		1487	it might be preferable to stop the real watcher before starting the
		1488	idle watcher, so the kernel will not have to process the event in case
		1489	the actual processing will be delayed for considerable time.
		1490
		1491	Here is an example of an I/O watcher that should run at a strictly lower
		1492	priority than the default, and which should only process data when no
		1493	other events are pending:
		1494
		1495	ev_idle idle; // actual processing watcher
		1496	ev_io io; // actual event watcher
		1497
		1498	static void
		1499	io_cb (EV_P_ ev_io *w, int revents)
1091	{	1500	{
1092	ev_io io;	1501	// stop the I/O watcher, we received the event, but
1093	int otherfd;	1502	// are not yet ready to handle it.
1094	void *somedata;	1503	ev_io_stop (EV_A_ w);
1095	struct whatever *mostinteresting;	1504
		1505	// start the idle watcher to handle the actual event.
		1506	// it will not be executed as long as other watchers
		1507	// with the default priority are receiving events.
		1508	ev_idle_start (EV_A_ &idle);
1096	};	1509	}
1097		1510
1098	...	1511	static void
1099	struct my_io w;	1512	idle_cb (EV_P_ ev_idle *w, int revents)
1100	ev_io_init (&w.io, my_cb, fd, EV_READ);
1101
1102	And since your callback will be called with a pointer to the watcher, you
1103	can cast it back to your own type:
1104
1105	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1106	{	1513	{
1107	struct my_io *w = (struct my_io *)w_;	1514	// actual processing
1108	...	1515	read (STDIN_FILENO, ...);
		1516
		1517	// have to start the I/O watcher again, as
		1518	// we have handled the event
		1519	ev_io_start (EV_P_ &io);
1109	}	1520	}
1110		1521
1111	More interesting and less C-conformant ways of casting your callback type	1522	// initialisation
1112	instead have been omitted.	1523	ev_idle_init (&idle, idle_cb);
		1524	ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ);
		1525	ev_io_start (EV_DEFAULT_ &io);
1113		1526
1114	Another common scenario is to use some data structure with multiple	1527	In the "real" world, it might also be beneficial to start a timer, so that
1115	embedded watchers:	1528	low-priority connections can not be locked out forever under load. This
1116		1529	enables your program to keep a lower latency for important connections
1117	struct my_biggy	1530	during short periods of high load, while not completely locking out less
1118	{	1531	important ones.
1119	int some_data;
1120	ev_timer t1;
1121	ev_timer t2;
1122	}
1123
1124	In this case getting the pointer to C<my_biggy> is a bit more
1125	complicated: Either you store the address of your C<my_biggy> struct
1126	in the C<data> member of the watcher (for woozies), or you need to use
1127	some pointer arithmetic using C<offsetof> inside your watchers (for real
1128	programmers):
1129
1130	#include <stddef.h>
1131
1132	static void
1133	t1_cb (EV_P_ ev_timer *w, int revents)
1134	{
1135	struct my_biggy big = (struct my_biggy *
1136	(((char *)w) - offsetof (struct my_biggy, t1));
1137	}
1138
1139	static void
1140	t2_cb (EV_P_ ev_timer *w, int revents)
1141	{
1142	struct my_biggy big = (struct my_biggy *
1143	(((char *)w) - offsetof (struct my_biggy, t2));
1144	}
1145		1532
1146		1533
1147	=head1 WATCHER TYPES	1534	=head1 WATCHER TYPES
1148		1535
1149	This section describes each watcher in detail, but will not repeat	1536	This section describes each watcher in detail, but will not repeat
…		…
1173	In general you can register as many read and/or write event watchers per	1560	In general you can register as many read and/or write event watchers per
1174	fd as you want (as long as you don't confuse yourself). Setting all file	1561	fd as you want (as long as you don't confuse yourself). Setting all file
1175	descriptors to non-blocking mode is also usually a good idea (but not	1562	descriptors to non-blocking mode is also usually a good idea (but not
1176	required if you know what you are doing).	1563	required if you know what you are doing).
1177		1564
1178	If you cannot use non-blocking mode, then force the use of a
1179	known-to-be-good backend (at the time of this writing, this includes only
1180	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>).
1181
1182	Another thing you have to watch out for is that it is quite easy to	1565	Another thing you have to watch out for is that it is quite easy to
1183	receive "spurious" readiness notifications, that is your callback might	1566	receive "spurious" readiness notifications, that is, your callback might
1184	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1567	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1185	because there is no data. Not only are some backends known to create a	1568	because there is no data. It is very easy to get into this situation even
1186	lot of those (for example Solaris ports), it is very easy to get into	1569	with a relatively standard program structure. Thus it is best to always
1187	this situation even with a relatively standard program structure. Thus	1570	use non-blocking I/O: An extra C<read>(2) returning C<EAGAIN> is far
1188	it is best to always use non-blocking I/O: An extra C<read>(2) returning
1189	C<EAGAIN> is far preferable to a program hanging until some data arrives.	1571	preferable to a program hanging until some data arrives.
1190		1572
1191	If you cannot run the fd in non-blocking mode (for example you should	1573	If you cannot run the fd in non-blocking mode (for example you should
1192	not play around with an Xlib connection), then you have to separately	1574	not play around with an Xlib connection), then you have to separately
1193	re-test whether a file descriptor is really ready with a known-to-be good	1575	re-test whether a file descriptor is really ready with a known-to-be good
1194	interface such as poll (fortunately in our Xlib example, Xlib already	1576	interface such as poll (fortunately in the case of Xlib, it already does
1195	does this on its own, so its quite safe to use). Some people additionally	1577	this on its own, so its quite safe to use). Some people additionally
1196	use C<SIGALRM> and an interval timer, just to be sure you won't block	1578	use C<SIGALRM> and an interval timer, just to be sure you won't block
1197	indefinitely.	1579	indefinitely.
1198		1580
1199	But really, best use non-blocking mode.	1581	But really, best use non-blocking mode.
1200		1582
…		…
1228		1610
1229	There is no workaround possible except not registering events	1611	There is no workaround possible except not registering events
1230	for potentially C<dup ()>'ed file descriptors, or to resort to	1612	for potentially C<dup ()>'ed file descriptors, or to resort to
1231	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.	1613	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1232		1614
		1615	=head3 The special problem of files
		1616
		1617	Many people try to use C<select> (or libev) on file descriptors
		1618	representing files, and expect it to become ready when their program
		1619	doesn't block on disk accesses (which can take a long time on their own).
		1620
		1621	However, this cannot ever work in the "expected" way - you get a readiness
		1622	notification as soon as the kernel knows whether and how much data is
		1623	there, and in the case of open files, that's always the case, so you
		1624	always get a readiness notification instantly, and your read (or possibly
		1625	write) will still block on the disk I/O.
		1626
		1627	Another way to view it is that in the case of sockets, pipes, character
		1628	devices and so on, there is another party (the sender) that delivers data
		1629	on its own, but in the case of files, there is no such thing: the disk
		1630	will not send data on its own, simply because it doesn't know what you
		1631	wish to read - you would first have to request some data.
		1632
		1633	Since files are typically not-so-well supported by advanced notification
		1634	mechanism, libev tries hard to emulate POSIX behaviour with respect
		1635	to files, even though you should not use it. The reason for this is
		1636	convenience: sometimes you want to watch STDIN or STDOUT, which is
		1637	usually a tty, often a pipe, but also sometimes files or special devices
		1638	(for example, C<epoll> on Linux works with F</dev/random> but not with
		1639	F</dev/urandom>), and even though the file might better be served with
		1640	asynchronous I/O instead of with non-blocking I/O, it is still useful when
		1641	it "just works" instead of freezing.
		1642
		1643	So avoid file descriptors pointing to files when you know it (e.g. use
		1644	libeio), but use them when it is convenient, e.g. for STDIN/STDOUT, or
		1645	when you rarely read from a file instead of from a socket, and want to
		1646	reuse the same code path.
		1647
1233	=head3 The special problem of fork	1648	=head3 The special problem of fork
1234		1649
1235	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit	1650	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit
1236	useless behaviour. Libev fully supports fork, but needs to be told about	1651	useless behaviour. Libev fully supports fork, but needs to be told about
1237	it in the child.	1652	it in the child if you want to continue to use it in the child.
1238		1653
1239	To support fork in your programs, you either have to call	1654	To support fork in your child processes, you have to call C<ev_loop_fork
1240	C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,	1655	()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to
1241	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1656	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1242	C<EVBACKEND_POLL>.
1243		1657
1244	=head3 The special problem of SIGPIPE	1658	=head3 The special problem of SIGPIPE
1245		1659
1246	While not really specific to libev, it is easy to forget about C<SIGPIPE>:	1660	While not really specific to libev, it is easy to forget about C<SIGPIPE>:
1247	when writing to a pipe whose other end has been closed, your program gets	1661	when writing to a pipe whose other end has been closed, your program gets
…		…
1250		1664
1251	So when you encounter spurious, unexplained daemon exits, make sure you	1665	So when you encounter spurious, unexplained daemon exits, make sure you
1252	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon	1666	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1253	somewhere, as that would have given you a big clue).	1667	somewhere, as that would have given you a big clue).
1254		1668
		1669	=head3 The special problem of accept()ing when you can't
		1670
		1671	Many implementations of the POSIX C<accept> function (for example,
		1672	found in post-2004 Linux) have the peculiar behaviour of not removing a
		1673	connection from the pending queue in all error cases.
		1674
		1675	For example, larger servers often run out of file descriptors (because
		1676	of resource limits), causing C<accept> to fail with C<ENFILE> but not
		1677	rejecting the connection, leading to libev signalling readiness on
		1678	the next iteration again (the connection still exists after all), and
		1679	typically causing the program to loop at 100% CPU usage.
		1680
		1681	Unfortunately, the set of errors that cause this issue differs between
		1682	operating systems, there is usually little the app can do to remedy the
		1683	situation, and no known thread-safe method of removing the connection to
		1684	cope with overload is known (to me).
		1685
		1686	One of the easiest ways to handle this situation is to just ignore it
		1687	- when the program encounters an overload, it will just loop until the
		1688	situation is over. While this is a form of busy waiting, no OS offers an
		1689	event-based way to handle this situation, so it's the best one can do.
		1690
		1691	A better way to handle the situation is to log any errors other than
		1692	C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
		1693	messages, and continue as usual, which at least gives the user an idea of
		1694	what could be wrong ("raise the ulimit!"). For extra points one could stop
		1695	the C<ev_io> watcher on the listening fd "for a while", which reduces CPU
		1696	usage.
		1697
		1698	If your program is single-threaded, then you could also keep a dummy file
		1699	descriptor for overload situations (e.g. by opening F</dev/null>), and
		1700	when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>,
		1701	close that fd, and create a new dummy fd. This will gracefully refuse
		1702	clients under typical overload conditions.
		1703
		1704	The last way to handle it is to simply log the error and C<exit>, as
		1705	is often done with C<malloc> failures, but this results in an easy
		1706	opportunity for a DoS attack.
1255		1707
1256	=head3 Watcher-Specific Functions	1708	=head3 Watcher-Specific Functions
1257		1709
1258	=over 4	1710	=over 4
1259		1711
…		…
1291	...	1743	...
1292	struct ev_loop *loop = ev_default_init (0);	1744	struct ev_loop *loop = ev_default_init (0);
1293	ev_io stdin_readable;	1745	ev_io stdin_readable;
1294	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1746	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1295	ev_io_start (loop, &stdin_readable);	1747	ev_io_start (loop, &stdin_readable);
1296	ev_loop (loop, 0);	1748	ev_run (loop, 0);
1297		1749
1298		1750
1299	=head2 C<ev_timer> - relative and optionally repeating timeouts	1751	=head2 C<ev_timer> - relative and optionally repeating timeouts
1300		1752
1301	Timer watchers are simple relative timers that generate an event after a	1753	Timer watchers are simple relative timers that generate an event after a
…		…
1306	year, it will still time out after (roughly) one hour. "Roughly" because	1758	year, it will still time out after (roughly) one hour. "Roughly" because
1307	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1759	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1308	monotonic clock option helps a lot here).	1760	monotonic clock option helps a lot here).
1309		1761
1310	The callback is guaranteed to be invoked only I<after> its timeout has	1762	The callback is guaranteed to be invoked only I<after> its timeout has
1311	passed, but if multiple timers become ready during the same loop iteration	1763	passed (not I<at>, so on systems with very low-resolution clocks this
1312	then order of execution is undefined.	1764	might introduce a small delay). If multiple timers become ready during the
		1765	same loop iteration then the ones with earlier time-out values are invoked
		1766	before ones of the same priority with later time-out values (but this is
		1767	no longer true when a callback calls C<ev_run> recursively).
1313		1768
1314	=head3 Be smart about timeouts	1769	=head3 Be smart about timeouts
1315		1770
1316	Many real-world problems involve some kind of timeout, usually for error	1771	Many real-world problems involve some kind of timeout, usually for error
1317	recovery. A typical example is an HTTP request - if the other side hangs,	1772	recovery. A typical example is an HTTP request - if the other side hangs,
…		…
1361	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>	1816	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
1362	member and C<ev_timer_again>.	1817	member and C<ev_timer_again>.
1363		1818
1364	At start:	1819	At start:
1365		1820
1366	ev_timer_init (timer, callback);	1821	ev_init (timer, callback);
1367	timer->repeat = 60.;	1822	timer->repeat = 60.;
1368	ev_timer_again (loop, timer);	1823	ev_timer_again (loop, timer);
1369		1824
1370	Each time there is some activity:	1825	Each time there is some activity:
1371		1826
…		…
1403	ev_tstamp timeout = last_activity + 60.;	1858	ev_tstamp timeout = last_activity + 60.;
1404		1859
1405	// if last_activity + 60. is older than now, we did time out	1860	// if last_activity + 60. is older than now, we did time out
1406	if (timeout < now)	1861	if (timeout < now)
1407	{	1862	{
1408	// timeout occured, take action	1863	// timeout occurred, take action
1409	}	1864	}
1410	else	1865	else
1411	{	1866	{
1412	// callback was invoked, but there was some activity, re-arm	1867	// callback was invoked, but there was some activity, re-arm
1413	// the watcher to fire in last_activity + 60, which is	1868	// the watcher to fire in last_activity + 60, which is
1414	// guaranteed to be in the future, so "again" is positive:	1869	// guaranteed to be in the future, so "again" is positive:
1415	w->again = timeout - now;	1870	w->repeat = timeout - now;
1416	ev_timer_again (EV_A_ w);	1871	ev_timer_again (EV_A_ w);
1417	}	1872	}
1418	}	1873	}
1419		1874
1420	To summarise the callback: first calculate the real timeout (defined	1875	To summarise the callback: first calculate the real timeout (defined
…		…
1433		1888
1434	To start the timer, simply initialise the watcher and set C<last_activity>	1889	To start the timer, simply initialise the watcher and set C<last_activity>
1435	to the current time (meaning we just have some activity :), then call the	1890	to the current time (meaning we just have some activity :), then call the
1436	callback, which will "do the right thing" and start the timer:	1891	callback, which will "do the right thing" and start the timer:
1437		1892
1438	ev_timer_init (timer, callback);	1893	ev_init (timer, callback);
1439	last_activity = ev_now (loop);	1894	last_activity = ev_now (loop);
1440	callback (loop, timer, EV_TIMEOUT);	1895	callback (loop, timer, EV_TIMER);
1441		1896
1442	And when there is some activity, simply store the current time in	1897	And when there is some activity, simply store the current time in
1443	C<last_activity>, no libev calls at all:	1898	C<last_activity>, no libev calls at all:
1444		1899
1445	last_actiivty = ev_now (loop);	1900	last_activity = ev_now (loop);
1446		1901
1447	This technique is slightly more complex, but in most cases where the	1902	This technique is slightly more complex, but in most cases where the
1448	time-out is unlikely to be triggered, much more efficient.	1903	time-out is unlikely to be triggered, much more efficient.
1449		1904
1450	Changing the timeout is trivial as well (if it isn't hard-coded in the	1905	Changing the timeout is trivial as well (if it isn't hard-coded in the
…		…
1488		1943
1489	=head3 The special problem of time updates	1944	=head3 The special problem of time updates
1490		1945
1491	Establishing the current time is a costly operation (it usually takes at	1946	Establishing the current time is a costly operation (it usually takes at
1492	least two system calls): EV therefore updates its idea of the current	1947	least two system calls): EV therefore updates its idea of the current
1493	time only before and after C<ev_loop> collects new events, which causes a	1948	time only before and after C<ev_run> collects new events, which causes a
1494	growing difference between C<ev_now ()> and C<ev_time ()> when handling	1949	growing difference between C<ev_now ()> and C<ev_time ()> when handling
1495	lots of events in one iteration.	1950	lots of events in one iteration.
1496		1951
1497	The relative timeouts are calculated relative to the C<ev_now ()>	1952	The relative timeouts are calculated relative to the C<ev_now ()>
1498	time. This is usually the right thing as this timestamp refers to the time	1953	time. This is usually the right thing as this timestamp refers to the time
…		…
1504		1959
1505	If the event loop is suspended for a long time, you can also force an	1960	If the event loop is suspended for a long time, you can also force an
1506	update of the time returned by C<ev_now ()> by calling C<ev_now_update	1961	update of the time returned by C<ev_now ()> by calling C<ev_now_update
1507	()>.	1962	()>.
1508		1963
		1964	=head3 The special problems of suspended animation
		1965
		1966	When you leave the server world it is quite customary to hit machines that
		1967	can suspend/hibernate - what happens to the clocks during such a suspend?
		1968
		1969	Some quick tests made with a Linux 2.6.28 indicate that a suspend freezes
		1970	all processes, while the clocks (C<times>, C<CLOCK_MONOTONIC>) continue
		1971	to run until the system is suspended, but they will not advance while the
		1972	system is suspended. That means, on resume, it will be as if the program
		1973	was frozen for a few seconds, but the suspend time will not be counted
		1974	towards C<ev_timer> when a monotonic clock source is used. The real time
		1975	clock advanced as expected, but if it is used as sole clocksource, then a
		1976	long suspend would be detected as a time jump by libev, and timers would
		1977	be adjusted accordingly.
		1978
		1979	I would not be surprised to see different behaviour in different between
		1980	operating systems, OS versions or even different hardware.
		1981
		1982	The other form of suspend (job control, or sending a SIGSTOP) will see a
		1983	time jump in the monotonic clocks and the realtime clock. If the program
		1984	is suspended for a very long time, and monotonic clock sources are in use,
		1985	then you can expect C<ev_timer>s to expire as the full suspension time
		1986	will be counted towards the timers. When no monotonic clock source is in
		1987	use, then libev will again assume a timejump and adjust accordingly.
		1988
		1989	It might be beneficial for this latter case to call C<ev_suspend>
		1990	and C<ev_resume> in code that handles C<SIGTSTP>, to at least get
		1991	deterministic behaviour in this case (you can do nothing against
		1992	C<SIGSTOP>).
		1993
1509	=head3 Watcher-Specific Functions and Data Members	1994	=head3 Watcher-Specific Functions and Data Members
1510		1995
1511	=over 4	1996	=over 4
1512		1997
1513	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	1998	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
…		…
1536	If the timer is started but non-repeating, stop it (as if it timed out).	2021	If the timer is started but non-repeating, stop it (as if it timed out).
1537		2022
1538	If the timer is repeating, either start it if necessary (with the	2023	If the timer is repeating, either start it if necessary (with the
1539	C<repeat> value), or reset the running timer to the C<repeat> value.	2024	C<repeat> value), or reset the running timer to the C<repeat> value.
1540		2025
1541	This sounds a bit complicated, see "Be smart about timeouts", above, for a	2026	This sounds a bit complicated, see L<Be smart about timeouts>, above, for a
1542	usage example.	2027	usage example.
		2028
		2029	=item ev_tstamp ev_timer_remaining (loop, ev_timer *)
		2030
		2031	Returns the remaining time until a timer fires. If the timer is active,
		2032	then this time is relative to the current event loop time, otherwise it's
		2033	the timeout value currently configured.
		2034
		2035	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
		2036	C<5>. When the timer is started and one second passes, C<ev_timer_remaining>
		2037	will return C<4>. When the timer expires and is restarted, it will return
		2038	roughly C<7> (likely slightly less as callback invocation takes some time,
		2039	too), and so on.
1543		2040
1544	=item ev_tstamp repeat [read-write]	2041	=item ev_tstamp repeat [read-write]
1545		2042
1546	The current C<repeat> value. Will be used each time the watcher times out	2043	The current C<repeat> value. Will be used each time the watcher times out
1547	or C<ev_timer_again> is called, and determines the next timeout (if any),	2044	or C<ev_timer_again> is called, and determines the next timeout (if any),
…		…
1573	}	2070	}
1574		2071
1575	ev_timer mytimer;	2072	ev_timer mytimer;
1576	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	2073	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1577	ev_timer_again (&mytimer); /* start timer */	2074	ev_timer_again (&mytimer); /* start timer */
1578	ev_loop (loop, 0);	2075	ev_run (loop, 0);
1579		2076
1580	// and in some piece of code that gets executed on any "activity":	2077	// and in some piece of code that gets executed on any "activity":
1581	// reset the timeout to start ticking again at 10 seconds	2078	// reset the timeout to start ticking again at 10 seconds
1582	ev_timer_again (&mytimer);	2079	ev_timer_again (&mytimer);
1583		2080
…		…
1585	=head2 C<ev_periodic> - to cron or not to cron?	2082	=head2 C<ev_periodic> - to cron or not to cron?
1586		2083
1587	Periodic watchers are also timers of a kind, but they are very versatile	2084	Periodic watchers are also timers of a kind, but they are very versatile
1588	(and unfortunately a bit complex).	2085	(and unfortunately a bit complex).
1589		2086
1590	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	2087	Unlike C<ev_timer>, periodic watchers are not based on real time (or
1591	but on wall clock time (absolute time). You can tell a periodic watcher	2088	relative time, the physical time that passes) but on wall clock time
1592	to trigger after some specific point in time. For example, if you tell a	2089	(absolute time, the thing you can read on your calender or clock). The
1593	periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now ()	2090	difference is that wall clock time can run faster or slower than real
1594	+ 10.>, that is, an absolute time not a delay) and then reset your system	2091	time, and time jumps are not uncommon (e.g. when you adjust your
1595	clock to January of the previous year, then it will take more than year	2092	wrist-watch).
1596	to trigger the event (unlike an C<ev_timer>, which would still trigger
1597	roughly 10 seconds later as it uses a relative timeout).
1598		2093
		2094	You can tell a periodic watcher to trigger after some specific point
		2095	in time: for example, if you tell a periodic watcher to trigger "in 10
		2096	seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time
		2097	not a delay) and then reset your system clock to January of the previous
		2098	year, then it will take a year or more to trigger the event (unlike an
		2099	C<ev_timer>, which would still trigger roughly 10 seconds after starting
		2100	it, as it uses a relative timeout).
		2101
1599	C<ev_periodic>s can also be used to implement vastly more complex timers,	2102	C<ev_periodic> watchers can also be used to implement vastly more complex
1600	such as triggering an event on each "midnight, local time", or other	2103	timers, such as triggering an event on each "midnight, local time", or
1601	complicated rules.	2104	other complicated rules. This cannot be done with C<ev_timer> watchers, as
		2105	those cannot react to time jumps.
1602		2106
1603	As with timers, the callback is guaranteed to be invoked only when the	2107	As with timers, the callback is guaranteed to be invoked only when the
1604	time (C<at>) has passed, but if multiple periodic timers become ready	2108	point in time where it is supposed to trigger has passed. If multiple
1605	during the same loop iteration, then order of execution is undefined.	2109	timers become ready during the same loop iteration then the ones with
		2110	earlier time-out values are invoked before ones with later time-out values
		2111	(but this is no longer true when a callback calls C<ev_run> recursively).
1606		2112
1607	=head3 Watcher-Specific Functions and Data Members	2113	=head3 Watcher-Specific Functions and Data Members
1608		2114
1609	=over 4	2115	=over 4
1610		2116
1611	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	2117	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1612		2118
1613	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	2119	=item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1614		2120
1615	Lots of arguments, lets sort it out... There are basically three modes of	2121	Lots of arguments, let's sort it out... There are basically three modes of
1616	operation, and we will explain them from simplest to most complex:	2122	operation, and we will explain them from simplest to most complex:
1617		2123
1618	=over 4	2124	=over 4
1619		2125
1620	=item * absolute timer (at = time, interval = reschedule_cb = 0)	2126	=item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0)
1621		2127
1622	In this configuration the watcher triggers an event after the wall clock	2128	In this configuration the watcher triggers an event after the wall clock
1623	time C<at> has passed. It will not repeat and will not adjust when a time	2129	time C<offset> has passed. It will not repeat and will not adjust when a
1624	jump occurs, that is, if it is to be run at January 1st 2011 then it will	2130	time jump occurs, that is, if it is to be run at January 1st 2011 then it
1625	only run when the system clock reaches or surpasses this time.	2131	will be stopped and invoked when the system clock reaches or surpasses
		2132	this point in time.
1626		2133
1627	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)	2134	=item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0)
1628		2135
1629	In this mode the watcher will always be scheduled to time out at the next	2136	In this mode the watcher will always be scheduled to time out at the next
1630	C<at + N * interval> time (for some integer N, which can also be negative)	2137	C<offset + N * interval> time (for some integer N, which can also be
1631	and then repeat, regardless of any time jumps.	2138	negative) and then repeat, regardless of any time jumps. The C<offset>
		2139	argument is merely an offset into the C<interval> periods.
1632		2140
1633	This can be used to create timers that do not drift with respect to the	2141	This can be used to create timers that do not drift with respect to the
1634	system clock, for example, here is a C<ev_periodic> that triggers each	2142	system clock, for example, here is an C<ev_periodic> that triggers each
1635	hour, on the hour:	2143	hour, on the hour (with respect to UTC):
1636		2144
1637	ev_periodic_set (&periodic, 0., 3600., 0);	2145	ev_periodic_set (&periodic, 0., 3600., 0);
1638		2146
1639	This doesn't mean there will always be 3600 seconds in between triggers,	2147	This doesn't mean there will always be 3600 seconds in between triggers,
1640	but only that the callback will be called when the system time shows a	2148	but only that the callback will be called when the system time shows a
1641	full hour (UTC), or more correctly, when the system time is evenly divisible	2149	full hour (UTC), or more correctly, when the system time is evenly divisible
1642	by 3600.	2150	by 3600.
1643		2151
1644	Another way to think about it (for the mathematically inclined) is that	2152	Another way to think about it (for the mathematically inclined) is that
1645	C<ev_periodic> will try to run the callback in this mode at the next possible	2153	C<ev_periodic> will try to run the callback in this mode at the next possible
1646	time where C<time = at (mod interval)>, regardless of any time jumps.	2154	time where C<time = offset (mod interval)>, regardless of any time jumps.
1647		2155
1648	For numerical stability it is preferable that the C<at> value is near	2156	For numerical stability it is preferable that the C<offset> value is near
1649	C<ev_now ()> (the current time), but there is no range requirement for	2157	C<ev_now ()> (the current time), but there is no range requirement for
1650	this value, and in fact is often specified as zero.	2158	this value, and in fact is often specified as zero.
1651		2159
1652	Note also that there is an upper limit to how often a timer can fire (CPU	2160	Note also that there is an upper limit to how often a timer can fire (CPU
1653	speed for example), so if C<interval> is very small then timing stability	2161	speed for example), so if C<interval> is very small then timing stability
1654	will of course deteriorate. Libev itself tries to be exact to be about one	2162	will of course deteriorate. Libev itself tries to be exact to be about one
1655	millisecond (if the OS supports it and the machine is fast enough).	2163	millisecond (if the OS supports it and the machine is fast enough).
1656		2164
1657	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)	2165	=item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback)
1658		2166
1659	In this mode the values for C<interval> and C<at> are both being	2167	In this mode the values for C<interval> and C<offset> are both being
1660	ignored. Instead, each time the periodic watcher gets scheduled, the	2168	ignored. Instead, each time the periodic watcher gets scheduled, the
1661	reschedule callback will be called with the watcher as first, and the	2169	reschedule callback will be called with the watcher as first, and the
1662	current time as second argument.	2170	current time as second argument.
1663		2171
1664	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,	2172	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever,
1665	ever, or make ANY event loop modifications whatsoever>.	2173	or make ANY other event loop modifications whatsoever, unless explicitly
		2174	allowed by documentation here>.
1666		2175
1667	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop	2176	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop
1668	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the	2177	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
1669	only event loop modification you are allowed to do).	2178	only event loop modification you are allowed to do).
1670		2179
…		…
1700	a different time than the last time it was called (e.g. in a crond like	2209	a different time than the last time it was called (e.g. in a crond like
1701	program when the crontabs have changed).	2210	program when the crontabs have changed).
1702		2211
1703	=item ev_tstamp ev_periodic_at (ev_periodic *)	2212	=item ev_tstamp ev_periodic_at (ev_periodic *)
1704		2213
1705	When active, returns the absolute time that the watcher is supposed to	2214	When active, returns the absolute time that the watcher is supposed
1706	trigger next.	2215	to trigger next. This is not the same as the C<offset> argument to
		2216	C<ev_periodic_set>, but indeed works even in interval and manual
		2217	rescheduling modes.
1707		2218
1708	=item ev_tstamp offset [read-write]	2219	=item ev_tstamp offset [read-write]
1709		2220
1710	When repeating, this contains the offset value, otherwise this is the	2221	When repeating, this contains the offset value, otherwise this is the
1711	absolute point in time (the C<at> value passed to C<ev_periodic_set>).	2222	absolute point in time (the C<offset> value passed to C<ev_periodic_set>,
		2223	although libev might modify this value for better numerical stability).
1712		2224
1713	Can be modified any time, but changes only take effect when the periodic	2225	Can be modified any time, but changes only take effect when the periodic
1714	timer fires or C<ev_periodic_again> is being called.	2226	timer fires or C<ev_periodic_again> is being called.
1715		2227
1716	=item ev_tstamp interval [read-write]	2228	=item ev_tstamp interval [read-write]
…		…
1732	Example: Call a callback every hour, or, more precisely, whenever the	2244	Example: Call a callback every hour, or, more precisely, whenever the
1733	system time is divisible by 3600. The callback invocation times have	2245	system time is divisible by 3600. The callback invocation times have
1734	potentially a lot of jitter, but good long-term stability.	2246	potentially a lot of jitter, but good long-term stability.
1735		2247
1736	static void	2248	static void
1737	clock_cb (struct ev_loop *loop, ev_io *w, int revents)	2249	clock_cb (struct ev_loop *loop, ev_periodic *w, int revents)
1738	{	2250	{
1739	... its now a full hour (UTC, or TAI or whatever your clock follows)	2251	... its now a full hour (UTC, or TAI or whatever your clock follows)
1740	}	2252	}
1741		2253
1742	ev_periodic hourly_tick;	2254	ev_periodic hourly_tick;
…		…
1765		2277
1766	=head2 C<ev_signal> - signal me when a signal gets signalled!	2278	=head2 C<ev_signal> - signal me when a signal gets signalled!
1767		2279
1768	Signal watchers will trigger an event when the process receives a specific	2280	Signal watchers will trigger an event when the process receives a specific
1769	signal one or more times. Even though signals are very asynchronous, libev	2281	signal one or more times. Even though signals are very asynchronous, libev
1770	will try it's best to deliver signals synchronously, i.e. as part of the	2282	will try its best to deliver signals synchronously, i.e. as part of the
1771	normal event processing, like any other event.	2283	normal event processing, like any other event.
1772		2284
1773	If you want signals asynchronously, just use C<sigaction> as you would	2285	If you want signals to be delivered truly asynchronously, just use
1774	do without libev and forget about sharing the signal. You can even use	2286	C<sigaction> as you would do without libev and forget about sharing
1775	C<ev_async> from a signal handler to synchronously wake up an event loop.	2287	the signal. You can even use C<ev_async> from a signal handler to
		2288	synchronously wake up an event loop.
1776		2289
1777	You can configure as many watchers as you like per signal. Only when the	2290	You can configure as many watchers as you like for the same signal, but
		2291	only within the same loop, i.e. you can watch for C<SIGINT> in your
		2292	default loop and for C<SIGIO> in another loop, but you cannot watch for
		2293	C<SIGINT> in both the default loop and another loop at the same time. At
		2294	the moment, C<SIGCHLD> is permanently tied to the default loop.
		2295
1778	first watcher gets started will libev actually register a signal handler	2296	When the first watcher gets started will libev actually register something
1779	with the kernel (thus it coexists with your own signal handlers as long as	2297	with the kernel (thus it coexists with your own signal handlers as long as
1780	you don't register any with libev for the same signal). Similarly, when	2298	you don't register any with libev for the same signal).
1781	the last signal watcher for a signal is stopped, libev will reset the
1782	signal handler to SIG_DFL (regardless of what it was set to before).
1783		2299
1784	If possible and supported, libev will install its handlers with	2300	If possible and supported, libev will install its handlers with
1785	C<SA_RESTART> behaviour enabled, so system calls should not be unduly	2301	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
1786	interrupted. If you have a problem with system calls getting interrupted by	2302	not be unduly interrupted. If you have a problem with system calls getting
1787	signals you can block all signals in an C<ev_check> watcher and unblock	2303	interrupted by signals you can block all signals in an C<ev_check> watcher
1788	them in an C<ev_prepare> watcher.	2304	and unblock them in an C<ev_prepare> watcher.
		2305
		2306	=head3 The special problem of inheritance over fork/execve/pthread_create
		2307
		2308	Both the signal mask (C<sigprocmask>) and the signal disposition
		2309	(C<sigaction>) are unspecified after starting a signal watcher (and after
		2310	stopping it again), that is, libev might or might not block the signal,
		2311	and might or might not set or restore the installed signal handler (but
		2312	see C<EVFLAG_NOSIGMASK>).
		2313
		2314	While this does not matter for the signal disposition (libev never
		2315	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
		2316	C<execve>), this matters for the signal mask: many programs do not expect
		2317	certain signals to be blocked.
		2318
		2319	This means that before calling C<exec> (from the child) you should reset
		2320	the signal mask to whatever "default" you expect (all clear is a good
		2321	choice usually).
		2322
		2323	The simplest way to ensure that the signal mask is reset in the child is
		2324	to install a fork handler with C<pthread_atfork> that resets it. That will
		2325	catch fork calls done by libraries (such as the libc) as well.
		2326
		2327	In current versions of libev, the signal will not be blocked indefinitely
		2328	unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces
		2329	the window of opportunity for problems, it will not go away, as libev
		2330	I<has> to modify the signal mask, at least temporarily.
		2331
		2332	So I can't stress this enough: I<If you do not reset your signal mask when
		2333	you expect it to be empty, you have a race condition in your code>. This
		2334	is not a libev-specific thing, this is true for most event libraries.
		2335
		2336	=head3 The special problem of threads signal handling
		2337
		2338	POSIX threads has problematic signal handling semantics, specifically,
		2339	a lot of functionality (sigfd, sigwait etc.) only really works if all
		2340	threads in a process block signals, which is hard to achieve.
		2341
		2342	When you want to use sigwait (or mix libev signal handling with your own
		2343	for the same signals), you can tackle this problem by globally blocking
		2344	all signals before creating any threads (or creating them with a fully set
		2345	sigprocmask) and also specifying the C<EVFLAG_NOSIGMASK> when creating
		2346	loops. Then designate one thread as "signal receiver thread" which handles
		2347	these signals. You can pass on any signals that libev might be interested
		2348	in by calling C<ev_feed_signal>.
1789		2349
1790	=head3 Watcher-Specific Functions and Data Members	2350	=head3 Watcher-Specific Functions and Data Members
1791		2351
1792	=over 4	2352	=over 4
1793		2353
…		…
1809	Example: Try to exit cleanly on SIGINT.	2369	Example: Try to exit cleanly on SIGINT.
1810		2370
1811	static void	2371	static void
1812	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)	2372	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
1813	{	2373	{
1814	ev_unloop (loop, EVUNLOOP_ALL);	2374	ev_break (loop, EVBREAK_ALL);
1815	}	2375	}
1816		2376
1817	ev_signal signal_watcher;	2377	ev_signal signal_watcher;
1818	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2378	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1819	ev_signal_start (loop, &signal_watcher);	2379	ev_signal_start (loop, &signal_watcher);
…		…
1825	some child status changes (most typically when a child of yours dies or	2385	some child status changes (most typically when a child of yours dies or
1826	exits). It is permissible to install a child watcher I<after> the child	2386	exits). It is permissible to install a child watcher I<after> the child
1827	has been forked (which implies it might have already exited), as long	2387	has been forked (which implies it might have already exited), as long
1828	as the event loop isn't entered (or is continued from a watcher), i.e.,	2388	as the event loop isn't entered (or is continued from a watcher), i.e.,
1829	forking and then immediately registering a watcher for the child is fine,	2389	forking and then immediately registering a watcher for the child is fine,
1830	but forking and registering a watcher a few event loop iterations later is	2390	but forking and registering a watcher a few event loop iterations later or
1831	not.	2391	in the next callback invocation is not.
1832		2392
1833	Only the default event loop is capable of handling signals, and therefore	2393	Only the default event loop is capable of handling signals, and therefore
1834	you can only register child watchers in the default event loop.	2394	you can only register child watchers in the default event loop.
1835		2395
		2396	Due to some design glitches inside libev, child watchers will always be
		2397	handled at maximum priority (their priority is set to C<EV_MAXPRI> by
		2398	libev)
		2399
1836	=head3 Process Interaction	2400	=head3 Process Interaction
1837		2401
1838	Libev grabs C<SIGCHLD> as soon as the default event loop is	2402	Libev grabs C<SIGCHLD> as soon as the default event loop is
1839	initialised. This is necessary to guarantee proper behaviour even if	2403	initialised. This is necessary to guarantee proper behaviour even if the
1840	the first child watcher is started after the child exits. The occurrence	2404	first child watcher is started after the child exits. The occurrence
1841	of C<SIGCHLD> is recorded asynchronously, but child reaping is done	2405	of C<SIGCHLD> is recorded asynchronously, but child reaping is done
1842	synchronously as part of the event loop processing. Libev always reaps all	2406	synchronously as part of the event loop processing. Libev always reaps all
1843	children, even ones not watched.	2407	children, even ones not watched.
1844		2408
1845	=head3 Overriding the Built-In Processing	2409	=head3 Overriding the Built-In Processing
…		…
1855	=head3 Stopping the Child Watcher	2419	=head3 Stopping the Child Watcher
1856		2420
1857	Currently, the child watcher never gets stopped, even when the	2421	Currently, the child watcher never gets stopped, even when the
1858	child terminates, so normally one needs to stop the watcher in the	2422	child terminates, so normally one needs to stop the watcher in the
1859	callback. Future versions of libev might stop the watcher automatically	2423	callback. Future versions of libev might stop the watcher automatically
1860	when a child exit is detected.	2424	when a child exit is detected (calling C<ev_child_stop> twice is not a
		2425	problem).
1861		2426
1862	=head3 Watcher-Specific Functions and Data Members	2427	=head3 Watcher-Specific Functions and Data Members
1863		2428
1864	=over 4	2429	=over 4
1865		2430
…		…
1927	C<stat> on that path in regular intervals (or when the OS says it changed)	2492	C<stat> on that path in regular intervals (or when the OS says it changed)
1928	and sees if it changed compared to the last time, invoking the callback if	2493	and sees if it changed compared to the last time, invoking the callback if
1929	it did.	2494	it did.
1930		2495
1931	The path does not need to exist: changing from "path exists" to "path does	2496	The path does not need to exist: changing from "path exists" to "path does
1932	not exist" is a status change like any other. The condition "path does	2497	not exist" is a status change like any other. The condition "path does not
1933	not exist" is signified by the C<st_nlink> field being zero (which is	2498	exist" (or more correctly "path cannot be stat'ed") is signified by the
1934	otherwise always forced to be at least one) and all the other fields of	2499	C<st_nlink> field being zero (which is otherwise always forced to be at
1935	the stat buffer having unspecified contents.	2500	least one) and all the other fields of the stat buffer having unspecified
		2501	contents.
1936		2502
1937	The path I<must not> end in a slash or contain special components such as	2503	The path I<must not> end in a slash or contain special components such as
1938	C<.> or C<..>. The path I<should> be absolute: If it is relative and	2504	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1939	your working directory changes, then the behaviour is undefined.	2505	your working directory changes, then the behaviour is undefined.
1940		2506
…		…
1950	This watcher type is not meant for massive numbers of stat watchers,	2516	This watcher type is not meant for massive numbers of stat watchers,
1951	as even with OS-supported change notifications, this can be	2517	as even with OS-supported change notifications, this can be
1952	resource-intensive.	2518	resource-intensive.
1953		2519
1954	At the time of this writing, the only OS-specific interface implemented	2520	At the time of this writing, the only OS-specific interface implemented
1955	is the Linux inotify interface (implementing kqueue support is left as	2521	is the Linux inotify interface (implementing kqueue support is left as an
1956	an exercise for the reader. Note, however, that the author sees no way	2522	exercise for the reader. Note, however, that the author sees no way of
1957	of implementing C<ev_stat> semantics with kqueue).	2523	implementing C<ev_stat> semantics with kqueue, except as a hint).
1958		2524
1959	=head3 ABI Issues (Largefile Support)	2525	=head3 ABI Issues (Largefile Support)
1960		2526
1961	Libev by default (unless the user overrides this) uses the default	2527	Libev by default (unless the user overrides this) uses the default
1962	compilation environment, which means that on systems with large file	2528	compilation environment, which means that on systems with large file
…		…
1973	to exchange stat structures with application programs compiled using the	2539	to exchange stat structures with application programs compiled using the
1974	default compilation environment.	2540	default compilation environment.
1975		2541
1976	=head3 Inotify and Kqueue	2542	=head3 Inotify and Kqueue
1977		2543
1978	When C<inotify (7)> support has been compiled into libev (generally	2544	When C<inotify (7)> support has been compiled into libev and present at
1979	only available with Linux 2.6.25 or above due to bugs in earlier	2545	runtime, it will be used to speed up change detection where possible. The
1980	implementations) and present at runtime, it will be used to speed up	2546	inotify descriptor will be created lazily when the first C<ev_stat>
1981	change detection where possible. The inotify descriptor will be created	2547	watcher is being started.
1982	lazily when the first C<ev_stat> watcher is being started.
1983		2548
1984	Inotify presence does not change the semantics of C<ev_stat> watchers	2549	Inotify presence does not change the semantics of C<ev_stat> watchers
1985	except that changes might be detected earlier, and in some cases, to avoid	2550	except that changes might be detected earlier, and in some cases, to avoid
1986	making regular C<stat> calls. Even in the presence of inotify support	2551	making regular C<stat> calls. Even in the presence of inotify support
1987	there are many cases where libev has to resort to regular C<stat> polling,	2552	there are many cases where libev has to resort to regular C<stat> polling,
1988	but as long as the path exists, libev usually gets away without polling.	2553	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		2554	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		2555	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		2556	xfs are fully working) libev usually gets away without polling.
1989		2557
1990	There is no support for kqueue, as apparently it cannot be used to	2558	There is no support for kqueue, as apparently it cannot be used to
1991	implement this functionality, due to the requirement of having a file	2559	implement this functionality, due to the requirement of having a file
1992	descriptor open on the object at all times, and detecting renames, unlinks	2560	descriptor open on the object at all times, and detecting renames, unlinks
1993	etc. is difficult.	2561	etc. is difficult.
		2562
		2563	=head3 C<stat ()> is a synchronous operation
		2564
		2565	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2566	the process. The exception are C<ev_stat> watchers - those call C<stat
		2567	()>, which is a synchronous operation.
		2568
		2569	For local paths, this usually doesn't matter: unless the system is very
		2570	busy or the intervals between stat's are large, a stat call will be fast,
		2571	as the path data is usually in memory already (except when starting the
		2572	watcher).
		2573
		2574	For networked file systems, calling C<stat ()> can block an indefinite
		2575	time due to network issues, and even under good conditions, a stat call
		2576	often takes multiple milliseconds.
		2577
		2578	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2579	paths, although this is fully supported by libev.
1994		2580
1995	=head3 The special problem of stat time resolution	2581	=head3 The special problem of stat time resolution
1996		2582
1997	The C<stat ()> system call only supports full-second resolution portably,	2583	The C<stat ()> system call only supports full-second resolution portably,
1998	and even on systems where the resolution is higher, most file systems	2584	and even on systems where the resolution is higher, most file systems
…		…
2147		2733
2148	=head3 Watcher-Specific Functions and Data Members	2734	=head3 Watcher-Specific Functions and Data Members
2149		2735
2150	=over 4	2736	=over 4
2151		2737
2152	=item ev_idle_init (ev_signal *, callback)	2738	=item ev_idle_init (ev_idle *, callback)
2153		2739
2154	Initialises and configures the idle watcher - it has no parameters of any	2740	Initialises and configures the idle watcher - it has no parameters of any
2155	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	2741	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
2156	believe me.	2742	believe me.
2157		2743
…		…
2170	// no longer anything immediate to do.	2756	// no longer anything immediate to do.
2171	}	2757	}
2172		2758
2173	ev_idle *idle_watcher = malloc (sizeof (ev_idle));	2759	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
2174	ev_idle_init (idle_watcher, idle_cb);	2760	ev_idle_init (idle_watcher, idle_cb);
2175	ev_idle_start (loop, idle_cb);	2761	ev_idle_start (loop, idle_watcher);
2176		2762
2177		2763
2178	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2764	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
2179		2765
2180	Prepare and check watchers are usually (but not always) used in pairs:	2766	Prepare and check watchers are usually (but not always) used in pairs:
2181	prepare watchers get invoked before the process blocks and check watchers	2767	prepare watchers get invoked before the process blocks and check watchers
2182	afterwards.	2768	afterwards.
2183		2769
2184	You I<must not> call C<ev_loop> or similar functions that enter	2770	You I<must not> call C<ev_run> or similar functions that enter
2185	the current event loop from either C<ev_prepare> or C<ev_check>	2771	the current event loop from either C<ev_prepare> or C<ev_check>
2186	watchers. Other loops than the current one are fine, however. The	2772	watchers. Other loops than the current one are fine, however. The
2187	rationale behind this is that you do not need to check for recursion in	2773	rationale behind this is that you do not need to check for recursion in
2188	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2774	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
2189	C<ev_check> so if you have one watcher of each kind they will always be	2775	C<ev_check> so if you have one watcher of each kind they will always be
…		…
2273	struct pollfd fds [nfd];	2859	struct pollfd fds [nfd];
2274	// actual code will need to loop here and realloc etc.	2860	// actual code will need to loop here and realloc etc.
2275	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	2861	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
2276		2862
2277	/* the callback is illegal, but won't be called as we stop during check */	2863	/* the callback is illegal, but won't be called as we stop during check */
2278	ev_timer_init (&tw, 0, timeout * 1e-3);	2864	ev_timer_init (&tw, 0, timeout * 1e-3, 0.);
2279	ev_timer_start (loop, &tw);	2865	ev_timer_start (loop, &tw);
2280		2866
2281	// create one ev_io per pollfd	2867	// create one ev_io per pollfd
2282	for (int i = 0; i < nfd; ++i)	2868	for (int i = 0; i < nfd; ++i)
2283	{	2869	{
…		…
2357		2943
2358	if (timeout >= 0)	2944	if (timeout >= 0)
2359	// create/start timer	2945	// create/start timer
2360		2946
2361	// poll	2947	// poll
2362	ev_loop (EV_A_ 0);	2948	ev_run (EV_A_ 0);
2363		2949
2364	// stop timer again	2950	// stop timer again
2365	if (timeout >= 0)	2951	if (timeout >= 0)
2366	ev_timer_stop (EV_A_ &to);	2952	ev_timer_stop (EV_A_ &to);
2367		2953
…		…
2396	some fds have to be watched and handled very quickly (with low latency),	2982	some fds have to be watched and handled very quickly (with low latency),
2397	and even priorities and idle watchers might have too much overhead. In	2983	and even priorities and idle watchers might have too much overhead. In
2398	this case you would put all the high priority stuff in one loop and all	2984	this case you would put all the high priority stuff in one loop and all
2399	the rest in a second one, and embed the second one in the first.	2985	the rest in a second one, and embed the second one in the first.
2400		2986
2401	As long as the watcher is active, the callback will be invoked every time	2987	As long as the watcher is active, the callback will be invoked every
2402	there might be events pending in the embedded loop. The callback must then	2988	time there might be events pending in the embedded loop. The callback
2403	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke	2989	must then call C<ev_embed_sweep (mainloop, watcher)> to make a single
2404	their callbacks (you could also start an idle watcher to give the embedded	2990	sweep and invoke their callbacks (the callback doesn't need to invoke the
2405	loop strictly lower priority for example). You can also set the callback	2991	C<ev_embed_sweep> function directly, it could also start an idle watcher
2406	to C<0>, in which case the embed watcher will automatically execute the	2992	to give the embedded loop strictly lower priority for example).
2407	embedded loop sweep.
2408		2993
2409	As long as the watcher is started it will automatically handle events. The	2994	You can also set the callback to C<0>, in which case the embed watcher
2410	callback will be invoked whenever some events have been handled. You can	2995	will automatically execute the embedded loop sweep whenever necessary.
2411	set the callback to C<0> to avoid having to specify one if you are not
2412	interested in that.
2413		2996
2414	Also, there have not currently been made special provisions for forking:	2997	Fork detection will be handled transparently while the C<ev_embed> watcher
2415	when you fork, you not only have to call C<ev_loop_fork> on both loops,	2998	is active, i.e., the embedded loop will automatically be forked when the
2416	but you will also have to stop and restart any C<ev_embed> watchers	2999	embedding loop forks. In other cases, the user is responsible for calling
2417	yourself - but you can use a fork watcher to handle this automatically,	3000	C<ev_loop_fork> on the embedded loop.
2418	and future versions of libev might do just that.
2419		3001
2420	Unfortunately, not all backends are embeddable: only the ones returned by	3002	Unfortunately, not all backends are embeddable: only the ones returned by
2421	C<ev_embeddable_backends> are, which, unfortunately, does not include any	3003	C<ev_embeddable_backends> are, which, unfortunately, does not include any
2422	portable one.	3004	portable one.
2423		3005
…		…
2449	if you do not want that, you need to temporarily stop the embed watcher).	3031	if you do not want that, you need to temporarily stop the embed watcher).
2450		3032
2451	=item ev_embed_sweep (loop, ev_embed *)	3033	=item ev_embed_sweep (loop, ev_embed *)
2452		3034
2453	Make a single, non-blocking sweep over the embedded loop. This works	3035	Make a single, non-blocking sweep over the embedded loop. This works
2454	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most	3036	similarly to C<ev_run (embedded_loop, EVRUN_NOWAIT)>, but in the most
2455	appropriate way for embedded loops.	3037	appropriate way for embedded loops.
2456		3038
2457	=item struct ev_loop *other [read-only]	3039	=item struct ev_loop *other [read-only]
2458		3040
2459	The embedded event loop.	3041	The embedded event loop.
…		…
2517	event loop blocks next and before C<ev_check> watchers are being called,	3099	event loop blocks next and before C<ev_check> watchers are being called,
2518	and only in the child after the fork. If whoever good citizen calling	3100	and only in the child after the fork. If whoever good citizen calling
2519	C<ev_default_fork> cheats and calls it in the wrong process, the fork	3101	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2520	handlers will be invoked, too, of course.	3102	handlers will be invoked, too, of course.
2521		3103
		3104	=head3 The special problem of life after fork - how is it possible?
		3105
		3106	Most uses of C<fork()> consist of forking, then some simple calls to set
		3107	up/change the process environment, followed by a call to C<exec()>. This
		3108	sequence should be handled by libev without any problems.
		3109
		3110	This changes when the application actually wants to do event handling
		3111	in the child, or both parent in child, in effect "continuing" after the
		3112	fork.
		3113
		3114	The default mode of operation (for libev, with application help to detect
		3115	forks) is to duplicate all the state in the child, as would be expected
		3116	when I<either> the parent I<or> the child process continues.
		3117
		3118	When both processes want to continue using libev, then this is usually the
		3119	wrong result. In that case, usually one process (typically the parent) is
		3120	supposed to continue with all watchers in place as before, while the other
		3121	process typically wants to start fresh, i.e. without any active watchers.
		3122
		3123	The cleanest and most efficient way to achieve that with libev is to
		3124	simply create a new event loop, which of course will be "empty", and
		3125	use that for new watchers. This has the advantage of not touching more
		3126	memory than necessary, and thus avoiding the copy-on-write, and the
		3127	disadvantage of having to use multiple event loops (which do not support
		3128	signal watchers).
		3129
		3130	When this is not possible, or you want to use the default loop for
		3131	other reasons, then in the process that wants to start "fresh", call
		3132	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
		3133	Destroying the default loop will "orphan" (not stop) all registered
		3134	watchers, so you have to be careful not to execute code that modifies
		3135	those watchers. Note also that in that case, you have to re-register any
		3136	signal watchers.
		3137
2522	=head3 Watcher-Specific Functions and Data Members	3138	=head3 Watcher-Specific Functions and Data Members
2523		3139
2524	=over 4	3140	=over 4
2525		3141
2526	=item ev_fork_init (ev_signal *, callback)	3142	=item ev_fork_init (ev_fork *, callback)
2527		3143
2528	Initialises and configures the fork watcher - it has no parameters of any	3144	Initialises and configures the fork watcher - it has no parameters of any
2529	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3145	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
2530	believe me.	3146	really.
2531		3147
2532	=back	3148	=back
2533		3149
2534		3150
		3151	=head2 C<ev_cleanup> - even the best things end
		3152
		3153	Cleanup watchers are called just before the event loop is being destroyed
		3154	by a call to C<ev_loop_destroy>.
		3155
		3156	While there is no guarantee that the event loop gets destroyed, cleanup
		3157	watchers provide a convenient method to install cleanup hooks for your
		3158	program, worker threads and so on - you just to make sure to destroy the
		3159	loop when you want them to be invoked.
		3160
		3161	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3162	all other watchers, they do not keep a reference to the event loop (which
		3163	makes a lot of sense if you think about it). Like all other watchers, you
		3164	can call libev functions in the callback, except C<ev_cleanup_start>.
		3165
		3166	=head3 Watcher-Specific Functions and Data Members
		3167
		3168	=over 4
		3169
		3170	=item ev_cleanup_init (ev_cleanup *, callback)
		3171
		3172	Initialises and configures the cleanup watcher - it has no parameters of
		3173	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3174	pointless, I assure you.
		3175
		3176	=back
		3177
		3178	Example: Register an atexit handler to destroy the default loop, so any
		3179	cleanup functions are called.
		3180
		3181	static void
		3182	program_exits (void)
		3183	{
		3184	ev_loop_destroy (EV_DEFAULT_UC);
		3185	}
		3186
		3187	...
		3188	atexit (program_exits);
		3189
		3190
2535	=head2 C<ev_async> - how to wake up another event loop	3191	=head2 C<ev_async> - how to wake up an event loop
2536		3192
2537	In general, you cannot use an C<ev_loop> from multiple threads or other	3193	In general, you cannot use an C<ev_loop> from multiple threads or other
2538	asynchronous sources such as signal handlers (as opposed to multiple event	3194	asynchronous sources such as signal handlers (as opposed to multiple event
2539	loops - those are of course safe to use in different threads).	3195	loops - those are of course safe to use in different threads).
2540		3196
2541	Sometimes, however, you need to wake up another event loop you do not	3197	Sometimes, however, you need to wake up an event loop you do not control,
2542	control, for example because it belongs to another thread. This is what	3198	for example because it belongs to another thread. This is what C<ev_async>
2543	C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you	3199	watchers do: as long as the C<ev_async> watcher is active, you can signal
2544	can signal it by calling C<ev_async_send>, which is thread- and signal	3200	it by calling C<ev_async_send>, which is thread- and signal safe.
2545	safe.
2546		3201
2547	This functionality is very similar to C<ev_signal> watchers, as signals,	3202	This functionality is very similar to C<ev_signal> watchers, as signals,
2548	too, are asynchronous in nature, and signals, too, will be compressed	3203	too, are asynchronous in nature, and signals, too, will be compressed
2549	(i.e. the number of callback invocations may be less than the number of	3204	(i.e. the number of callback invocations may be less than the number of
2550	C<ev_async_sent> calls).	3205	C<ev_async_sent> calls). In fact, you could use signal watchers as a kind
		3206	of "global async watchers" by using a watcher on an otherwise unused
		3207	signal, and C<ev_feed_signal> to signal this watcher from another thread,
		3208	even without knowing which loop owns the signal.
2551		3209
2552	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not	3210	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not
2553	just the default loop.	3211	just the default loop.
2554		3212
2555	=head3 Queueing	3213	=head3 Queueing
2556		3214
2557	C<ev_async> does not support queueing of data in any way. The reason	3215	C<ev_async> does not support queueing of data in any way. The reason
2558	is that the author does not know of a simple (or any) algorithm for a	3216	is that the author does not know of a simple (or any) algorithm for a
2559	multiple-writer-single-reader queue that works in all cases and doesn't	3217	multiple-writer-single-reader queue that works in all cases and doesn't
2560	need elaborate support such as pthreads.	3218	need elaborate support such as pthreads or unportable memory access
		3219	semantics.
2561		3220
2562	That means that if you want to queue data, you have to provide your own	3221	That means that if you want to queue data, you have to provide your own
2563	queue. But at least I can tell you how to implement locking around your	3222	queue. But at least I can tell you how to implement locking around your
2564	queue:	3223	queue:
2565		3224
…		…
2649	trust me.	3308	trust me.
2650		3309
2651	=item ev_async_send (loop, ev_async *)	3310	=item ev_async_send (loop, ev_async *)
2652		3311
2653	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3312	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
2654	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3313	an C<EV_ASYNC> event on the watcher into the event loop, and instantly
		3314	returns.
		3315
2655	C<ev_feed_event>, this call is safe to do from other threads, signal or	3316	Unlike C<ev_feed_event>, this call is safe to do from other threads,
2656	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3317	signal or similar contexts (see the discussion of C<EV_ATOMIC_T> in the
2657	section below on what exactly this means).	3318	embedding section below on what exactly this means).
2658		3319
		3320	Note that, as with other watchers in libev, multiple events might get
		3321	compressed into a single callback invocation (another way to look at this
		3322	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,
		3323	reset when the event loop detects that).
		3324
2659	This call incurs the overhead of a system call only once per loop iteration,	3325	This call incurs the overhead of a system call only once per event loop
2660	so while the overhead might be noticeable, it doesn't apply to repeated	3326	iteration, so while the overhead might be noticeable, it doesn't apply to
2661	calls to C<ev_async_send>.	3327	repeated calls to C<ev_async_send> for the same event loop.
2662		3328
2663	=item bool = ev_async_pending (ev_async *)	3329	=item bool = ev_async_pending (ev_async *)
2664		3330
2665	Returns a non-zero value when C<ev_async_send> has been called on the	3331	Returns a non-zero value when C<ev_async_send> has been called on the
2666	watcher but the event has not yet been processed (or even noted) by the	3332	watcher but the event has not yet been processed (or even noted) by the
…		…
2669	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When	3335	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When
2670	the loop iterates next and checks for the watcher to have become active,	3336	the loop iterates next and checks for the watcher to have become active,
2671	it will reset the flag again. C<ev_async_pending> can be used to very	3337	it will reset the flag again. C<ev_async_pending> can be used to very
2672	quickly check whether invoking the loop might be a good idea.	3338	quickly check whether invoking the loop might be a good idea.
2673		3339
2674	Not that this does I<not> check whether the watcher itself is pending, only	3340	Not that this does I<not> check whether the watcher itself is pending,
2675	whether it has been requested to make this watcher pending.	3341	only whether it has been requested to make this watcher pending: there
		3342	is a time window between the event loop checking and resetting the async
		3343	notification, and the callback being invoked.
2676		3344
2677	=back	3345	=back
2678		3346
2679		3347
2680	=head1 OTHER FUNCTIONS	3348	=head1 OTHER FUNCTIONS
…		…
2697		3365
2698	If C<timeout> is less than 0, then no timeout watcher will be	3366	If C<timeout> is less than 0, then no timeout watcher will be
2699	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	3367	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
2700	repeat = 0) will be started. C<0> is a valid timeout.	3368	repeat = 0) will be started. C<0> is a valid timeout.
2701		3369
2702	The callback has the type C<void (*cb)(int revents, void *arg)> and gets	3370	The callback has the type C<void (*cb)(int revents, void *arg)> and is
2703	passed an C<revents> set like normal event callbacks (a combination of	3371	passed an C<revents> set like normal event callbacks (a combination of
2704	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	3372	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMER>) and the C<arg>
2705	value passed to C<ev_once>. Note that it is possible to receive I<both>	3373	value passed to C<ev_once>. Note that it is possible to receive I<both>
2706	a timeout and an io event at the same time - you probably should give io	3374	a timeout and an io event at the same time - you probably should give io
2707	events precedence.	3375	events precedence.
2708		3376
2709	Example: wait up to ten seconds for data to appear on STDIN_FILENO.	3377	Example: wait up to ten seconds for data to appear on STDIN_FILENO.
2710		3378
2711	static void stdin_ready (int revents, void *arg)	3379	static void stdin_ready (int revents, void *arg)
2712	{	3380	{
2713	if (revents & EV_READ)	3381	if (revents & EV_READ)
2714	/* stdin might have data for us, joy! */;	3382	/* stdin might have data for us, joy! */;
2715	else if (revents & EV_TIMEOUT)	3383	else if (revents & EV_TIMER)
2716	/* doh, nothing entered */;	3384	/* doh, nothing entered */;
2717	}	3385	}
2718		3386
2719	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3387	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
2720		3388
2721	=item ev_feed_event (struct ev_loop *, watcher *, int revents)
2722
2723	Feeds the given event set into the event loop, as if the specified event
2724	had happened for the specified watcher (which must be a pointer to an
2725	initialised but not necessarily started event watcher).
2726
2727	=item ev_feed_fd_event (struct ev_loop *, int fd, int revents)	3389	=item ev_feed_fd_event (loop, int fd, int revents)
2728		3390
2729	Feed an event on the given fd, as if a file descriptor backend detected	3391	Feed an event on the given fd, as if a file descriptor backend detected
2730	the given events it.	3392	the given events it.
2731		3393
2732	=item ev_feed_signal_event (struct ev_loop *loop, int signum)	3394	=item ev_feed_signal_event (loop, int signum)
2733		3395
2734	Feed an event as if the given signal occurred (C<loop> must be the default	3396	Feed an event as if the given signal occurred. See also C<ev_feed_signal>,
2735	loop!).	3397	which is async-safe.
2736		3398
2737	=back	3399	=back
		3400
		3401
		3402	=head1 COMMON OR USEFUL IDIOMS (OR BOTH)
		3403
		3404	This section explains some common idioms that are not immediately
		3405	obvious. Note that examples are sprinkled over the whole manual, and this
		3406	section only contains stuff that wouldn't fit anywhere else.
		3407
		3408	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
		3409
		3410	Each watcher has, by default, a C<void *data> member that you can read
		3411	or modify at any time: libev will completely ignore it. This can be used
		3412	to associate arbitrary data with your watcher. If you need more data and
		3413	don't want to allocate memory separately and store a pointer to it in that
		3414	data member, you can also "subclass" the watcher type and provide your own
		3415	data:
		3416
		3417	struct my_io
		3418	{
		3419	ev_io io;
		3420	int otherfd;
		3421	void *somedata;
		3422	struct whatever *mostinteresting;
		3423	};
		3424
		3425	...
		3426	struct my_io w;
		3427	ev_io_init (&w.io, my_cb, fd, EV_READ);
		3428
		3429	And since your callback will be called with a pointer to the watcher, you
		3430	can cast it back to your own type:
		3431
		3432	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
		3433	{
		3434	struct my_io *w = (struct my_io *)w_;
		3435	...
		3436	}
		3437
		3438	More interesting and less C-conformant ways of casting your callback
		3439	function type instead have been omitted.
		3440
		3441	=head2 BUILDING YOUR OWN COMPOSITE WATCHERS
		3442
		3443	Another common scenario is to use some data structure with multiple
		3444	embedded watchers, in effect creating your own watcher that combines
		3445	multiple libev event sources into one "super-watcher":
		3446
		3447	struct my_biggy
		3448	{
		3449	int some_data;
		3450	ev_timer t1;
		3451	ev_timer t2;
		3452	}
		3453
		3454	In this case getting the pointer to C<my_biggy> is a bit more
		3455	complicated: Either you store the address of your C<my_biggy> struct in
		3456	the C<data> member of the watcher (for woozies or C++ coders), or you need
		3457	to use some pointer arithmetic using C<offsetof> inside your watchers (for
		3458	real programmers):
		3459
		3460	#include <stddef.h>
		3461
		3462	static void
		3463	t1_cb (EV_P_ ev_timer *w, int revents)
		3464	{
		3465	struct my_biggy big = (struct my_biggy *)
		3466	(((char *)w) - offsetof (struct my_biggy, t1));
		3467	}
		3468
		3469	static void
		3470	t2_cb (EV_P_ ev_timer *w, int revents)
		3471	{
		3472	struct my_biggy big = (struct my_biggy *)
		3473	(((char *)w) - offsetof (struct my_biggy, t2));
		3474	}
		3475
		3476	=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS
		3477
		3478	Often (especially in GUI toolkits) there are places where you have
		3479	I<modal> interaction, which is most easily implemented by recursively
		3480	invoking C<ev_run>.
		3481
		3482	This brings the problem of exiting - a callback might want to finish the
		3483	main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but
		3484	a modal "Are you sure?" dialog is still waiting), or just the nested one
		3485	and not the main one (e.g. user clocked "Ok" in a modal dialog), or some
		3486	other combination: In these cases, C<ev_break> will not work alone.
		3487
		3488	The solution is to maintain "break this loop" variable for each C<ev_run>
		3489	invocation, and use a loop around C<ev_run> until the condition is
		3490	triggered, using C<EVRUN_ONCE>:
		3491
		3492	// main loop
		3493	int exit_main_loop = 0;
		3494
		3495	while (!exit_main_loop)
		3496	ev_run (EV_DEFAULT_ EVRUN_ONCE);
		3497
		3498	// in a model watcher
		3499	int exit_nested_loop = 0;
		3500
		3501	while (!exit_nested_loop)
		3502	ev_run (EV_A_ EVRUN_ONCE);
		3503
		3504	To exit from any of these loops, just set the corresponding exit variable:
		3505
		3506	// exit modal loop
		3507	exit_nested_loop = 1;
		3508
		3509	// exit main program, after modal loop is finished
		3510	exit_main_loop = 1;
		3511
		3512	// exit both
		3513	exit_main_loop = exit_nested_loop = 1;
		3514
		3515	=head2 THREAD LOCKING EXAMPLE
		3516
		3517	Here is a fictitious example of how to run an event loop in a different
		3518	thread from where callbacks are being invoked and watchers are
		3519	created/added/removed.
		3520
		3521	For a real-world example, see the C<EV::Loop::Async> perl module,
		3522	which uses exactly this technique (which is suited for many high-level
		3523	languages).
		3524
		3525	The example uses a pthread mutex to protect the loop data, a condition
		3526	variable to wait for callback invocations, an async watcher to notify the
		3527	event loop thread and an unspecified mechanism to wake up the main thread.
		3528
		3529	First, you need to associate some data with the event loop:
		3530
		3531	typedef struct {
		3532	mutex_t lock; /* global loop lock */
		3533	ev_async async_w;
		3534	thread_t tid;
		3535	cond_t invoke_cv;
		3536	} userdata;
		3537
		3538	void prepare_loop (EV_P)
		3539	{
		3540	// for simplicity, we use a static userdata struct.
		3541	static userdata u;
		3542
		3543	ev_async_init (&u->async_w, async_cb);
		3544	ev_async_start (EV_A_ &u->async_w);
		3545
		3546	pthread_mutex_init (&u->lock, 0);
		3547	pthread_cond_init (&u->invoke_cv, 0);
		3548
		3549	// now associate this with the loop
		3550	ev_set_userdata (EV_A_ u);
		3551	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		3552	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		3553
		3554	// then create the thread running ev_run
		3555	pthread_create (&u->tid, 0, l_run, EV_A);
		3556	}
		3557
		3558	The callback for the C<ev_async> watcher does nothing: the watcher is used
		3559	solely to wake up the event loop so it takes notice of any new watchers
		3560	that might have been added:
		3561
		3562	static void
		3563	async_cb (EV_P_ ev_async *w, int revents)
		3564	{
		3565	// just used for the side effects
		3566	}
		3567
		3568	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		3569	protecting the loop data, respectively.
		3570
		3571	static void
		3572	l_release (EV_P)
		3573	{
		3574	userdata *u = ev_userdata (EV_A);
		3575	pthread_mutex_unlock (&u->lock);
		3576	}
		3577
		3578	static void
		3579	l_acquire (EV_P)
		3580	{
		3581	userdata *u = ev_userdata (EV_A);
		3582	pthread_mutex_lock (&u->lock);
		3583	}
		3584
		3585	The event loop thread first acquires the mutex, and then jumps straight
		3586	into C<ev_run>:
		3587
		3588	void *
		3589	l_run (void *thr_arg)
		3590	{
		3591	struct ev_loop *loop = (struct ev_loop *)thr_arg;
		3592
		3593	l_acquire (EV_A);
		3594	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		3595	ev_run (EV_A_ 0);
		3596	l_release (EV_A);
		3597
		3598	return 0;
		3599	}
		3600
		3601	Instead of invoking all pending watchers, the C<l_invoke> callback will
		3602	signal the main thread via some unspecified mechanism (signals? pipe
		3603	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		3604	have been called (in a while loop because a) spurious wakeups are possible
		3605	and b) skipping inter-thread-communication when there are no pending
		3606	watchers is very beneficial):
		3607
		3608	static void
		3609	l_invoke (EV_P)
		3610	{
		3611	userdata *u = ev_userdata (EV_A);
		3612
		3613	while (ev_pending_count (EV_A))
		3614	{
		3615	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		3616	pthread_cond_wait (&u->invoke_cv, &u->lock);
		3617	}
		3618	}
		3619
		3620	Now, whenever the main thread gets told to invoke pending watchers, it
		3621	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		3622	thread to continue:
		3623
		3624	static void
		3625	real_invoke_pending (EV_P)
		3626	{
		3627	userdata *u = ev_userdata (EV_A);
		3628
		3629	pthread_mutex_lock (&u->lock);
		3630	ev_invoke_pending (EV_A);
		3631	pthread_cond_signal (&u->invoke_cv);
		3632	pthread_mutex_unlock (&u->lock);
		3633	}
		3634
		3635	Whenever you want to start/stop a watcher or do other modifications to an
		3636	event loop, you will now have to lock:
		3637
		3638	ev_timer timeout_watcher;
		3639	userdata *u = ev_userdata (EV_A);
		3640
		3641	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		3642
		3643	pthread_mutex_lock (&u->lock);
		3644	ev_timer_start (EV_A_ &timeout_watcher);
		3645	ev_async_send (EV_A_ &u->async_w);
		3646	pthread_mutex_unlock (&u->lock);
		3647
		3648	Note that sending the C<ev_async> watcher is required because otherwise
		3649	an event loop currently blocking in the kernel will have no knowledge
		3650	about the newly added timer. By waking up the loop it will pick up any new
		3651	watchers in the next event loop iteration.
		3652
		3653	=head2 THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS
		3654
		3655	While the overhead of a callback that e.g. schedules a thread is small, it
		3656	is still an overhead. If you embed libev, and your main usage is with some
		3657	kind of threads or coroutines, you might want to customise libev so that
		3658	doesn't need callbacks anymore.
		3659
		3660	Imagine you have coroutines that you can switch to using a function
		3661	C<switch_to (coro)>, that libev runs in a coroutine called C<libev_coro>
		3662	and that due to some magic, the currently active coroutine is stored in a
		3663	global called C<current_coro>. Then you can build your own "wait for libev
		3664	event" primitive by changing C<EV_CB_DECLARE> and C<EV_CB_INVOKE> (note
		3665	the differing C<;> conventions):
		3666
		3667	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3668	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb)
		3669
		3670	That means instead of having a C callback function, you store the
		3671	coroutine to switch to in each watcher, and instead of having libev call
		3672	your callback, you instead have it switch to that coroutine.
		3673
		3674	A coroutine might now wait for an event with a function called
		3675	C<wait_for_event>. (the watcher needs to be started, as always, but it doesn't
		3676	matter when, or whether the watcher is active or not when this function is
		3677	called):
		3678
		3679	void
		3680	wait_for_event (ev_watcher *w)
		3681	{
		3682	ev_cb_set (w) = current_coro;
		3683	switch_to (libev_coro);
		3684	}
		3685
		3686	That basically suspends the coroutine inside C<wait_for_event> and
		3687	continues the libev coroutine, which, when appropriate, switches back to
		3688	this or any other coroutine. I am sure if you sue this your own :)
		3689
		3690	You can do similar tricks if you have, say, threads with an event queue -
		3691	instead of storing a coroutine, you store the queue object and instead of
		3692	switching to a coroutine, you push the watcher onto the queue and notify
		3693	any waiters.
		3694
		3695	To embed libev, see L<EMBEDDING>, but in short, it's easiest to create two
		3696	files, F<my_ev.h> and F<my_ev.c> that include the respective libev files:
		3697
		3698	// my_ev.h
		3699	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3700	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb);
		3701	#include "../libev/ev.h"
		3702
		3703	// my_ev.c
		3704	#define EV_H "my_ev.h"
		3705	#include "../libev/ev.c"
		3706
		3707	And then use F<my_ev.h> when you would normally use F<ev.h>, and compile
		3708	F<my_ev.c> into your project. When properly specifying include paths, you
		3709	can even use F<ev.h> as header file name directly.
2738		3710
2739		3711
2740	=head1 LIBEVENT EMULATION	3712	=head1 LIBEVENT EMULATION
2741		3713
2742	Libev offers a compatibility emulation layer for libevent. It cannot	3714	Libev offers a compatibility emulation layer for libevent. It cannot
2743	emulate the internals of libevent, so here are some usage hints:	3715	emulate the internals of libevent, so here are some usage hints:
2744		3716
2745	=over 4	3717	=over 4
		3718
		3719	=item * Only the libevent-1.4.1-beta API is being emulated.
		3720
		3721	This was the newest libevent version available when libev was implemented,
		3722	and is still mostly unchanged in 2010.
2746		3723
2747	=item * Use it by including <event.h>, as usual.	3724	=item * Use it by including <event.h>, as usual.
2748		3725
2749	=item * The following members are fully supported: ev_base, ev_callback,	3726	=item * The following members are fully supported: ev_base, ev_callback,
2750	ev_arg, ev_fd, ev_res, ev_events.	3727	ev_arg, ev_fd, ev_res, ev_events.
…		…
2756	=item * Priorities are not currently supported. Initialising priorities	3733	=item * Priorities are not currently supported. Initialising priorities
2757	will fail and all watchers will have the same priority, even though there	3734	will fail and all watchers will have the same priority, even though there
2758	is an ev_pri field.	3735	is an ev_pri field.
2759		3736
2760	=item * In libevent, the last base created gets the signals, in libev, the	3737	=item * In libevent, the last base created gets the signals, in libev, the
2761	first base created (== the default loop) gets the signals.	3738	base that registered the signal gets the signals.
2762		3739
2763	=item * Other members are not supported.	3740	=item * Other members are not supported.
2764		3741
2765	=item * The libev emulation is I<not> ABI compatible to libevent, you need	3742	=item * The libev emulation is I<not> ABI compatible to libevent, you need
2766	to use the libev header file and library.	3743	to use the libev header file and library.
…		…
2785	Care has been taken to keep the overhead low. The only data member the C++	3762	Care has been taken to keep the overhead low. The only data member the C++
2786	classes add (compared to plain C-style watchers) is the event loop pointer	3763	classes add (compared to plain C-style watchers) is the event loop pointer
2787	that the watcher is associated with (or no additional members at all if	3764	that the watcher is associated with (or no additional members at all if
2788	you disable C<EV_MULTIPLICITY> when embedding libev).	3765	you disable C<EV_MULTIPLICITY> when embedding libev).
2789		3766
2790	Currently, functions, and static and non-static member functions can be	3767	Currently, functions, static and non-static member functions and classes
2791	used as callbacks. Other types should be easy to add as long as they only	3768	with C<operator ()> can be used as callbacks. Other types should be easy
2792	need one additional pointer for context. If you need support for other	3769	to add as long as they only need one additional pointer for context. If
2793	types of functors please contact the author (preferably after implementing	3770	you need support for other types of functors please contact the author
2794	it).	3771	(preferably after implementing it).
2795		3772
2796	Here is a list of things available in the C<ev> namespace:	3773	Here is a list of things available in the C<ev> namespace:
2797		3774
2798	=over 4	3775	=over 4
2799		3776
…		…
2817		3794
2818	=over 4	3795	=over 4
2819		3796
2820	=item ev::TYPE::TYPE ()	3797	=item ev::TYPE::TYPE ()
2821		3798
2822	=item ev::TYPE::TYPE (struct ev_loop *)	3799	=item ev::TYPE::TYPE (loop)
2823		3800
2824	=item ev::TYPE::~TYPE	3801	=item ev::TYPE::~TYPE
2825		3802
2826	The constructor (optionally) takes an event loop to associate the watcher	3803	The constructor (optionally) takes an event loop to associate the watcher
2827	with. If it is omitted, it will use C<EV_DEFAULT>.	3804	with. If it is omitted, it will use C<EV_DEFAULT>.
…		…
2859		3836
2860	myclass obj;	3837	myclass obj;
2861	ev::io iow;	3838	ev::io iow;
2862	iow.set <myclass, &myclass::io_cb> (&obj);	3839	iow.set <myclass, &myclass::io_cb> (&obj);
2863		3840
		3841	=item w->set (object *)
		3842
		3843	This is a variation of a method callback - leaving out the method to call
		3844	will default the method to C<operator ()>, which makes it possible to use
		3845	functor objects without having to manually specify the C<operator ()> all
		3846	the time. Incidentally, you can then also leave out the template argument
		3847	list.
		3848
		3849	The C<operator ()> method prototype must be C<void operator ()(watcher &w,
		3850	int revents)>.
		3851
		3852	See the method-C<set> above for more details.
		3853
		3854	Example: use a functor object as callback.
		3855
		3856	struct myfunctor
		3857	{
		3858	void operator() (ev::io &w, int revents)
		3859	{
		3860	...
		3861	}
		3862	}
		3863
		3864	myfunctor f;
		3865
		3866	ev::io w;
		3867	w.set (&f);
		3868
2864	=item w->set<function> (void *data = 0)	3869	=item w->set<function> (void *data = 0)
2865		3870
2866	Also sets a callback, but uses a static method or plain function as	3871	Also sets a callback, but uses a static method or plain function as
2867	callback. The optional C<data> argument will be stored in the watcher's	3872	callback. The optional C<data> argument will be stored in the watcher's
2868	C<data> member and is free for you to use.	3873	C<data> member and is free for you to use.
…		…
2874	Example: Use a plain function as callback.	3879	Example: Use a plain function as callback.
2875		3880
2876	static void io_cb (ev::io &w, int revents) { }	3881	static void io_cb (ev::io &w, int revents) { }
2877	iow.set <io_cb> ();	3882	iow.set <io_cb> ();
2878		3883
2879	=item w->set (struct ev_loop *)	3884	=item w->set (loop)
2880		3885
2881	Associates a different C<struct ev_loop> with this watcher. You can only	3886	Associates a different C<struct ev_loop> with this watcher. You can only
2882	do this when the watcher is inactive (and not pending either).	3887	do this when the watcher is inactive (and not pending either).
2883		3888
2884	=item w->set ([arguments])	3889	=item w->set ([arguments])
2885		3890
2886	Basically the same as C<ev_TYPE_set>, with the same arguments. Must be	3891	Basically the same as C<ev_TYPE_set>, with the same arguments. Either this
2887	called at least once. Unlike the C counterpart, an active watcher gets	3892	method or a suitable start method must be called at least once. Unlike the
2888	automatically stopped and restarted when reconfiguring it with this	3893	C counterpart, an active watcher gets automatically stopped and restarted
2889	method.	3894	when reconfiguring it with this method.
2890		3895
2891	=item w->start ()	3896	=item w->start ()
2892		3897
2893	Starts the watcher. Note that there is no C<loop> argument, as the	3898	Starts the watcher. Note that there is no C<loop> argument, as the
2894	constructor already stores the event loop.	3899	constructor already stores the event loop.
2895		3900
		3901	=item w->start ([arguments])
		3902
		3903	Instead of calling C<set> and C<start> methods separately, it is often
		3904	convenient to wrap them in one call. Uses the same type of arguments as
		3905	the configure C<set> method of the watcher.
		3906
2896	=item w->stop ()	3907	=item w->stop ()
2897		3908
2898	Stops the watcher if it is active. Again, no C<loop> argument.	3909	Stops the watcher if it is active. Again, no C<loop> argument.
2899		3910
2900	=item w->again () (C<ev::timer>, C<ev::periodic> only)	3911	=item w->again () (C<ev::timer>, C<ev::periodic> only)
…		…
2912		3923
2913	=back	3924	=back
2914		3925
2915	=back	3926	=back
2916		3927
2917	Example: Define a class with an IO and idle watcher, start one of them in	3928	Example: Define a class with two I/O and idle watchers, start the I/O
2918	the constructor.	3929	watchers in the constructor.
2919		3930
2920	class myclass	3931	class myclass
2921	{	3932	{
2922	ev::io io ; void io_cb (ev::io &w, int revents);	3933	ev::io io ; void io_cb (ev::io &w, int revents);
		3934	ev::io2 io2 ; void io2_cb (ev::io &w, int revents);
2923	ev::idle idle; void idle_cb (ev::idle &w, int revents);	3935	ev::idle idle; void idle_cb (ev::idle &w, int revents);
2924		3936
2925	myclass (int fd)	3937	myclass (int fd)
2926	{	3938	{
2927	io .set <myclass, &myclass::io_cb > (this);	3939	io .set <myclass, &myclass::io_cb > (this);
		3940	io2 .set <myclass, &myclass::io2_cb > (this);
2928	idle.set <myclass, &myclass::idle_cb> (this);	3941	idle.set <myclass, &myclass::idle_cb> (this);
2929		3942
2930	io.start (fd, ev::READ);	3943	io.set (fd, ev::WRITE); // configure the watcher
		3944	io.start (); // start it whenever convenient
		3945
		3946	io2.start (fd, ev::READ); // set + start in one call
2931	}	3947	}
2932	};	3948	};
2933		3949
2934		3950
2935	=head1 OTHER LANGUAGE BINDINGS	3951	=head1 OTHER LANGUAGE BINDINGS
…		…
2954	L<http://software.schmorp.de/pkg/EV>.	3970	L<http://software.schmorp.de/pkg/EV>.
2955		3971
2956	=item Python	3972	=item Python
2957		3973
2958	Python bindings can be found at L<http://code.google.com/p/pyev/>. It	3974	Python bindings can be found at L<http://code.google.com/p/pyev/>. It
2959	seems to be quite complete and well-documented. Note, however, that the	3975	seems to be quite complete and well-documented.
2960	patch they require for libev is outright dangerous as it breaks the ABI
2961	for everybody else, and therefore, should never be applied in an installed
2962	libev (if python requires an incompatible ABI then it needs to embed
2963	libev).
2964		3976
2965	=item Ruby	3977	=item Ruby
2966		3978
2967	Tony Arcieri has written a ruby extension that offers access to a subset	3979	Tony Arcieri has written a ruby extension that offers access to a subset
2968	of the libev API and adds file handle abstractions, asynchronous DNS and	3980	of the libev API and adds file handle abstractions, asynchronous DNS and
2969	more on top of it. It can be found via gem servers. Its homepage is at	3981	more on top of it. It can be found via gem servers. Its homepage is at
2970	L<http://rev.rubyforge.org/>.	3982	L<http://rev.rubyforge.org/>.
2971		3983
		3984	Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190>
		3985	makes rev work even on mingw.
		3986
		3987	=item Haskell
		3988
		3989	A haskell binding to libev is available at
		3990	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.
		3991
2972	=item D	3992	=item D
2973		3993
2974	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3994	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2975	be found at L<http://proj.llucax.com.ar/wiki/evd>.	3995	be found at L<http://proj.llucax.com.ar/wiki/evd>.
2976		3996
2977	=item Ocaml	3997	=item Ocaml
2978		3998
2979	Erkki Seppala has written Ocaml bindings for libev, to be found at	3999	Erkki Seppala has written Ocaml bindings for libev, to be found at
2980	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.	4000	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
		4001
		4002	=item Lua
		4003
		4004	Brian Maher has written a partial interface to libev for lua (at the
		4005	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
		4006	L<http://github.com/brimworks/lua-ev>.
2981		4007
2982	=back	4008	=back
2983		4009
2984		4010
2985	=head1 MACRO MAGIC	4011	=head1 MACRO MAGIC
…		…
2999	loop argument"). The C<EV_A> form is used when this is the sole argument,	4025	loop argument"). The C<EV_A> form is used when this is the sole argument,
3000	C<EV_A_> is used when other arguments are following. Example:	4026	C<EV_A_> is used when other arguments are following. Example:
3001		4027
3002	ev_unref (EV_A);	4028	ev_unref (EV_A);
3003	ev_timer_add (EV_A_ watcher);	4029	ev_timer_add (EV_A_ watcher);
3004	ev_loop (EV_A_ 0);	4030	ev_run (EV_A_ 0);
3005		4031
3006	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,	4032	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
3007	which is often provided by the following macro.	4033	which is often provided by the following macro.
3008		4034
3009	=item C<EV_P>, C<EV_P_>	4035	=item C<EV_P>, C<EV_P_>
…		…
3049	}	4075	}
3050		4076
3051	ev_check check;	4077	ev_check check;
3052	ev_check_init (&check, check_cb);	4078	ev_check_init (&check, check_cb);
3053	ev_check_start (EV_DEFAULT_ &check);	4079	ev_check_start (EV_DEFAULT_ &check);
3054	ev_loop (EV_DEFAULT_ 0);	4080	ev_run (EV_DEFAULT_ 0);
3055		4081
3056	=head1 EMBEDDING	4082	=head1 EMBEDDING
3057		4083
3058	Libev can (and often is) directly embedded into host	4084	Libev can (and often is) directly embedded into host
3059	applications. Examples of applications that embed it include the Deliantra	4085	applications. Examples of applications that embed it include the Deliantra
…		…
3139	libev.m4	4165	libev.m4
3140		4166
3141	=head2 PREPROCESSOR SYMBOLS/MACROS	4167	=head2 PREPROCESSOR SYMBOLS/MACROS
3142		4168
3143	Libev can be configured via a variety of preprocessor symbols you have to	4169	Libev can be configured via a variety of preprocessor symbols you have to
3144	define before including any of its files. The default in the absence of	4170	define before including (or compiling) any of its files. The default in
3145	autoconf is documented for every option.	4171	the absence of autoconf is documented for every option.
		4172
		4173	Symbols marked with "(h)" do not change the ABI, and can have different
		4174	values when compiling libev vs. including F<ev.h>, so it is permissible
		4175	to redefine them before including F<ev.h> without breaking compatibility
		4176	to a compiled library. All other symbols change the ABI, which means all
		4177	users of libev and the libev code itself must be compiled with compatible
		4178	settings.
3146		4179
3147	=over 4	4180	=over 4
3148		4181
		4182	=item EV_COMPAT3 (h)
		4183
		4184	Backwards compatibility is a major concern for libev. This is why this
		4185	release of libev comes with wrappers for the functions and symbols that
		4186	have been renamed between libev version 3 and 4.
		4187
		4188	You can disable these wrappers (to test compatibility with future
		4189	versions) by defining C<EV_COMPAT3> to C<0> when compiling your
		4190	sources. This has the additional advantage that you can drop the C<struct>
		4191	from C<struct ev_loop> declarations, as libev will provide an C<ev_loop>
		4192	typedef in that case.
		4193
		4194	In some future version, the default for C<EV_COMPAT3> will become C<0>,
		4195	and in some even more future version the compatibility code will be
		4196	removed completely.
		4197
3149	=item EV_STANDALONE	4198	=item EV_STANDALONE (h)
3150		4199
3151	Must always be C<1> if you do not use autoconf configuration, which	4200	Must always be C<1> if you do not use autoconf configuration, which
3152	keeps libev from including F<config.h>, and it also defines dummy	4201	keeps libev from including F<config.h>, and it also defines dummy
3153	implementations for some libevent functions (such as logging, which is not	4202	implementations for some libevent functions (such as logging, which is not
3154	supported). It will also not define any of the structs usually found in	4203	supported). It will also not define any of the structs usually found in
3155	F<event.h> that are not directly supported by the libev core alone.	4204	F<event.h> that are not directly supported by the libev core alone.
3156		4205
		4206	In standalone mode, libev will still try to automatically deduce the
		4207	configuration, but has to be more conservative.
		4208
3157	=item EV_USE_MONOTONIC	4209	=item EV_USE_MONOTONIC
3158		4210
3159	If defined to be C<1>, libev will try to detect the availability of the	4211	If defined to be C<1>, libev will try to detect the availability of the
3160	monotonic clock option at both compile time and runtime. Otherwise no use	4212	monotonic clock option at both compile time and runtime. Otherwise no
3161	of the monotonic clock option will be attempted. If you enable this, you	4213	use of the monotonic clock option will be attempted. If you enable this,
3162	usually have to link against librt or something similar. Enabling it when	4214	you usually have to link against librt or something similar. Enabling it
3163	the functionality isn't available is safe, though, although you have	4215	when the functionality isn't available is safe, though, although you have
3164	to make sure you link against any libraries where the C<clock_gettime>	4216	to make sure you link against any libraries where the C<clock_gettime>
3165	function is hiding in (often F<-lrt>).	4217	function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>.
3166		4218
3167	=item EV_USE_REALTIME	4219	=item EV_USE_REALTIME
3168		4220
3169	If defined to be C<1>, libev will try to detect the availability of the	4221	If defined to be C<1>, libev will try to detect the availability of the
3170	real-time clock option at compile time (and assume its availability at	4222	real-time clock option at compile time (and assume its availability
3171	runtime if successful). Otherwise no use of the real-time clock option will	4223	at runtime if successful). Otherwise no use of the real-time clock
3172	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	4224	option will be attempted. This effectively replaces C<gettimeofday>
3173	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	4225	by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect
3174	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	4226	correctness. See the note about libraries in the description of
		4227	C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of
		4228	C<EV_USE_CLOCK_SYSCALL>.
		4229
		4230	=item EV_USE_CLOCK_SYSCALL
		4231
		4232	If defined to be C<1>, libev will try to use a direct syscall instead
		4233	of calling the system-provided C<clock_gettime> function. This option
		4234	exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt>
		4235	unconditionally pulls in C<libpthread>, slowing down single-threaded
		4236	programs needlessly. Using a direct syscall is slightly slower (in
		4237	theory), because no optimised vdso implementation can be used, but avoids
		4238	the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or
		4239	higher, as it simplifies linking (no need for C<-lrt>).
3175		4240
3176	=item EV_USE_NANOSLEEP	4241	=item EV_USE_NANOSLEEP
3177		4242
3178	If defined to be C<1>, libev will assume that C<nanosleep ()> is available	4243	If defined to be C<1>, libev will assume that C<nanosleep ()> is available
3179	and will use it for delays. Otherwise it will use C<select ()>.	4244	and will use it for delays. Otherwise it will use C<select ()>.
…		…
3195		4260
3196	=item EV_SELECT_USE_FD_SET	4261	=item EV_SELECT_USE_FD_SET
3197		4262
3198	If defined to C<1>, then the select backend will use the system C<fd_set>	4263	If defined to C<1>, then the select backend will use the system C<fd_set>
3199	structure. This is useful if libev doesn't compile due to a missing	4264	structure. This is useful if libev doesn't compile due to a missing
3200	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on	4265	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout
3201	exotic systems. This usually limits the range of file descriptors to some	4266	on exotic systems. This usually limits the range of file descriptors to
3202	low limit such as 1024 or might have other limitations (winsocket only	4267	some low limit such as 1024 or might have other limitations (winsocket
3203	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	4268	only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
3204	influence the size of the C<fd_set> used.	4269	configures the maximum size of the C<fd_set>.
3205		4270
3206	=item EV_SELECT_IS_WINSOCKET	4271	=item EV_SELECT_IS_WINSOCKET
3207		4272
3208	When defined to C<1>, the select backend will assume that	4273	When defined to C<1>, the select backend will assume that
3209	select/socket/connect etc. don't understand file descriptors but	4274	select/socket/connect etc. don't understand file descriptors but
…		…
3211	be used is the winsock select). This means that it will call	4276	be used is the winsock select). This means that it will call
3212	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,	4277	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
3213	it is assumed that all these functions actually work on fds, even	4278	it is assumed that all these functions actually work on fds, even
3214	on win32. Should not be defined on non-win32 platforms.	4279	on win32. Should not be defined on non-win32 platforms.
3215		4280
3216	=item EV_FD_TO_WIN32_HANDLE	4281	=item EV_FD_TO_WIN32_HANDLE(fd)
3217		4282
3218	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map	4283	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map
3219	file descriptors to socket handles. When not defining this symbol (the	4284	file descriptors to socket handles. When not defining this symbol (the
3220	default), then libev will call C<_get_osfhandle>, which is usually	4285	default), then libev will call C<_get_osfhandle>, which is usually
3221	correct. In some cases, programs use their own file descriptor management,	4286	correct. In some cases, programs use their own file descriptor management,
3222	in which case they can provide this function to map fds to socket handles.	4287	in which case they can provide this function to map fds to socket handles.
		4288
		4289	=item EV_WIN32_HANDLE_TO_FD(handle)
		4290
		4291	If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors
		4292	using the standard C<_open_osfhandle> function. For programs implementing
		4293	their own fd to handle mapping, overwriting this function makes it easier
		4294	to do so. This can be done by defining this macro to an appropriate value.
		4295
		4296	=item EV_WIN32_CLOSE_FD(fd)
		4297
		4298	If programs implement their own fd to handle mapping on win32, then this
		4299	macro can be used to override the C<close> function, useful to unregister
		4300	file descriptors again. Note that the replacement function has to close
		4301	the underlying OS handle.
3223		4302
3224	=item EV_USE_POLL	4303	=item EV_USE_POLL
3225		4304
3226	If defined to be C<1>, libev will compile in support for the C<poll>(2)	4305	If defined to be C<1>, libev will compile in support for the C<poll>(2)
3227	backend. Otherwise it will be enabled on non-win32 platforms. It	4306	backend. Otherwise it will be enabled on non-win32 platforms. It
…		…
3274	as well as for signal and thread safety in C<ev_async> watchers.	4353	as well as for signal and thread safety in C<ev_async> watchers.
3275		4354
3276	In the absence of this define, libev will use C<sig_atomic_t volatile>	4355	In the absence of this define, libev will use C<sig_atomic_t volatile>
3277	(from F<signal.h>), which is usually good enough on most platforms.	4356	(from F<signal.h>), which is usually good enough on most platforms.
3278		4357
3279	=item EV_H	4358	=item EV_H (h)
3280		4359
3281	The name of the F<ev.h> header file used to include it. The default if	4360	The name of the F<ev.h> header file used to include it. The default if
3282	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be	4361	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
3283	used to virtually rename the F<ev.h> header file in case of conflicts.	4362	used to virtually rename the F<ev.h> header file in case of conflicts.
3284		4363
3285	=item EV_CONFIG_H	4364	=item EV_CONFIG_H (h)
3286		4365
3287	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override	4366	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
3288	F<ev.c>'s idea of where to find the F<config.h> file, similarly to	4367	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
3289	C<EV_H>, above.	4368	C<EV_H>, above.
3290		4369
3291	=item EV_EVENT_H	4370	=item EV_EVENT_H (h)
3292		4371
3293	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea	4372	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
3294	of how the F<event.h> header can be found, the default is C<"event.h">.	4373	of how the F<event.h> header can be found, the default is C<"event.h">.
3295		4374
3296	=item EV_PROTOTYPES	4375	=item EV_PROTOTYPES (h)
3297		4376
3298	If defined to be C<0>, then F<ev.h> will not define any function	4377	If defined to be C<0>, then F<ev.h> will not define any function
3299	prototypes, but still define all the structs and other symbols. This is	4378	prototypes, but still define all the structs and other symbols. This is
3300	occasionally useful if you want to provide your own wrapper functions	4379	occasionally useful if you want to provide your own wrapper functions
3301	around libev functions.	4380	around libev functions.
…		…
3323	fine.	4402	fine.
3324		4403
3325	If your embedding application does not need any priorities, defining these	4404	If your embedding application does not need any priorities, defining these
3326	both to C<0> will save some memory and CPU.	4405	both to C<0> will save some memory and CPU.
3327		4406
3328	=item EV_PERIODIC_ENABLE	4407	=item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE,
		4408	EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE,
		4409	EV_ASYNC_ENABLE, EV_CHILD_ENABLE.
3329		4410
3330	If undefined or defined to be C<1>, then periodic timers are supported. If	4411	If undefined or defined to be C<1> (and the platform supports it), then
3331	defined to be C<0>, then they are not. Disabling them saves a few kB of	4412	the respective watcher type is supported. If defined to be C<0>, then it
3332	code.	4413	is not. Disabling watcher types mainly saves code size.
3333		4414
3334	=item EV_IDLE_ENABLE	4415	=item EV_FEATURES
3335
3336	If undefined or defined to be C<1>, then idle watchers are supported. If
3337	defined to be C<0>, then they are not. Disabling them saves a few kB of
3338	code.
3339
3340	=item EV_EMBED_ENABLE
3341
3342	If undefined or defined to be C<1>, then embed watchers are supported. If
3343	defined to be C<0>, then they are not. Embed watchers rely on most other
3344	watcher types, which therefore must not be disabled.
3345
3346	=item EV_STAT_ENABLE
3347
3348	If undefined or defined to be C<1>, then stat watchers are supported. If
3349	defined to be C<0>, then they are not.
3350
3351	=item EV_FORK_ENABLE
3352
3353	If undefined or defined to be C<1>, then fork watchers are supported. If
3354	defined to be C<0>, then they are not.
3355
3356	=item EV_ASYNC_ENABLE
3357
3358	If undefined or defined to be C<1>, then async watchers are supported. If
3359	defined to be C<0>, then they are not.
3360
3361	=item EV_MINIMAL
3362		4416
3363	If you need to shave off some kilobytes of code at the expense of some	4417	If you need to shave off some kilobytes of code at the expense of some
3364	speed, define this symbol to C<1>. Currently this is used to override some	4418	speed (but with the full API), you can define this symbol to request
3365	inlining decisions, saves roughly 30% code size on amd64. It also selects a	4419	certain subsets of functionality. The default is to enable all features
3366	much smaller 2-heap for timer management over the default 4-heap.	4420	that can be enabled on the platform.
		4421
		4422	A typical way to use this symbol is to define it to C<0> (or to a bitset
		4423	with some broad features you want) and then selectively re-enable
		4424	additional parts you want, for example if you want everything minimal,
		4425	but multiple event loop support, async and child watchers and the poll
		4426	backend, use this:
		4427
		4428	#define EV_FEATURES 0
		4429	#define EV_MULTIPLICITY 1
		4430	#define EV_USE_POLL 1
		4431	#define EV_CHILD_ENABLE 1
		4432	#define EV_ASYNC_ENABLE 1
		4433
		4434	The actual value is a bitset, it can be a combination of the following
		4435	values:
		4436
		4437	=over 4
		4438
		4439	=item C<1> - faster/larger code
		4440
		4441	Use larger code to speed up some operations.
		4442
		4443	Currently this is used to override some inlining decisions (enlarging the
		4444	code size by roughly 30% on amd64).
		4445
		4446	When optimising for size, use of compiler flags such as C<-Os> with
		4447	gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of
		4448	assertions.
		4449
		4450	=item C<2> - faster/larger data structures
		4451
		4452	Replaces the small 2-heap for timer management by a faster 4-heap, larger
		4453	hash table sizes and so on. This will usually further increase code size
		4454	and can additionally have an effect on the size of data structures at
		4455	runtime.
		4456
		4457	=item C<4> - full API configuration
		4458
		4459	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
		4460	enables multiplicity (C<EV_MULTIPLICITY>=1).
		4461
		4462	=item C<8> - full API
		4463
		4464	This enables a lot of the "lesser used" API functions. See C<ev.h> for
		4465	details on which parts of the API are still available without this
		4466	feature, and do not complain if this subset changes over time.
		4467
		4468	=item C<16> - enable all optional watcher types
		4469
		4470	Enables all optional watcher types. If you want to selectively enable
		4471	only some watcher types other than I/O and timers (e.g. prepare,
		4472	embed, async, child...) you can enable them manually by defining
		4473	C<EV_watchertype_ENABLE> to C<1> instead.
		4474
		4475	=item C<32> - enable all backends
		4476
		4477	This enables all backends - without this feature, you need to enable at
		4478	least one backend manually (C<EV_USE_SELECT> is a good choice).
		4479
		4480	=item C<64> - enable OS-specific "helper" APIs
		4481
		4482	Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by
		4483	default.
		4484
		4485	=back
		4486
		4487	Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0>
		4488	reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb
		4489	code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O
		4490	watchers, timers and monotonic clock support.
		4491
		4492	With an intelligent-enough linker (gcc+binutils are intelligent enough
		4493	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
		4494	your program might be left out as well - a binary starting a timer and an
		4495	I/O watcher then might come out at only 5Kb.
		4496
		4497	=item EV_AVOID_STDIO
		4498
		4499	If this is set to C<1> at compiletime, then libev will avoid using stdio
		4500	functions (printf, scanf, perror etc.). This will increase the code size
		4501	somewhat, but if your program doesn't otherwise depend on stdio and your
		4502	libc allows it, this avoids linking in the stdio library which is quite
		4503	big.
		4504
		4505	Note that error messages might become less precise when this option is
		4506	enabled.
		4507
		4508	=item EV_NSIG
		4509
		4510	The highest supported signal number, +1 (or, the number of
		4511	signals): Normally, libev tries to deduce the maximum number of signals
		4512	automatically, but sometimes this fails, in which case it can be
		4513	specified. Also, using a lower number than detected (C<32> should be
		4514	good for about any system in existence) can save some memory, as libev
		4515	statically allocates some 12-24 bytes per signal number.
3367		4516
3368	=item EV_PID_HASHSIZE	4517	=item EV_PID_HASHSIZE
3369		4518
3370	C<ev_child> watchers use a small hash table to distribute workload by	4519	C<ev_child> watchers use a small hash table to distribute workload by
3371	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	4520	pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled),
3372	than enough. If you need to manage thousands of children you might want to	4521	usually more than enough. If you need to manage thousands of children you
3373	increase this value (I<must> be a power of two).	4522	might want to increase this value (I<must> be a power of two).
3374		4523
3375	=item EV_INOTIFY_HASHSIZE	4524	=item EV_INOTIFY_HASHSIZE
3376		4525
3377	C<ev_stat> watchers use a small hash table to distribute workload by	4526	C<ev_stat> watchers use a small hash table to distribute workload by
3378	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	4527	inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES>
3379	usually more than enough. If you need to manage thousands of C<ev_stat>	4528	disabled), usually more than enough. If you need to manage thousands of
3380	watchers you might want to increase this value (I<must> be a power of	4529	C<ev_stat> watchers you might want to increase this value (I<must> be a
3381	two).	4530	power of two).
3382		4531
3383	=item EV_USE_4HEAP	4532	=item EV_USE_4HEAP
3384		4533
3385	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4534	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3386	timer and periodics heaps, libev uses a 4-heap when this symbol is defined	4535	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
3387	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably	4536	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
3388	faster performance with many (thousands) of watchers.	4537	faster performance with many (thousands) of watchers.
3389		4538
3390	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4539	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3391	(disabled).	4540	will be C<0>.
3392		4541
3393	=item EV_HEAP_CACHE_AT	4542	=item EV_HEAP_CACHE_AT
3394		4543
3395	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4544	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3396	timer and periodics heaps, libev can cache the timestamp (I<at>) within	4545	timer and periodics heaps, libev can cache the timestamp (I<at>) within
3397	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),	4546	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
3398	which uses 8-12 bytes more per watcher and a few hundred bytes more code,	4547	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
3399	but avoids random read accesses on heap changes. This improves performance	4548	but avoids random read accesses on heap changes. This improves performance
3400	noticeably with many (hundreds) of watchers.	4549	noticeably with many (hundreds) of watchers.
3401		4550
3402	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4551	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3403	(disabled).	4552	will be C<0>.
3404		4553
3405	=item EV_VERIFY	4554	=item EV_VERIFY
3406		4555
3407	Controls how much internal verification (see C<ev_loop_verify ()>) will	4556	Controls how much internal verification (see C<ev_verify ()>) will
3408	be done: If set to C<0>, no internal verification code will be compiled	4557	be done: If set to C<0>, no internal verification code will be compiled
3409	in. If set to C<1>, then verification code will be compiled in, but not	4558	in. If set to C<1>, then verification code will be compiled in, but not
3410	called. If set to C<2>, then the internal verification code will be	4559	called. If set to C<2>, then the internal verification code will be
3411	called once per loop, which can slow down libev. If set to C<3>, then the	4560	called once per loop, which can slow down libev. If set to C<3>, then the
3412	verification code will be called very frequently, which will slow down	4561	verification code will be called very frequently, which will slow down
3413	libev considerably.	4562	libev considerably.
3414		4563
3415	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be	4564	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3416	C<0>.	4565	will be C<0>.
3417		4566
3418	=item EV_COMMON	4567	=item EV_COMMON
3419		4568
3420	By default, all watchers have a C<void *data> member. By redefining	4569	By default, all watchers have a C<void *data> member. By redefining
3421	this macro to a something else you can include more and other types of	4570	this macro to something else you can include more and other types of
3422	members. You have to define it each time you include one of the files,	4571	members. You have to define it each time you include one of the files,
3423	though, and it must be identical each time.	4572	though, and it must be identical each time.
3424		4573
3425	For example, the perl EV module uses something like this:	4574	For example, the perl EV module uses something like this:
3426		4575
…		…
3479	file.	4628	file.
3480		4629
3481	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	4630	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
3482	that everybody includes and which overrides some configure choices:	4631	that everybody includes and which overrides some configure choices:
3483		4632
3484	#define EV_MINIMAL 1	4633	#define EV_FEATURES 8
3485	#define EV_USE_POLL 0	4634	#define EV_USE_SELECT 1
3486	#define EV_MULTIPLICITY 0
3487	#define EV_PERIODIC_ENABLE 0	4635	#define EV_PREPARE_ENABLE 1
		4636	#define EV_IDLE_ENABLE 1
3488	#define EV_STAT_ENABLE 0	4637	#define EV_SIGNAL_ENABLE 1
3489	#define EV_FORK_ENABLE 0	4638	#define EV_CHILD_ENABLE 1
		4639	#define EV_USE_STDEXCEPT 0
3490	#define EV_CONFIG_H <config.h>	4640	#define EV_CONFIG_H <config.h>
3491	#define EV_MINPRI 0
3492	#define EV_MAXPRI 0
3493		4641
3494	#include "ev++.h"	4642	#include "ev++.h"
3495		4643
3496	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4644	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
3497		4645
3498	#include "ev_cpp.h"	4646	#include "ev_cpp.h"
3499	#include "ev.c"	4647	#include "ev.c"
3500		4648
3501	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES	4649	=head1 INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT
3502		4650
3503	=head2 THREADS AND COROUTINES	4651	=head2 THREADS AND COROUTINES
3504		4652
3505	=head3 THREADS	4653	=head3 THREADS
3506		4654
…		…
3557	default loop and triggering an C<ev_async> watcher from the default loop	4705	default loop and triggering an C<ev_async> watcher from the default loop
3558	watcher callback into the event loop interested in the signal.	4706	watcher callback into the event loop interested in the signal.
3559		4707
3560	=back	4708	=back
3561		4709
		4710	See also L<THREAD LOCKING EXAMPLE>.
		4711
3562	=head3 COROUTINES	4712	=head3 COROUTINES
3563		4713
3564	Libev is very accommodating to coroutines ("cooperative threads"):	4714	Libev is very accommodating to coroutines ("cooperative threads"):
3565	libev fully supports nesting calls to its functions from different	4715	libev fully supports nesting calls to its functions from different
3566	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4716	coroutines (e.g. you can call C<ev_run> on the same loop from two
3567	different coroutines, and switch freely between both coroutines running the	4717	different coroutines, and switch freely between both coroutines running
3568	loop, as long as you don't confuse yourself). The only exception is that	4718	the loop, as long as you don't confuse yourself). The only exception is
3569	you must not do this from C<ev_periodic> reschedule callbacks.	4719	that you must not do this from C<ev_periodic> reschedule callbacks.
3570		4720
3571	Care has been taken to ensure that libev does not keep local state inside	4721	Care has been taken to ensure that libev does not keep local state inside
3572	C<ev_loop>, and other calls do not usually allow for coroutine switches as	4722	C<ev_run>, and other calls do not usually allow for coroutine switches as
3573	they do not call any callbacks.	4723	they do not call any callbacks.
3574		4724
3575	=head2 COMPILER WARNINGS	4725	=head2 COMPILER WARNINGS
3576		4726
3577	Depending on your compiler and compiler settings, you might get no or a	4727	Depending on your compiler and compiler settings, you might get no or a
…		…
3588	maintainable.	4738	maintainable.
3589		4739
3590	And of course, some compiler warnings are just plain stupid, or simply	4740	And of course, some compiler warnings are just plain stupid, or simply
3591	wrong (because they don't actually warn about the condition their message	4741	wrong (because they don't actually warn about the condition their message
3592	seems to warn about). For example, certain older gcc versions had some	4742	seems to warn about). For example, certain older gcc versions had some
3593	warnings that resulted an extreme number of false positives. These have	4743	warnings that resulted in an extreme number of false positives. These have
3594	been fixed, but some people still insist on making code warn-free with	4744	been fixed, but some people still insist on making code warn-free with
3595	such buggy versions.	4745	such buggy versions.
3596		4746
3597	While libev is written to generate as few warnings as possible,	4747	While libev is written to generate as few warnings as possible,
3598	"warn-free" code is not a goal, and it is recommended not to build libev	4748	"warn-free" code is not a goal, and it is recommended not to build libev
…		…
3634	I suggest using suppression lists.	4784	I suggest using suppression lists.
3635		4785
3636		4786
3637	=head1 PORTABILITY NOTES	4787	=head1 PORTABILITY NOTES
3638		4788
		4789	=head2 GNU/LINUX 32 BIT LIMITATIONS
		4790
		4791	GNU/Linux is the only common platform that supports 64 bit file/large file
		4792	interfaces but I<disables> them by default.
		4793
		4794	That means that libev compiled in the default environment doesn't support
		4795	files larger than 2GiB or so, which mainly affects C<ev_stat> watchers.
		4796
		4797	Unfortunately, many programs try to work around this GNU/Linux issue
		4798	by enabling the large file API, which makes them incompatible with the
		4799	standard libev compiled for their system.
		4800
		4801	Likewise, libev cannot enable the large file API itself as this would
		4802	suddenly make it incompatible to the default compile time environment,
		4803	i.e. all programs not using special compile switches.
		4804
		4805	=head2 OS/X AND DARWIN BUGS
		4806
		4807	The whole thing is a bug if you ask me - basically any system interface
		4808	you touch is broken, whether it is locales, poll, kqueue or even the
		4809	OpenGL drivers.
		4810
		4811	=head3 C<kqueue> is buggy
		4812
		4813	The kqueue syscall is broken in all known versions - most versions support
		4814	only sockets, many support pipes.
		4815
		4816	Libev tries to work around this by not using C<kqueue> by default on this
		4817	rotten platform, but of course you can still ask for it when creating a
		4818	loop - embedding a socket-only kqueue loop into a select-based one is
		4819	probably going to work well.
		4820
		4821	=head3 C<poll> is buggy
		4822
		4823	Instead of fixing C<kqueue>, Apple replaced their (working) C<poll>
		4824	implementation by something calling C<kqueue> internally around the 10.5.6
		4825	release, so now C<kqueue> I<and> C<poll> are broken.
		4826
		4827	Libev tries to work around this by not using C<poll> by default on
		4828	this rotten platform, but of course you can still ask for it when creating
		4829	a loop.
		4830
		4831	=head3 C<select> is buggy
		4832
		4833	All that's left is C<select>, and of course Apple found a way to fuck this
		4834	one up as well: On OS/X, C<select> actively limits the number of file
		4835	descriptors you can pass in to 1024 - your program suddenly crashes when
		4836	you use more.
		4837
		4838	There is an undocumented "workaround" for this - defining
		4839	C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should>
		4840	work on OS/X.
		4841
		4842	=head2 SOLARIS PROBLEMS AND WORKAROUNDS
		4843
		4844	=head3 C<errno> reentrancy
		4845
		4846	The default compile environment on Solaris is unfortunately so
		4847	thread-unsafe that you can't even use components/libraries compiled
		4848	without C<-D_REENTRANT> in a threaded program, which, of course, isn't
		4849	defined by default. A valid, if stupid, implementation choice.
		4850
		4851	If you want to use libev in threaded environments you have to make sure
		4852	it's compiled with C<_REENTRANT> defined.
		4853
		4854	=head3 Event port backend
		4855
		4856	The scalable event interface for Solaris is called "event
		4857	ports". Unfortunately, this mechanism is very buggy in all major
		4858	releases. If you run into high CPU usage, your program freezes or you get
		4859	a large number of spurious wakeups, make sure you have all the relevant
		4860	and latest kernel patches applied. No, I don't know which ones, but there
		4861	are multiple ones to apply, and afterwards, event ports actually work
		4862	great.
		4863
		4864	If you can't get it to work, you can try running the program by setting
		4865	the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and
		4866	C<select> backends.
		4867
		4868	=head2 AIX POLL BUG
		4869
		4870	AIX unfortunately has a broken C<poll.h> header. Libev works around
		4871	this by trying to avoid the poll backend altogether (i.e. it's not even
		4872	compiled in), which normally isn't a big problem as C<select> works fine
		4873	with large bitsets on AIX, and AIX is dead anyway.
		4874
3639	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS	4875	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
		4876
		4877	=head3 General issues
3640		4878
3641	Win32 doesn't support any of the standards (e.g. POSIX) that libev	4879	Win32 doesn't support any of the standards (e.g. POSIX) that libev
3642	requires, and its I/O model is fundamentally incompatible with the POSIX	4880	requires, and its I/O model is fundamentally incompatible with the POSIX
3643	model. Libev still offers limited functionality on this platform in	4881	model. Libev still offers limited functionality on this platform in
3644	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	4882	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
3645	descriptors. This only applies when using Win32 natively, not when using	4883	descriptors. This only applies when using Win32 natively, not when using
3646	e.g. cygwin.	4884	e.g. cygwin. Actually, it only applies to the microsofts own compilers,
		4885	as every compielr comes with a slightly differently broken/incompatible
		4886	environment.
3647		4887
3648	Lifting these limitations would basically require the full	4888	Lifting these limitations would basically require the full
3649	re-implementation of the I/O system. If you are into these kinds of	4889	re-implementation of the I/O system. If you are into this kind of thing,
3650	things, then note that glib does exactly that for you in a very portable	4890	then note that glib does exactly that for you in a very portable way (note
3651	way (note also that glib is the slowest event library known to man).	4891	also that glib is the slowest event library known to man).
3652		4892
3653	There is no supported compilation method available on windows except	4893	There is no supported compilation method available on windows except
3654	embedding it into other applications.	4894	embedding it into other applications.
		4895
		4896	Sensible signal handling is officially unsupported by Microsoft - libev
		4897	tries its best, but under most conditions, signals will simply not work.
3655		4898
3656	Not a libev limitation but worth mentioning: windows apparently doesn't	4899	Not a libev limitation but worth mentioning: windows apparently doesn't
3657	accept large writes: instead of resulting in a partial write, windows will	4900	accept large writes: instead of resulting in a partial write, windows will
3658	either accept everything or return C<ENOBUFS> if the buffer is too large,	4901	either accept everything or return C<ENOBUFS> if the buffer is too large,
3659	so make sure you only write small amounts into your sockets (less than a	4902	so make sure you only write small amounts into your sockets (less than a
…		…
3664	the abysmal performance of winsockets, using a large number of sockets	4907	the abysmal performance of winsockets, using a large number of sockets
3665	is not recommended (and not reasonable). If your program needs to use	4908	is not recommended (and not reasonable). If your program needs to use
3666	more than a hundred or so sockets, then likely it needs to use a totally	4909	more than a hundred or so sockets, then likely it needs to use a totally
3667	different implementation for windows, as libev offers the POSIX readiness	4910	different implementation for windows, as libev offers the POSIX readiness
3668	notification model, which cannot be implemented efficiently on windows	4911	notification model, which cannot be implemented efficiently on windows
3669	(Microsoft monopoly games).	4912	(due to Microsoft monopoly games).
3670		4913
3671	A typical way to use libev under windows is to embed it (see the embedding	4914	A typical way to use libev under windows is to embed it (see the embedding
3672	section for details) and use the following F<evwrap.h> header file instead	4915	section for details) and use the following F<evwrap.h> header file instead
3673	of F<ev.h>:	4916	of F<ev.h>:
3674		4917
…		…
3681	you do I<not> compile the F<ev.c> or any other embedded source files!):	4924	you do I<not> compile the F<ev.c> or any other embedded source files!):
3682		4925
3683	#include "evwrap.h"	4926	#include "evwrap.h"
3684	#include "ev.c"	4927	#include "ev.c"
3685		4928
3686	=over 4
3687
3688	=item The winsocket select function	4929	=head3 The winsocket C<select> function
3689		4930
3690	The winsocket C<select> function doesn't follow POSIX in that it	4931	The winsocket C<select> function doesn't follow POSIX in that it
3691	requires socket I<handles> and not socket I<file descriptors> (it is	4932	requires socket I<handles> and not socket I<file descriptors> (it is
3692	also extremely buggy). This makes select very inefficient, and also	4933	also extremely buggy). This makes select very inefficient, and also
3693	requires a mapping from file descriptors to socket handles (the Microsoft	4934	requires a mapping from file descriptors to socket handles (the Microsoft
…		…
3702	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */	4943	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
3703		4944
3704	Note that winsockets handling of fd sets is O(n), so you can easily get a	4945	Note that winsockets handling of fd sets is O(n), so you can easily get a
3705	complexity in the O(n²) range when using win32.	4946	complexity in the O(n²) range when using win32.
3706		4947
3707	=item Limited number of file descriptors	4948	=head3 Limited number of file descriptors
3708		4949
3709	Windows has numerous arbitrary (and low) limits on things.	4950	Windows has numerous arbitrary (and low) limits on things.
3710		4951
3711	Early versions of winsocket's select only supported waiting for a maximum	4952	Early versions of winsocket's select only supported waiting for a maximum
3712	of C<64> handles (probably owning to the fact that all windows kernels	4953	of C<64> handles (probably owning to the fact that all windows kernels
3713	can only wait for C<64> things at the same time internally; Microsoft	4954	can only wait for C<64> things at the same time internally; Microsoft
3714	recommends spawning a chain of threads and wait for 63 handles and the	4955	recommends spawning a chain of threads and wait for 63 handles and the
3715	previous thread in each. Great).	4956	previous thread in each. Sounds great!).
3716		4957
3717	Newer versions support more handles, but you need to define C<FD_SETSIZE>	4958	Newer versions support more handles, but you need to define C<FD_SETSIZE>
3718	to some high number (e.g. C<2048>) before compiling the winsocket select	4959	to some high number (e.g. C<2048>) before compiling the winsocket select
3719	call (which might be in libev or elsewhere, for example, perl does its own	4960	call (which might be in libev or elsewhere, for example, perl and many
3720	select emulation on windows).	4961	other interpreters do their own select emulation on windows).
3721		4962
3722	Another limit is the number of file descriptors in the Microsoft runtime	4963	Another limit is the number of file descriptors in the Microsoft runtime
3723	libraries, which by default is C<64> (there must be a hidden I<64> fetish	4964	libraries, which by default is C<64> (there must be a hidden I<64>
3724	or something like this inside Microsoft). You can increase this by calling	4965	fetish or something like this inside Microsoft). You can increase this
3725	C<_setmaxstdio>, which can increase this limit to C<2048> (another	4966	by calling C<_setmaxstdio>, which can increase this limit to C<2048>
3726	arbitrary limit), but is broken in many versions of the Microsoft runtime	4967	(another arbitrary limit), but is broken in many versions of the Microsoft
3727	libraries.
3728
3729	This might get you to about C<512> or C<2048> sockets (depending on	4968	runtime libraries. This might get you to about C<512> or C<2048> sockets
3730	windows version and/or the phase of the moon). To get more, you need to	4969	(depending on windows version and/or the phase of the moon). To get more,
3731	wrap all I/O functions and provide your own fd management, but the cost of	4970	you need to wrap all I/O functions and provide your own fd management, but
3732	calling select (O(n²)) will likely make this unworkable.	4971	the cost of calling select (O(n²)) will likely make this unworkable.
3733
3734	=back
3735		4972
3736	=head2 PORTABILITY REQUIREMENTS	4973	=head2 PORTABILITY REQUIREMENTS
3737		4974
3738	In addition to a working ISO-C implementation and of course the	4975	In addition to a working ISO-C implementation and of course the
3739	backend-specific APIs, libev relies on a few additional extensions:	4976	backend-specific APIs, libev relies on a few additional extensions:
…		…
3746	Libev assumes not only that all watcher pointers have the same internal	4983	Libev assumes not only that all watcher pointers have the same internal
3747	structure (guaranteed by POSIX but not by ISO C for example), but it also	4984	structure (guaranteed by POSIX but not by ISO C for example), but it also
3748	assumes that the same (machine) code can be used to call any watcher	4985	assumes that the same (machine) code can be used to call any watcher
3749	callback: The watcher callbacks have different type signatures, but libev	4986	callback: The watcher callbacks have different type signatures, but libev
3750	calls them using an C<ev_watcher *> internally.	4987	calls them using an C<ev_watcher *> internally.
		4988
		4989	=item pointer accesses must be thread-atomic
		4990
		4991	Accessing a pointer value must be atomic, it must both be readable and
		4992	writable in one piece - this is the case on all current architectures.
3751		4993
3752	=item C<sig_atomic_t volatile> must be thread-atomic as well	4994	=item C<sig_atomic_t volatile> must be thread-atomic as well
3753		4995
3754	The type C<sig_atomic_t volatile> (or whatever is defined as	4996	The type C<sig_atomic_t volatile> (or whatever is defined as
3755	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different	4997	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
…		…
3778	watchers.	5020	watchers.
3779		5021
3780	=item C<double> must hold a time value in seconds with enough accuracy	5022	=item C<double> must hold a time value in seconds with enough accuracy
3781		5023
3782	The type C<double> is used to represent timestamps. It is required to	5024	The type C<double> is used to represent timestamps. It is required to
3783	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	5025	have at least 51 bits of mantissa (and 9 bits of exponent), which is
3784	enough for at least into the year 4000. This requirement is fulfilled by	5026	good enough for at least into the year 4000 with millisecond accuracy
		5027	(the design goal for libev). This requirement is overfulfilled by
3785	implementations implementing IEEE 754 (basically all existing ones).	5028	implementations using IEEE 754, which is basically all existing ones. With
		5029	IEEE 754 doubles, you get microsecond accuracy until at least 2200.
3786		5030
3787	=back	5031	=back
3788		5032
3789	If you know of other additional requirements drop me a note.	5033	If you know of other additional requirements drop me a note.
3790		5034
…		…
3858	involves iterating over all running async watchers or all signal numbers.	5102	involves iterating over all running async watchers or all signal numbers.
3859		5103
3860	=back	5104	=back
3861		5105
3862		5106
		5107	=head1 PORTING FROM LIBEV 3.X TO 4.X
		5108
		5109	The major version 4 introduced some incompatible changes to the API.
		5110
		5111	At the moment, the C<ev.h> header file provides compatibility definitions
		5112	for all changes, so most programs should still compile. The compatibility
		5113	layer might be removed in later versions of libev, so better update to the
		5114	new API early than late.
		5115
		5116	=over 4
		5117
		5118	=item C<EV_COMPAT3> backwards compatibility mechanism
		5119
		5120	The backward compatibility mechanism can be controlled by
		5121	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		5122	section.
		5123
		5124	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		5125
		5126	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		5127
		5128	ev_loop_destroy (EV_DEFAULT_UC);
		5129	ev_loop_fork (EV_DEFAULT);
		5130
		5131	=item function/symbol renames
		5132
		5133	A number of functions and symbols have been renamed:
		5134
		5135	ev_loop => ev_run
		5136	EVLOOP_NONBLOCK => EVRUN_NOWAIT
		5137	EVLOOP_ONESHOT => EVRUN_ONCE
		5138
		5139	ev_unloop => ev_break
		5140	EVUNLOOP_CANCEL => EVBREAK_CANCEL
		5141	EVUNLOOP_ONE => EVBREAK_ONE
		5142	EVUNLOOP_ALL => EVBREAK_ALL
		5143
		5144	EV_TIMEOUT => EV_TIMER
		5145
		5146	ev_loop_count => ev_iteration
		5147	ev_loop_depth => ev_depth
		5148	ev_loop_verify => ev_verify
		5149
		5150	Most functions working on C<struct ev_loop> objects don't have an
		5151	C<ev_loop_> prefix, so it was removed; C<ev_loop>, C<ev_unloop> and
		5152	associated constants have been renamed to not collide with the C<struct
		5153	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
		5154	as all other watcher types. Note that C<ev_loop_fork> is still called
		5155	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
		5156	typedef.
		5157
		5158	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
		5159
		5160	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
		5161	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
		5162	and work, but the library code will of course be larger.
		5163
		5164	=back
		5165
		5166
		5167	=head1 GLOSSARY
		5168
		5169	=over 4
		5170
		5171	=item active
		5172
		5173	A watcher is active as long as it has been started and not yet stopped.
		5174	See L<WATCHER STATES> for details.
		5175
		5176	=item application
		5177
		5178	In this document, an application is whatever is using libev.
		5179
		5180	=item backend
		5181
		5182	The part of the code dealing with the operating system interfaces.
		5183
		5184	=item callback
		5185
		5186	The address of a function that is called when some event has been
		5187	detected. Callbacks are being passed the event loop, the watcher that
		5188	received the event, and the actual event bitset.
		5189
		5190	=item callback/watcher invocation
		5191
		5192	The act of calling the callback associated with a watcher.
		5193
		5194	=item event
		5195
		5196	A change of state of some external event, such as data now being available
		5197	for reading on a file descriptor, time having passed or simply not having
		5198	any other events happening anymore.
		5199
		5200	In libev, events are represented as single bits (such as C<EV_READ> or
		5201	C<EV_TIMER>).
		5202
		5203	=item event library
		5204
		5205	A software package implementing an event model and loop.
		5206
		5207	=item event loop
		5208
		5209	An entity that handles and processes external events and converts them
		5210	into callback invocations.
		5211
		5212	=item event model
		5213
		5214	The model used to describe how an event loop handles and processes
		5215	watchers and events.
		5216
		5217	=item pending
		5218
		5219	A watcher is pending as soon as the corresponding event has been
		5220	detected. See L<WATCHER STATES> for details.
		5221
		5222	=item real time
		5223
		5224	The physical time that is observed. It is apparently strictly monotonic :)
		5225
		5226	=item wall-clock time
		5227
		5228	The time and date as shown on clocks. Unlike real time, it can actually
		5229	be wrong and jump forwards and backwards, e.g. when you adjust your
		5230	clock.
		5231
		5232	=item watcher
		5233
		5234	A data structure that describes interest in certain events. Watchers need
		5235	to be started (attached to an event loop) before they can receive events.
		5236
		5237	=back
		5238
3863	=head1 AUTHOR	5239	=head1 AUTHOR
3864		5240
3865	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.	5241	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5242	Magnusson and Emanuele Giaquinta, and minor corrections by many others.
3866		5243

Diff Legend

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