ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.276 by root, Tue Dec 29 13:11:00 2009 UTC vs.
Revision 1.335 by root, Mon Oct 25 10:32:05 2010 UTC

…		…
26	puts ("stdin ready");	26	puts ("stdin ready");
27	// for one-shot events, one must manually stop the watcher	27	// for one-shot events, one must manually stop the watcher
28	// with its corresponding stop function.	28	// with its corresponding stop function.
29	ev_io_stop (EV_A_ w);	29	ev_io_stop (EV_A_ w);
30		30
31	// this causes all nested ev_loop's to stop iterating	31	// this causes all nested ev_run's to stop iterating
32	ev_unloop (EV_A_ EVUNLOOP_ALL);	32	ev_break (EV_A_ EVBREAK_ALL);
33	}	33	}
34		34
35	// another callback, this time for a time-out	35	// another callback, this time for a time-out
36	static void	36	static void
37	timeout_cb (EV_P_ ev_timer *w, int revents)	37	timeout_cb (EV_P_ ev_timer *w, int revents)
38	{	38	{
39	puts ("timeout");	39	puts ("timeout");
40	// this causes the innermost ev_loop to stop iterating	40	// this causes the innermost ev_run to stop iterating
41	ev_unloop (EV_A_ EVUNLOOP_ONE);	41	ev_break (EV_A_ EVBREAK_ONE);
42	}	42	}
43		43
44	int	44	int
45	main (void)	45	main (void)
46	{	46	{
47	// use the default event loop unless you have special needs	47	// use the default event loop unless you have special needs
48	struct ev_loop *loop = ev_default_loop (0);	48	struct ev_loop *loop = EV_DEFAULT;
49		49
50	// initialise an io watcher, then start it	50	// initialise an io watcher, then start it
51	// this one will watch for stdin to become readable	51	// this one will watch for stdin to become readable
52	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);	52	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
53	ev_io_start (loop, &stdin_watcher);	53	ev_io_start (loop, &stdin_watcher);
…		…
56	// simple non-repeating 5.5 second timeout	56	// simple non-repeating 5.5 second timeout
57	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);	57	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
58	ev_timer_start (loop, &timeout_watcher);	58	ev_timer_start (loop, &timeout_watcher);
59		59
60	// now wait for events to arrive	60	// now wait for events to arrive
61	ev_loop (loop, 0);	61	ev_run (loop, 0);
62		62
63	// unloop was called, so exit	63	// unloop was called, so exit
64	return 0;	64	return 0;
65	}	65	}
66		66
…		…
75	While this document tries to be as complete as possible in documenting	75	While this document tries to be as complete as possible in documenting
76	libev, its usage and the rationale behind its design, it is not a tutorial	76	libev, its usage and the rationale behind its design, it is not a tutorial
77	on event-based programming, nor will it introduce event-based programming	77	on event-based programming, nor will it introduce event-based programming
78	with libev.	78	with libev.
79		79
80	Familarity with event based programming techniques in general is assumed	80	Familiarity with event based programming techniques in general is assumed
81	throughout this document.	81	throughout this document.
		82
		83	=head1 WHAT TO READ WHEN IN A HURRY
		84
		85	This manual tries to be very detailed, but unfortunately, this also makes
		86	it very long. If you just want to know the basics of libev, I suggest
		87	reading L<ANATOMY OF A WATCHER>, then the L<EXAMPLE PROGRAM> above and
		88	look up the missing functions in L<GLOBAL FUNCTIONS> and the C<ev_io> and
		89	C<ev_timer> sections in L<WATCHER TYPES>.
82		90
83	=head1 ABOUT LIBEV	91	=head1 ABOUT LIBEV
84		92
85	Libev is an event loop: you register interest in certain events (such as a	93	Libev is an event loop: you register interest in certain events (such as a
86	file descriptor being readable or a timeout occurring), and it will manage	94	file descriptor being readable or a timeout occurring), and it will manage
…		…
124	this argument.	132	this argument.
125		133
126	=head2 TIME REPRESENTATION	134	=head2 TIME REPRESENTATION
127		135
128	Libev represents time as a single floating point number, representing	136	Libev represents time as a single floating point number, representing
129	the (fractional) number of seconds since the (POSIX) epoch (somewhere	137	the (fractional) number of seconds since the (POSIX) epoch (in practice
130	near the beginning of 1970, details are complicated, don't ask). This	138	somewhere near the beginning of 1970, details are complicated, don't
131	type is called C<ev_tstamp>, which is what you should use too. It usually	139	ask). This type is called C<ev_tstamp>, which is what you should use
132	aliases to the C<double> type in C. When you need to do any calculations	140	too. It usually aliases to the C<double> type in C. When you need to do
133	on it, you should treat it as some floating point value. Unlike the name	141	any calculations on it, you should treat it as some floating point value.
		142
134	component C<stamp> might indicate, it is also used for time differences	143	Unlike the name component C<stamp> might indicate, it is also used for
135	throughout libev.	144	time differences (e.g. delays) throughout libev.
136		145
137	=head1 ERROR HANDLING	146	=head1 ERROR HANDLING
138		147
139	Libev knows three classes of errors: operating system errors, usage errors	148	Libev knows three classes of errors: operating system errors, usage errors
140	and internal errors (bugs).	149	and internal errors (bugs).
…		…
164		173
165	=item ev_tstamp ev_time ()	174	=item ev_tstamp ev_time ()
166		175
167	Returns the current time as libev would use it. Please note that the	176	Returns the current time as libev would use it. Please note that the
168	C<ev_now> function is usually faster and also often returns the timestamp	177	C<ev_now> function is usually faster and also often returns the timestamp
169	you actually want to know.	178	you actually want to know. Also interesting is the combination of
		179	C<ev_update_now> and C<ev_now>.
170		180
171	=item ev_sleep (ev_tstamp interval)	181	=item ev_sleep (ev_tstamp interval)
172		182
173	Sleep for the given interval: The current thread will be blocked until	183	Sleep for the given interval: The current thread will be blocked until
174	either it is interrupted or the given time interval has passed. Basically	184	either it is interrupted or the given time interval has passed. Basically
…		…
191	as this indicates an incompatible change. Minor versions are usually	201	as this indicates an incompatible change. Minor versions are usually
192	compatible to older versions, so a larger minor version alone is usually	202	compatible to older versions, so a larger minor version alone is usually
193	not a problem.	203	not a problem.
194		204
195	Example: Make sure we haven't accidentally been linked against the wrong	205	Example: Make sure we haven't accidentally been linked against the wrong
196	version.	206	version (note, however, that this will not detect other ABI mismatches,
		207	such as LFS or reentrancy).
197		208
198	assert (("libev version mismatch",	209	assert (("libev version mismatch",
199	ev_version_major () == EV_VERSION_MAJOR	210	ev_version_major () == EV_VERSION_MAJOR
200	&& ev_version_minor () >= EV_VERSION_MINOR));	211	&& ev_version_minor () >= EV_VERSION_MINOR));
201		212
…		…
212	assert (("sorry, no epoll, no sex",	223	assert (("sorry, no epoll, no sex",
213	ev_supported_backends () & EVBACKEND_EPOLL));	224	ev_supported_backends () & EVBACKEND_EPOLL));
214		225
215	=item unsigned int ev_recommended_backends ()	226	=item unsigned int ev_recommended_backends ()
216		227
217	Return the set of all backends compiled into this binary of libev and also	228	Return the set of all backends compiled into this binary of libev and
218	recommended for this platform. This set is often smaller than the one	229	also recommended for this platform, meaning it will work for most file
		230	descriptor types. This set is often smaller than the one returned by
219	returned by C<ev_supported_backends>, as for example kqueue is broken on	231	C<ev_supported_backends>, as for example kqueue is broken on most BSDs
220	most BSDs and will not be auto-detected unless you explicitly request it	232	and will not be auto-detected unless you explicitly request it (assuming
221	(assuming you know what you are doing). This is the set of backends that	233	you know what you are doing). This is the set of backends that libev will
222	libev will probe for if you specify no backends explicitly.	234	probe for if you specify no backends explicitly.
223		235
224	=item unsigned int ev_embeddable_backends ()	236	=item unsigned int ev_embeddable_backends ()
225		237
226	Returns the set of backends that are embeddable in other event loops. This	238	Returns the set of backends that are embeddable in other event loops. This
227	is the theoretical, all-platform, value. To find which backends	239	value is platform-specific but can include backends not available on the
228	might be supported on the current system, you would need to look at	240	current system. To find which embeddable backends might be supported on
229	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	241	the current system, you would need to look at C<ev_embeddable_backends ()
230	recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
231		243
232	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
233		245
234	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]	246	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]
235		247
…		…
289	...	301	...
290	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
291		303
292	=back	304	=back
293		305
294	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	306	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
295		307
296	An event loop is described by a C<struct ev_loop *> (the C<struct>	308	An event loop is described by a C<struct ev_loop *> (the C<struct> is
297	is I<not> optional in this case, as there is also an C<ev_loop>	309	I<not> optional in this case unless libev 3 compatibility is disabled, as
298	I<function>).	310	libev 3 had an C<ev_loop> function colliding with the struct name).
299		311
300	The library knows two types of such loops, the I<default> loop, which	312	The library knows two types of such loops, the I<default> loop, which
301	supports signals and child events, and dynamically created loops which do	313	supports child process events, and dynamically created event loops which
302	not.	314	do not.
303		315
304	=over 4	316	=over 4
305		317
306	=item struct ev_loop *ev_default_loop (unsigned int flags)	318	=item struct ev_loop *ev_default_loop (unsigned int flags)
307		319
308	This will initialise the default event loop if it hasn't been initialised	320	This returns the "default" event loop object, which is what you should
309	yet and return it. If the default loop could not be initialised, returns	321	normally use when you just need "the event loop". Event loop objects and
310	false. If it already was initialised it simply returns it (and ignores the	322	the C<flags> parameter are described in more detail in the entry for
311	flags. If that is troubling you, check C<ev_backend ()> afterwards).	323	C<ev_loop_new>.
		324
		325	If the default loop is already initialised then this function simply
		326	returns it (and ignores the flags. If that is troubling you, check
		327	C<ev_backend ()> afterwards). Otherwise it will create it with the given
		328	flags, which should almost always be C<0>, unless the caller is also the
		329	one calling C<ev_run> or otherwise qualifies as "the main program".
312		330
313	If you don't know what event loop to use, use the one returned from this	331	If you don't know what event loop to use, use the one returned from this
314	function.	332	function (or via the C<EV_DEFAULT> macro).
315		333
316	Note that this function is I<not> thread-safe, so if you want to use it	334	Note that this function is I<not> thread-safe, so if you want to use it
317	from multiple threads, you have to lock (note also that this is unlikely,	335	from multiple threads, you have to employ some kind of mutex (note also
318	as loops cannot be shared easily between threads anyway).	336	that this case is unlikely, as loops cannot be shared easily between
		337	threads anyway).
319		338
320	The default loop is the only loop that can handle C<ev_signal> and	339	The default loop is the only loop that can handle C<ev_child> watchers,
321	C<ev_child> watchers, and to do this, it always registers a handler	340	and to do this, it always registers a handler for C<SIGCHLD>. If this is
322	for C<SIGCHLD>. If this is a problem for your application you can either	341	a problem for your application you can either create a dynamic loop with
323	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	342	C<ev_loop_new> which doesn't do that, or you can simply overwrite the
324	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	343	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
325	C<ev_default_init>.	344
		345	Example: This is the most typical usage.
		346
		347	if (!ev_default_loop (0))
		348	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
		349
		350	Example: Restrict libev to the select and poll backends, and do not allow
		351	environment settings to be taken into account:
		352
		353	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
		354
		355	=item struct ev_loop *ev_loop_new (unsigned int flags)
		356
		357	This will create and initialise a new event loop object. If the loop
		358	could not be initialised, returns false.
		359
		360	Note that this function I<is> thread-safe, and one common way to use
		361	libev with threads is indeed to create one loop per thread, and using the
		362	default loop in the "main" or "initial" thread.
326		363
327	The flags argument can be used to specify special behaviour or specific	364	The flags argument can be used to specify special behaviour or specific
328	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).	365	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
329		366
330	The following flags are supported:	367	The following flags are supported:
…		…
345	useful to try out specific backends to test their performance, or to work	382	useful to try out specific backends to test their performance, or to work
346	around bugs.	383	around bugs.
347		384
348	=item C<EVFLAG_FORKCHECK>	385	=item C<EVFLAG_FORKCHECK>
349		386
350	Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after	387	Instead of calling C<ev_loop_fork> manually after a fork, you can also
351	a fork, you can also make libev check for a fork in each iteration by	388	make libev check for a fork in each iteration by enabling this flag.
352	enabling this flag.
353		389
354	This works by calling C<getpid ()> on every iteration of the loop,	390	This works by calling C<getpid ()> on every iteration of the loop,
355	and thus this might slow down your event loop if you do a lot of loop	391	and thus this might slow down your event loop if you do a lot of loop
356	iterations and little real work, but is usually not noticeable (on my	392	iterations and little real work, but is usually not noticeable (on my
357	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence	393	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence
…		…
370	When this flag is specified, then libev will not attempt to use the	406	When this flag is specified, then libev will not attempt to use the
371	I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and	407	I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and
372	testing, this flag can be useful to conserve inotify file descriptors, as	408	testing, this flag can be useful to conserve inotify file descriptors, as
373	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.	409	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
374		410
375	=item C<EVFLAG_NOSIGFD>	411	=item C<EVFLAG_SIGNALFD>
376		412
377	When this flag is specified, then libev will not attempt to use the	413	When this flag is specified, then libev will attempt to use the
378	I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This is	414	I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API
379	probably only useful to work around any bugs in libev. Consequently, this	415	delivers signals synchronously, which makes it both faster and might make
380	flag might go away once the signalfd functionality is considered stable,	416	it possible to get the queued signal data. It can also simplify signal
381	so it's useful mostly in environment variables and not in program code.	417	handling with threads, as long as you properly block signals in your
		418	threads that are not interested in handling them.
		419
		420	Signalfd will not be used by default as this changes your signal mask, and
		421	there are a lot of shoddy libraries and programs (glib's threadpool for
		422	example) that can't properly initialise their signal masks.
382		423
383	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	424	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
384		425
385	This is your standard select(2) backend. Not I<completely> standard, as	426	This is your standard select(2) backend. Not I<completely> standard, as
386	libev tries to roll its own fd_set with no limits on the number of fds,	427	libev tries to roll its own fd_set with no limits on the number of fds,
…		…
434	of course I<doesn't>, and epoll just loves to report events for totally	475	of course I<doesn't>, and epoll just loves to report events for totally
435	I<different> file descriptors (even already closed ones, so one cannot	476	I<different> file descriptors (even already closed ones, so one cannot
436	even remove them from the set) than registered in the set (especially	477	even remove them from the set) than registered in the set (especially
437	on SMP systems). Libev tries to counter these spurious notifications by	478	on SMP systems). Libev tries to counter these spurious notifications by
438	employing an additional generation counter and comparing that against the	479	employing an additional generation counter and comparing that against the
439	events to filter out spurious ones, recreating the set when required.	480	events to filter out spurious ones, recreating the set when required. Last
		481	not least, it also refuses to work with some file descriptors which work
		482	perfectly fine with C<select> (files, many character devices...).
440		483
441	While stopping, setting and starting an I/O watcher in the same iteration	484	While stopping, setting and starting an I/O watcher in the same iteration
442	will result in some caching, there is still a system call per such	485	will result in some caching, there is still a system call per such
443	incident (because the same I<file descriptor> could point to a different	486	incident (because the same I<file descriptor> could point to a different
444	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed	487	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
…		…
542	If one or more of the backend flags are or'ed into the flags value,	585	If one or more of the backend flags are or'ed into the flags value,
543	then only these backends will be tried (in the reverse order as listed	586	then only these backends will be tried (in the reverse order as listed
544	here). If none are specified, all backends in C<ev_recommended_backends	587	here). If none are specified, all backends in C<ev_recommended_backends
545	()> will be tried.	588	()> will be tried.
546		589
547	Example: This is the most typical usage.
548
549	if (!ev_default_loop (0))
550	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
551
552	Example: Restrict libev to the select and poll backends, and do not allow
553	environment settings to be taken into account:
554
555	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
556
557	Example: Use whatever libev has to offer, but make sure that kqueue is
558	used if available (warning, breaks stuff, best use only with your own
559	private event loop and only if you know the OS supports your types of
560	fds):
561
562	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
563
564	=item struct ev_loop *ev_loop_new (unsigned int flags)
565
566	Similar to C<ev_default_loop>, but always creates a new event loop that is
567	always distinct from the default loop. Unlike the default loop, it cannot
568	handle signal and child watchers, and attempts to do so will be greeted by
569	undefined behaviour (or a failed assertion if assertions are enabled).
570
571	Note that this function I<is> thread-safe, and the recommended way to use
572	libev with threads is indeed to create one loop per thread, and using the
573	default loop in the "main" or "initial" thread.
574
575	Example: Try to create a event loop that uses epoll and nothing else.	590	Example: Try to create a event loop that uses epoll and nothing else.
576		591
577	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	592	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
578	if (!epoller)	593	if (!epoller)
579	fatal ("no epoll found here, maybe it hides under your chair");	594	fatal ("no epoll found here, maybe it hides under your chair");
580		595
		596	Example: Use whatever libev has to offer, but make sure that kqueue is
		597	used if available.
		598
		599	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE);
		600
581	=item ev_default_destroy ()	601	=item ev_loop_destroy (loop)
582		602
583	Destroys the default loop again (frees all memory and kernel state	603	Destroys an event loop object (frees all memory and kernel state
584	etc.). None of the active event watchers will be stopped in the normal	604	etc.). None of the active event watchers will be stopped in the normal
585	sense, so e.g. C<ev_is_active> might still return true. It is your	605	sense, so e.g. C<ev_is_active> might still return true. It is your
586	responsibility to either stop all watchers cleanly yourself I<before>	606	responsibility to either stop all watchers cleanly yourself I<before>
587	calling this function, or cope with the fact afterwards (which is usually	607	calling this function, or cope with the fact afterwards (which is usually
588	the easiest thing, you can just ignore the watchers and/or C<free ()> them	608	the easiest thing, you can just ignore the watchers and/or C<free ()> them
…		…
590		610
591	Note that certain global state, such as signal state (and installed signal	611	Note that certain global state, such as signal state (and installed signal
592	handlers), will not be freed by this function, and related watchers (such	612	handlers), will not be freed by this function, and related watchers (such
593	as signal and child watchers) would need to be stopped manually.	613	as signal and child watchers) would need to be stopped manually.
594		614
595	In general it is not advisable to call this function except in the	615	This function is normally used on loop objects allocated by
596	rare occasion where you really need to free e.g. the signal handling	616	C<ev_loop_new>, but it can also be used on the default loop returned by
		617	C<ev_default_loop>, in which case it is not thread-safe.
		618
		619	Note that it is not advisable to call this function on the default loop
		620	except in the rare occasion where you really need to free it's resources.
597	pipe fds. If you need dynamically allocated loops it is better to use	621	If you need dynamically allocated loops it is better to use C<ev_loop_new>
598	C<ev_loop_new> and C<ev_loop_destroy>.	622	and C<ev_loop_destroy>.
599		623
600	=item ev_loop_destroy (loop)	624	=item ev_loop_fork (loop)
601		625
602	Like C<ev_default_destroy>, but destroys an event loop created by an
603	earlier call to C<ev_loop_new>.
604
605	=item ev_default_fork ()
606
607	This function sets a flag that causes subsequent C<ev_loop> iterations	626	This function sets a flag that causes subsequent C<ev_run> iterations to
608	to reinitialise the kernel state for backends that have one. Despite the	627	reinitialise the kernel state for backends that have one. Despite the
609	name, you can call it anytime, but it makes most sense after forking, in	628	name, you can call it anytime, but it makes most sense after forking, in
610	the child process (or both child and parent, but that again makes little	629	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
611	sense). You I<must> call it in the child before using any of the libev	630	child before resuming or calling C<ev_run>.
612	functions, and it will only take effect at the next C<ev_loop> iteration.	631
		632	Again, you I<have> to call it on I<any> loop that you want to re-use after
		633	a fork, I<even if you do not plan to use the loop in the parent>. This is
		634	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
		635	during fork.
613		636
614	On the other hand, you only need to call this function in the child	637	On the other hand, you only need to call this function in the child
615	process if and only if you want to use the event library in the child. If	638	process if and only if you want to use the event loop in the child. If
616	you just fork+exec, you don't have to call it at all.	639	you just fork+exec or create a new loop in the child, you don't have to
		640	call it at all (in fact, C<epoll> is so badly broken that it makes a
		641	difference, but libev will usually detect this case on its own and do a
		642	costly reset of the backend).
617		643
618	The function itself is quite fast and it's usually not a problem to call	644	The function itself is quite fast and it's usually not a problem to call
619	it just in case after a fork. To make this easy, the function will fit in	645	it just in case after a fork.
620	quite nicely into a call to C<pthread_atfork>:
621		646
		647	Example: Automate calling C<ev_loop_fork> on the default loop when
		648	using pthreads.
		649
		650	static void
		651	post_fork_child (void)
		652	{
		653	ev_loop_fork (EV_DEFAULT);
		654	}
		655
		656	...
622	pthread_atfork (0, 0, ev_default_fork);	657	pthread_atfork (0, 0, post_fork_child);
623
624	=item ev_loop_fork (loop)
625
626	Like C<ev_default_fork>, but acts on an event loop created by
627	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
628	after fork that you want to re-use in the child, and how you do this is
629	entirely your own problem.
630		658
631	=item int ev_is_default_loop (loop)	659	=item int ev_is_default_loop (loop)
632		660
633	Returns true when the given loop is, in fact, the default loop, and false	661	Returns true when the given loop is, in fact, the default loop, and false
634	otherwise.	662	otherwise.
635		663
636	=item unsigned int ev_loop_count (loop)	664	=item unsigned int ev_iteration (loop)
637		665
638	Returns the count of loop iterations for the loop, which is identical to	666	Returns the current iteration count for the event loop, which is identical
639	the number of times libev did poll for new events. It starts at C<0> and	667	to the number of times libev did poll for new events. It starts at C<0>
640	happily wraps around with enough iterations.	668	and happily wraps around with enough iterations.
641		669
642	This value can sometimes be useful as a generation counter of sorts (it	670	This value can sometimes be useful as a generation counter of sorts (it
643	"ticks" the number of loop iterations), as it roughly corresponds with	671	"ticks" the number of loop iterations), as it roughly corresponds with
644	C<ev_prepare> and C<ev_check> calls.	672	C<ev_prepare> and C<ev_check> calls - and is incremented between the
		673	prepare and check phases.
645		674
646	=item unsigned int ev_loop_depth (loop)	675	=item unsigned int ev_depth (loop)
647		676
648	Returns the number of times C<ev_loop> was entered minus the number of	677	Returns the number of times C<ev_run> was entered minus the number of
649	times C<ev_loop> was exited, in other words, the recursion depth.	678	times C<ev_run> was exited, in other words, the recursion depth.
650		679
651	Outside C<ev_loop>, this number is zero. In a callback, this number is	680	Outside C<ev_run>, this number is zero. In a callback, this number is
652	C<1>, unless C<ev_loop> was invoked recursively (or from another thread),	681	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
653	in which case it is higher.	682	in which case it is higher.
654		683
655	Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread	684	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread
656	etc.), doesn't count as exit.	685	etc.), doesn't count as "exit" - consider this as a hint to avoid such
		686	ungentleman-like behaviour unless it's really convenient.
657		687
658	=item unsigned int ev_backend (loop)	688	=item unsigned int ev_backend (loop)
659		689
660	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	690	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
661	use.	691	use.
…		…
670		700
671	=item ev_now_update (loop)	701	=item ev_now_update (loop)
672		702
673	Establishes the current time by querying the kernel, updating the time	703	Establishes the current time by querying the kernel, updating the time
674	returned by C<ev_now ()> in the progress. This is a costly operation and	704	returned by C<ev_now ()> in the progress. This is a costly operation and
675	is usually done automatically within C<ev_loop ()>.	705	is usually done automatically within C<ev_run ()>.
676		706
677	This function is rarely useful, but when some event callback runs for a	707	This function is rarely useful, but when some event callback runs for a
678	very long time without entering the event loop, updating libev's idea of	708	very long time without entering the event loop, updating libev's idea of
679	the current time is a good idea.	709	the current time is a good idea.
680		710
…		…
682		712
683	=item ev_suspend (loop)	713	=item ev_suspend (loop)
684		714
685	=item ev_resume (loop)	715	=item ev_resume (loop)
686		716
687	These two functions suspend and resume a loop, for use when the loop is	717	These two functions suspend and resume an event loop, for use when the
688	not used for a while and timeouts should not be processed.	718	loop is not used for a while and timeouts should not be processed.
689		719
690	A typical use case would be an interactive program such as a game: When	720	A typical use case would be an interactive program such as a game: When
691	the user presses C<^Z> to suspend the game and resumes it an hour later it	721	the user presses C<^Z> to suspend the game and resumes it an hour later it
692	would be best to handle timeouts as if no time had actually passed while	722	would be best to handle timeouts as if no time had actually passed while
693	the program was suspended. This can be achieved by calling C<ev_suspend>	723	the program was suspended. This can be achieved by calling C<ev_suspend>
…		…
695	C<ev_resume> directly afterwards to resume timer processing.	725	C<ev_resume> directly afterwards to resume timer processing.
696		726
697	Effectively, all C<ev_timer> watchers will be delayed by the time spend	727	Effectively, all C<ev_timer> watchers will be delayed by the time spend
698	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers	728	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers
699	will be rescheduled (that is, they will lose any events that would have	729	will be rescheduled (that is, they will lose any events that would have
700	occured while suspended).	730	occurred while suspended).
701		731
702	After calling C<ev_suspend> you B<must not> call I<any> function on the	732	After calling C<ev_suspend> you B<must not> call I<any> function on the
703	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>	733	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>
704	without a previous call to C<ev_suspend>.	734	without a previous call to C<ev_suspend>.
705		735
706	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the	736	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
707	event loop time (see C<ev_now_update>).	737	event loop time (see C<ev_now_update>).
708		738
709	=item ev_loop (loop, int flags)	739	=item ev_run (loop, int flags)
710		740
711	Finally, this is it, the event handler. This function usually is called	741	Finally, this is it, the event handler. This function usually is called
712	after you have initialised all your watchers and you want to start	742	after you have initialised all your watchers and you want to start
713	handling events.	743	handling events. It will ask the operating system for any new events, call
		744	the watcher callbacks, an then repeat the whole process indefinitely: This
		745	is why event loops are called I<loops>.
714		746
715	If the flags argument is specified as C<0>, it will not return until	747	If the flags argument is specified as C<0>, it will keep handling events
716	either no event watchers are active anymore or C<ev_unloop> was called.	748	until either no event watchers are active anymore or C<ev_break> was
		749	called.
717		750
718	Please note that an explicit C<ev_unloop> is usually better than	751	Please note that an explicit C<ev_break> is usually better than
719	relying on all watchers to be stopped when deciding when a program has	752	relying on all watchers to be stopped when deciding when a program has
720	finished (especially in interactive programs), but having a program	753	finished (especially in interactive programs), but having a program
721	that automatically loops as long as it has to and no longer by virtue	754	that automatically loops as long as it has to and no longer by virtue
722	of relying on its watchers stopping correctly, that is truly a thing of	755	of relying on its watchers stopping correctly, that is truly a thing of
723	beauty.	756	beauty.
724		757
725	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	758	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
726	those events and any already outstanding ones, but will not block your	759	those events and any already outstanding ones, but will not wait and
727	process in case there are no events and will return after one iteration of	760	block your process in case there are no events and will return after one
728	the loop.	761	iteration of the loop. This is sometimes useful to poll and handle new
		762	events while doing lengthy calculations, to keep the program responsive.
729		763
730	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	764	A flags value of C<EVRUN_ONCE> will look for new events (waiting if
731	necessary) and will handle those and any already outstanding ones. It	765	necessary) and will handle those and any already outstanding ones. It
732	will block your process until at least one new event arrives (which could	766	will block your process until at least one new event arrives (which could
733	be an event internal to libev itself, so there is no guarantee that a	767	be an event internal to libev itself, so there is no guarantee that a
734	user-registered callback will be called), and will return after one	768	user-registered callback will be called), and will return after one
735	iteration of the loop.	769	iteration of the loop.
736		770
737	This is useful if you are waiting for some external event in conjunction	771	This is useful if you are waiting for some external event in conjunction
738	with something not expressible using other libev watchers (i.e. "roll your	772	with something not expressible using other libev watchers (i.e. "roll your
739	own C<ev_loop>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is	773	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
740	usually a better approach for this kind of thing.	774	usually a better approach for this kind of thing.
741		775
742	Here are the gory details of what C<ev_loop> does:	776	Here are the gory details of what C<ev_run> does:
743		777
		778	- Increment loop depth.
		779	- Reset the ev_break status.
744	- Before the first iteration, call any pending watchers.	780	- Before the first iteration, call any pending watchers.
		781	LOOP:
745	* If EVFLAG_FORKCHECK was used, check for a fork.	782	- If EVFLAG_FORKCHECK was used, check for a fork.
746	- If a fork was detected (by any means), queue and call all fork watchers.	783	- If a fork was detected (by any means), queue and call all fork watchers.
747	- Queue and call all prepare watchers.	784	- Queue and call all prepare watchers.
		785	- If ev_break was called, goto FINISH.
748	- If we have been forked, detach and recreate the kernel state	786	- If we have been forked, detach and recreate the kernel state
749	as to not disturb the other process.	787	as to not disturb the other process.
750	- Update the kernel state with all outstanding changes.	788	- Update the kernel state with all outstanding changes.
751	- Update the "event loop time" (ev_now ()).	789	- Update the "event loop time" (ev_now ()).
752	- Calculate for how long to sleep or block, if at all	790	- Calculate for how long to sleep or block, if at all
753	(active idle watchers, EVLOOP_NONBLOCK or not having	791	(active idle watchers, EVRUN_NOWAIT or not having
754	any active watchers at all will result in not sleeping).	792	any active watchers at all will result in not sleeping).
755	- Sleep if the I/O and timer collect interval say so.	793	- Sleep if the I/O and timer collect interval say so.
		794	- Increment loop iteration counter.
756	- Block the process, waiting for any events.	795	- Block the process, waiting for any events.
757	- Queue all outstanding I/O (fd) events.	796	- Queue all outstanding I/O (fd) events.
758	- Update the "event loop time" (ev_now ()), and do time jump adjustments.	797	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
759	- Queue all expired timers.	798	- Queue all expired timers.
760	- Queue all expired periodics.	799	- Queue all expired periodics.
761	- Unless any events are pending now, queue all idle watchers.	800	- Queue all idle watchers with priority higher than that of pending events.
762	- Queue all check watchers.	801	- Queue all check watchers.
763	- Call all queued watchers in reverse order (i.e. check watchers first).	802	- Call all queued watchers in reverse order (i.e. check watchers first).
764	Signals and child watchers are implemented as I/O watchers, and will	803	Signals and child watchers are implemented as I/O watchers, and will
765	be handled here by queueing them when their watcher gets executed.	804	be handled here by queueing them when their watcher gets executed.
766	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	805	- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT
767	were used, or there are no active watchers, return, otherwise	806	were used, or there are no active watchers, goto FINISH, otherwise
768	continue with step *.	807	continue with step LOOP.
		808	FINISH:
		809	- Reset the ev_break status iff it was EVBREAK_ONE.
		810	- Decrement the loop depth.
		811	- Return.
769		812
770	Example: Queue some jobs and then loop until no events are outstanding	813	Example: Queue some jobs and then loop until no events are outstanding
771	anymore.	814	anymore.
772		815
773	... queue jobs here, make sure they register event watchers as long	816	... queue jobs here, make sure they register event watchers as long
774	... as they still have work to do (even an idle watcher will do..)	817	... as they still have work to do (even an idle watcher will do..)
775	ev_loop (my_loop, 0);	818	ev_run (my_loop, 0);
776	... jobs done or somebody called unloop. yeah!	819	... jobs done or somebody called unloop. yeah!
777		820
778	=item ev_unloop (loop, how)	821	=item ev_break (loop, how)
779		822
780	Can be used to make a call to C<ev_loop> return early (but only after it	823	Can be used to make a call to C<ev_run> return early (but only after it
781	has processed all outstanding events). The C<how> argument must be either	824	has processed all outstanding events). The C<how> argument must be either
782	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	825	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
783	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	826	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
784		827
785	This "unloop state" will be cleared when entering C<ev_loop> again.	828	This "unloop state" will be cleared when entering C<ev_run> again.
786		829
787	It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls.	830	It is safe to call C<ev_break> from outside any C<ev_run> calls. ##TODO##
788		831
789	=item ev_ref (loop)	832	=item ev_ref (loop)
790		833
791	=item ev_unref (loop)	834	=item ev_unref (loop)
792		835
793	Ref/unref can be used to add or remove a reference count on the event	836	Ref/unref can be used to add or remove a reference count on the event
794	loop: Every watcher keeps one reference, and as long as the reference	837	loop: Every watcher keeps one reference, and as long as the reference
795	count is nonzero, C<ev_loop> will not return on its own.	838	count is nonzero, C<ev_run> will not return on its own.
796		839
797	This is useful when you have a watcher that you never intend to	840	This is useful when you have a watcher that you never intend to
798	unregister, but that nevertheless should not keep C<ev_loop> from	841	unregister, but that nevertheless should not keep C<ev_run> from
799	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>	842	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
800	before stopping it.	843	before stopping it.
801		844
802	As an example, libev itself uses this for its internal signal pipe: It	845	As an example, libev itself uses this for its internal signal pipe: It
803	is not visible to the libev user and should not keep C<ev_loop> from	846	is not visible to the libev user and should not keep C<ev_run> from
804	exiting if no event watchers registered by it are active. It is also an	847	exiting if no event watchers registered by it are active. It is also an
805	excellent way to do this for generic recurring timers or from within	848	excellent way to do this for generic recurring timers or from within
806	third-party libraries. Just remember to I<unref after start> and I<ref	849	third-party libraries. Just remember to I<unref after start> and I<ref
807	before stop> (but only if the watcher wasn't active before, or was active	850	before stop> (but only if the watcher wasn't active before, or was active
808	before, respectively. Note also that libev might stop watchers itself	851	before, respectively. Note also that libev might stop watchers itself
809	(e.g. non-repeating timers) in which case you have to C<ev_ref>	852	(e.g. non-repeating timers) in which case you have to C<ev_ref>
810	in the callback).	853	in the callback).
811		854
812	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	855	Example: Create a signal watcher, but keep it from keeping C<ev_run>
813	running when nothing else is active.	856	running when nothing else is active.
814		857
815	ev_signal exitsig;	858	ev_signal exitsig;
816	ev_signal_init (&exitsig, sig_cb, SIGINT);	859	ev_signal_init (&exitsig, sig_cb, SIGINT);
817	ev_signal_start (loop, &exitsig);	860	ev_signal_start (loop, &exitsig);
…		…
862	usually doesn't make much sense to set it to a lower value than C<0.01>,	905	usually doesn't make much sense to set it to a lower value than C<0.01>,
863	as this approaches the timing granularity of most systems. Note that if	906	as this approaches the timing granularity of most systems. Note that if
864	you do transactions with the outside world and you can't increase the	907	you do transactions with the outside world and you can't increase the
865	parallelity, then this setting will limit your transaction rate (if you	908	parallelity, then this setting will limit your transaction rate (if you
866	need to poll once per transaction and the I/O collect interval is 0.01,	909	need to poll once per transaction and the I/O collect interval is 0.01,
867	then you can't do more than 100 transations per second).	910	then you can't do more than 100 transactions per second).
868		911
869	Setting the I<timeout collect interval> can improve the opportunity for	912	Setting the I<timeout collect interval> can improve the opportunity for
870	saving power, as the program will "bundle" timer callback invocations that	913	saving power, as the program will "bundle" timer callback invocations that
871	are "near" in time together, by delaying some, thus reducing the number of	914	are "near" in time together, by delaying some, thus reducing the number of
872	times the process sleeps and wakes up again. Another useful technique to	915	times the process sleeps and wakes up again. Another useful technique to
…		…
880	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);	923	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
881		924
882	=item ev_invoke_pending (loop)	925	=item ev_invoke_pending (loop)
883		926
884	This call will simply invoke all pending watchers while resetting their	927	This call will simply invoke all pending watchers while resetting their
885	pending state. Normally, C<ev_loop> does this automatically when required,	928	pending state. Normally, C<ev_run> does this automatically when required,
886	but when overriding the invoke callback this call comes handy.	929	but when overriding the invoke callback this call comes handy. This
		930	function can be invoked from a watcher - this can be useful for example
		931	when you want to do some lengthy calculation and want to pass further
		932	event handling to another thread (you still have to make sure only one
		933	thread executes within C<ev_invoke_pending> or C<ev_run> of course).
887		934
888	=item int ev_pending_count (loop)	935	=item int ev_pending_count (loop)
889		936
890	Returns the number of pending watchers - zero indicates that no watchers	937	Returns the number of pending watchers - zero indicates that no watchers
891	are pending.	938	are pending.
892		939
893	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))	940	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
894		941
895	This overrides the invoke pending functionality of the loop: Instead of	942	This overrides the invoke pending functionality of the loop: Instead of
896	invoking all pending watchers when there are any, C<ev_loop> will call	943	invoking all pending watchers when there are any, C<ev_run> will call
897	this callback instead. This is useful, for example, when you want to	944	this callback instead. This is useful, for example, when you want to
898	invoke the actual watchers inside another context (another thread etc.).	945	invoke the actual watchers inside another context (another thread etc.).
899		946
900	If you want to reset the callback, use C<ev_invoke_pending> as new	947	If you want to reset the callback, use C<ev_invoke_pending> as new
901	callback.	948	callback.
…		…
904		951
905	Sometimes you want to share the same loop between multiple threads. This	952	Sometimes you want to share the same loop between multiple threads. This
906	can be done relatively simply by putting mutex_lock/unlock calls around	953	can be done relatively simply by putting mutex_lock/unlock calls around
907	each call to a libev function.	954	each call to a libev function.
908		955
909	However, C<ev_loop> can run an indefinite time, so it is not feasible to	956	However, C<ev_run> can run an indefinite time, so it is not feasible
910	wait for it to return. One way around this is to wake up the loop via	957	to wait for it to return. One way around this is to wake up the event
911	C<ev_unloop> and C<av_async_send>, another way is to set these I<release>	958	loop via C<ev_break> and C<av_async_send>, another way is to set these
912	and I<acquire> callbacks on the loop.	959	I<release> and I<acquire> callbacks on the loop.
913		960
914	When set, then C<release> will be called just before the thread is	961	When set, then C<release> will be called just before the thread is
915	suspended waiting for new events, and C<acquire> is called just	962	suspended waiting for new events, and C<acquire> is called just
916	afterwards.	963	afterwards.
917		964
…		…
920		967
921	While event loop modifications are allowed between invocations of	968	While event loop modifications are allowed between invocations of
922	C<release> and C<acquire> (that's their only purpose after all), no	969	C<release> and C<acquire> (that's their only purpose after all), no
923	modifications done will affect the event loop, i.e. adding watchers will	970	modifications done will affect the event loop, i.e. adding watchers will
924	have no effect on the set of file descriptors being watched, or the time	971	have no effect on the set of file descriptors being watched, or the time
925	waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it	972	waited. Use an C<ev_async> watcher to wake up C<ev_run> when you want it
926	to take note of any changes you made.	973	to take note of any changes you made.
927		974
928	In theory, threads executing C<ev_loop> will be async-cancel safe between	975	In theory, threads executing C<ev_run> will be async-cancel safe between
929	invocations of C<release> and C<acquire>.	976	invocations of C<release> and C<acquire>.
930		977
931	See also the locking example in the C<THREADS> section later in this	978	See also the locking example in the C<THREADS> section later in this
932	document.	979	document.
933		980
…		…
942	These two functions can be used to associate arbitrary data with a loop,	989	These two functions can be used to associate arbitrary data with a loop,
943	and are intended solely for the C<invoke_pending_cb>, C<release> and	990	and are intended solely for the C<invoke_pending_cb>, C<release> and
944	C<acquire> callbacks described above, but of course can be (ab-)used for	991	C<acquire> callbacks described above, but of course can be (ab-)used for
945	any other purpose as well.	992	any other purpose as well.
946		993
947	=item ev_loop_verify (loop)	994	=item ev_verify (loop)
948		995
949	This function only does something when C<EV_VERIFY> support has been	996	This function only does something when C<EV_VERIFY> support has been
950	compiled in, which is the default for non-minimal builds. It tries to go	997	compiled in, which is the default for non-minimal builds. It tries to go
951	through all internal structures and checks them for validity. If anything	998	through all internal structures and checks them for validity. If anything
952	is found to be inconsistent, it will print an error message to standard	999	is found to be inconsistent, it will print an error message to standard
…		…
963		1010
964	In the following description, uppercase C<TYPE> in names stands for the	1011	In the following description, uppercase C<TYPE> in names stands for the
965	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer	1012	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
966	watchers and C<ev_io_start> for I/O watchers.	1013	watchers and C<ev_io_start> for I/O watchers.
967		1014
968	A watcher is a structure that you create and register to record your	1015	A watcher is an opaque structure that you allocate and register to record
969	interest in some event. For instance, if you want to wait for STDIN to	1016	your interest in some event. To make a concrete example, imagine you want
970	become readable, you would create an C<ev_io> watcher for that:	1017	to wait for STDIN to become readable, you would create an C<ev_io> watcher
		1018	for that:
971		1019
972	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)	1020	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
973	{	1021	{
974	ev_io_stop (w);	1022	ev_io_stop (w);
975	ev_unloop (loop, EVUNLOOP_ALL);	1023	ev_break (loop, EVBREAK_ALL);
976	}	1024	}
977		1025
978	struct ev_loop *loop = ev_default_loop (0);	1026	struct ev_loop *loop = ev_default_loop (0);
979		1027
980	ev_io stdin_watcher;	1028	ev_io stdin_watcher;
981		1029
982	ev_init (&stdin_watcher, my_cb);	1030	ev_init (&stdin_watcher, my_cb);
983	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	1031	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
984	ev_io_start (loop, &stdin_watcher);	1032	ev_io_start (loop, &stdin_watcher);
985		1033
986	ev_loop (loop, 0);	1034	ev_run (loop, 0);
987		1035
988	As you can see, you are responsible for allocating the memory for your	1036	As you can see, you are responsible for allocating the memory for your
989	watcher structures (and it is I<usually> a bad idea to do this on the	1037	watcher structures (and it is I<usually> a bad idea to do this on the
990	stack).	1038	stack).
991		1039
992	Each watcher has an associated watcher structure (called C<struct ev_TYPE>	1040	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
993	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).	1041	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
994		1042
995	Each watcher structure must be initialised by a call to C<ev_init	1043	Each watcher structure must be initialised by a call to C<ev_init (watcher
996	(watcher *, callback)>, which expects a callback to be provided. This	1044	*, callback)>, which expects a callback to be provided. This callback is
997	callback gets invoked each time the event occurs (or, in the case of I/O	1045	invoked each time the event occurs (or, in the case of I/O watchers, each
998	watchers, each time the event loop detects that the file descriptor given	1046	time the event loop detects that the file descriptor given is readable
999	is readable and/or writable).	1047	and/or writable).
1000		1048
1001	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>	1049	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
1002	macro to configure it, with arguments specific to the watcher type. There	1050	macro to configure it, with arguments specific to the watcher type. There
1003	is also a macro to combine initialisation and setting in one call: C<<	1051	is also a macro to combine initialisation and setting in one call: C<<
1004	ev_TYPE_init (watcher *, callback, ...) >>.	1052	ev_TYPE_init (watcher *, callback, ...) >>.
…		…
1027	=item C<EV_WRITE>	1075	=item C<EV_WRITE>
1028		1076
1029	The file descriptor in the C<ev_io> watcher has become readable and/or	1077	The file descriptor in the C<ev_io> watcher has become readable and/or
1030	writable.	1078	writable.
1031		1079
1032	=item C<EV_TIMEOUT>	1080	=item C<EV_TIMER>
1033		1081
1034	The C<ev_timer> watcher has timed out.	1082	The C<ev_timer> watcher has timed out.
1035		1083
1036	=item C<EV_PERIODIC>	1084	=item C<EV_PERIODIC>
1037		1085
…		…
1055		1103
1056	=item C<EV_PREPARE>	1104	=item C<EV_PREPARE>
1057		1105
1058	=item C<EV_CHECK>	1106	=item C<EV_CHECK>
1059		1107
1060	All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts	1108	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts
1061	to gather new events, and all C<ev_check> watchers are invoked just after	1109	to gather new events, and all C<ev_check> watchers are invoked just after
1062	C<ev_loop> has gathered them, but before it invokes any callbacks for any	1110	C<ev_run> has gathered them, but before it invokes any callbacks for any
1063	received events. Callbacks of both watcher types can start and stop as	1111	received events. Callbacks of both watcher types can start and stop as
1064	many watchers as they want, and all of them will be taken into account	1112	many watchers as they want, and all of them will be taken into account
1065	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	1113	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
1066	C<ev_loop> from blocking).	1114	C<ev_run> from blocking).
1067		1115
1068	=item C<EV_EMBED>	1116	=item C<EV_EMBED>
1069		1117
1070	The embedded event loop specified in the C<ev_embed> watcher needs attention.	1118	The embedded event loop specified in the C<ev_embed> watcher needs attention.
1071		1119
1072	=item C<EV_FORK>	1120	=item C<EV_FORK>
1073		1121
1074	The event loop has been resumed in the child process after fork (see	1122	The event loop has been resumed in the child process after fork (see
1075	C<ev_fork>).	1123	C<ev_fork>).
		1124
		1125	=item C<EV_CLEANUP>
		1126
		1127	The event loop is about to be destroyed (see C<ev_cleanup>).
1076		1128
1077	=item C<EV_ASYNC>	1129	=item C<EV_ASYNC>
1078		1130
1079	The given async watcher has been asynchronously notified (see C<ev_async>).	1131	The given async watcher has been asynchronously notified (see C<ev_async>).
1080		1132
…		…
1252		1304
1253	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related	1305	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
1254	functions that do not need a watcher.	1306	functions that do not need a watcher.
1255		1307
1256	=back	1308	=back
1257
1258		1309
1259	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1310	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
1260		1311
1261	Each watcher has, by default, a member C<void *data> that you can change	1312	Each watcher has, by default, a member C<void *data> that you can change
1262	and read at any time: libev will completely ignore it. This can be used	1313	and read at any time: libev will completely ignore it. This can be used
…		…
1318	t2_cb (EV_P_ ev_timer *w, int revents)	1369	t2_cb (EV_P_ ev_timer *w, int revents)
1319	{	1370	{
1320	struct my_biggy big = (struct my_biggy *)	1371	struct my_biggy big = (struct my_biggy *)
1321	(((char *)w) - offsetof (struct my_biggy, t2));	1372	(((char *)w) - offsetof (struct my_biggy, t2));
1322	}	1373	}
		1374
		1375	=head2 WATCHER STATES
		1376
		1377	There are various watcher states mentioned throughout this manual -
		1378	active, pending and so on. In this section these states and the rules to
		1379	transition between them will be described in more detail - and while these
		1380	rules might look complicated, they usually do "the right thing".
		1381
		1382	=over 4
		1383
		1384	=item initialiased
		1385
		1386	Before a watcher can be registered with the event looop it has to be
		1387	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
		1388	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
		1389
		1390	In this state it is simply some block of memory that is suitable for use
		1391	in an event loop. It can be moved around, freed, reused etc. at will.
		1392
		1393	=item started/running/active
		1394
		1395	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
		1396	property of the event loop, and is actively waiting for events. While in
		1397	this state it cannot be accessed (except in a few documented ways), moved,
		1398	freed or anything else - the only legal thing is to keep a pointer to it,
		1399	and call libev functions on it that are documented to work on active watchers.
		1400
		1401	=item pending
		1402
		1403	If a watcher is active and libev determines that an event it is interested
		1404	in has occurred (such as a timer expiring), it will become pending. It will
		1405	stay in this pending state until either it is stopped or its callback is
		1406	about to be invoked, so it is not normally pending inside the watcher
		1407	callback.
		1408
		1409	The watcher might or might not be active while it is pending (for example,
		1410	an expired non-repeating timer can be pending but no longer active). If it
		1411	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
		1412	but it is still property of the event loop at this time, so cannot be
		1413	moved, freed or reused. And if it is active the rules described in the
		1414	previous item still apply.
		1415
		1416	It is also possible to feed an event on a watcher that is not active (e.g.
		1417	via C<ev_feed_event>), in which case it becomes pending without being
		1418	active.
		1419
		1420	=item stopped
		1421
		1422	A watcher can be stopped implicitly by libev (in which case it might still
		1423	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
		1424	latter will clear any pending state the watcher might be in, regardless
		1425	of whether it was active or not, so stopping a watcher explicitly before
		1426	freeing it is often a good idea.
		1427
		1428	While stopped (and not pending) the watcher is essentially in the
		1429	initialised state, that is it can be reused, moved, modified in any way
		1430	you wish.
		1431
		1432	=back
1323		1433
1324	=head2 WATCHER PRIORITY MODELS	1434	=head2 WATCHER PRIORITY MODELS
1325		1435
1326	Many event loops support I<watcher priorities>, which are usually small	1436	Many event loops support I<watcher priorities>, which are usually small
1327	integers that influence the ordering of event callback invocation	1437	integers that influence the ordering of event callback invocation
…		…
1370		1480
1371	For example, to emulate how many other event libraries handle priorities,	1481	For example, to emulate how many other event libraries handle priorities,
1372	you can associate an C<ev_idle> watcher to each such watcher, and in	1482	you can associate an C<ev_idle> watcher to each such watcher, and in
1373	the normal watcher callback, you just start the idle watcher. The real	1483	the normal watcher callback, you just start the idle watcher. The real
1374	processing is done in the idle watcher callback. This causes libev to	1484	processing is done in the idle watcher callback. This causes libev to
1375	continously poll and process kernel event data for the watcher, but when	1485	continuously poll and process kernel event data for the watcher, but when
1376	the lock-out case is known to be rare (which in turn is rare :), this is	1486	the lock-out case is known to be rare (which in turn is rare :), this is
1377	workable.	1487	workable.
1378		1488
1379	Usually, however, the lock-out model implemented that way will perform	1489	Usually, however, the lock-out model implemented that way will perform
1380	miserably under the type of load it was designed to handle. In that case,	1490	miserably under the type of load it was designed to handle. In that case,
…		…
1394	{	1504	{
1395	// stop the I/O watcher, we received the event, but	1505	// stop the I/O watcher, we received the event, but
1396	// are not yet ready to handle it.	1506	// are not yet ready to handle it.
1397	ev_io_stop (EV_A_ w);	1507	ev_io_stop (EV_A_ w);
1398		1508
1399	// start the idle watcher to ahndle the actual event.	1509	// start the idle watcher to handle the actual event.
1400	// it will not be executed as long as other watchers	1510	// it will not be executed as long as other watchers
1401	// with the default priority are receiving events.	1511	// with the default priority are receiving events.
1402	ev_idle_start (EV_A_ &idle);	1512	ev_idle_start (EV_A_ &idle);
1403	}	1513	}
1404		1514
…		…
1458		1568
1459	If you cannot use non-blocking mode, then force the use of a	1569	If you cannot use non-blocking mode, then force the use of a
1460	known-to-be-good backend (at the time of this writing, this includes only	1570	known-to-be-good backend (at the time of this writing, this includes only
1461	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file	1571	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
1462	descriptors for which non-blocking operation makes no sense (such as	1572	descriptors for which non-blocking operation makes no sense (such as
1463	files) - libev doesn't guarentee any specific behaviour in that case.	1573	files) - libev doesn't guarantee any specific behaviour in that case.
1464		1574
1465	Another thing you have to watch out for is that it is quite easy to	1575	Another thing you have to watch out for is that it is quite easy to
1466	receive "spurious" readiness notifications, that is your callback might	1576	receive "spurious" readiness notifications, that is your callback might
1467	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1577	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1468	because there is no data. Not only are some backends known to create a	1578	because there is no data. Not only are some backends known to create a
…		…
1533		1643
1534	So when you encounter spurious, unexplained daemon exits, make sure you	1644	So when you encounter spurious, unexplained daemon exits, make sure you
1535	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon	1645	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1536	somewhere, as that would have given you a big clue).	1646	somewhere, as that would have given you a big clue).
1537		1647
		1648	=head3 The special problem of accept()ing when you can't
		1649
		1650	Many implementations of the POSIX C<accept> function (for example,
		1651	found in post-2004 Linux) have the peculiar behaviour of not removing a
		1652	connection from the pending queue in all error cases.
		1653
		1654	For example, larger servers often run out of file descriptors (because
		1655	of resource limits), causing C<accept> to fail with C<ENFILE> but not
		1656	rejecting the connection, leading to libev signalling readiness on
		1657	the next iteration again (the connection still exists after all), and
		1658	typically causing the program to loop at 100% CPU usage.
		1659
		1660	Unfortunately, the set of errors that cause this issue differs between
		1661	operating systems, there is usually little the app can do to remedy the
		1662	situation, and no known thread-safe method of removing the connection to
		1663	cope with overload is known (to me).
		1664
		1665	One of the easiest ways to handle this situation is to just ignore it
		1666	- when the program encounters an overload, it will just loop until the
		1667	situation is over. While this is a form of busy waiting, no OS offers an
		1668	event-based way to handle this situation, so it's the best one can do.
		1669
		1670	A better way to handle the situation is to log any errors other than
		1671	C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
		1672	messages, and continue as usual, which at least gives the user an idea of
		1673	what could be wrong ("raise the ulimit!"). For extra points one could stop
		1674	the C<ev_io> watcher on the listening fd "for a while", which reduces CPU
		1675	usage.
		1676
		1677	If your program is single-threaded, then you could also keep a dummy file
		1678	descriptor for overload situations (e.g. by opening F</dev/null>), and
		1679	when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>,
		1680	close that fd, and create a new dummy fd. This will gracefully refuse
		1681	clients under typical overload conditions.
		1682
		1683	The last way to handle it is to simply log the error and C<exit>, as
		1684	is often done with C<malloc> failures, but this results in an easy
		1685	opportunity for a DoS attack.
1538		1686
1539	=head3 Watcher-Specific Functions	1687	=head3 Watcher-Specific Functions
1540		1688
1541	=over 4	1689	=over 4
1542		1690
…		…
1574	...	1722	...
1575	struct ev_loop *loop = ev_default_init (0);	1723	struct ev_loop *loop = ev_default_init (0);
1576	ev_io stdin_readable;	1724	ev_io stdin_readable;
1577	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1725	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1578	ev_io_start (loop, &stdin_readable);	1726	ev_io_start (loop, &stdin_readable);
1579	ev_loop (loop, 0);	1727	ev_run (loop, 0);
1580		1728
1581		1729
1582	=head2 C<ev_timer> - relative and optionally repeating timeouts	1730	=head2 C<ev_timer> - relative and optionally repeating timeouts
1583		1731
1584	Timer watchers are simple relative timers that generate an event after a	1732	Timer watchers are simple relative timers that generate an event after a
…		…
1593	The callback is guaranteed to be invoked only I<after> its timeout has	1741	The callback is guaranteed to be invoked only I<after> its timeout has
1594	passed (not I<at>, so on systems with very low-resolution clocks this	1742	passed (not I<at>, so on systems with very low-resolution clocks this
1595	might introduce a small delay). If multiple timers become ready during the	1743	might introduce a small delay). If multiple timers become ready during the
1596	same loop iteration then the ones with earlier time-out values are invoked	1744	same loop iteration then the ones with earlier time-out values are invoked
1597	before ones of the same priority with later time-out values (but this is	1745	before ones of the same priority with later time-out values (but this is
1598	no longer true when a callback calls C<ev_loop> recursively).	1746	no longer true when a callback calls C<ev_run> recursively).
1599		1747
1600	=head3 Be smart about timeouts	1748	=head3 Be smart about timeouts
1601		1749
1602	Many real-world problems involve some kind of timeout, usually for error	1750	Many real-world problems involve some kind of timeout, usually for error
1603	recovery. A typical example is an HTTP request - if the other side hangs,	1751	recovery. A typical example is an HTTP request - if the other side hangs,
…		…
1689	ev_tstamp timeout = last_activity + 60.;	1837	ev_tstamp timeout = last_activity + 60.;
1690		1838
1691	// if last_activity + 60. is older than now, we did time out	1839	// if last_activity + 60. is older than now, we did time out
1692	if (timeout < now)	1840	if (timeout < now)
1693	{	1841	{
1694	// timeout occured, take action	1842	// timeout occurred, take action
1695	}	1843	}
1696	else	1844	else
1697	{	1845	{
1698	// callback was invoked, but there was some activity, re-arm	1846	// callback was invoked, but there was some activity, re-arm
1699	// the watcher to fire in last_activity + 60, which is	1847	// the watcher to fire in last_activity + 60, which is
…		…
1721	to the current time (meaning we just have some activity :), then call the	1869	to the current time (meaning we just have some activity :), then call the
1722	callback, which will "do the right thing" and start the timer:	1870	callback, which will "do the right thing" and start the timer:
1723		1871
1724	ev_init (timer, callback);	1872	ev_init (timer, callback);
1725	last_activity = ev_now (loop);	1873	last_activity = ev_now (loop);
1726	callback (loop, timer, EV_TIMEOUT);	1874	callback (loop, timer, EV_TIMER);
1727		1875
1728	And when there is some activity, simply store the current time in	1876	And when there is some activity, simply store the current time in
1729	C<last_activity>, no libev calls at all:	1877	C<last_activity>, no libev calls at all:
1730		1878
1731	last_actiivty = ev_now (loop);	1879	last_activity = ev_now (loop);
1732		1880
1733	This technique is slightly more complex, but in most cases where the	1881	This technique is slightly more complex, but in most cases where the
1734	time-out is unlikely to be triggered, much more efficient.	1882	time-out is unlikely to be triggered, much more efficient.
1735		1883
1736	Changing the timeout is trivial as well (if it isn't hard-coded in the	1884	Changing the timeout is trivial as well (if it isn't hard-coded in the
…		…
1774		1922
1775	=head3 The special problem of time updates	1923	=head3 The special problem of time updates
1776		1924
1777	Establishing the current time is a costly operation (it usually takes at	1925	Establishing the current time is a costly operation (it usually takes at
1778	least two system calls): EV therefore updates its idea of the current	1926	least two system calls): EV therefore updates its idea of the current
1779	time only before and after C<ev_loop> collects new events, which causes a	1927	time only before and after C<ev_run> collects new events, which causes a
1780	growing difference between C<ev_now ()> and C<ev_time ()> when handling	1928	growing difference between C<ev_now ()> and C<ev_time ()> when handling
1781	lots of events in one iteration.	1929	lots of events in one iteration.
1782		1930
1783	The relative timeouts are calculated relative to the C<ev_now ()>	1931	The relative timeouts are calculated relative to the C<ev_now ()>
1784	time. This is usually the right thing as this timestamp refers to the time	1932	time. This is usually the right thing as this timestamp refers to the time
…		…
1862	Returns the remaining time until a timer fires. If the timer is active,	2010	Returns the remaining time until a timer fires. If the timer is active,
1863	then this time is relative to the current event loop time, otherwise it's	2011	then this time is relative to the current event loop time, otherwise it's
1864	the timeout value currently configured.	2012	the timeout value currently configured.
1865		2013
1866	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns	2014	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
1867	C<5>. When the timer is started and one second passes, C<ev_timer_remain>	2015	C<5>. When the timer is started and one second passes, C<ev_timer_remaining>
1868	will return C<4>. When the timer expires and is restarted, it will return	2016	will return C<4>. When the timer expires and is restarted, it will return
1869	roughly C<7> (likely slightly less as callback invocation takes some time,	2017	roughly C<7> (likely slightly less as callback invocation takes some time,
1870	too), and so on.	2018	too), and so on.
1871		2019
1872	=item ev_tstamp repeat [read-write]	2020	=item ev_tstamp repeat [read-write]
…		…
1901	}	2049	}
1902		2050
1903	ev_timer mytimer;	2051	ev_timer mytimer;
1904	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	2052	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1905	ev_timer_again (&mytimer); /* start timer */	2053	ev_timer_again (&mytimer); /* start timer */
1906	ev_loop (loop, 0);	2054	ev_run (loop, 0);
1907		2055
1908	// and in some piece of code that gets executed on any "activity":	2056	// and in some piece of code that gets executed on any "activity":
1909	// reset the timeout to start ticking again at 10 seconds	2057	// reset the timeout to start ticking again at 10 seconds
1910	ev_timer_again (&mytimer);	2058	ev_timer_again (&mytimer);
1911		2059
…		…
1937		2085
1938	As with timers, the callback is guaranteed to be invoked only when the	2086	As with timers, the callback is guaranteed to be invoked only when the
1939	point in time where it is supposed to trigger has passed. If multiple	2087	point in time where it is supposed to trigger has passed. If multiple
1940	timers become ready during the same loop iteration then the ones with	2088	timers become ready during the same loop iteration then the ones with
1941	earlier time-out values are invoked before ones with later time-out values	2089	earlier time-out values are invoked before ones with later time-out values
1942	(but this is no longer true when a callback calls C<ev_loop> recursively).	2090	(but this is no longer true when a callback calls C<ev_run> recursively).
1943		2091
1944	=head3 Watcher-Specific Functions and Data Members	2092	=head3 Watcher-Specific Functions and Data Members
1945		2093
1946	=over 4	2094	=over 4
1947		2095
…		…
2075	Example: Call a callback every hour, or, more precisely, whenever the	2223	Example: Call a callback every hour, or, more precisely, whenever the
2076	system time is divisible by 3600. The callback invocation times have	2224	system time is divisible by 3600. The callback invocation times have
2077	potentially a lot of jitter, but good long-term stability.	2225	potentially a lot of jitter, but good long-term stability.
2078		2226
2079	static void	2227	static void
2080	clock_cb (struct ev_loop *loop, ev_io *w, int revents)	2228	clock_cb (struct ev_loop *loop, ev_periodic *w, int revents)
2081	{	2229	{
2082	... its now a full hour (UTC, or TAI or whatever your clock follows)	2230	... its now a full hour (UTC, or TAI or whatever your clock follows)
2083	}	2231	}
2084		2232
2085	ev_periodic hourly_tick;	2233	ev_periodic hourly_tick;
…		…
2132	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should	2280	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
2133	not be unduly interrupted. If you have a problem with system calls getting	2281	not be unduly interrupted. If you have a problem with system calls getting
2134	interrupted by signals you can block all signals in an C<ev_check> watcher	2282	interrupted by signals you can block all signals in an C<ev_check> watcher
2135	and unblock them in an C<ev_prepare> watcher.	2283	and unblock them in an C<ev_prepare> watcher.
2136		2284
2137	=head3 The special problem of inheritance over execve	2285	=head3 The special problem of inheritance over fork/execve/pthread_create
2138		2286
2139	Both the signal mask (C<sigprocmask>) and the signal disposition	2287	Both the signal mask (C<sigprocmask>) and the signal disposition
2140	(C<sigaction>) are unspecified after starting a signal watcher (and after	2288	(C<sigaction>) are unspecified after starting a signal watcher (and after
2141	stopping it again), that is, libev might or might not block the signal,	2289	stopping it again), that is, libev might or might not block the signal,
2142	and might or might not set or restore the installed signal handler.	2290	and might or might not set or restore the installed signal handler.
…		…
2152		2300
2153	The simplest way to ensure that the signal mask is reset in the child is	2301	The simplest way to ensure that the signal mask is reset in the child is
2154	to install a fork handler with C<pthread_atfork> that resets it. That will	2302	to install a fork handler with C<pthread_atfork> that resets it. That will
2155	catch fork calls done by libraries (such as the libc) as well.	2303	catch fork calls done by libraries (such as the libc) as well.
2156		2304
2157	In current versions of libev, you can also ensure that the signal mask is	2305	In current versions of libev, the signal will not be blocked indefinitely
2158	not blocking any signals (except temporarily, so thread users watch out)	2306	unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces
2159	by specifying the C<EVFLAG_NOSIGFD> when creating the event loop. This	2307	the window of opportunity for problems, it will not go away, as libev
2160	is not guaranteed for future versions, however.	2308	I<has> to modify the signal mask, at least temporarily.
		2309
		2310	So I can't stress this enough: I<If you do not reset your signal mask when
		2311	you expect it to be empty, you have a race condition in your code>. This
		2312	is not a libev-specific thing, this is true for most event libraries.
2161		2313
2162	=head3 Watcher-Specific Functions and Data Members	2314	=head3 Watcher-Specific Functions and Data Members
2163		2315
2164	=over 4	2316	=over 4
2165		2317
…		…
2181	Example: Try to exit cleanly on SIGINT.	2333	Example: Try to exit cleanly on SIGINT.
2182		2334
2183	static void	2335	static void
2184	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)	2336	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
2185	{	2337	{
2186	ev_unloop (loop, EVUNLOOP_ALL);	2338	ev_break (loop, EVBREAK_ALL);
2187	}	2339	}
2188		2340
2189	ev_signal signal_watcher;	2341	ev_signal signal_watcher;
2190	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2342	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
2191	ev_signal_start (loop, &signal_watcher);	2343	ev_signal_start (loop, &signal_watcher);
…		…
2577		2729
2578	Prepare and check watchers are usually (but not always) used in pairs:	2730	Prepare and check watchers are usually (but not always) used in pairs:
2579	prepare watchers get invoked before the process blocks and check watchers	2731	prepare watchers get invoked before the process blocks and check watchers
2580	afterwards.	2732	afterwards.
2581		2733
2582	You I<must not> call C<ev_loop> or similar functions that enter	2734	You I<must not> call C<ev_run> or similar functions that enter
2583	the current event loop from either C<ev_prepare> or C<ev_check>	2735	the current event loop from either C<ev_prepare> or C<ev_check>
2584	watchers. Other loops than the current one are fine, however. The	2736	watchers. Other loops than the current one are fine, however. The
2585	rationale behind this is that you do not need to check for recursion in	2737	rationale behind this is that you do not need to check for recursion in
2586	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2738	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
2587	C<ev_check> so if you have one watcher of each kind they will always be	2739	C<ev_check> so if you have one watcher of each kind they will always be
…		…
2755		2907
2756	if (timeout >= 0)	2908	if (timeout >= 0)
2757	// create/start timer	2909	// create/start timer
2758		2910
2759	// poll	2911	// poll
2760	ev_loop (EV_A_ 0);	2912	ev_run (EV_A_ 0);
2761		2913
2762	// stop timer again	2914	// stop timer again
2763	if (timeout >= 0)	2915	if (timeout >= 0)
2764	ev_timer_stop (EV_A_ &to);	2916	ev_timer_stop (EV_A_ &to);
2765		2917
…		…
2843	if you do not want that, you need to temporarily stop the embed watcher).	2995	if you do not want that, you need to temporarily stop the embed watcher).
2844		2996
2845	=item ev_embed_sweep (loop, ev_embed *)	2997	=item ev_embed_sweep (loop, ev_embed *)
2846		2998
2847	Make a single, non-blocking sweep over the embedded loop. This works	2999	Make a single, non-blocking sweep over the embedded loop. This works
2848	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most	3000	similarly to C<ev_run (embedded_loop, EVRUN_NOWAIT)>, but in the most
2849	appropriate way for embedded loops.	3001	appropriate way for embedded loops.
2850		3002
2851	=item struct ev_loop *other [read-only]	3003	=item struct ev_loop *other [read-only]
2852		3004
2853	The embedded event loop.	3005	The embedded event loop.
…		…
2913	C<ev_default_fork> cheats and calls it in the wrong process, the fork	3065	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2914	handlers will be invoked, too, of course.	3066	handlers will be invoked, too, of course.
2915		3067
2916	=head3 The special problem of life after fork - how is it possible?	3068	=head3 The special problem of life after fork - how is it possible?
2917		3069
2918	Most uses of C<fork()> consist of forking, then some simple calls to ste	3070	Most uses of C<fork()> consist of forking, then some simple calls to set
2919	up/change the process environment, followed by a call to C<exec()>. This	3071	up/change the process environment, followed by a call to C<exec()>. This
2920	sequence should be handled by libev without any problems.	3072	sequence should be handled by libev without any problems.
2921		3073
2922	This changes when the application actually wants to do event handling	3074	This changes when the application actually wants to do event handling
2923	in the child, or both parent in child, in effect "continuing" after the	3075	in the child, or both parent in child, in effect "continuing" after the
…		…
2939	disadvantage of having to use multiple event loops (which do not support	3091	disadvantage of having to use multiple event loops (which do not support
2940	signal watchers).	3092	signal watchers).
2941		3093
2942	When this is not possible, or you want to use the default loop for	3094	When this is not possible, or you want to use the default loop for
2943	other reasons, then in the process that wants to start "fresh", call	3095	other reasons, then in the process that wants to start "fresh", call
2944	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying	3096	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
2945	the default loop will "orphan" (not stop) all registered watchers, so you	3097	Destroying the default loop will "orphan" (not stop) all registered
2946	have to be careful not to execute code that modifies those watchers. Note	3098	watchers, so you have to be careful not to execute code that modifies
2947	also that in that case, you have to re-register any signal watchers.	3099	those watchers. Note also that in that case, you have to re-register any
		3100	signal watchers.
2948		3101
2949	=head3 Watcher-Specific Functions and Data Members	3102	=head3 Watcher-Specific Functions and Data Members
2950		3103
2951	=over 4	3104	=over 4
2952		3105
2953	=item ev_fork_init (ev_signal *, callback)	3106	=item ev_fork_init (ev_fork *, callback)
2954		3107
2955	Initialises and configures the fork watcher - it has no parameters of any	3108	Initialises and configures the fork watcher - it has no parameters of any
2956	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3109	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
2957	believe me.	3110	really.
2958		3111
2959	=back	3112	=back
2960		3113
2961		3114
		3115	=head2 C<ev_cleanup> - even the best things end
		3116
		3117	Cleanup watchers are called just before the event loop is being destroyed
		3118	by a call to C<ev_loop_destroy>.
		3119
		3120	While there is no guarantee that the event loop gets destroyed, cleanup
		3121	watchers provide a convenient method to install cleanup hooks for your
		3122	program, worker threads and so on - you just to make sure to destroy the
		3123	loop when you want them to be invoked.
		3124
		3125	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3126	all other watchers, they do not keep a reference to the event loop (which
		3127	makes a lot of sense if you think about it). Like all other watchers, you
		3128	can call libev functions in the callback, except C<ev_cleanup_start>.
		3129
		3130	=head3 Watcher-Specific Functions and Data Members
		3131
		3132	=over 4
		3133
		3134	=item ev_cleanup_init (ev_cleanup *, callback)
		3135
		3136	Initialises and configures the cleanup watcher - it has no parameters of
		3137	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3138	pointless, I assure you.
		3139
		3140	=back
		3141
		3142	Example: Register an atexit handler to destroy the default loop, so any
		3143	cleanup functions are called.
		3144
		3145	static void
		3146	program_exits (void)
		3147	{
		3148	ev_loop_destroy (EV_DEFAULT_UC);
		3149	}
		3150
		3151	...
		3152	atexit (program_exits);
		3153
		3154
2962	=head2 C<ev_async> - how to wake up another event loop	3155	=head2 C<ev_async> - how to wake up an event loop
2963		3156
2964	In general, you cannot use an C<ev_loop> from multiple threads or other	3157	In general, you cannot use an C<ev_run> from multiple threads or other
2965	asynchronous sources such as signal handlers (as opposed to multiple event	3158	asynchronous sources such as signal handlers (as opposed to multiple event
2966	loops - those are of course safe to use in different threads).	3159	loops - those are of course safe to use in different threads).
2967		3160
2968	Sometimes, however, you need to wake up another event loop you do not	3161	Sometimes, however, you need to wake up an event loop you do not control,
2969	control, for example because it belongs to another thread. This is what	3162	for example because it belongs to another thread. This is what C<ev_async>
2970	C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you	3163	watchers do: as long as the C<ev_async> watcher is active, you can signal
2971	can signal it by calling C<ev_async_send>, which is thread- and signal	3164	it by calling C<ev_async_send>, which is thread- and signal safe.
2972	safe.
2973		3165
2974	This functionality is very similar to C<ev_signal> watchers, as signals,	3166	This functionality is very similar to C<ev_signal> watchers, as signals,
2975	too, are asynchronous in nature, and signals, too, will be compressed	3167	too, are asynchronous in nature, and signals, too, will be compressed
2976	(i.e. the number of callback invocations may be less than the number of	3168	(i.e. the number of callback invocations may be less than the number of
2977	C<ev_async_sent> calls).	3169	C<ev_async_sent> calls).
…		…
3132		3324
3133	If C<timeout> is less than 0, then no timeout watcher will be	3325	If C<timeout> is less than 0, then no timeout watcher will be
3134	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	3326	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
3135	repeat = 0) will be started. C<0> is a valid timeout.	3327	repeat = 0) will be started. C<0> is a valid timeout.
3136		3328
3137	The callback has the type C<void (*cb)(int revents, void *arg)> and gets	3329	The callback has the type C<void (*cb)(int revents, void *arg)> and is
3138	passed an C<revents> set like normal event callbacks (a combination of	3330	passed an C<revents> set like normal event callbacks (a combination of
3139	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	3331	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMER>) and the C<arg>
3140	value passed to C<ev_once>. Note that it is possible to receive I<both>	3332	value passed to C<ev_once>. Note that it is possible to receive I<both>
3141	a timeout and an io event at the same time - you probably should give io	3333	a timeout and an io event at the same time - you probably should give io
3142	events precedence.	3334	events precedence.
3143		3335
3144	Example: wait up to ten seconds for data to appear on STDIN_FILENO.	3336	Example: wait up to ten seconds for data to appear on STDIN_FILENO.
3145		3337
3146	static void stdin_ready (int revents, void *arg)	3338	static void stdin_ready (int revents, void *arg)
3147	{	3339	{
3148	if (revents & EV_READ)	3340	if (revents & EV_READ)
3149	/* stdin might have data for us, joy! */;	3341	/* stdin might have data for us, joy! */;
3150	else if (revents & EV_TIMEOUT)	3342	else if (revents & EV_TIMER)
3151	/* doh, nothing entered */;	3343	/* doh, nothing entered */;
3152	}	3344	}
3153		3345
3154	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3346	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
3155		3347
…		…
3289	myclass obj;	3481	myclass obj;
3290	ev::io iow;	3482	ev::io iow;
3291	iow.set <myclass, &myclass::io_cb> (&obj);	3483	iow.set <myclass, &myclass::io_cb> (&obj);
3292		3484
3293	=item w->set (object *)	3485	=item w->set (object *)
3294
3295	This is an B<experimental> feature that might go away in a future version.
3296		3486
3297	This is a variation of a method callback - leaving out the method to call	3487	This is a variation of a method callback - leaving out the method to call
3298	will default the method to C<operator ()>, which makes it possible to use	3488	will default the method to C<operator ()>, which makes it possible to use
3299	functor objects without having to manually specify the C<operator ()> all	3489	functor objects without having to manually specify the C<operator ()> all
3300	the time. Incidentally, you can then also leave out the template argument	3490	the time. Incidentally, you can then also leave out the template argument
…		…
3340	Associates a different C<struct ev_loop> with this watcher. You can only	3530	Associates a different C<struct ev_loop> with this watcher. You can only
3341	do this when the watcher is inactive (and not pending either).	3531	do this when the watcher is inactive (and not pending either).
3342		3532
3343	=item w->set ([arguments])	3533	=item w->set ([arguments])
3344		3534
3345	Basically the same as C<ev_TYPE_set>, with the same arguments. Must be	3535	Basically the same as C<ev_TYPE_set>, with the same arguments. Either this
3346	called at least once. Unlike the C counterpart, an active watcher gets	3536	method or a suitable start method must be called at least once. Unlike the
3347	automatically stopped and restarted when reconfiguring it with this	3537	C counterpart, an active watcher gets automatically stopped and restarted
3348	method.	3538	when reconfiguring it with this method.
3349		3539
3350	=item w->start ()	3540	=item w->start ()
3351		3541
3352	Starts the watcher. Note that there is no C<loop> argument, as the	3542	Starts the watcher. Note that there is no C<loop> argument, as the
3353	constructor already stores the event loop.	3543	constructor already stores the event loop.
3354		3544
		3545	=item w->start ([arguments])
		3546
		3547	Instead of calling C<set> and C<start> methods separately, it is often
		3548	convenient to wrap them in one call. Uses the same type of arguments as
		3549	the configure C<set> method of the watcher.
		3550
3355	=item w->stop ()	3551	=item w->stop ()
3356		3552
3357	Stops the watcher if it is active. Again, no C<loop> argument.	3553	Stops the watcher if it is active. Again, no C<loop> argument.
3358		3554
3359	=item w->again () (C<ev::timer>, C<ev::periodic> only)	3555	=item w->again () (C<ev::timer>, C<ev::periodic> only)
…		…
3371		3567
3372	=back	3568	=back
3373		3569
3374	=back	3570	=back
3375		3571
3376	Example: Define a class with an IO and idle watcher, start one of them in	3572	Example: Define a class with two I/O and idle watchers, start the I/O
3377	the constructor.	3573	watchers in the constructor.
3378		3574
3379	class myclass	3575	class myclass
3380	{	3576	{
3381	ev::io io ; void io_cb (ev::io &w, int revents);	3577	ev::io io ; void io_cb (ev::io &w, int revents);
		3578	ev::io2 io2 ; void io2_cb (ev::io &w, int revents);
3382	ev::idle idle; void idle_cb (ev::idle &w, int revents);	3579	ev::idle idle; void idle_cb (ev::idle &w, int revents);
3383		3580
3384	myclass (int fd)	3581	myclass (int fd)
3385	{	3582	{
3386	io .set <myclass, &myclass::io_cb > (this);	3583	io .set <myclass, &myclass::io_cb > (this);
		3584	io2 .set <myclass, &myclass::io2_cb > (this);
3387	idle.set <myclass, &myclass::idle_cb> (this);	3585	idle.set <myclass, &myclass::idle_cb> (this);
3388		3586
3389	io.start (fd, ev::READ);	3587	io.set (fd, ev::WRITE); // configure the watcher
		3588	io.start (); // start it whenever convenient
		3589
		3590	io2.start (fd, ev::READ); // set + start in one call
3390	}	3591	}
3391	};	3592	};
3392		3593
3393		3594
3394	=head1 OTHER LANGUAGE BINDINGS	3595	=head1 OTHER LANGUAGE BINDINGS
…		…
3442	Erkki Seppala has written Ocaml bindings for libev, to be found at	3643	Erkki Seppala has written Ocaml bindings for libev, to be found at
3443	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.	3644	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
3444		3645
3445	=item Lua	3646	=item Lua
3446		3647
3447	Brian Maher has written a partial interface to libev	3648	Brian Maher has written a partial interface to libev for lua (at the
3448	for lua (only C<ev_io> and C<ev_timer>), to be found at	3649	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
3449	L<http://github.com/brimworks/lua-ev>.	3650	L<http://github.com/brimworks/lua-ev>.
3450		3651
3451	=back	3652	=back
3452		3653
3453		3654
…		…
3468	loop argument"). The C<EV_A> form is used when this is the sole argument,	3669	loop argument"). The C<EV_A> form is used when this is the sole argument,
3469	C<EV_A_> is used when other arguments are following. Example:	3670	C<EV_A_> is used when other arguments are following. Example:
3470		3671
3471	ev_unref (EV_A);	3672	ev_unref (EV_A);
3472	ev_timer_add (EV_A_ watcher);	3673	ev_timer_add (EV_A_ watcher);
3473	ev_loop (EV_A_ 0);	3674	ev_run (EV_A_ 0);
3474		3675
3475	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,	3676	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
3476	which is often provided by the following macro.	3677	which is often provided by the following macro.
3477		3678
3478	=item C<EV_P>, C<EV_P_>	3679	=item C<EV_P>, C<EV_P_>
…		…
3518	}	3719	}
3519		3720
3520	ev_check check;	3721	ev_check check;
3521	ev_check_init (&check, check_cb);	3722	ev_check_init (&check, check_cb);
3522	ev_check_start (EV_DEFAULT_ &check);	3723	ev_check_start (EV_DEFAULT_ &check);
3523	ev_loop (EV_DEFAULT_ 0);	3724	ev_run (EV_DEFAULT_ 0);
3524		3725
3525	=head1 EMBEDDING	3726	=head1 EMBEDDING
3526		3727
3527	Libev can (and often is) directly embedded into host	3728	Libev can (and often is) directly embedded into host
3528	applications. Examples of applications that embed it include the Deliantra	3729	applications. Examples of applications that embed it include the Deliantra
…		…
3608	libev.m4	3809	libev.m4
3609		3810
3610	=head2 PREPROCESSOR SYMBOLS/MACROS	3811	=head2 PREPROCESSOR SYMBOLS/MACROS
3611		3812
3612	Libev can be configured via a variety of preprocessor symbols you have to	3813	Libev can be configured via a variety of preprocessor symbols you have to
3613	define before including any of its files. The default in the absence of	3814	define before including (or compiling) any of its files. The default in
3614	autoconf is documented for every option.	3815	the absence of autoconf is documented for every option.
		3816
		3817	Symbols marked with "(h)" do not change the ABI, and can have different
		3818	values when compiling libev vs. including F<ev.h>, so it is permissible
		3819	to redefine them before including F<ev.h> without breaking compatibility
		3820	to a compiled library. All other symbols change the ABI, which means all
		3821	users of libev and the libev code itself must be compiled with compatible
		3822	settings.
3615		3823
3616	=over 4	3824	=over 4
3617		3825
		3826	=item EV_COMPAT3 (h)
		3827
		3828	Backwards compatibility is a major concern for libev. This is why this
		3829	release of libev comes with wrappers for the functions and symbols that
		3830	have been renamed between libev version 3 and 4.
		3831
		3832	You can disable these wrappers (to test compatibility with future
		3833	versions) by defining C<EV_COMPAT3> to C<0> when compiling your
		3834	sources. This has the additional advantage that you can drop the C<struct>
		3835	from C<struct ev_loop> declarations, as libev will provide an C<ev_loop>
		3836	typedef in that case.
		3837
		3838	In some future version, the default for C<EV_COMPAT3> will become C<0>,
		3839	and in some even more future version the compatibility code will be
		3840	removed completely.
		3841
3618	=item EV_STANDALONE	3842	=item EV_STANDALONE (h)
3619		3843
3620	Must always be C<1> if you do not use autoconf configuration, which	3844	Must always be C<1> if you do not use autoconf configuration, which
3621	keeps libev from including F<config.h>, and it also defines dummy	3845	keeps libev from including F<config.h>, and it also defines dummy
3622	implementations for some libevent functions (such as logging, which is not	3846	implementations for some libevent functions (such as logging, which is not
3623	supported). It will also not define any of the structs usually found in	3847	supported). It will also not define any of the structs usually found in
…		…
3773	as well as for signal and thread safety in C<ev_async> watchers.	3997	as well as for signal and thread safety in C<ev_async> watchers.
3774		3998
3775	In the absence of this define, libev will use C<sig_atomic_t volatile>	3999	In the absence of this define, libev will use C<sig_atomic_t volatile>
3776	(from F<signal.h>), which is usually good enough on most platforms.	4000	(from F<signal.h>), which is usually good enough on most platforms.
3777		4001
3778	=item EV_H	4002	=item EV_H (h)
3779		4003
3780	The name of the F<ev.h> header file used to include it. The default if	4004	The name of the F<ev.h> header file used to include it. The default if
3781	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be	4005	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
3782	used to virtually rename the F<ev.h> header file in case of conflicts.	4006	used to virtually rename the F<ev.h> header file in case of conflicts.
3783		4007
3784	=item EV_CONFIG_H	4008	=item EV_CONFIG_H (h)
3785		4009
3786	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override	4010	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
3787	F<ev.c>'s idea of where to find the F<config.h> file, similarly to	4011	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
3788	C<EV_H>, above.	4012	C<EV_H>, above.
3789		4013
3790	=item EV_EVENT_H	4014	=item EV_EVENT_H (h)
3791		4015
3792	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea	4016	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
3793	of how the F<event.h> header can be found, the default is C<"event.h">.	4017	of how the F<event.h> header can be found, the default is C<"event.h">.
3794		4018
3795	=item EV_PROTOTYPES	4019	=item EV_PROTOTYPES (h)
3796		4020
3797	If defined to be C<0>, then F<ev.h> will not define any function	4021	If defined to be C<0>, then F<ev.h> will not define any function
3798	prototypes, but still define all the structs and other symbols. This is	4022	prototypes, but still define all the structs and other symbols. This is
3799	occasionally useful if you want to provide your own wrapper functions	4023	occasionally useful if you want to provide your own wrapper functions
3800	around libev functions.	4024	around libev functions.
…		…
3822	fine.	4046	fine.
3823		4047
3824	If your embedding application does not need any priorities, defining these	4048	If your embedding application does not need any priorities, defining these
3825	both to C<0> will save some memory and CPU.	4049	both to C<0> will save some memory and CPU.
3826		4050
3827	=item EV_PERIODIC_ENABLE	4051	=item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE,
		4052	EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE,
		4053	EV_ASYNC_ENABLE, EV_CHILD_ENABLE.
3828		4054
3829	If undefined or defined to be C<1>, then periodic timers are supported. If	4055	If undefined or defined to be C<1> (and the platform supports it), then
3830	defined to be C<0>, then they are not. Disabling them saves a few kB of	4056	the respective watcher type is supported. If defined to be C<0>, then it
3831	code.	4057	is not. Disabling watcher types mainly saves code size.
3832		4058
3833	=item EV_IDLE_ENABLE	4059	=item EV_FEATURES
3834
3835	If undefined or defined to be C<1>, then idle watchers are supported. If
3836	defined to be C<0>, then they are not. Disabling them saves a few kB of
3837	code.
3838
3839	=item EV_EMBED_ENABLE
3840
3841	If undefined or defined to be C<1>, then embed watchers are supported. If
3842	defined to be C<0>, then they are not. Embed watchers rely on most other
3843	watcher types, which therefore must not be disabled.
3844
3845	=item EV_STAT_ENABLE
3846
3847	If undefined or defined to be C<1>, then stat watchers are supported. If
3848	defined to be C<0>, then they are not.
3849
3850	=item EV_FORK_ENABLE
3851
3852	If undefined or defined to be C<1>, then fork watchers are supported. If
3853	defined to be C<0>, then they are not.
3854
3855	=item EV_ASYNC_ENABLE
3856
3857	If undefined or defined to be C<1>, then async watchers are supported. If
3858	defined to be C<0>, then they are not.
3859
3860	=item EV_MINIMAL
3861		4060
3862	If you need to shave off some kilobytes of code at the expense of some	4061	If you need to shave off some kilobytes of code at the expense of some
3863	speed (but with the full API), define this symbol to C<1>. Currently this	4062	speed (but with the full API), you can define this symbol to request
3864	is used to override some inlining decisions, saves roughly 30% code size	4063	certain subsets of functionality. The default is to enable all features
3865	on amd64. It also selects a much smaller 2-heap for timer management over	4064	that can be enabled on the platform.
3866	the default 4-heap.
3867		4065
3868	You can save even more by disabling watcher types you do not need	4066	A typical way to use this symbol is to define it to C<0> (or to a bitset
3869	and setting C<EV_MAXPRI> == C<EV_MINPRI>. Also, disabling C<assert>	4067	with some broad features you want) and then selectively re-enable
3870	(C<-DNDEBUG>) will usually reduce code size a lot.	4068	additional parts you want, for example if you want everything minimal,
		4069	but multiple event loop support, async and child watchers and the poll
		4070	backend, use this:
3871		4071
3872	Defining C<EV_MINIMAL> to C<2> will additionally reduce the core API to	4072	#define EV_FEATURES 0
3873	provide a bare-bones event library. See C<ev.h> for details on what parts	4073	#define EV_MULTIPLICITY 1
3874	of the API are still available, and do not complain if this subset changes	4074	#define EV_USE_POLL 1
3875	over time.	4075	#define EV_CHILD_ENABLE 1
		4076	#define EV_ASYNC_ENABLE 1
		4077
		4078	The actual value is a bitset, it can be a combination of the following
		4079	values:
		4080
		4081	=over 4
		4082
		4083	=item C<1> - faster/larger code
		4084
		4085	Use larger code to speed up some operations.
		4086
		4087	Currently this is used to override some inlining decisions (enlarging the
		4088	code size by roughly 30% on amd64).
		4089
		4090	When optimising for size, use of compiler flags such as C<-Os> with
		4091	gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of
		4092	assertions.
		4093
		4094	=item C<2> - faster/larger data structures
		4095
		4096	Replaces the small 2-heap for timer management by a faster 4-heap, larger
		4097	hash table sizes and so on. This will usually further increase code size
		4098	and can additionally have an effect on the size of data structures at
		4099	runtime.
		4100
		4101	=item C<4> - full API configuration
		4102
		4103	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
		4104	enables multiplicity (C<EV_MULTIPLICITY>=1).
		4105
		4106	=item C<8> - full API
		4107
		4108	This enables a lot of the "lesser used" API functions. See C<ev.h> for
		4109	details on which parts of the API are still available without this
		4110	feature, and do not complain if this subset changes over time.
		4111
		4112	=item C<16> - enable all optional watcher types
		4113
		4114	Enables all optional watcher types. If you want to selectively enable
		4115	only some watcher types other than I/O and timers (e.g. prepare,
		4116	embed, async, child...) you can enable them manually by defining
		4117	C<EV_watchertype_ENABLE> to C<1> instead.
		4118
		4119	=item C<32> - enable all backends
		4120
		4121	This enables all backends - without this feature, you need to enable at
		4122	least one backend manually (C<EV_USE_SELECT> is a good choice).
		4123
		4124	=item C<64> - enable OS-specific "helper" APIs
		4125
		4126	Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by
		4127	default.
		4128
		4129	=back
		4130
		4131	Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0>
		4132	reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb
		4133	code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O
		4134	watchers, timers and monotonic clock support.
		4135
		4136	With an intelligent-enough linker (gcc+binutils are intelligent enough
		4137	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
		4138	your program might be left out as well - a binary starting a timer and an
		4139	I/O watcher then might come out at only 5Kb.
		4140
		4141	=item EV_AVOID_STDIO
		4142
		4143	If this is set to C<1> at compiletime, then libev will avoid using stdio
		4144	functions (printf, scanf, perror etc.). This will increase the code size
		4145	somewhat, but if your program doesn't otherwise depend on stdio and your
		4146	libc allows it, this avoids linking in the stdio library which is quite
		4147	big.
		4148
		4149	Note that error messages might become less precise when this option is
		4150	enabled.
3876		4151
3877	=item EV_NSIG	4152	=item EV_NSIG
3878		4153
3879	The highest supported signal number, +1 (or, the number of	4154	The highest supported signal number, +1 (or, the number of
3880	signals): Normally, libev tries to deduce the maximum number of signals	4155	signals): Normally, libev tries to deduce the maximum number of signals
3881	automatically, but sometimes this fails, in which case it can be	4156	automatically, but sometimes this fails, in which case it can be
3882	specified. Also, using a lower number than detected (C<32> should be	4157	specified. Also, using a lower number than detected (C<32> should be
3883	good for about any system in existance) can save some memory, as libev	4158	good for about any system in existence) can save some memory, as libev
3884	statically allocates some 12-24 bytes per signal number.	4159	statically allocates some 12-24 bytes per signal number.
3885		4160
3886	=item EV_PID_HASHSIZE	4161	=item EV_PID_HASHSIZE
3887		4162
3888	C<ev_child> watchers use a small hash table to distribute workload by	4163	C<ev_child> watchers use a small hash table to distribute workload by
3889	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	4164	pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled),
3890	than enough. If you need to manage thousands of children you might want to	4165	usually more than enough. If you need to manage thousands of children you
3891	increase this value (I<must> be a power of two).	4166	might want to increase this value (I<must> be a power of two).
3892		4167
3893	=item EV_INOTIFY_HASHSIZE	4168	=item EV_INOTIFY_HASHSIZE
3894		4169
3895	C<ev_stat> watchers use a small hash table to distribute workload by	4170	C<ev_stat> watchers use a small hash table to distribute workload by
3896	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	4171	inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES>
3897	usually more than enough. If you need to manage thousands of C<ev_stat>	4172	disabled), usually more than enough. If you need to manage thousands of
3898	watchers you might want to increase this value (I<must> be a power of	4173	C<ev_stat> watchers you might want to increase this value (I<must> be a
3899	two).	4174	power of two).
3900		4175
3901	=item EV_USE_4HEAP	4176	=item EV_USE_4HEAP
3902		4177
3903	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4178	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3904	timer and periodics heaps, libev uses a 4-heap when this symbol is defined	4179	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
3905	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably	4180	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
3906	faster performance with many (thousands) of watchers.	4181	faster performance with many (thousands) of watchers.
3907		4182
3908	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4183	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3909	(disabled).	4184	will be C<0>.
3910		4185
3911	=item EV_HEAP_CACHE_AT	4186	=item EV_HEAP_CACHE_AT
3912		4187
3913	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4188	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3914	timer and periodics heaps, libev can cache the timestamp (I<at>) within	4189	timer and periodics heaps, libev can cache the timestamp (I<at>) within
3915	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),	4190	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
3916	which uses 8-12 bytes more per watcher and a few hundred bytes more code,	4191	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
3917	but avoids random read accesses on heap changes. This improves performance	4192	but avoids random read accesses on heap changes. This improves performance
3918	noticeably with many (hundreds) of watchers.	4193	noticeably with many (hundreds) of watchers.
3919		4194
3920	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4195	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3921	(disabled).	4196	will be C<0>.
3922		4197
3923	=item EV_VERIFY	4198	=item EV_VERIFY
3924		4199
3925	Controls how much internal verification (see C<ev_loop_verify ()>) will	4200	Controls how much internal verification (see C<ev_verify ()>) will
3926	be done: If set to C<0>, no internal verification code will be compiled	4201	be done: If set to C<0>, no internal verification code will be compiled
3927	in. If set to C<1>, then verification code will be compiled in, but not	4202	in. If set to C<1>, then verification code will be compiled in, but not
3928	called. If set to C<2>, then the internal verification code will be	4203	called. If set to C<2>, then the internal verification code will be
3929	called once per loop, which can slow down libev. If set to C<3>, then the	4204	called once per loop, which can slow down libev. If set to C<3>, then the
3930	verification code will be called very frequently, which will slow down	4205	verification code will be called very frequently, which will slow down
3931	libev considerably.	4206	libev considerably.
3932		4207
3933	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be	4208	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3934	C<0>.	4209	will be C<0>.
3935		4210
3936	=item EV_COMMON	4211	=item EV_COMMON
3937		4212
3938	By default, all watchers have a C<void *data> member. By redefining	4213	By default, all watchers have a C<void *data> member. By redefining
3939	this macro to a something else you can include more and other types of	4214	this macro to something else you can include more and other types of
3940	members. You have to define it each time you include one of the files,	4215	members. You have to define it each time you include one of the files,
3941	though, and it must be identical each time.	4216	though, and it must be identical each time.
3942		4217
3943	For example, the perl EV module uses something like this:	4218	For example, the perl EV module uses something like this:
3944		4219
…		…
3997	file.	4272	file.
3998		4273
3999	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	4274	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
4000	that everybody includes and which overrides some configure choices:	4275	that everybody includes and which overrides some configure choices:
4001		4276
4002	#define EV_MINIMAL 1	4277	#define EV_FEATURES 8
4003	#define EV_USE_POLL 0	4278	#define EV_USE_SELECT 1
4004	#define EV_MULTIPLICITY 0
4005	#define EV_PERIODIC_ENABLE 0	4279	#define EV_PREPARE_ENABLE 1
		4280	#define EV_IDLE_ENABLE 1
4006	#define EV_STAT_ENABLE 0	4281	#define EV_SIGNAL_ENABLE 1
4007	#define EV_FORK_ENABLE 0	4282	#define EV_CHILD_ENABLE 1
		4283	#define EV_USE_STDEXCEPT 0
4008	#define EV_CONFIG_H <config.h>	4284	#define EV_CONFIG_H <config.h>
4009	#define EV_MINPRI 0
4010	#define EV_MAXPRI 0
4011		4285
4012	#include "ev++.h"	4286	#include "ev++.h"
4013		4287
4014	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4288	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
4015		4289
…		…
4146	userdata *u = ev_userdata (EV_A);	4420	userdata *u = ev_userdata (EV_A);
4147	pthread_mutex_lock (&u->lock);	4421	pthread_mutex_lock (&u->lock);
4148	}	4422	}
4149		4423
4150	The event loop thread first acquires the mutex, and then jumps straight	4424	The event loop thread first acquires the mutex, and then jumps straight
4151	into C<ev_loop>:	4425	into C<ev_run>:
4152		4426
4153	void *	4427	void *
4154	l_run (void *thr_arg)	4428	l_run (void *thr_arg)
4155	{	4429	{
4156	struct ev_loop *loop = (struct ev_loop *)thr_arg;	4430	struct ev_loop *loop = (struct ev_loop *)thr_arg;
4157		4431
4158	l_acquire (EV_A);	4432	l_acquire (EV_A);
4159	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);	4433	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
4160	ev_loop (EV_A_ 0);	4434	ev_run (EV_A_ 0);
4161	l_release (EV_A);	4435	l_release (EV_A);
4162		4436
4163	return 0;	4437	return 0;
4164	}	4438	}
4165		4439
…		…
4217		4491
4218	=head3 COROUTINES	4492	=head3 COROUTINES
4219		4493
4220	Libev is very accommodating to coroutines ("cooperative threads"):	4494	Libev is very accommodating to coroutines ("cooperative threads"):
4221	libev fully supports nesting calls to its functions from different	4495	libev fully supports nesting calls to its functions from different
4222	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4496	coroutines (e.g. you can call C<ev_run> on the same loop from two
4223	different coroutines, and switch freely between both coroutines running	4497	different coroutines, and switch freely between both coroutines running
4224	the loop, as long as you don't confuse yourself). The only exception is	4498	the loop, as long as you don't confuse yourself). The only exception is
4225	that you must not do this from C<ev_periodic> reschedule callbacks.	4499	that you must not do this from C<ev_periodic> reschedule callbacks.
4226		4500
4227	Care has been taken to ensure that libev does not keep local state inside	4501	Care has been taken to ensure that libev does not keep local state inside
4228	C<ev_loop>, and other calls do not usually allow for coroutine switches as	4502	C<ev_run>, and other calls do not usually allow for coroutine switches as
4229	they do not call any callbacks.	4503	they do not call any callbacks.
4230		4504
4231	=head2 COMPILER WARNINGS	4505	=head2 COMPILER WARNINGS
4232		4506
4233	Depending on your compiler and compiler settings, you might get no or a	4507	Depending on your compiler and compiler settings, you might get no or a
…		…
4244	maintainable.	4518	maintainable.
4245		4519
4246	And of course, some compiler warnings are just plain stupid, or simply	4520	And of course, some compiler warnings are just plain stupid, or simply
4247	wrong (because they don't actually warn about the condition their message	4521	wrong (because they don't actually warn about the condition their message
4248	seems to warn about). For example, certain older gcc versions had some	4522	seems to warn about). For example, certain older gcc versions had some
4249	warnings that resulted an extreme number of false positives. These have	4523	warnings that resulted in an extreme number of false positives. These have
4250	been fixed, but some people still insist on making code warn-free with	4524	been fixed, but some people still insist on making code warn-free with
4251	such buggy versions.	4525	such buggy versions.
4252		4526
4253	While libev is written to generate as few warnings as possible,	4527	While libev is written to generate as few warnings as possible,
4254	"warn-free" code is not a goal, and it is recommended not to build libev	4528	"warn-free" code is not a goal, and it is recommended not to build libev
…		…
4290	I suggest using suppression lists.	4564	I suggest using suppression lists.
4291		4565
4292		4566
4293	=head1 PORTABILITY NOTES	4567	=head1 PORTABILITY NOTES
4294		4568
		4569	=head2 GNU/LINUX 32 BIT LIMITATIONS
		4570
		4571	GNU/Linux is the only common platform that supports 64 bit file/large file
		4572	interfaces but I<disables> them by default.
		4573
		4574	That means that libev compiled in the default environment doesn't support
		4575	files larger than 2GiB or so, which mainly affects C<ev_stat> watchers.
		4576
		4577	Unfortunately, many programs try to work around this GNU/Linux issue
		4578	by enabling the large file API, which makes them incompatible with the
		4579	standard libev compiled for their system.
		4580
		4581	Likewise, libev cannot enable the large file API itself as this would
		4582	suddenly make it incompatible to the default compile time environment,
		4583	i.e. all programs not using special compile switches.
		4584
		4585	=head2 OS/X AND DARWIN BUGS
		4586
		4587	The whole thing is a bug if you ask me - basically any system interface
		4588	you touch is broken, whether it is locales, poll, kqueue or even the
		4589	OpenGL drivers.
		4590
		4591	=head3 C<kqueue> is buggy
		4592
		4593	The kqueue syscall is broken in all known versions - most versions support
		4594	only sockets, many support pipes.
		4595
		4596	Libev tries to work around this by not using C<kqueue> by default on this
		4597	rotten platform, but of course you can still ask for it when creating a
		4598	loop - embedding a socket-only kqueue loop into a select-based one is
		4599	probably going to work well.
		4600
		4601	=head3 C<poll> is buggy
		4602
		4603	Instead of fixing C<kqueue>, Apple replaced their (working) C<poll>
		4604	implementation by something calling C<kqueue> internally around the 10.5.6
		4605	release, so now C<kqueue> I<and> C<poll> are broken.
		4606
		4607	Libev tries to work around this by not using C<poll> by default on
		4608	this rotten platform, but of course you can still ask for it when creating
		4609	a loop.
		4610
		4611	=head3 C<select> is buggy
		4612
		4613	All that's left is C<select>, and of course Apple found a way to fuck this
		4614	one up as well: On OS/X, C<select> actively limits the number of file
		4615	descriptors you can pass in to 1024 - your program suddenly crashes when
		4616	you use more.
		4617
		4618	There is an undocumented "workaround" for this - defining
		4619	C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should>
		4620	work on OS/X.
		4621
		4622	=head2 SOLARIS PROBLEMS AND WORKAROUNDS
		4623
		4624	=head3 C<errno> reentrancy
		4625
		4626	The default compile environment on Solaris is unfortunately so
		4627	thread-unsafe that you can't even use components/libraries compiled
		4628	without C<-D_REENTRANT> in a threaded program, which, of course, isn't
		4629	defined by default. A valid, if stupid, implementation choice.
		4630
		4631	If you want to use libev in threaded environments you have to make sure
		4632	it's compiled with C<_REENTRANT> defined.
		4633
		4634	=head3 Event port backend
		4635
		4636	The scalable event interface for Solaris is called "event
		4637	ports". Unfortunately, this mechanism is very buggy in all major
		4638	releases. If you run into high CPU usage, your program freezes or you get
		4639	a large number of spurious wakeups, make sure you have all the relevant
		4640	and latest kernel patches applied. No, I don't know which ones, but there
		4641	are multiple ones to apply, and afterwards, event ports actually work
		4642	great.
		4643
		4644	If you can't get it to work, you can try running the program by setting
		4645	the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and
		4646	C<select> backends.
		4647
		4648	=head2 AIX POLL BUG
		4649
		4650	AIX unfortunately has a broken C<poll.h> header. Libev works around
		4651	this by trying to avoid the poll backend altogether (i.e. it's not even
		4652	compiled in), which normally isn't a big problem as C<select> works fine
		4653	with large bitsets on AIX, and AIX is dead anyway.
		4654
4295	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS	4655	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
		4656
		4657	=head3 General issues
4296		4658
4297	Win32 doesn't support any of the standards (e.g. POSIX) that libev	4659	Win32 doesn't support any of the standards (e.g. POSIX) that libev
4298	requires, and its I/O model is fundamentally incompatible with the POSIX	4660	requires, and its I/O model is fundamentally incompatible with the POSIX
4299	model. Libev still offers limited functionality on this platform in	4661	model. Libev still offers limited functionality on this platform in
4300	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	4662	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
4301	descriptors. This only applies when using Win32 natively, not when using	4663	descriptors. This only applies when using Win32 natively, not when using
4302	e.g. cygwin.	4664	e.g. cygwin. Actually, it only applies to the microsofts own compilers,
		4665	as every compielr comes with a slightly differently broken/incompatible
		4666	environment.
4303		4667
4304	Lifting these limitations would basically require the full	4668	Lifting these limitations would basically require the full
4305	re-implementation of the I/O system. If you are into these kinds of	4669	re-implementation of the I/O system. If you are into this kind of thing,
4306	things, then note that glib does exactly that for you in a very portable	4670	then note that glib does exactly that for you in a very portable way (note
4307	way (note also that glib is the slowest event library known to man).	4671	also that glib is the slowest event library known to man).
4308		4672
4309	There is no supported compilation method available on windows except	4673	There is no supported compilation method available on windows except
4310	embedding it into other applications.	4674	embedding it into other applications.
4311		4675
4312	Sensible signal handling is officially unsupported by Microsoft - libev	4676	Sensible signal handling is officially unsupported by Microsoft - libev
…		…
4340	you do I<not> compile the F<ev.c> or any other embedded source files!):	4704	you do I<not> compile the F<ev.c> or any other embedded source files!):
4341		4705
4342	#include "evwrap.h"	4706	#include "evwrap.h"
4343	#include "ev.c"	4707	#include "ev.c"
4344		4708
4345	=over 4
4346
4347	=item The winsocket select function	4709	=head3 The winsocket C<select> function
4348		4710
4349	The winsocket C<select> function doesn't follow POSIX in that it	4711	The winsocket C<select> function doesn't follow POSIX in that it
4350	requires socket I<handles> and not socket I<file descriptors> (it is	4712	requires socket I<handles> and not socket I<file descriptors> (it is
4351	also extremely buggy). This makes select very inefficient, and also	4713	also extremely buggy). This makes select very inefficient, and also
4352	requires a mapping from file descriptors to socket handles (the Microsoft	4714	requires a mapping from file descriptors to socket handles (the Microsoft
…		…
4361	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */	4723	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
4362		4724
4363	Note that winsockets handling of fd sets is O(n), so you can easily get a	4725	Note that winsockets handling of fd sets is O(n), so you can easily get a
4364	complexity in the O(n²) range when using win32.	4726	complexity in the O(n²) range when using win32.
4365		4727
4366	=item Limited number of file descriptors	4728	=head3 Limited number of file descriptors
4367		4729
4368	Windows has numerous arbitrary (and low) limits on things.	4730	Windows has numerous arbitrary (and low) limits on things.
4369		4731
4370	Early versions of winsocket's select only supported waiting for a maximum	4732	Early versions of winsocket's select only supported waiting for a maximum
4371	of C<64> handles (probably owning to the fact that all windows kernels	4733	of C<64> handles (probably owning to the fact that all windows kernels
…		…
4386	runtime libraries. This might get you to about C<512> or C<2048> sockets	4748	runtime libraries. This might get you to about C<512> or C<2048> sockets
4387	(depending on windows version and/or the phase of the moon). To get more,	4749	(depending on windows version and/or the phase of the moon). To get more,
4388	you need to wrap all I/O functions and provide your own fd management, but	4750	you need to wrap all I/O functions and provide your own fd management, but
4389	the cost of calling select (O(n²)) will likely make this unworkable.	4751	the cost of calling select (O(n²)) will likely make this unworkable.
4390		4752
4391	=back
4392
4393	=head2 PORTABILITY REQUIREMENTS	4753	=head2 PORTABILITY REQUIREMENTS
4394		4754
4395	In addition to a working ISO-C implementation and of course the	4755	In addition to a working ISO-C implementation and of course the
4396	backend-specific APIs, libev relies on a few additional extensions:	4756	backend-specific APIs, libev relies on a few additional extensions:
4397		4757
…		…
4403	Libev assumes not only that all watcher pointers have the same internal	4763	Libev assumes not only that all watcher pointers have the same internal
4404	structure (guaranteed by POSIX but not by ISO C for example), but it also	4764	structure (guaranteed by POSIX but not by ISO C for example), but it also
4405	assumes that the same (machine) code can be used to call any watcher	4765	assumes that the same (machine) code can be used to call any watcher
4406	callback: The watcher callbacks have different type signatures, but libev	4766	callback: The watcher callbacks have different type signatures, but libev
4407	calls them using an C<ev_watcher *> internally.	4767	calls them using an C<ev_watcher *> internally.
		4768
		4769	=item pointer accesses must be thread-atomic
		4770
		4771	Accessing a pointer value must be atomic, it must both be readable and
		4772	writable in one piece - this is the case on all current architectures.
4408		4773
4409	=item C<sig_atomic_t volatile> must be thread-atomic as well	4774	=item C<sig_atomic_t volatile> must be thread-atomic as well
4410		4775
4411	The type C<sig_atomic_t volatile> (or whatever is defined as	4776	The type C<sig_atomic_t volatile> (or whatever is defined as
4412	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different	4777	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
…		…
4435	watchers.	4800	watchers.
4436		4801
4437	=item C<double> must hold a time value in seconds with enough accuracy	4802	=item C<double> must hold a time value in seconds with enough accuracy
4438		4803
4439	The type C<double> is used to represent timestamps. It is required to	4804	The type C<double> is used to represent timestamps. It is required to
4440	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	4805	have at least 51 bits of mantissa (and 9 bits of exponent), which is
4441	enough for at least into the year 4000. This requirement is fulfilled by	4806	good enough for at least into the year 4000 with millisecond accuracy
		4807	(the design goal for libev). This requirement is overfulfilled by
4442	implementations implementing IEEE 754, which is basically all existing	4808	implementations using IEEE 754, which is basically all existing ones. With
4443	ones. With IEEE 754 doubles, you get microsecond accuracy until at least	4809	IEEE 754 doubles, you get microsecond accuracy until at least 2200.
4444	2200.
4445		4810
4446	=back	4811	=back
4447		4812
4448	If you know of other additional requirements drop me a note.	4813	If you know of other additional requirements drop me a note.
4449		4814
…		…
4517	involves iterating over all running async watchers or all signal numbers.	4882	involves iterating over all running async watchers or all signal numbers.
4518		4883
4519	=back	4884	=back
4520		4885
4521		4886
		4887	=head1 PORTING FROM LIBEV 3.X TO 4.X
		4888
		4889	The major version 4 introduced some incompatible changes to the API.
		4890
		4891	At the moment, the C<ev.h> header file provides compatibility definitions
		4892	for all changes, so most programs should still compile. The compatibility
		4893	layer might be removed in later versions of libev, so better update to the
		4894	new API early than late.
		4895
		4896	=over 4
		4897
		4898	=item C<EV_COMPAT3> backwards compatibility mechanism
		4899
		4900	The backward compatibility mechanism can be controlled by
		4901	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		4902	section.
		4903
		4904	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		4905
		4906	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		4907
		4908	ev_loop_destroy (EV_DEFAULT_UC);
		4909	ev_loop_fork (EV_DEFAULT);
		4910
		4911	=item function/symbol renames
		4912
		4913	A number of functions and symbols have been renamed:
		4914
		4915	ev_loop => ev_run
		4916	EVLOOP_NONBLOCK => EVRUN_NOWAIT
		4917	EVLOOP_ONESHOT => EVRUN_ONCE
		4918
		4919	ev_unloop => ev_break
		4920	EVUNLOOP_CANCEL => EVBREAK_CANCEL
		4921	EVUNLOOP_ONE => EVBREAK_ONE
		4922	EVUNLOOP_ALL => EVBREAK_ALL
		4923
		4924	EV_TIMEOUT => EV_TIMER
		4925
		4926	ev_loop_count => ev_iteration
		4927	ev_loop_depth => ev_depth
		4928	ev_loop_verify => ev_verify
		4929
		4930	Most functions working on C<struct ev_loop> objects don't have an
		4931	C<ev_loop_> prefix, so it was removed; C<ev_loop>, C<ev_unloop> and
		4932	associated constants have been renamed to not collide with the C<struct
		4933	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
		4934	as all other watcher types. Note that C<ev_loop_fork> is still called
		4935	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
		4936	typedef.
		4937
		4938	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
		4939
		4940	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
		4941	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
		4942	and work, but the library code will of course be larger.
		4943
		4944	=back
		4945
		4946
4522	=head1 GLOSSARY	4947	=head1 GLOSSARY
4523		4948
4524	=over 4	4949	=over 4
4525		4950
4526	=item active	4951	=item active
4527		4952
4528	A watcher is active as long as it has been started (has been attached to	4953	A watcher is active as long as it has been started and not yet stopped.
4529	an event loop) but not yet stopped (disassociated from the event loop).	4954	See L<WATCHER STATES> for details.
4530		4955
4531	=item application	4956	=item application
4532		4957
4533	In this document, an application is whatever is using libev.	4958	In this document, an application is whatever is using libev.
		4959
		4960	=item backend
		4961
		4962	The part of the code dealing with the operating system interfaces.
4534		4963
4535	=item callback	4964	=item callback
4536		4965
4537	The address of a function that is called when some event has been	4966	The address of a function that is called when some event has been
4538	detected. Callbacks are being passed the event loop, the watcher that	4967	detected. Callbacks are being passed the event loop, the watcher that
4539	received the event, and the actual event bitset.	4968	received the event, and the actual event bitset.
4540		4969
4541	=item callback invocation	4970	=item callback/watcher invocation
4542		4971
4543	The act of calling the callback associated with a watcher.	4972	The act of calling the callback associated with a watcher.
4544		4973
4545	=item event	4974	=item event
4546		4975
4547	A change of state of some external event, such as data now being available	4976	A change of state of some external event, such as data now being available
4548	for reading on a file descriptor, time having passed or simply not having	4977	for reading on a file descriptor, time having passed or simply not having
4549	any other events happening anymore.	4978	any other events happening anymore.
4550		4979
4551	In libev, events are represented as single bits (such as C<EV_READ> or	4980	In libev, events are represented as single bits (such as C<EV_READ> or
4552	C<EV_TIMEOUT>).	4981	C<EV_TIMER>).
4553		4982
4554	=item event library	4983	=item event library
4555		4984
4556	A software package implementing an event model and loop.	4985	A software package implementing an event model and loop.
4557		4986
…		…
4565	The model used to describe how an event loop handles and processes	4994	The model used to describe how an event loop handles and processes
4566	watchers and events.	4995	watchers and events.
4567		4996
4568	=item pending	4997	=item pending
4569		4998
4570	A watcher is pending as soon as the corresponding event has been detected,	4999	A watcher is pending as soon as the corresponding event has been
4571	and stops being pending as soon as the watcher will be invoked or its	5000	detected. See L<WATCHER STATES> for details.
4572	pending status is explicitly cleared by the application.
4573
4574	A watcher can be pending, but not active. Stopping a watcher also clears
4575	its pending status.
4576		5001
4577	=item real time	5002	=item real time
4578		5003
4579	The physical time that is observed. It is apparently strictly monotonic :)	5004	The physical time that is observed. It is apparently strictly monotonic :)
4580		5005
…		…
4587	=item watcher	5012	=item watcher
4588		5013
4589	A data structure that describes interest in certain events. Watchers need	5014	A data structure that describes interest in certain events. Watchers need
4590	to be started (attached to an event loop) before they can receive events.	5015	to be started (attached to an event loop) before they can receive events.
4591		5016
4592	=item watcher invocation
4593
4594	The act of calling the callback associated with a watcher.
4595
4596	=back	5017	=back
4597		5018
4598	=head1 AUTHOR	5019	=head1 AUTHOR
4599		5020
4600	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.	5021	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5022	Magnusson and Emanuele Giaquinta.
4601		5023

Diff Legend

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