ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.27 by root, Wed Nov 14 05:02:07 2007 UTC vs.
Revision 1.62 by root, Thu Nov 29 17:28:13 2007 UTC

…		…
3	libev - a high performance full-featured event loop written in C	3	libev - a high performance full-featured event loop written in C
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	#include <ev.h>	7	#include <ev.h>
		8
		9	=head1 EXAMPLE PROGRAM
		10
		11	#include <ev.h>
		12
		13	ev_io stdin_watcher;
		14	ev_timer timeout_watcher;
		15
		16	/* called when data readable on stdin */
		17	static void
		18	stdin_cb (EV_P_ struct ev_io *w, int revents)
		19	{
		20	/* puts ("stdin ready"); */
		21	ev_io_stop (EV_A_ w); /* just a syntax example */
		22	ev_unloop (EV_A_ EVUNLOOP_ALL); /* leave all loop calls */
		23	}
		24
		25	static void
		26	timeout_cb (EV_P_ struct ev_timer *w, int revents)
		27	{
		28	/* puts ("timeout"); */
		29	ev_unloop (EV_A_ EVUNLOOP_ONE); /* leave one loop call */
		30	}
		31
		32	int
		33	main (void)
		34	{
		35	struct ev_loop *loop = ev_default_loop (0);
		36
		37	/* initialise an io watcher, then start it */
		38	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
		39	ev_io_start (loop, &stdin_watcher);
		40
		41	/* simple non-repeating 5.5 second timeout */
		42	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		43	ev_timer_start (loop, &timeout_watcher);
		44
		45	/* loop till timeout or data ready */
		46	ev_loop (loop, 0);
		47
		48	return 0;
		49	}
8		50
9	=head1 DESCRIPTION	51	=head1 DESCRIPTION
10		52
11	Libev is an event loop: you register interest in certain events (such as a	53	Libev is an event loop: you register interest in certain events (such as a
12	file descriptor being readable or a timeout occuring), and it will manage	54	file descriptor being readable or a timeout occuring), and it will manage
…		…
21	details of the event, and then hand it over to libev by I<starting> the	63	details of the event, and then hand it over to libev by I<starting> the
22	watcher.	64	watcher.
23		65
24	=head1 FEATURES	66	=head1 FEATURES
25		67
26	Libev supports select, poll, the linux-specific epoll and the bsd-specific	68	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
27	kqueue mechanisms for file descriptor events, relative timers, absolute	69	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
28	timers with customised rescheduling, signal events, process status change	70	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
29	events (related to SIGCHLD), and event watchers dealing with the event	71	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers
30	loop mechanism itself (idle, prepare and check watchers). It also is quite	72	with customised rescheduling (C<ev_periodic>), synchronous signals
		73	(C<ev_signal>), process status change events (C<ev_child>), and event
		74	watchers dealing with the event loop mechanism itself (C<ev_idle>,
		75	C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as
		76	file watchers (C<ev_stat>) and even limited support for fork events
		77	(C<ev_fork>).
		78
		79	It also is quite fast (see this
31	fast (see this L<benchmark|http://libev.schmorp.de/bench.html> comparing	80	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent
32	it to libevent for example).	81	for example).
33		82
34	=head1 CONVENTIONS	83	=head1 CONVENTIONS
35		84
36	Libev is very configurable. In this manual the default configuration	85	Libev is very configurable. In this manual the default configuration will
37	will be described, which supports multiple event loops. For more info	86	be described, which supports multiple event loops. For more info about
38	about various configuration options please have a look at the file	87	various configuration options please have a look at B<EMBED> section in
39	F<README.embed> in the libev distribution. If libev was configured without	88	this manual. If libev was configured without support for multiple event
40	support for multiple event loops, then all functions taking an initial	89	loops, then all functions taking an initial argument of name C<loop>
41	argument of name C<loop> (which is always of type C<struct ev_loop *>)	90	(which is always of type C<struct ev_loop *>) will not have this argument.
42	will not have this argument.
43		91
44	=head1 TIME REPRESENTATION	92	=head1 TIME REPRESENTATION
45		93
46	Libev represents time as a single floating point number, representing the	94	Libev represents time as a single floating point number, representing the
47	(fractional) number of seconds since the (POSIX) epoch (somewhere near	95	(fractional) number of seconds since the (POSIX) epoch (somewhere near
48	the beginning of 1970, details are complicated, don't ask). This type is	96	the beginning of 1970, details are complicated, don't ask). This type is
49	called C<ev_tstamp>, which is what you should use too. It usually aliases	97	called C<ev_tstamp>, which is what you should use too. It usually aliases
50	to the double type in C.	98	to the C<double> type in C, and when you need to do any calculations on
		99	it, you should treat it as such.
51		100
52	=head1 GLOBAL FUNCTIONS	101	=head1 GLOBAL FUNCTIONS
53		102
54	These functions can be called anytime, even before initialising the	103	These functions can be called anytime, even before initialising the
55	library in any way.	104	library in any way.
…		…
75	Usually, it's a good idea to terminate if the major versions mismatch,	124	Usually, it's a good idea to terminate if the major versions mismatch,
76	as this indicates an incompatible change. Minor versions are usually	125	as this indicates an incompatible change. Minor versions are usually
77	compatible to older versions, so a larger minor version alone is usually	126	compatible to older versions, so a larger minor version alone is usually
78	not a problem.	127	not a problem.
79		128
		129	Example: Make sure we haven't accidentally been linked against the wrong
		130	version.
		131
		132	assert (("libev version mismatch",
		133	ev_version_major () == EV_VERSION_MAJOR
		134	&& ev_version_minor () >= EV_VERSION_MINOR));
		135
		136	=item unsigned int ev_supported_backends ()
		137
		138	Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
		139	value) compiled into this binary of libev (independent of their
		140	availability on the system you are running on). See C<ev_default_loop> for
		141	a description of the set values.
		142
		143	Example: make sure we have the epoll method, because yeah this is cool and
		144	a must have and can we have a torrent of it please!!!11
		145
		146	assert (("sorry, no epoll, no sex",
		147	ev_supported_backends () & EVBACKEND_EPOLL));
		148
		149	=item unsigned int ev_recommended_backends ()
		150
		151	Return the set of all backends compiled into this binary of libev and also
		152	recommended for this platform. This set is often smaller than the one
		153	returned by C<ev_supported_backends>, as for example kqueue is broken on
		154	most BSDs and will not be autodetected unless you explicitly request it
		155	(assuming you know what you are doing). This is the set of backends that
		156	libev will probe for if you specify no backends explicitly.
		157
		158	=item unsigned int ev_embeddable_backends ()
		159
		160	Returns the set of backends that are embeddable in other event loops. This
		161	is the theoretical, all-platform, value. To find which backends
		162	might be supported on the current system, you would need to look at
		163	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for
		164	recommended ones.
		165
		166	See the description of C<ev_embed> watchers for more info.
		167
80	=item ev_set_allocator (void *(*cb)(void *ptr, long size))	168	=item ev_set_allocator (void *(*cb)(void *ptr, long size))
81		169
82	Sets the allocation function to use (the prototype is similar to the	170	Sets the allocation function to use (the prototype is similar - the
83	realloc C function, the semantics are identical). It is used to allocate	171	semantics is identical - to the realloc C function). It is used to
84	and free memory (no surprises here). If it returns zero when memory	172	allocate and free memory (no surprises here). If it returns zero when
85	needs to be allocated, the library might abort or take some potentially	173	memory needs to be allocated, the library might abort or take some
86	destructive action. The default is your system realloc function.	174	potentially destructive action. The default is your system realloc
		175	function.
87		176
88	You could override this function in high-availability programs to, say,	177	You could override this function in high-availability programs to, say,
89	free some memory if it cannot allocate memory, to use a special allocator,	178	free some memory if it cannot allocate memory, to use a special allocator,
90	or even to sleep a while and retry until some memory is available.	179	or even to sleep a while and retry until some memory is available.
		180
		181	Example: Replace the libev allocator with one that waits a bit and then
		182	retries).
		183
		184	static void *
		185	persistent_realloc (void *ptr, size_t size)
		186	{
		187	for (;;)
		188	{
		189	void *newptr = realloc (ptr, size);
		190
		191	if (newptr)
		192	return newptr;
		193
		194	sleep (60);
		195	}
		196	}
		197
		198	...
		199	ev_set_allocator (persistent_realloc);
91		200
92	=item ev_set_syserr_cb (void (*cb)(const char *msg));	201	=item ev_set_syserr_cb (void (*cb)(const char *msg));
93		202
94	Set the callback function to call on a retryable syscall error (such	203	Set the callback function to call on a retryable syscall error (such
95	as failed select, poll, epoll_wait). The message is a printable string	204	as failed select, poll, epoll_wait). The message is a printable string
…		…
97	callback is set, then libev will expect it to remedy the sitution, no	206	callback is set, then libev will expect it to remedy the sitution, no
98	matter what, when it returns. That is, libev will generally retry the	207	matter what, when it returns. That is, libev will generally retry the
99	requested operation, or, if the condition doesn't go away, do bad stuff	208	requested operation, or, if the condition doesn't go away, do bad stuff
100	(such as abort).	209	(such as abort).
101		210
		211	Example: This is basically the same thing that libev does internally, too.
		212
		213	static void
		214	fatal_error (const char *msg)
		215	{
		216	perror (msg);
		217	abort ();
		218	}
		219
		220	...
		221	ev_set_syserr_cb (fatal_error);
		222
102	=back	223	=back
103		224
104	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	225	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP
105		226
106	An event loop is described by a C<struct ev_loop *>. The library knows two	227	An event loop is described by a C<struct ev_loop *>. The library knows two
…		…
119	=item struct ev_loop *ev_default_loop (unsigned int flags)	240	=item struct ev_loop *ev_default_loop (unsigned int flags)
120		241
121	This will initialise the default event loop if it hasn't been initialised	242	This will initialise the default event loop if it hasn't been initialised
122	yet and return it. If the default loop could not be initialised, returns	243	yet and return it. If the default loop could not be initialised, returns
123	false. If it already was initialised it simply returns it (and ignores the	244	false. If it already was initialised it simply returns it (and ignores the
124	flags).	245	flags. If that is troubling you, check C<ev_backend ()> afterwards).
125		246
126	If you don't know what event loop to use, use the one returned from this	247	If you don't know what event loop to use, use the one returned from this
127	function.	248	function.
128		249
129	The flags argument can be used to specify special behaviour or specific	250	The flags argument can be used to specify special behaviour or specific
130	backends to use, and is usually specified as 0 (or EVFLAG_AUTO).	251	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
131		252
132	It supports the following flags:	253	The following flags are supported:
133		254
134	=over 4	255	=over 4
135		256
136	=item C<EVFLAG_AUTO>	257	=item C<EVFLAG_AUTO>
137		258
…		…
145	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will	266	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
146	override the flags completely if it is found in the environment. This is	267	override the flags completely if it is found in the environment. This is
147	useful to try out specific backends to test their performance, or to work	268	useful to try out specific backends to test their performance, or to work
148	around bugs.	269	around bugs.
149		270
		271	=item C<EVFLAG_FORKCHECK>
		272
		273	Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after
		274	a fork, you can also make libev check for a fork in each iteration by
		275	enabling this flag.
		276
		277	This works by calling C<getpid ()> on every iteration of the loop,
		278	and thus this might slow down your event loop if you do a lot of loop
		279	iterations and little real work, but is usually not noticable (on my
		280	Linux system for example, C<getpid> is actually a simple 5-insn sequence
		281	without a syscall and thus I<very> fast, but my Linux system also has
		282	C<pthread_atfork> which is even faster).
		283
		284	The big advantage of this flag is that you can forget about fork (and
		285	forget about forgetting to tell libev about forking) when you use this
		286	flag.
		287
		288	This flag setting cannot be overriden or specified in the C<LIBEV_FLAGS>
		289	environment variable.
		290
150	=item C<EVMETHOD_SELECT> (portable select backend)	291	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
151		292
		293	This is your standard select(2) backend. Not I<completely> standard, as
		294	libev tries to roll its own fd_set with no limits on the number of fds,
		295	but if that fails, expect a fairly low limit on the number of fds when
		296	using this backend. It doesn't scale too well (O(highest_fd)), but its usually
		297	the fastest backend for a low number of fds.
		298
152	=item C<EVMETHOD_POLL> (poll backend, available everywhere except on windows)	299	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
153		300
154	=item C<EVMETHOD_EPOLL> (linux only)	301	And this is your standard poll(2) backend. It's more complicated than
		302	select, but handles sparse fds better and has no artificial limit on the
		303	number of fds you can use (except it will slow down considerably with a
		304	lot of inactive fds). It scales similarly to select, i.e. O(total_fds).
155		305
156	=item C<EVMETHOD_KQUEUE> (some bsds only)	306	=item C<EVBACKEND_EPOLL> (value 4, Linux)
157		307
158	=item C<EVMETHOD_DEVPOLL> (solaris 8 only)	308	For few fds, this backend is a bit little slower than poll and select,
		309	but it scales phenomenally better. While poll and select usually scale like
		310	O(total_fds) where n is the total number of fds (or the highest fd), epoll scales
		311	either O(1) or O(active_fds).
159		312
160	=item C<EVMETHOD_PORT> (solaris 10 only)	313	While stopping and starting an I/O watcher in the same iteration will
		314	result in some caching, there is still a syscall per such incident
		315	(because the fd could point to a different file description now), so its
		316	best to avoid that. Also, dup()ed file descriptors might not work very
		317	well if you register events for both fds.
		318
		319	Please note that epoll sometimes generates spurious notifications, so you
		320	need to use non-blocking I/O or other means to avoid blocking when no data
		321	(or space) is available.
		322
		323	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
		324
		325	Kqueue deserves special mention, as at the time of this writing, it
		326	was broken on all BSDs except NetBSD (usually it doesn't work with
		327	anything but sockets and pipes, except on Darwin, where of course its
		328	completely useless). For this reason its not being "autodetected"
		329	unless you explicitly specify it explicitly in the flags (i.e. using
		330	C<EVBACKEND_KQUEUE>).
		331
		332	It scales in the same way as the epoll backend, but the interface to the
		333	kernel is more efficient (which says nothing about its actual speed, of
		334	course). While starting and stopping an I/O watcher does not cause an
		335	extra syscall as with epoll, it still adds up to four event changes per
		336	incident, so its best to avoid that.
		337
		338	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
		339
		340	This is not implemented yet (and might never be).
		341
		342	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
		343
		344	This uses the Solaris 10 port mechanism. As with everything on Solaris,
		345	it's really slow, but it still scales very well (O(active_fds)).
		346
		347	Please note that solaris ports can result in a lot of spurious
		348	notifications, so you need to use non-blocking I/O or other means to avoid
		349	blocking when no data (or space) is available.
		350
		351	=item C<EVBACKEND_ALL>
		352
		353	Try all backends (even potentially broken ones that wouldn't be tried
		354	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
		355	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
		356
		357	=back
161		358
162	If one or more of these are ored into the flags value, then only these	359	If one or more of these are ored into the flags value, then only these
163	backends will be tried (in the reverse order as given here). If one are	360	backends will be tried (in the reverse order as given here). If none are
164	specified, any backend will do.	361	specified, most compiled-in backend will be tried, usually in reverse
		362	order of their flag values :)
165		363
166	=back	364	The most typical usage is like this:
		365
		366	if (!ev_default_loop (0))
		367	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
		368
		369	Restrict libev to the select and poll backends, and do not allow
		370	environment settings to be taken into account:
		371
		372	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
		373
		374	Use whatever libev has to offer, but make sure that kqueue is used if
		375	available (warning, breaks stuff, best use only with your own private
		376	event loop and only if you know the OS supports your types of fds):
		377
		378	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
167		379
168	=item struct ev_loop *ev_loop_new (unsigned int flags)	380	=item struct ev_loop *ev_loop_new (unsigned int flags)
169		381
170	Similar to C<ev_default_loop>, but always creates a new event loop that is	382	Similar to C<ev_default_loop>, but always creates a new event loop that is
171	always distinct from the default loop. Unlike the default loop, it cannot	383	always distinct from the default loop. Unlike the default loop, it cannot
172	handle signal and child watchers, and attempts to do so will be greeted by	384	handle signal and child watchers, and attempts to do so will be greeted by
173	undefined behaviour (or a failed assertion if assertions are enabled).	385	undefined behaviour (or a failed assertion if assertions are enabled).
174		386
		387	Example: Try to create a event loop that uses epoll and nothing else.
		388
		389	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
		390	if (!epoller)
		391	fatal ("no epoll found here, maybe it hides under your chair");
		392
175	=item ev_default_destroy ()	393	=item ev_default_destroy ()
176		394
177	Destroys the default loop again (frees all memory and kernel state	395	Destroys the default loop again (frees all memory and kernel state
178	etc.). This stops all registered event watchers (by not touching them in	396	etc.). None of the active event watchers will be stopped in the normal
179	any way whatsoever, although you cannot rely on this :).	397	sense, so e.g. C<ev_is_active> might still return true. It is your
		398	responsibility to either stop all watchers cleanly yoursef I<before>
		399	calling this function, or cope with the fact afterwards (which is usually
		400	the easiest thing, youc na just ignore the watchers and/or C<free ()> them
		401	for example).
180		402
181	=item ev_loop_destroy (loop)	403	=item ev_loop_destroy (loop)
182		404
183	Like C<ev_default_destroy>, but destroys an event loop created by an	405	Like C<ev_default_destroy>, but destroys an event loop created by an
184	earlier call to C<ev_loop_new>.	406	earlier call to C<ev_loop_new>.
…		…
188	This function reinitialises the kernel state for backends that have	410	This function reinitialises the kernel state for backends that have
189	one. Despite the name, you can call it anytime, but it makes most sense	411	one. Despite the name, you can call it anytime, but it makes most sense
190	after forking, in either the parent or child process (or both, but that	412	after forking, in either the parent or child process (or both, but that
191	again makes little sense).	413	again makes little sense).
192		414
193	You I<must> call this function after forking if and only if you want to	415	You I<must> call this function in the child process after forking if and
194	use the event library in both processes. If you just fork+exec, you don't	416	only if you want to use the event library in both processes. If you just
195	have to call it.	417	fork+exec, you don't have to call it.
196		418
197	The function itself is quite fast and it's usually not a problem to call	419	The function itself is quite fast and it's usually not a problem to call
198	it just in case after a fork. To make this easy, the function will fit in	420	it just in case after a fork. To make this easy, the function will fit in
199	quite nicely into a call to C<pthread_atfork>:	421	quite nicely into a call to C<pthread_atfork>:
200		422
201	pthread_atfork (0, 0, ev_default_fork);	423	pthread_atfork (0, 0, ev_default_fork);
202		424
		425	At the moment, C<EVBACKEND_SELECT> and C<EVBACKEND_POLL> are safe to use
		426	without calling this function, so if you force one of those backends you
		427	do not need to care.
		428
203	=item ev_loop_fork (loop)	429	=item ev_loop_fork (loop)
204		430
205	Like C<ev_default_fork>, but acts on an event loop created by	431	Like C<ev_default_fork>, but acts on an event loop created by
206	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	432	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
207	after fork, and how you do this is entirely your own problem.	433	after fork, and how you do this is entirely your own problem.
208		434
209	=item unsigned int ev_method (loop)	435	=item unsigned int ev_backend (loop)
210		436
211	Returns one of the C<EVMETHOD_*> flags indicating the event backend in	437	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
212	use.	438	use.
213		439
214	=item ev_tstamp ev_now (loop)	440	=item ev_tstamp ev_now (loop)
215		441
216	Returns the current "event loop time", which is the time the event loop	442	Returns the current "event loop time", which is the time the event loop
217	got events and started processing them. This timestamp does not change	443	received events and started processing them. This timestamp does not
218	as long as callbacks are being processed, and this is also the base time	444	change as long as callbacks are being processed, and this is also the base
219	used for relative timers. You can treat it as the timestamp of the event	445	time used for relative timers. You can treat it as the timestamp of the
220	occuring (or more correctly, the mainloop finding out about it).	446	event occuring (or more correctly, libev finding out about it).
221		447
222	=item ev_loop (loop, int flags)	448	=item ev_loop (loop, int flags)
223		449
224	Finally, this is it, the event handler. This function usually is called	450	Finally, this is it, the event handler. This function usually is called
225	after you initialised all your watchers and you want to start handling	451	after you initialised all your watchers and you want to start handling
226	events.	452	events.
227		453
228	If the flags argument is specified as 0, it will not return until either	454	If the flags argument is specified as C<0>, it will not return until
229	no event watchers are active anymore or C<ev_unloop> was called.	455	either no event watchers are active anymore or C<ev_unloop> was called.
		456
		457	Please note that an explicit C<ev_unloop> is usually better than
		458	relying on all watchers to be stopped when deciding when a program has
		459	finished (especially in interactive programs), but having a program that
		460	automatically loops as long as it has to and no longer by virtue of
		461	relying on its watchers stopping correctly is a thing of beauty.
230		462
231	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	463	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle
232	those events and any outstanding ones, but will not block your process in	464	those events and any outstanding ones, but will not block your process in
233	case there are no events and will return after one iteration of the loop.	465	case there are no events and will return after one iteration of the loop.
234		466
235	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	467	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
236	neccessary) and will handle those and any outstanding ones. It will block	468	neccessary) and will handle those and any outstanding ones. It will block
237	your process until at least one new event arrives, and will return after	469	your process until at least one new event arrives, and will return after
238	one iteration of the loop.	470	one iteration of the loop. This is useful if you are waiting for some
		471	external event in conjunction with something not expressible using other
		472	libev watchers. However, a pair of C<ev_prepare>/C<ev_check> watchers is
		473	usually a better approach for this kind of thing.
239		474
240	This flags value could be used to implement alternative looping
241	constructs, but the C<prepare> and C<check> watchers provide a better and
242	more generic mechanism.
243
244	Here are the gory details of what ev_loop does:	475	Here are the gory details of what C<ev_loop> does:
245		476
246	1. If there are no active watchers (reference count is zero), return.	477	* If there are no active watchers (reference count is zero), return.
247	2. Queue and immediately call all prepare watchers.	478	- Queue prepare watchers and then call all outstanding watchers.
248	3. If we have been forked, recreate the kernel state.	479	- If we have been forked, recreate the kernel state.
249	4. Update the kernel state with all outstanding changes.	480	- Update the kernel state with all outstanding changes.
250	5. Update the "event loop time".	481	- Update the "event loop time".
251	6. Calculate for how long to block.	482	- Calculate for how long to block.
252	7. Block the process, waiting for events.	483	- Block the process, waiting for any events.
		484	- Queue all outstanding I/O (fd) events.
253	8. Update the "event loop time" and do time jump handling.	485	- Update the "event loop time" and do time jump handling.
254	9. Queue all outstanding timers.	486	- Queue all outstanding timers.
255	10. Queue all outstanding periodics.	487	- Queue all outstanding periodics.
256	11. If no events are pending now, queue all idle watchers.	488	- If no events are pending now, queue all idle watchers.
257	12. Queue all check watchers.	489	- Queue all check watchers.
258	13. Call all queued watchers in reverse order (i.e. check watchers first).	490	- Call all queued watchers in reverse order (i.e. check watchers first).
		491	Signals and child watchers are implemented as I/O watchers, and will
		492	be handled here by queueing them when their watcher gets executed.
259	14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	493	- If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
260	was used, return, otherwise continue with step #1.	494	were used, return, otherwise continue with step *.
		495
		496	Example: Queue some jobs and then loop until no events are outsanding
		497	anymore.
		498
		499	... queue jobs here, make sure they register event watchers as long
		500	... as they still have work to do (even an idle watcher will do..)
		501	ev_loop (my_loop, 0);
		502	... jobs done. yeah!
261		503
262	=item ev_unloop (loop, how)	504	=item ev_unloop (loop, how)
263		505
264	Can be used to make a call to C<ev_loop> return early (but only after it	506	Can be used to make a call to C<ev_loop> return early (but only after it
265	has processed all outstanding events). The C<how> argument must be either	507	has processed all outstanding events). The C<how> argument must be either
…		…
279	visible to the libev user and should not keep C<ev_loop> from exiting if	521	visible to the libev user and should not keep C<ev_loop> from exiting if
280	no event watchers registered by it are active. It is also an excellent	522	no event watchers registered by it are active. It is also an excellent
281	way to do this for generic recurring timers or from within third-party	523	way to do this for generic recurring timers or from within third-party
282	libraries. Just remember to I<unref after start> and I<ref before stop>.	524	libraries. Just remember to I<unref after start> and I<ref before stop>.
283		525
		526	Example: Create a signal watcher, but keep it from keeping C<ev_loop>
		527	running when nothing else is active.
		528
		529	struct ev_signal exitsig;
		530	ev_signal_init (&exitsig, sig_cb, SIGINT);
		531	ev_signal_start (loop, &exitsig);
		532	evf_unref (loop);
		533
		534	Example: For some weird reason, unregister the above signal handler again.
		535
		536	ev_ref (loop);
		537	ev_signal_stop (loop, &exitsig);
		538
284	=back	539	=back
		540
285		541
286	=head1 ANATOMY OF A WATCHER	542	=head1 ANATOMY OF A WATCHER
287		543
288	A watcher is a structure that you create and register to record your	544	A watcher is a structure that you create and register to record your
289	interest in some event. For instance, if you want to wait for STDIN to	545	interest in some event. For instance, if you want to wait for STDIN to
…		…
322	*) >>), and you can stop watching for events at any time by calling the	578	*) >>), and you can stop watching for events at any time by calling the
323	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	579	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.
324		580
325	As long as your watcher is active (has been started but not stopped) you	581	As long as your watcher is active (has been started but not stopped) you
326	must not touch the values stored in it. Most specifically you must never	582	must not touch the values stored in it. Most specifically you must never
327	reinitialise it or call its set method.	583	reinitialise it or call its C<set> macro.
328
329	You can check whether an event is active by calling the C<ev_is_active
330	(watcher *)> macro. To see whether an event is outstanding (but the
331	callback for it has not been called yet) you can use the C<ev_is_pending
332	(watcher *)> macro.
333		584
334	Each and every callback receives the event loop pointer as first, the	585	Each and every callback receives the event loop pointer as first, the
335	registered watcher structure as second, and a bitset of received events as	586	registered watcher structure as second, and a bitset of received events as
336	third argument.	587	third argument.
337		588
…		…
361	The signal specified in the C<ev_signal> watcher has been received by a thread.	612	The signal specified in the C<ev_signal> watcher has been received by a thread.
362		613
363	=item C<EV_CHILD>	614	=item C<EV_CHILD>
364		615
365	The pid specified in the C<ev_child> watcher has received a status change.	616	The pid specified in the C<ev_child> watcher has received a status change.
		617
		618	=item C<EV_STAT>
		619
		620	The path specified in the C<ev_stat> watcher changed its attributes somehow.
366		621
367	=item C<EV_IDLE>	622	=item C<EV_IDLE>
368		623
369	The C<ev_idle> watcher has determined that you have nothing better to do.	624	The C<ev_idle> watcher has determined that you have nothing better to do.
370		625
…		…
378	received events. Callbacks of both watcher types can start and stop as	633	received events. Callbacks of both watcher types can start and stop as
379	many watchers as they want, and all of them will be taken into account	634	many watchers as they want, and all of them will be taken into account
380	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	635	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
381	C<ev_loop> from blocking).	636	C<ev_loop> from blocking).
382		637
		638	=item C<EV_EMBED>
		639
		640	The embedded event loop specified in the C<ev_embed> watcher needs attention.
		641
		642	=item C<EV_FORK>
		643
		644	The event loop has been resumed in the child process after fork (see
		645	C<ev_fork>).
		646
383	=item C<EV_ERROR>	647	=item C<EV_ERROR>
384		648
385	An unspecified error has occured, the watcher has been stopped. This might	649	An unspecified error has occured, the watcher has been stopped. This might
386	happen because the watcher could not be properly started because libev	650	happen because the watcher could not be properly started because libev
387	ran out of memory, a file descriptor was found to be closed or any other	651	ran out of memory, a file descriptor was found to be closed or any other
…		…
393	your callbacks is well-written it can just attempt the operation and cope	657	your callbacks is well-written it can just attempt the operation and cope
394	with the error from read() or write(). This will not work in multithreaded	658	with the error from read() or write(). This will not work in multithreaded
395	programs, though, so beware.	659	programs, though, so beware.
396		660
397	=back	661	=back
		662
		663	=head2 GENERIC WATCHER FUNCTIONS
		664
		665	In the following description, C<TYPE> stands for the watcher type,
		666	e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.
		667
		668	=over 4
		669
		670	=item C<ev_init> (ev_TYPE *watcher, callback)
		671
		672	This macro initialises the generic portion of a watcher. The contents
		673	of the watcher object can be arbitrary (so C<malloc> will do). Only
		674	the generic parts of the watcher are initialised, you I<need> to call
		675	the type-specific C<ev_TYPE_set> macro afterwards to initialise the
		676	type-specific parts. For each type there is also a C<ev_TYPE_init> macro
		677	which rolls both calls into one.
		678
		679	You can reinitialise a watcher at any time as long as it has been stopped
		680	(or never started) and there are no pending events outstanding.
		681
		682	The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,
		683	int revents)>.
		684
		685	=item C<ev_TYPE_set> (ev_TYPE *, [args])
		686
		687	This macro initialises the type-specific parts of a watcher. You need to
		688	call C<ev_init> at least once before you call this macro, but you can
		689	call C<ev_TYPE_set> any number of times. You must not, however, call this
		690	macro on a watcher that is active (it can be pending, however, which is a
		691	difference to the C<ev_init> macro).
		692
		693	Although some watcher types do not have type-specific arguments
		694	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
		695
		696	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
		697
		698	This convinience macro rolls both C<ev_init> and C<ev_TYPE_set> macro
		699	calls into a single call. This is the most convinient method to initialise
		700	a watcher. The same limitations apply, of course.
		701
		702	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)
		703
		704	Starts (activates) the given watcher. Only active watchers will receive
		705	events. If the watcher is already active nothing will happen.
		706
		707	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)
		708
		709	Stops the given watcher again (if active) and clears the pending
		710	status. It is possible that stopped watchers are pending (for example,
		711	non-repeating timers are being stopped when they become pending), but
		712	C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If
		713	you want to free or reuse the memory used by the watcher it is therefore a
		714	good idea to always call its C<ev_TYPE_stop> function.
		715
		716	=item bool ev_is_active (ev_TYPE *watcher)
		717
		718	Returns a true value iff the watcher is active (i.e. it has been started
		719	and not yet been stopped). As long as a watcher is active you must not modify
		720	it.
		721
		722	=item bool ev_is_pending (ev_TYPE *watcher)
		723
		724	Returns a true value iff the watcher is pending, (i.e. it has outstanding
		725	events but its callback has not yet been invoked). As long as a watcher
		726	is pending (but not active) you must not call an init function on it (but
		727	C<ev_TYPE_set> is safe) and you must make sure the watcher is available to
		728	libev (e.g. you cnanot C<free ()> it).
		729
		730	=item callback ev_cb (ev_TYPE *watcher)
		731
		732	Returns the callback currently set on the watcher.
		733
		734	=item ev_cb_set (ev_TYPE *watcher, callback)
		735
		736	Change the callback. You can change the callback at virtually any time
		737	(modulo threads).
		738
		739	=back
		740
398		741
399	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	742	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
400		743
401	Each watcher has, by default, a member C<void *data> that you can change	744	Each watcher has, by default, a member C<void *data> that you can change
402	and read at any time, libev will completely ignore it. This can be used	745	and read at any time, libev will completely ignore it. This can be used
…		…
420	{	763	{
421	struct my_io *w = (struct my_io *)w_;	764	struct my_io *w = (struct my_io *)w_;
422	...	765	...
423	}	766	}
424		767
425	More interesting and less C-conformant ways of catsing your callback type	768	More interesting and less C-conformant ways of casting your callback type
426	have been omitted....	769	instead have been omitted.
		770
		771	Another common scenario is having some data structure with multiple
		772	watchers:
		773
		774	struct my_biggy
		775	{
		776	int some_data;
		777	ev_timer t1;
		778	ev_timer t2;
		779	}
		780
		781	In this case getting the pointer to C<my_biggy> is a bit more complicated,
		782	you need to use C<offsetof>:
		783
		784	#include <stddef.h>
		785
		786	static void
		787	t1_cb (EV_P_ struct ev_timer *w, int revents)
		788	{
		789	struct my_biggy big = (struct my_biggy *
		790	(((char *)w) - offsetof (struct my_biggy, t1));
		791	}
		792
		793	static void
		794	t2_cb (EV_P_ struct ev_timer *w, int revents)
		795	{
		796	struct my_biggy big = (struct my_biggy *
		797	(((char *)w) - offsetof (struct my_biggy, t2));
		798	}
427		799
428		800
429	=head1 WATCHER TYPES	801	=head1 WATCHER TYPES
430		802
431	This section describes each watcher in detail, but will not repeat	803	This section describes each watcher in detail, but will not repeat
432	information given in the last section.	804	information given in the last section. Any initialisation/set macros,
		805	functions and members specific to the watcher type are explained.
433		806
		807	Members are additionally marked with either I<[read-only]>, meaning that,
		808	while the watcher is active, you can look at the member and expect some
		809	sensible content, but you must not modify it (you can modify it while the
		810	watcher is stopped to your hearts content), or I<[read-write]>, which
		811	means you can expect it to have some sensible content while the watcher
		812	is active, but you can also modify it. Modifying it may not do something
		813	sensible or take immediate effect (or do anything at all), but libev will
		814	not crash or malfunction in any way.
		815
		816
434	=head2 C<ev_io> - is this file descriptor readable or writable	817	=head2 C<ev_io> - is this file descriptor readable or writable?
435		818
436	I/O watchers check whether a file descriptor is readable or writable	819	I/O watchers check whether a file descriptor is readable or writable
437	in each iteration of the event loop (This behaviour is called	820	in each iteration of the event loop, or, more precisely, when reading
438	level-triggering because you keep receiving events as long as the	821	would not block the process and writing would at least be able to write
439	condition persists. Remember you can stop the watcher if you don't want to	822	some data. This behaviour is called level-triggering because you keep
440	act on the event and neither want to receive future events).	823	receiving events as long as the condition persists. Remember you can stop
		824	the watcher if you don't want to act on the event and neither want to
		825	receive future events.
441		826
442	In general you can register as many read and/or write event watchers per	827	In general you can register as many read and/or write event watchers per
443	fd as you want (as long as you don't confuse yourself). Setting all file	828	fd as you want (as long as you don't confuse yourself). Setting all file
444	descriptors to non-blocking mode is also usually a good idea (but not	829	descriptors to non-blocking mode is also usually a good idea (but not
445	required if you know what you are doing).	830	required if you know what you are doing).
446		831
447	You have to be careful with dup'ed file descriptors, though. Some backends	832	You have to be careful with dup'ed file descriptors, though. Some backends
448	(the linux epoll backend is a notable example) cannot handle dup'ed file	833	(the linux epoll backend is a notable example) cannot handle dup'ed file
449	descriptors correctly if you register interest in two or more fds pointing	834	descriptors correctly if you register interest in two or more fds pointing
450	to the same underlying file/socket etc. description (that is, they share	835	to the same underlying file/socket/etc. description (that is, they share
451	the same underlying "file open").	836	the same underlying "file open").
452		837
453	If you must do this, then force the use of a known-to-be-good backend	838	If you must do this, then force the use of a known-to-be-good backend
454	(at the time of this writing, this includes only EVMETHOD_SELECT and	839	(at the time of this writing, this includes only C<EVBACKEND_SELECT> and
455	EVMETHOD_POLL).	840	C<EVBACKEND_POLL>).
		841
		842	Another thing you have to watch out for is that it is quite easy to
		843	receive "spurious" readyness notifications, that is your callback might
		844	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
		845	because there is no data. Not only are some backends known to create a
		846	lot of those (for example solaris ports), it is very easy to get into
		847	this situation even with a relatively standard program structure. Thus
		848	it is best to always use non-blocking I/O: An extra C<read>(2) returning
		849	C<EAGAIN> is far preferable to a program hanging until some data arrives.
		850
		851	If you cannot run the fd in non-blocking mode (for example you should not
		852	play around with an Xlib connection), then you have to seperately re-test
		853	wether a file descriptor is really ready with a known-to-be good interface
		854	such as poll (fortunately in our Xlib example, Xlib already does this on
		855	its own, so its quite safe to use).
456		856
457	=over 4	857	=over 4
458		858
459	=item ev_io_init (ev_io *, callback, int fd, int events)	859	=item ev_io_init (ev_io *, callback, int fd, int events)
460		860
461	=item ev_io_set (ev_io *, int fd, int events)	861	=item ev_io_set (ev_io *, int fd, int events)
462		862
463	Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive	863	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to
464	events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ |	864	rceeive events for and events is either C<EV_READ>, C<EV_WRITE> or
465	EV_WRITE> to receive the given events.	865	C<EV_READ | EV_WRITE> to receive the given events.
		866
		867	=item int fd [read-only]
		868
		869	The file descriptor being watched.
		870
		871	=item int events [read-only]
		872
		873	The events being watched.
466		874
467	=back	875	=back
468		876
		877	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well
		878	readable, but only once. Since it is likely line-buffered, you could
		879	attempt to read a whole line in the callback.
		880
		881	static void
		882	stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)
		883	{
		884	ev_io_stop (loop, w);
		885	.. read from stdin here (or from w->fd) and haqndle any I/O errors
		886	}
		887
		888	...
		889	struct ev_loop *loop = ev_default_init (0);
		890	struct ev_io stdin_readable;
		891	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
		892	ev_io_start (loop, &stdin_readable);
		893	ev_loop (loop, 0);
		894
		895
469	=head2 C<ev_timer> - relative and optionally recurring timeouts	896	=head2 C<ev_timer> - relative and optionally repeating timeouts
470		897
471	Timer watchers are simple relative timers that generate an event after a	898	Timer watchers are simple relative timers that generate an event after a
472	given time, and optionally repeating in regular intervals after that.	899	given time, and optionally repeating in regular intervals after that.
473		900
474	The timers are based on real time, that is, if you register an event that	901	The timers are based on real time, that is, if you register an event that
475	times out after an hour and you reset your system clock to last years	902	times out after an hour and you reset your system clock to last years
476	time, it will still time out after (roughly) and hour. "Roughly" because	903	time, it will still time out after (roughly) and hour. "Roughly" because
477	detecting time jumps is hard, and soem inaccuracies are unavoidable (the	904	detecting time jumps is hard, and some inaccuracies are unavoidable (the
478	monotonic clock option helps a lot here).	905	monotonic clock option helps a lot here).
479		906
480	The relative timeouts are calculated relative to the C<ev_now ()>	907	The relative timeouts are calculated relative to the C<ev_now ()>
481	time. This is usually the right thing as this timestamp refers to the time	908	time. This is usually the right thing as this timestamp refers to the time
482	of the event triggering whatever timeout you are modifying/starting. If	909	of the event triggering whatever timeout you are modifying/starting. If
483	you suspect event processing to be delayed and you *need* to base the timeout	910	you suspect event processing to be delayed and you I<need> to base the timeout
484	on the current time, use something like this to adjust for this:	911	on the current time, use something like this to adjust for this:
485		912
486	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	913	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
		914
		915	The callback is guarenteed to be invoked only when its timeout has passed,
		916	but if multiple timers become ready during the same loop iteration then
		917	order of execution is undefined.
487		918
488	=over 4	919	=over 4
489		920
490	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	921	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
491		922
…		…
505	=item ev_timer_again (loop)	936	=item ev_timer_again (loop)
506		937
507	This will act as if the timer timed out and restart it again if it is	938	This will act as if the timer timed out and restart it again if it is
508	repeating. The exact semantics are:	939	repeating. The exact semantics are:
509		940
		941	If the timer is pending, its pending status is cleared.
		942
510	If the timer is started but nonrepeating, stop it.	943	If the timer is started but nonrepeating, stop it (as if it timed out).
511		944
512	If the timer is repeating, either start it if necessary (with the repeat	945	If the timer is repeating, either start it if necessary (with the
513	value), or reset the running timer to the repeat value.	946	C<repeat> value), or reset the running timer to the C<repeat> value.
514		947
515	This sounds a bit complicated, but here is a useful and typical	948	This sounds a bit complicated, but here is a useful and typical
516	example: Imagine you have a tcp connection and you want a so-called idle	949	example: Imagine you have a tcp connection and you want a so-called idle
517	timeout, that is, you want to be called when there have been, say, 60	950	timeout, that is, you want to be called when there have been, say, 60
518	seconds of inactivity on the socket. The easiest way to do this is to	951	seconds of inactivity on the socket. The easiest way to do this is to
519	configure an C<ev_timer> with after=repeat=60 and calling ev_timer_again each	952	configure an C<ev_timer> with a C<repeat> value of C<60> and then call
520	time you successfully read or write some data. If you go into an idle	953	C<ev_timer_again> each time you successfully read or write some data. If
521	state where you do not expect data to travel on the socket, you can stop	954	you go into an idle state where you do not expect data to travel on the
522	the timer, and again will automatically restart it if need be.	955	socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
		956	automatically restart it if need be.
		957
		958	That means you can ignore the C<after> value and C<ev_timer_start>
		959	altogether and only ever use the C<repeat> value and C<ev_timer_again>:
		960
		961	ev_timer_init (timer, callback, 0., 5.);
		962	ev_timer_again (loop, timer);
		963	...
		964	timer->again = 17.;
		965	ev_timer_again (loop, timer);
		966	...
		967	timer->again = 10.;
		968	ev_timer_again (loop, timer);
		969
		970	This is more slightly efficient then stopping/starting the timer each time
		971	you want to modify its timeout value.
		972
		973	=item ev_tstamp repeat [read-write]
		974
		975	The current C<repeat> value. Will be used each time the watcher times out
		976	or C<ev_timer_again> is called and determines the next timeout (if any),
		977	which is also when any modifications are taken into account.
523		978
524	=back	979	=back
525		980
		981	Example: Create a timer that fires after 60 seconds.
		982
		983	static void
		984	one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
		985	{
		986	.. one minute over, w is actually stopped right here
		987	}
		988
		989	struct ev_timer mytimer;
		990	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
		991	ev_timer_start (loop, &mytimer);
		992
		993	Example: Create a timeout timer that times out after 10 seconds of
		994	inactivity.
		995
		996	static void
		997	timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
		998	{
		999	.. ten seconds without any activity
		1000	}
		1001
		1002	struct ev_timer mytimer;
		1003	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
		1004	ev_timer_again (&mytimer); /* start timer */
		1005	ev_loop (loop, 0);
		1006
		1007	// and in some piece of code that gets executed on any "activity":
		1008	// reset the timeout to start ticking again at 10 seconds
		1009	ev_timer_again (&mytimer);
		1010
		1011
526	=head2 C<ev_periodic> - to cron or not to cron	1012	=head2 C<ev_periodic> - to cron or not to cron?
527		1013
528	Periodic watchers are also timers of a kind, but they are very versatile	1014	Periodic watchers are also timers of a kind, but they are very versatile
529	(and unfortunately a bit complex).	1015	(and unfortunately a bit complex).
530		1016
531	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	1017	Unlike C<ev_timer>'s, they are not based on real time (or relative time)
532	but on wallclock time (absolute time). You can tell a periodic watcher	1018	but on wallclock time (absolute time). You can tell a periodic watcher
533	to trigger "at" some specific point in time. For example, if you tell a	1019	to trigger "at" some specific point in time. For example, if you tell a
534	periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now ()	1020	periodic watcher to trigger in 10 seconds (by specifiying e.g. C<ev_now ()
535	+ 10.>) and then reset your system clock to the last year, then it will	1021	+ 10.>) and then reset your system clock to the last year, then it will
536	take a year to trigger the event (unlike an C<ev_timer>, which would trigger	1022	take a year to trigger the event (unlike an C<ev_timer>, which would trigger
537	roughly 10 seconds later and of course not if you reset your system time	1023	roughly 10 seconds later and of course not if you reset your system time
538	again).	1024	again).
539		1025
540	They can also be used to implement vastly more complex timers, such as	1026	They can also be used to implement vastly more complex timers, such as
541	triggering an event on eahc midnight, local time.	1027	triggering an event on eahc midnight, local time.
542		1028
		1029	As with timers, the callback is guarenteed to be invoked only when the
		1030	time (C<at>) has been passed, but if multiple periodic timers become ready
		1031	during the same loop iteration then order of execution is undefined.
		1032
543	=over 4	1033	=over 4
544		1034
545	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	1035	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)
546		1036
547	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	1037	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)
548		1038
549	Lots of arguments, lets sort it out... There are basically three modes of	1039	Lots of arguments, lets sort it out... There are basically three modes of
550	operation, and we will explain them from simplest to complex:	1040	operation, and we will explain them from simplest to complex:
551
552		1041
553	=over 4	1042	=over 4
554		1043
555	=item * absolute timer (interval = reschedule_cb = 0)	1044	=item * absolute timer (interval = reschedule_cb = 0)
556		1045
…		…
620	Simply stops and restarts the periodic watcher again. This is only useful	1109	Simply stops and restarts the periodic watcher again. This is only useful
621	when you changed some parameters or the reschedule callback would return	1110	when you changed some parameters or the reschedule callback would return
622	a different time than the last time it was called (e.g. in a crond like	1111	a different time than the last time it was called (e.g. in a crond like
623	program when the crontabs have changed).	1112	program when the crontabs have changed).
624		1113
		1114	=item ev_tstamp interval [read-write]
		1115
		1116	The current interval value. Can be modified any time, but changes only
		1117	take effect when the periodic timer fires or C<ev_periodic_again> is being
		1118	called.
		1119
		1120	=item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]
		1121
		1122	The current reschedule callback, or C<0>, if this functionality is
		1123	switched off. Can be changed any time, but changes only take effect when
		1124	the periodic timer fires or C<ev_periodic_again> is being called.
		1125
625	=back	1126	=back
626		1127
		1128	Example: Call a callback every hour, or, more precisely, whenever the
		1129	system clock is divisible by 3600. The callback invocation times have
		1130	potentially a lot of jittering, but good long-term stability.
		1131
		1132	static void
		1133	clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)
		1134	{
		1135	... its now a full hour (UTC, or TAI or whatever your clock follows)
		1136	}
		1137
		1138	struct ev_periodic hourly_tick;
		1139	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
		1140	ev_periodic_start (loop, &hourly_tick);
		1141
		1142	Example: The same as above, but use a reschedule callback to do it:
		1143
		1144	#include <math.h>
		1145
		1146	static ev_tstamp
		1147	my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)
		1148	{
		1149	return fmod (now, 3600.) + 3600.;
		1150	}
		1151
		1152	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
		1153
		1154	Example: Call a callback every hour, starting now:
		1155
		1156	struct ev_periodic hourly_tick;
		1157	ev_periodic_init (&hourly_tick, clock_cb,
		1158	fmod (ev_now (loop), 3600.), 3600., 0);
		1159	ev_periodic_start (loop, &hourly_tick);
		1160
		1161
627	=head2 C<ev_signal> - signal me when a signal gets signalled	1162	=head2 C<ev_signal> - signal me when a signal gets signalled!
628		1163
629	Signal watchers will trigger an event when the process receives a specific	1164	Signal watchers will trigger an event when the process receives a specific
630	signal one or more times. Even though signals are very asynchronous, libev	1165	signal one or more times. Even though signals are very asynchronous, libev
631	will try it's best to deliver signals synchronously, i.e. as part of the	1166	will try it's best to deliver signals synchronously, i.e. as part of the
632	normal event processing, like any other event.	1167	normal event processing, like any other event.
…		…
645	=item ev_signal_set (ev_signal *, int signum)	1180	=item ev_signal_set (ev_signal *, int signum)
646		1181
647	Configures the watcher to trigger on the given signal number (usually one	1182	Configures the watcher to trigger on the given signal number (usually one
648	of the C<SIGxxx> constants).	1183	of the C<SIGxxx> constants).
649		1184
		1185	=item int signum [read-only]
		1186
		1187	The signal the watcher watches out for.
		1188
650	=back	1189	=back
651		1190
		1191
652	=head2 C<ev_child> - wait for pid status changes	1192	=head2 C<ev_child> - watch out for process status changes
653		1193
654	Child watchers trigger when your process receives a SIGCHLD in response to	1194	Child watchers trigger when your process receives a SIGCHLD in response to
655	some child status changes (most typically when a child of yours dies).	1195	some child status changes (most typically when a child of yours dies).
656		1196
657	=over 4	1197	=over 4
…		…
665	at the C<rstatus> member of the C<ev_child> watcher structure to see	1205	at the C<rstatus> member of the C<ev_child> watcher structure to see
666	the status word (use the macros from C<sys/wait.h> and see your systems	1206	the status word (use the macros from C<sys/wait.h> and see your systems
667	C<waitpid> documentation). The C<rpid> member contains the pid of the	1207	C<waitpid> documentation). The C<rpid> member contains the pid of the
668	process causing the status change.	1208	process causing the status change.
669		1209
		1210	=item int pid [read-only]
		1211
		1212	The process id this watcher watches out for, or C<0>, meaning any process id.
		1213
		1214	=item int rpid [read-write]
		1215
		1216	The process id that detected a status change.
		1217
		1218	=item int rstatus [read-write]
		1219
		1220	The process exit/trace status caused by C<rpid> (see your systems
		1221	C<waitpid> and C<sys/wait.h> documentation for details).
		1222
670	=back	1223	=back
671		1224
		1225	Example: Try to exit cleanly on SIGINT and SIGTERM.
		1226
		1227	static void
		1228	sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
		1229	{
		1230	ev_unloop (loop, EVUNLOOP_ALL);
		1231	}
		1232
		1233	struct ev_signal signal_watcher;
		1234	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
		1235	ev_signal_start (loop, &sigint_cb);
		1236
		1237
		1238	=head2 C<ev_stat> - did the file attributes just change?
		1239
		1240	This watches a filesystem path for attribute changes. That is, it calls
		1241	C<stat> regularly (or when the OS says it changed) and sees if it changed
		1242	compared to the last time, invoking the callback if it did.
		1243
		1244	The path does not need to exist: changing from "path exists" to "path does
		1245	not exist" is a status change like any other. The condition "path does
		1246	not exist" is signified by the C<st_nlink> field being zero (which is
		1247	otherwise always forced to be at least one) and all the other fields of
		1248	the stat buffer having unspecified contents.
		1249
		1250	The path I<should> be absolute and I<must not> end in a slash. If it is
		1251	relative and your working directory changes, the behaviour is undefined.
		1252
		1253	Since there is no standard to do this, the portable implementation simply
		1254	calls C<stat (2)> regularly on the path to see if it changed somehow. You
		1255	can specify a recommended polling interval for this case. If you specify
		1256	a polling interval of C<0> (highly recommended!) then a I<suitable,
		1257	unspecified default> value will be used (which you can expect to be around
		1258	five seconds, although this might change dynamically). Libev will also
		1259	impose a minimum interval which is currently around C<0.1>, but thats
		1260	usually overkill.
		1261
		1262	This watcher type is not meant for massive numbers of stat watchers,
		1263	as even with OS-supported change notifications, this can be
		1264	resource-intensive.
		1265
		1266	At the time of this writing, only the Linux inotify interface is
		1267	implemented (implementing kqueue support is left as an exercise for the
		1268	reader). Inotify will be used to give hints only and should not change the
		1269	semantics of C<ev_stat> watchers, which means that libev sometimes needs
		1270	to fall back to regular polling again even with inotify, but changes are
		1271	usually detected immediately, and if the file exists there will be no
		1272	polling.
		1273
		1274	=over 4
		1275
		1276	=item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)
		1277
		1278	=item ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)
		1279
		1280	Configures the watcher to wait for status changes of the given
		1281	C<path>. The C<interval> is a hint on how quickly a change is expected to
		1282	be detected and should normally be specified as C<0> to let libev choose
		1283	a suitable value. The memory pointed to by C<path> must point to the same
		1284	path for as long as the watcher is active.
		1285
		1286	The callback will be receive C<EV_STAT> when a change was detected,
		1287	relative to the attributes at the time the watcher was started (or the
		1288	last change was detected).
		1289
		1290	=item ev_stat_stat (ev_stat *)
		1291
		1292	Updates the stat buffer immediately with new values. If you change the
		1293	watched path in your callback, you could call this fucntion to avoid
		1294	detecting this change (while introducing a race condition). Can also be
		1295	useful simply to find out the new values.
		1296
		1297	=item ev_statdata attr [read-only]
		1298
		1299	The most-recently detected attributes of the file. Although the type is of
		1300	C<ev_statdata>, this is usually the (or one of the) C<struct stat> types
		1301	suitable for your system. If the C<st_nlink> member is C<0>, then there
		1302	was some error while C<stat>ing the file.
		1303
		1304	=item ev_statdata prev [read-only]
		1305
		1306	The previous attributes of the file. The callback gets invoked whenever
		1307	C<prev> != C<attr>.
		1308
		1309	=item ev_tstamp interval [read-only]
		1310
		1311	The specified interval.
		1312
		1313	=item const char *path [read-only]
		1314
		1315	The filesystem path that is being watched.
		1316
		1317	=back
		1318
		1319	Example: Watch C</etc/passwd> for attribute changes.
		1320
		1321	static void
		1322	passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
		1323	{
		1324	/* /etc/passwd changed in some way */
		1325	if (w->attr.st_nlink)
		1326	{
		1327	printf ("passwd current size %ld\n", (long)w->attr.st_size);
		1328	printf ("passwd current atime %ld\n", (long)w->attr.st_mtime);
		1329	printf ("passwd current mtime %ld\n", (long)w->attr.st_mtime);
		1330	}
		1331	else
		1332	/* you shalt not abuse printf for puts */
		1333	puts ("wow, /etc/passwd is not there, expect problems. "
		1334	"if this is windows, they already arrived\n");
		1335	}
		1336
		1337	...
		1338	ev_stat passwd;
		1339
		1340	ev_stat_init (&passwd, passwd_cb, "/etc/passwd");
		1341	ev_stat_start (loop, &passwd);
		1342
		1343
672	=head2 C<ev_idle> - when you've got nothing better to do	1344	=head2 C<ev_idle> - when you've got nothing better to do...
673		1345
674	Idle watchers trigger events when there are no other events are pending	1346	Idle watchers trigger events when there are no other events are pending
675	(prepare, check and other idle watchers do not count). That is, as long	1347	(prepare, check and other idle watchers do not count). That is, as long
676	as your process is busy handling sockets or timeouts (or even signals,	1348	as your process is busy handling sockets or timeouts (or even signals,
677	imagine) it will not be triggered. But when your process is idle all idle	1349	imagine) it will not be triggered. But when your process is idle all idle
…		…
695	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	1367	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
696	believe me.	1368	believe me.
697		1369
698	=back	1370	=back
699		1371
		1372	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
		1373	callback, free it. Also, use no error checking, as usual.
		1374
		1375	static void
		1376	idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)
		1377	{
		1378	free (w);
		1379	// now do something you wanted to do when the program has
		1380	// no longer asnything immediate to do.
		1381	}
		1382
		1383	struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));
		1384	ev_idle_init (idle_watcher, idle_cb);
		1385	ev_idle_start (loop, idle_cb);
		1386
		1387
700	=head2 C<ev_prepare> and C<ev_check> - customise your event loop	1388	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
701		1389
702	Prepare and check watchers are usually (but not always) used in tandem:	1390	Prepare and check watchers are usually (but not always) used in tandem:
703	prepare watchers get invoked before the process blocks and check watchers	1391	prepare watchers get invoked before the process blocks and check watchers
704	afterwards.	1392	afterwards.
705		1393
		1394	You I<must not> call C<ev_loop> or similar functions that enter
		1395	the current event loop from either C<ev_prepare> or C<ev_check>
		1396	watchers. Other loops than the current one are fine, however. The
		1397	rationale behind this is that you do not need to check for recursion in
		1398	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
		1399	C<ev_check> so if you have one watcher of each kind they will always be
		1400	called in pairs bracketing the blocking call.
		1401
706	Their main purpose is to integrate other event mechanisms into libev. This	1402	Their main purpose is to integrate other event mechanisms into libev and
707	could be used, for example, to track variable changes, implement your own	1403	their use is somewhat advanced. This could be used, for example, to track
708	watchers, integrate net-snmp or a coroutine library and lots more.	1404	variable changes, implement your own watchers, integrate net-snmp or a
		1405	coroutine library and lots more. They are also occasionally useful if
		1406	you cache some data and want to flush it before blocking (for example,
		1407	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>
		1408	watcher).
709		1409
710	This is done by examining in each prepare call which file descriptors need	1410	This is done by examining in each prepare call which file descriptors need
711	to be watched by the other library, registering C<ev_io> watchers for	1411	to be watched by the other library, registering C<ev_io> watchers for
712	them and starting an C<ev_timer> watcher for any timeouts (many libraries	1412	them and starting an C<ev_timer> watcher for any timeouts (many libraries
713	provide just this functionality). Then, in the check watcher you check for	1413	provide just this functionality). Then, in the check watcher you check for
…		…
735	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>	1435	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>
736	macros, but using them is utterly, utterly and completely pointless.	1436	macros, but using them is utterly, utterly and completely pointless.
737		1437
738	=back	1438	=back
739		1439
		1440	Example: To include a library such as adns, you would add IO watchers
		1441	and a timeout watcher in a prepare handler, as required by libadns, and
		1442	in a check watcher, destroy them and call into libadns. What follows is
		1443	pseudo-code only of course:
		1444
		1445	static ev_io iow [nfd];
		1446	static ev_timer tw;
		1447
		1448	static void
		1449	io_cb (ev_loop *loop, ev_io *w, int revents)
		1450	{
		1451	// set the relevant poll flags
		1452	// could also call adns_processreadable etc. here
		1453	struct pollfd *fd = (struct pollfd *)w->data;
		1454	if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
		1455	if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
		1456	}
		1457
		1458	// create io watchers for each fd and a timer before blocking
		1459	static void
		1460	adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
		1461	{
		1462	int timeout = 3600000;truct pollfd fds [nfd];
		1463	// actual code will need to loop here and realloc etc.
		1464	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
		1465
		1466	/* the callback is illegal, but won't be called as we stop during check */
		1467	ev_timer_init (&tw, 0, timeout * 1e-3);
		1468	ev_timer_start (loop, &tw);
		1469
		1470	// create on ev_io per pollfd
		1471	for (int i = 0; i < nfd; ++i)
		1472	{
		1473	ev_io_init (iow + i, io_cb, fds [i].fd,
		1474	((fds [i].events & POLLIN ? EV_READ : 0)
		1475	| (fds [i].events & POLLOUT ? EV_WRITE : 0)));
		1476
		1477	fds [i].revents = 0;
		1478	iow [i].data = fds + i;
		1479	ev_io_start (loop, iow + i);
		1480	}
		1481	}
		1482
		1483	// stop all watchers after blocking
		1484	static void
		1485	adns_check_cb (ev_loop *loop, ev_check *w, int revents)
		1486	{
		1487	ev_timer_stop (loop, &tw);
		1488
		1489	for (int i = 0; i < nfd; ++i)
		1490	ev_io_stop (loop, iow + i);
		1491
		1492	adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
		1493	}
		1494
		1495
		1496	=head2 C<ev_embed> - when one backend isn't enough...
		1497
		1498	This is a rather advanced watcher type that lets you embed one event loop
		1499	into another (currently only C<ev_io> events are supported in the embedded
		1500	loop, other types of watchers might be handled in a delayed or incorrect
		1501	fashion and must not be used).
		1502
		1503	There are primarily two reasons you would want that: work around bugs and
		1504	prioritise I/O.
		1505
		1506	As an example for a bug workaround, the kqueue backend might only support
		1507	sockets on some platform, so it is unusable as generic backend, but you
		1508	still want to make use of it because you have many sockets and it scales
		1509	so nicely. In this case, you would create a kqueue-based loop and embed it
		1510	into your default loop (which might use e.g. poll). Overall operation will
		1511	be a bit slower because first libev has to poll and then call kevent, but
		1512	at least you can use both at what they are best.
		1513
		1514	As for prioritising I/O: rarely you have the case where some fds have
		1515	to be watched and handled very quickly (with low latency), and even
		1516	priorities and idle watchers might have too much overhead. In this case
		1517	you would put all the high priority stuff in one loop and all the rest in
		1518	a second one, and embed the second one in the first.
		1519
		1520	As long as the watcher is active, the callback will be invoked every time
		1521	there might be events pending in the embedded loop. The callback must then
		1522	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke
		1523	their callbacks (you could also start an idle watcher to give the embedded
		1524	loop strictly lower priority for example). You can also set the callback
		1525	to C<0>, in which case the embed watcher will automatically execute the
		1526	embedded loop sweep.
		1527
		1528	As long as the watcher is started it will automatically handle events. The
		1529	callback will be invoked whenever some events have been handled. You can
		1530	set the callback to C<0> to avoid having to specify one if you are not
		1531	interested in that.
		1532
		1533	Also, there have not currently been made special provisions for forking:
		1534	when you fork, you not only have to call C<ev_loop_fork> on both loops,
		1535	but you will also have to stop and restart any C<ev_embed> watchers
		1536	yourself.
		1537
		1538	Unfortunately, not all backends are embeddable, only the ones returned by
		1539	C<ev_embeddable_backends> are, which, unfortunately, does not include any
		1540	portable one.
		1541
		1542	So when you want to use this feature you will always have to be prepared
		1543	that you cannot get an embeddable loop. The recommended way to get around
		1544	this is to have a separate variables for your embeddable loop, try to
		1545	create it, and if that fails, use the normal loop for everything:
		1546
		1547	struct ev_loop *loop_hi = ev_default_init (0);
		1548	struct ev_loop *loop_lo = 0;
		1549	struct ev_embed embed;
		1550
		1551	// see if there is a chance of getting one that works
		1552	// (remember that a flags value of 0 means autodetection)
		1553	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
		1554	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
		1555	: 0;
		1556
		1557	// if we got one, then embed it, otherwise default to loop_hi
		1558	if (loop_lo)
		1559	{
		1560	ev_embed_init (&embed, 0, loop_lo);
		1561	ev_embed_start (loop_hi, &embed);
		1562	}
		1563	else
		1564	loop_lo = loop_hi;
		1565
		1566	=over 4
		1567
		1568	=item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)
		1569
		1570	=item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)
		1571
		1572	Configures the watcher to embed the given loop, which must be
		1573	embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be
		1574	invoked automatically, otherwise it is the responsibility of the callback
		1575	to invoke it (it will continue to be called until the sweep has been done,
		1576	if you do not want thta, you need to temporarily stop the embed watcher).
		1577
		1578	=item ev_embed_sweep (loop, ev_embed *)
		1579
		1580	Make a single, non-blocking sweep over the embedded loop. This works
		1581	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most
		1582	apropriate way for embedded loops.
		1583
		1584	=item struct ev_loop *loop [read-only]
		1585
		1586	The embedded event loop.
		1587
		1588	=back
		1589
		1590
		1591	=head2 C<ev_fork> - the audacity to resume the event loop after a fork
		1592
		1593	Fork watchers are called when a C<fork ()> was detected (usually because
		1594	whoever is a good citizen cared to tell libev about it by calling
		1595	C<ev_default_fork> or C<ev_loop_fork>). The invocation is done before the
		1596	event loop blocks next and before C<ev_check> watchers are being called,
		1597	and only in the child after the fork. If whoever good citizen calling
		1598	C<ev_default_fork> cheats and calls it in the wrong process, the fork
		1599	handlers will be invoked, too, of course.
		1600
		1601	=over 4
		1602
		1603	=item ev_fork_init (ev_signal *, callback)
		1604
		1605	Initialises and configures the fork watcher - it has no parameters of any
		1606	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
		1607	believe me.
		1608
		1609	=back
		1610
		1611
740	=head1 OTHER FUNCTIONS	1612	=head1 OTHER FUNCTIONS
741		1613
742	There are some other functions of possible interest. Described. Here. Now.	1614	There are some other functions of possible interest. Described. Here. Now.
743		1615
744	=over 4	1616	=over 4
…		…
773	/* stdin might have data for us, joy! */;	1645	/* stdin might have data for us, joy! */;
774	}	1646	}
775		1647
776	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	1648	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
777		1649
778	=item ev_feed_event (loop, watcher, int events)	1650	=item ev_feed_event (ev_loop *, watcher *, int revents)
779		1651
780	Feeds the given event set into the event loop, as if the specified event	1652	Feeds the given event set into the event loop, as if the specified event
781	had happened for the specified watcher (which must be a pointer to an	1653	had happened for the specified watcher (which must be a pointer to an
782	initialised but not necessarily started event watcher).	1654	initialised but not necessarily started event watcher).
783		1655
784	=item ev_feed_fd_event (loop, int fd, int revents)	1656	=item ev_feed_fd_event (ev_loop *, int fd, int revents)
785		1657
786	Feed an event on the given fd, as if a file descriptor backend detected	1658	Feed an event on the given fd, as if a file descriptor backend detected
787	the given events it.	1659	the given events it.
788		1660
789	=item ev_feed_signal_event (loop, int signum)	1661	=item ev_feed_signal_event (ev_loop *loop, int signum)
790		1662
791	Feed an event as if the given signal occured (loop must be the default loop!).	1663	Feed an event as if the given signal occured (C<loop> must be the default
		1664	loop!).
792		1665
793	=back	1666	=back
		1667
794		1668
795	=head1 LIBEVENT EMULATION	1669	=head1 LIBEVENT EMULATION
796		1670
797	Libev offers a compatibility emulation layer for libevent. It cannot	1671	Libev offers a compatibility emulation layer for libevent. It cannot
798	emulate the internals of libevent, so here are some usage hints:	1672	emulate the internals of libevent, so here are some usage hints:
…		…
819		1693
820	=back	1694	=back
821		1695
822	=head1 C++ SUPPORT	1696	=head1 C++ SUPPORT
823		1697
824	TBD.	1698	Libev comes with some simplistic wrapper classes for C++ that mainly allow
		1699	you to use some convinience methods to start/stop watchers and also change
		1700	the callback model to a model using method callbacks on objects.
		1701
		1702	To use it,
		1703
		1704	#include <ev++.h>
		1705
		1706	(it is not installed by default). This automatically includes F<ev.h>
		1707	and puts all of its definitions (many of them macros) into the global
		1708	namespace. All C++ specific things are put into the C<ev> namespace.
		1709
		1710	It should support all the same embedding options as F<ev.h>, most notably
		1711	C<EV_MULTIPLICITY>.
		1712
		1713	Here is a list of things available in the C<ev> namespace:
		1714
		1715	=over 4
		1716
		1717	=item C<ev::READ>, C<ev::WRITE> etc.
		1718
		1719	These are just enum values with the same values as the C<EV_READ> etc.
		1720	macros from F<ev.h>.
		1721
		1722	=item C<ev::tstamp>, C<ev::now>
		1723
		1724	Aliases to the same types/functions as with the C<ev_> prefix.
		1725
		1726	=item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc.
		1727
		1728	For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of
		1729	the same name in the C<ev> namespace, with the exception of C<ev_signal>
		1730	which is called C<ev::sig> to avoid clashes with the C<signal> macro
		1731	defines by many implementations.
		1732
		1733	All of those classes have these methods:
		1734
		1735	=over 4
		1736
		1737	=item ev::TYPE::TYPE (object *, object::method *)
		1738
		1739	=item ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)
		1740
		1741	=item ev::TYPE::~TYPE
		1742
		1743	The constructor takes a pointer to an object and a method pointer to
		1744	the event handler callback to call in this class. The constructor calls
		1745	C<ev_init> for you, which means you have to call the C<set> method
		1746	before starting it. If you do not specify a loop then the constructor
		1747	automatically associates the default loop with this watcher.
		1748
		1749	The destructor automatically stops the watcher if it is active.
		1750
		1751	=item w->set (struct ev_loop *)
		1752
		1753	Associates a different C<struct ev_loop> with this watcher. You can only
		1754	do this when the watcher is inactive (and not pending either).
		1755
		1756	=item w->set ([args])
		1757
		1758	Basically the same as C<ev_TYPE_set>, with the same args. Must be
		1759	called at least once. Unlike the C counterpart, an active watcher gets
		1760	automatically stopped and restarted.
		1761
		1762	=item w->start ()
		1763
		1764	Starts the watcher. Note that there is no C<loop> argument as the
		1765	constructor already takes the loop.
		1766
		1767	=item w->stop ()
		1768
		1769	Stops the watcher if it is active. Again, no C<loop> argument.
		1770
		1771	=item w->again () C<ev::timer>, C<ev::periodic> only
		1772
		1773	For C<ev::timer> and C<ev::periodic>, this invokes the corresponding
		1774	C<ev_TYPE_again> function.
		1775
		1776	=item w->sweep () C<ev::embed> only
		1777
		1778	Invokes C<ev_embed_sweep>.
		1779
		1780	=item w->update () C<ev::stat> only
		1781
		1782	Invokes C<ev_stat_stat>.
		1783
		1784	=back
		1785
		1786	=back
		1787
		1788	Example: Define a class with an IO and idle watcher, start one of them in
		1789	the constructor.
		1790
		1791	class myclass
		1792	{
		1793	ev_io io; void io_cb (ev::io &w, int revents);
		1794	ev_idle idle void idle_cb (ev::idle &w, int revents);
		1795
		1796	myclass ();
		1797	}
		1798
		1799	myclass::myclass (int fd)
		1800	: io (this, &myclass::io_cb),
		1801	idle (this, &myclass::idle_cb)
		1802	{
		1803	io.start (fd, ev::READ);
		1804	}
		1805
		1806
		1807	=head1 MACRO MAGIC
		1808
		1809	Libev can be compiled with a variety of options, the most fundemantal is
		1810	C<EV_MULTIPLICITY>. This option determines wether (most) functions and
		1811	callbacks have an initial C<struct ev_loop *> argument.
		1812
		1813	To make it easier to write programs that cope with either variant, the
		1814	following macros are defined:
		1815
		1816	=over 4
		1817
		1818	=item C<EV_A>, C<EV_A_>
		1819
		1820	This provides the loop I<argument> for functions, if one is required ("ev
		1821	loop argument"). The C<EV_A> form is used when this is the sole argument,
		1822	C<EV_A_> is used when other arguments are following. Example:
		1823
		1824	ev_unref (EV_A);
		1825	ev_timer_add (EV_A_ watcher);
		1826	ev_loop (EV_A_ 0);
		1827
		1828	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
		1829	which is often provided by the following macro.
		1830
		1831	=item C<EV_P>, C<EV_P_>
		1832
		1833	This provides the loop I<parameter> for functions, if one is required ("ev
		1834	loop parameter"). The C<EV_P> form is used when this is the sole parameter,
		1835	C<EV_P_> is used when other parameters are following. Example:
		1836
		1837	// this is how ev_unref is being declared
		1838	static void ev_unref (EV_P);
		1839
		1840	// this is how you can declare your typical callback
		1841	static void cb (EV_P_ ev_timer *w, int revents)
		1842
		1843	It declares a parameter C<loop> of type C<struct ev_loop *>, quite
		1844	suitable for use with C<EV_A>.
		1845
		1846	=item C<EV_DEFAULT>, C<EV_DEFAULT_>
		1847
		1848	Similar to the other two macros, this gives you the value of the default
		1849	loop, if multiple loops are supported ("ev loop default").
		1850
		1851	=back
		1852
		1853	Example: Declare and initialise a check watcher, working regardless of
		1854	wether multiple loops are supported or not.
		1855
		1856	static void
		1857	check_cb (EV_P_ ev_timer *w, int revents)
		1858	{
		1859	ev_check_stop (EV_A_ w);
		1860	}
		1861
		1862	ev_check check;
		1863	ev_check_init (&check, check_cb);
		1864	ev_check_start (EV_DEFAULT_ &check);
		1865	ev_loop (EV_DEFAULT_ 0);
		1866
		1867
		1868	=head1 EMBEDDING
		1869
		1870	Libev can (and often is) directly embedded into host
		1871	applications. Examples of applications that embed it include the Deliantra
		1872	Game Server, the EV perl module, the GNU Virtual Private Ethernet (gvpe)
		1873	and rxvt-unicode.
		1874
		1875	The goal is to enable you to just copy the neecssary files into your
		1876	source directory without having to change even a single line in them, so
		1877	you can easily upgrade by simply copying (or having a checked-out copy of
		1878	libev somewhere in your source tree).
		1879
		1880	=head2 FILESETS
		1881
		1882	Depending on what features you need you need to include one or more sets of files
		1883	in your app.
		1884
		1885	=head3 CORE EVENT LOOP
		1886
		1887	To include only the libev core (all the C<ev_*> functions), with manual
		1888	configuration (no autoconf):
		1889
		1890	#define EV_STANDALONE 1
		1891	#include "ev.c"
		1892
		1893	This will automatically include F<ev.h>, too, and should be done in a
		1894	single C source file only to provide the function implementations. To use
		1895	it, do the same for F<ev.h> in all files wishing to use this API (best
		1896	done by writing a wrapper around F<ev.h> that you can include instead and
		1897	where you can put other configuration options):
		1898
		1899	#define EV_STANDALONE 1
		1900	#include "ev.h"
		1901
		1902	Both header files and implementation files can be compiled with a C++
		1903	compiler (at least, thats a stated goal, and breakage will be treated
		1904	as a bug).
		1905
		1906	You need the following files in your source tree, or in a directory
		1907	in your include path (e.g. in libev/ when using -Ilibev):
		1908
		1909	ev.h
		1910	ev.c
		1911	ev_vars.h
		1912	ev_wrap.h
		1913
		1914	ev_win32.c required on win32 platforms only
		1915
		1916	ev_select.c only when select backend is enabled (which is by default)
		1917	ev_poll.c only when poll backend is enabled (disabled by default)
		1918	ev_epoll.c only when the epoll backend is enabled (disabled by default)
		1919	ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
		1920	ev_port.c only when the solaris port backend is enabled (disabled by default)
		1921
		1922	F<ev.c> includes the backend files directly when enabled, so you only need
		1923	to compile this single file.
		1924
		1925	=head3 LIBEVENT COMPATIBILITY API
		1926
		1927	To include the libevent compatibility API, also include:
		1928
		1929	#include "event.c"
		1930
		1931	in the file including F<ev.c>, and:
		1932
		1933	#include "event.h"
		1934
		1935	in the files that want to use the libevent API. This also includes F<ev.h>.
		1936
		1937	You need the following additional files for this:
		1938
		1939	event.h
		1940	event.c
		1941
		1942	=head3 AUTOCONF SUPPORT
		1943
		1944	Instead of using C<EV_STANDALONE=1> and providing your config in
		1945	whatever way you want, you can also C<m4_include([libev.m4])> in your
		1946	F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then
		1947	include F<config.h> and configure itself accordingly.
		1948
		1949	For this of course you need the m4 file:
		1950
		1951	libev.m4
		1952
		1953	=head2 PREPROCESSOR SYMBOLS/MACROS
		1954
		1955	Libev can be configured via a variety of preprocessor symbols you have to define
		1956	before including any of its files. The default is not to build for multiplicity
		1957	and only include the select backend.
		1958
		1959	=over 4
		1960
		1961	=item EV_STANDALONE
		1962
		1963	Must always be C<1> if you do not use autoconf configuration, which
		1964	keeps libev from including F<config.h>, and it also defines dummy
		1965	implementations for some libevent functions (such as logging, which is not
		1966	supported). It will also not define any of the structs usually found in
		1967	F<event.h> that are not directly supported by the libev core alone.
		1968
		1969	=item EV_USE_MONOTONIC
		1970
		1971	If defined to be C<1>, libev will try to detect the availability of the
		1972	monotonic clock option at both compiletime and runtime. Otherwise no use
		1973	of the monotonic clock option will be attempted. If you enable this, you
		1974	usually have to link against librt or something similar. Enabling it when
		1975	the functionality isn't available is safe, though, althoguh you have
		1976	to make sure you link against any libraries where the C<clock_gettime>
		1977	function is hiding in (often F<-lrt>).
		1978
		1979	=item EV_USE_REALTIME
		1980
		1981	If defined to be C<1>, libev will try to detect the availability of the
		1982	realtime clock option at compiletime (and assume its availability at
		1983	runtime if successful). Otherwise no use of the realtime clock option will
		1984	be attempted. This effectively replaces C<gettimeofday> by C<clock_get
		1985	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See tzhe note about libraries
		1986	in the description of C<EV_USE_MONOTONIC>, though.
		1987
		1988	=item EV_USE_SELECT
		1989
		1990	If undefined or defined to be C<1>, libev will compile in support for the
		1991	C<select>(2) backend. No attempt at autodetection will be done: if no
		1992	other method takes over, select will be it. Otherwise the select backend
		1993	will not be compiled in.
		1994
		1995	=item EV_SELECT_USE_FD_SET
		1996
		1997	If defined to C<1>, then the select backend will use the system C<fd_set>
		1998	structure. This is useful if libev doesn't compile due to a missing
		1999	C<NFDBITS> or C<fd_mask> definition or it misguesses the bitset layout on
		2000	exotic systems. This usually limits the range of file descriptors to some
		2001	low limit such as 1024 or might have other limitations (winsocket only
		2002	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might
		2003	influence the size of the C<fd_set> used.
		2004
		2005	=item EV_SELECT_IS_WINSOCKET
		2006
		2007	When defined to C<1>, the select backend will assume that
		2008	select/socket/connect etc. don't understand file descriptors but
		2009	wants osf handles on win32 (this is the case when the select to
		2010	be used is the winsock select). This means that it will call
		2011	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
		2012	it is assumed that all these functions actually work on fds, even
		2013	on win32. Should not be defined on non-win32 platforms.
		2014
		2015	=item EV_USE_POLL
		2016
		2017	If defined to be C<1>, libev will compile in support for the C<poll>(2)
		2018	backend. Otherwise it will be enabled on non-win32 platforms. It
		2019	takes precedence over select.
		2020
		2021	=item EV_USE_EPOLL
		2022
		2023	If defined to be C<1>, libev will compile in support for the Linux
		2024	C<epoll>(7) backend. Its availability will be detected at runtime,
		2025	otherwise another method will be used as fallback. This is the
		2026	preferred backend for GNU/Linux systems.
		2027
		2028	=item EV_USE_KQUEUE
		2029
		2030	If defined to be C<1>, libev will compile in support for the BSD style
		2031	C<kqueue>(2) backend. Its actual availability will be detected at runtime,
		2032	otherwise another method will be used as fallback. This is the preferred
		2033	backend for BSD and BSD-like systems, although on most BSDs kqueue only
		2034	supports some types of fds correctly (the only platform we found that
		2035	supports ptys for example was NetBSD), so kqueue might be compiled in, but
		2036	not be used unless explicitly requested. The best way to use it is to find
		2037	out whether kqueue supports your type of fd properly and use an embedded
		2038	kqueue loop.
		2039
		2040	=item EV_USE_PORT
		2041
		2042	If defined to be C<1>, libev will compile in support for the Solaris
		2043	10 port style backend. Its availability will be detected at runtime,
		2044	otherwise another method will be used as fallback. This is the preferred
		2045	backend for Solaris 10 systems.
		2046
		2047	=item EV_USE_DEVPOLL
		2048
		2049	reserved for future expansion, works like the USE symbols above.
		2050
		2051	=item EV_USE_INOTIFY
		2052
		2053	If defined to be C<1>, libev will compile in support for the Linux inotify
		2054	interface to speed up C<ev_stat> watchers. Its actual availability will
		2055	be detected at runtime.
		2056
		2057	=item EV_H
		2058
		2059	The name of the F<ev.h> header file used to include it. The default if
		2060	undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This
		2061	can be used to virtually rename the F<ev.h> header file in case of conflicts.
		2062
		2063	=item EV_CONFIG_H
		2064
		2065	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
		2066	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
		2067	C<EV_H>, above.
		2068
		2069	=item EV_EVENT_H
		2070
		2071	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
		2072	of how the F<event.h> header can be found.
		2073
		2074	=item EV_PROTOTYPES
		2075
		2076	If defined to be C<0>, then F<ev.h> will not define any function
		2077	prototypes, but still define all the structs and other symbols. This is
		2078	occasionally useful if you want to provide your own wrapper functions
		2079	around libev functions.
		2080
		2081	=item EV_MULTIPLICITY
		2082
		2083	If undefined or defined to C<1>, then all event-loop-specific functions
		2084	will have the C<struct ev_loop *> as first argument, and you can create
		2085	additional independent event loops. Otherwise there will be no support
		2086	for multiple event loops and there is no first event loop pointer
		2087	argument. Instead, all functions act on the single default loop.
		2088
		2089	=item EV_PERIODIC_ENABLE
		2090
		2091	If undefined or defined to be C<1>, then periodic timers are supported. If
		2092	defined to be C<0>, then they are not. Disabling them saves a few kB of
		2093	code.
		2094
		2095	=item EV_EMBED_ENABLE
		2096
		2097	If undefined or defined to be C<1>, then embed watchers are supported. If
		2098	defined to be C<0>, then they are not.
		2099
		2100	=item EV_STAT_ENABLE
		2101
		2102	If undefined or defined to be C<1>, then stat watchers are supported. If
		2103	defined to be C<0>, then they are not.
		2104
		2105	=item EV_FORK_ENABLE
		2106
		2107	If undefined or defined to be C<1>, then fork watchers are supported. If
		2108	defined to be C<0>, then they are not.
		2109
		2110	=item EV_MINIMAL
		2111
		2112	If you need to shave off some kilobytes of code at the expense of some
		2113	speed, define this symbol to C<1>. Currently only used for gcc to override
		2114	some inlining decisions, saves roughly 30% codesize of amd64.
		2115
		2116	=item EV_PID_HASHSIZE
		2117
		2118	C<ev_child> watchers use a small hash table to distribute workload by
		2119	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more
		2120	than enough. If you need to manage thousands of children you might want to
		2121	increase this value (I<must> be a power of two).
		2122
		2123	=item EV_INOTIFY_HASHSIZE
		2124
		2125	C<ev_staz> watchers use a small hash table to distribute workload by
		2126	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),
		2127	usually more than enough. If you need to manage thousands of C<ev_stat>
		2128	watchers you might want to increase this value (I<must> be a power of
		2129	two).
		2130
		2131	=item EV_COMMON
		2132
		2133	By default, all watchers have a C<void *data> member. By redefining
		2134	this macro to a something else you can include more and other types of
		2135	members. You have to define it each time you include one of the files,
		2136	though, and it must be identical each time.
		2137
		2138	For example, the perl EV module uses something like this:
		2139
		2140	#define EV_COMMON \
		2141	SV *self; /* contains this struct */ \
		2142	SV *cb_sv, *fh /* note no trailing ";" */
		2143
		2144	=item EV_CB_DECLARE (type)
		2145
		2146	=item EV_CB_INVOKE (watcher, revents)
		2147
		2148	=item ev_set_cb (ev, cb)
		2149
		2150	Can be used to change the callback member declaration in each watcher,
		2151	and the way callbacks are invoked and set. Must expand to a struct member
		2152	definition and a statement, respectively. See the F<ev.v> header file for
		2153	their default definitions. One possible use for overriding these is to
		2154	avoid the C<struct ev_loop *> as first argument in all cases, or to use
		2155	method calls instead of plain function calls in C++.
		2156
		2157	=head2 EXAMPLES
		2158
		2159	For a real-world example of a program the includes libev
		2160	verbatim, you can have a look at the EV perl module
		2161	(L<http://software.schmorp.de/pkg/EV.html>). It has the libev files in
		2162	the F<libev/> subdirectory and includes them in the F<EV/EVAPI.h> (public
		2163	interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file
		2164	will be compiled. It is pretty complex because it provides its own header
		2165	file.
		2166
		2167	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
		2168	that everybody includes and which overrides some autoconf choices:
		2169
		2170	#define EV_USE_POLL 0
		2171	#define EV_MULTIPLICITY 0
		2172	#define EV_PERIODICS 0
		2173	#define EV_CONFIG_H <config.h>
		2174
		2175	#include "ev++.h"
		2176
		2177	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
		2178
		2179	#include "ev_cpp.h"
		2180	#include "ev.c"
		2181
		2182
		2183	=head1 COMPLEXITIES
		2184
		2185	In this section the complexities of (many of) the algorithms used inside
		2186	libev will be explained. For complexity discussions about backends see the
		2187	documentation for C<ev_default_init>.
		2188
		2189	=over 4
		2190
		2191	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)
		2192
		2193	=item Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)
		2194
		2195	=item Starting io/check/prepare/idle/signal/child watchers: O(1)
		2196
		2197	=item Stopping check/prepare/idle watchers: O(1)
		2198
		2199	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
		2200
		2201	=item Finding the next timer per loop iteration: O(1)
		2202
		2203	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
		2204
		2205	=item Activating one watcher: O(1)
		2206
		2207	=back
		2208
825		2209
826	=head1 AUTHOR	2210	=head1 AUTHOR
827		2211
828	Marc Lehmann <libev@schmorp.de>.	2212	Marc Lehmann <libev@schmorp.de>.
829		2213

Diff Legend

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