ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.299 by sf-exg, Sat Aug 28 21:42:12 2010 UTC vs.
Revision 1.343 by root, Wed Nov 10 13:39:10 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
…		…
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	Familiarity 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 (in practise	137	the (fractional) number of seconds since the (POSIX) epoch (in practice
130	somewhere near the beginning of 1970, details are complicated, don't	138	somewhere near the beginning of 1970, details are complicated, don't
131	ask). This type is called C<ev_tstamp>, which is what you should use	139	ask). This type is called C<ev_tstamp>, which is what you should use
132	too. It usually aliases to the C<double> type in C. When you need to do	140	too. It usually aliases to the C<double> type in C. When you need to do
133	any calculations on it, you should treat it as some floating point value.	141	any calculations on it, you should treat it as some floating point value.
134		142
…		…
165		173
166	=item ev_tstamp ev_time ()	174	=item ev_tstamp ev_time ()
167		175
168	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
169	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
170	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>.
171		180
172	=item ev_sleep (ev_tstamp interval)	181	=item ev_sleep (ev_tstamp interval)
173		182
174	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
175	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
…		…
192	as this indicates an incompatible change. Minor versions are usually	201	as this indicates an incompatible change. Minor versions are usually
193	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
194	not a problem.	203	not a problem.
195		204
196	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
197	version (note, however, that this will not detect ABI mismatches :).	206	version (note, however, that this will not detect other ABI mismatches,
		207	such as LFS or reentrancy).
198		208
199	assert (("libev version mismatch",	209	assert (("libev version mismatch",
200	ev_version_major () == EV_VERSION_MAJOR	210	ev_version_major () == EV_VERSION_MAJOR
201	&& ev_version_minor () >= EV_VERSION_MINOR));	211	&& ev_version_minor () >= EV_VERSION_MINOR));
202		212
…		…
213	assert (("sorry, no epoll, no sex",	223	assert (("sorry, no epoll, no sex",
214	ev_supported_backends () & EVBACKEND_EPOLL));	224	ev_supported_backends () & EVBACKEND_EPOLL));
215		225
216	=item unsigned int ev_recommended_backends ()	226	=item unsigned int ev_recommended_backends ()
217		227
218	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
219	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
220	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
221	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
222	(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
223	libev will probe for if you specify no backends explicitly.	234	probe for if you specify no backends explicitly.
224		235
225	=item unsigned int ev_embeddable_backends ()	236	=item unsigned int ev_embeddable_backends ()
226		237
227	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
228	is the theoretical, all-platform, value. To find which backends	239	value is platform-specific but can include backends not available on the
229	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
230	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	241	the current system, you would need to look at C<ev_embeddable_backends ()
231	recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
232		243
233	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
234		245
235	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]	246	=item ev_set_allocator (void *(*cb)(void *ptr, long size))
236		247
237	Sets the allocation function to use (the prototype is similar - the	248	Sets the allocation function to use (the prototype is similar - the
238	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is	249	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is
239	used to allocate and free memory (no surprises here). If it returns zero	250	used to allocate and free memory (no surprises here). If it returns zero
240	when memory needs to be allocated (C<size != 0>), the library might abort	251	when memory needs to be allocated (C<size != 0>), the library might abort
…		…
266	}	277	}
267		278
268	...	279	...
269	ev_set_allocator (persistent_realloc);	280	ev_set_allocator (persistent_realloc);
270		281
271	=item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]	282	=item ev_set_syserr_cb (void (*cb)(const char *msg))
272		283
273	Set the callback function to call on a retryable system call error (such	284	Set the callback function to call on a retryable system call error (such
274	as failed select, poll, epoll_wait). The message is a printable string	285	as failed select, poll, epoll_wait). The message is a printable string
275	indicating the system call or subsystem causing the problem. If this	286	indicating the system call or subsystem causing the problem. If this
276	callback is set, then libev will expect it to remedy the situation, no	287	callback is set, then libev will expect it to remedy the situation, no
…		…
290	...	301	...
291	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
292		303
293	=back	304	=back
294		305
295	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	306	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
296		307
297	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
298	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
299	I<function>).	310	libev 3 had an C<ev_loop> function colliding with the struct name).
300		311
301	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
302	supports signals and child events, and dynamically created loops which do	313	supports child process events, and dynamically created event loops which
303	not.	314	do not.
304		315
305	=over 4	316	=over 4
306		317
307	=item struct ev_loop *ev_default_loop (unsigned int flags)	318	=item struct ev_loop *ev_default_loop (unsigned int flags)
308		319
309	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
310	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
311	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
312	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".
313		330
314	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
315	function.	332	function (or via the C<EV_DEFAULT> macro).
316		333
317	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
318	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
319	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).
320		338
321	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,
322	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
323	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
324	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
325	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	343	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
326	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	This function is thread-safe, and one common way to use libev with
		361	threads is indeed to create one loop per thread, and using the default
		362	loop in the "main" or "initial" thread.
327		363
328	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
329	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>).
330		366
331	The following flags are supported:	367	The following flags are supported:
…		…
366	environment variable.	402	environment variable.
367		403
368	=item C<EVFLAG_NOINOTIFY>	404	=item C<EVFLAG_NOINOTIFY>
369		405
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 its 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_SIGNALFD>	411	=item C<EVFLAG_SIGNALFD>
376		412
377	When this flag is specified, then libev will 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 API	414	I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API
379	delivers signals synchronously, which makes it both faster and might make	415	delivers signals synchronously, which makes it both faster and might make
380	it possible to get the queued signal data. It can also simplify signal	416	it possible to get the queued signal data. It can also simplify signal
381	handling with threads, as long as you properly block signals in your	417	handling with threads, as long as you properly block signals in your
382	threads that are not interested in handling them.	418	threads that are not interested in handling them.
383		419
…		…
427	epoll scales either O(1) or O(active_fds).	463	epoll scales either O(1) or O(active_fds).
428		464
429	The epoll mechanism deserves honorable mention as the most misdesigned	465	The epoll mechanism deserves honorable mention as the most misdesigned
430	of the more advanced event mechanisms: mere annoyances include silently	466	of the more advanced event mechanisms: mere annoyances include silently
431	dropping file descriptors, requiring a system call per change per file	467	dropping file descriptors, requiring a system call per change per file
432	descriptor (and unnecessary guessing of parameters), problems with dup and	468	descriptor (and unnecessary guessing of parameters), problems with dup,
		469	returning before the timeout value, resulting in additional iterations
		470	(and only giving 5ms accuracy while select on the same platform gives
433	so on. The biggest issue is fork races, however - if a program forks then	471	0.1ms) and so on. The biggest issue is fork races, however - if a program
434	I<both> parent and child process have to recreate the epoll set, which can	472	forks then I<both> parent and child process have to recreate the epoll
435	take considerable time (one syscall per file descriptor) and is of course	473	set, which can take considerable time (one syscall per file descriptor)
436	hard to detect.	474	and is of course hard to detect.
437		475
438	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but	476	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
439	of course I<doesn't>, and epoll just loves to report events for totally	477	of course I<doesn't>, and epoll just loves to report events for totally
440	I<different> file descriptors (even already closed ones, so one cannot	478	I<different> file descriptors (even already closed ones, so one cannot
441	even remove them from the set) than registered in the set (especially	479	even remove them from the set) than registered in the set (especially
442	on SMP systems). Libev tries to counter these spurious notifications by	480	on SMP systems). Libev tries to counter these spurious notifications by
443	employing an additional generation counter and comparing that against the	481	employing an additional generation counter and comparing that against the
444	events to filter out spurious ones, recreating the set when required.	482	events to filter out spurious ones, recreating the set when required. Last
		483	not least, it also refuses to work with some file descriptors which work
		484	perfectly fine with C<select> (files, many character devices...).
		485
		486	Epoll is truly the train wreck analog among event poll mechanisms.
445		487
446	While stopping, setting and starting an I/O watcher in the same iteration	488	While stopping, setting and starting an I/O watcher in the same iteration
447	will result in some caching, there is still a system call per such	489	will result in some caching, there is still a system call per such
448	incident (because the same I<file descriptor> could point to a different	490	incident (because the same I<file descriptor> could point to a different
449	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed	491	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
…		…
547	If one or more of the backend flags are or'ed into the flags value,	589	If one or more of the backend flags are or'ed into the flags value,
548	then only these backends will be tried (in the reverse order as listed	590	then only these backends will be tried (in the reverse order as listed
549	here). If none are specified, all backends in C<ev_recommended_backends	591	here). If none are specified, all backends in C<ev_recommended_backends
550	()> will be tried.	592	()> will be tried.
551		593
552	Example: This is the most typical usage.
553
554	if (!ev_default_loop (0))
555	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
556
557	Example: Restrict libev to the select and poll backends, and do not allow
558	environment settings to be taken into account:
559
560	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
561
562	Example: Use whatever libev has to offer, but make sure that kqueue is
563	used if available (warning, breaks stuff, best use only with your own
564	private event loop and only if you know the OS supports your types of
565	fds):
566
567	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
568
569	=item struct ev_loop *ev_loop_new (unsigned int flags)
570
571	Similar to C<ev_default_loop>, but always creates a new event loop that is
572	always distinct from the default loop.
573
574	Note that this function I<is> thread-safe, and one common way to use
575	libev with threads is indeed to create one loop per thread, and using the
576	default loop in the "main" or "initial" thread.
577
578	Example: Try to create a event loop that uses epoll and nothing else.	594	Example: Try to create a event loop that uses epoll and nothing else.
579		595
580	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	596	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
581	if (!epoller)	597	if (!epoller)
582	fatal ("no epoll found here, maybe it hides under your chair");	598	fatal ("no epoll found here, maybe it hides under your chair");
583		599
		600	Example: Use whatever libev has to offer, but make sure that kqueue is
		601	used if available.
		602
		603	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE);
		604
584	=item ev_default_destroy ()	605	=item ev_loop_destroy (loop)
585		606
586	Destroys the default loop (frees all memory and kernel state etc.). None	607	Destroys an event loop object (frees all memory and kernel state
587	of the active event watchers will be stopped in the normal sense, so	608	etc.). None of the active event watchers will be stopped in the normal
588	e.g. C<ev_is_active> might still return true. It is your responsibility to	609	sense, so e.g. C<ev_is_active> might still return true. It is your
589	either stop all watchers cleanly yourself I<before> calling this function,	610	responsibility to either stop all watchers cleanly yourself I<before>
590	or cope with the fact afterwards (which is usually the easiest thing, you	611	calling this function, or cope with the fact afterwards (which is usually
591	can just ignore the watchers and/or C<free ()> them for example).	612	the easiest thing, you can just ignore the watchers and/or C<free ()> them
		613	for example).
592		614
593	Note that certain global state, such as signal state (and installed signal	615	Note that certain global state, such as signal state (and installed signal
594	handlers), will not be freed by this function, and related watchers (such	616	handlers), will not be freed by this function, and related watchers (such
595	as signal and child watchers) would need to be stopped manually.	617	as signal and child watchers) would need to be stopped manually.
596		618
597	In general it is not advisable to call this function except in the	619	This function is normally used on loop objects allocated by
598	rare occasion where you really need to free e.g. the signal handling	620	C<ev_loop_new>, but it can also be used on the default loop returned by
		621	C<ev_default_loop>, in which case it is not thread-safe.
		622
		623	Note that it is not advisable to call this function on the default loop
		624	except in the rare occasion where you really need to free its resources.
599	pipe fds. If you need dynamically allocated loops it is better to use	625	If you need dynamically allocated loops it is better to use C<ev_loop_new>
600	C<ev_loop_new> and C<ev_loop_destroy>.	626	and C<ev_loop_destroy>.
601		627
602	=item ev_loop_destroy (loop)	628	=item ev_loop_fork (loop)
603		629
604	Like C<ev_default_destroy>, but destroys an event loop created by an
605	earlier call to C<ev_loop_new>.
606
607	=item ev_default_fork ()
608
609	This function sets a flag that causes subsequent C<ev_loop> iterations	630	This function sets a flag that causes subsequent C<ev_run> iterations to
610	to reinitialise the kernel state for backends that have one. Despite the	631	reinitialise the kernel state for backends that have one. Despite the
611	name, you can call it anytime, but it makes most sense after forking, in	632	name, you can call it anytime, but it makes most sense after forking, in
612	the child process (or both child and parent, but that again makes little	633	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
613	sense). You I<must> call it in the child before using any of the libev	634	child before resuming or calling C<ev_run>.
614	functions, and it will only take effect at the next C<ev_loop> iteration.
615		635
616	Again, you I<have> to call it on I<any> loop that you want to re-use after	636	Again, you I<have> to call it on I<any> loop that you want to re-use after
617	a fork, I<even if you do not plan to use the loop in the parent>. This is	637	a fork, I<even if you do not plan to use the loop in the parent>. This is
618	because some kernel interfaces *cough* I<kqueue> *cough* do funny things	638	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
619	during fork.	639	during fork.
620		640
621	On the other hand, you only need to call this function in the child	641	On the other hand, you only need to call this function in the child
622	process if and only if you want to use the event loop in the child. If you	642	process if and only if you want to use the event loop in the child. If
623	just fork+exec or create a new loop in the child, you don't have to call	643	you just fork+exec or create a new loop in the child, you don't have to
624	it at all.	644	call it at all (in fact, C<epoll> is so badly broken that it makes a
		645	difference, but libev will usually detect this case on its own and do a
		646	costly reset of the backend).
625		647
626	The function itself is quite fast and it's usually not a problem to call	648	The function itself is quite fast and it's usually not a problem to call
627	it just in case after a fork. To make this easy, the function will fit in	649	it just in case after a fork.
628	quite nicely into a call to C<pthread_atfork>:
629		650
		651	Example: Automate calling C<ev_loop_fork> on the default loop when
		652	using pthreads.
		653
		654	static void
		655	post_fork_child (void)
		656	{
		657	ev_loop_fork (EV_DEFAULT);
		658	}
		659
		660	...
630	pthread_atfork (0, 0, ev_default_fork);	661	pthread_atfork (0, 0, post_fork_child);
631
632	=item ev_loop_fork (loop)
633
634	Like C<ev_default_fork>, but acts on an event loop created by
635	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
636	after fork that you want to re-use in the child, and how you keep track of
637	them is entirely your own problem.
638		662
639	=item int ev_is_default_loop (loop)	663	=item int ev_is_default_loop (loop)
640		664
641	Returns true when the given loop is, in fact, the default loop, and false	665	Returns true when the given loop is, in fact, the default loop, and false
642	otherwise.	666	otherwise.
643		667
644	=item unsigned int ev_iteration (loop)	668	=item unsigned int ev_iteration (loop)
645		669
646	Returns the current iteration count for the loop, which is identical to	670	Returns the current iteration count for the event loop, which is identical
647	the number of times libev did poll for new events. It starts at C<0> and	671	to the number of times libev did poll for new events. It starts at C<0>
648	happily wraps around with enough iterations.	672	and happily wraps around with enough iterations.
649		673
650	This value can sometimes be useful as a generation counter of sorts (it	674	This value can sometimes be useful as a generation counter of sorts (it
651	"ticks" the number of loop iterations), as it roughly corresponds with	675	"ticks" the number of loop iterations), as it roughly corresponds with
652	C<ev_prepare> and C<ev_check> calls - and is incremented between the	676	C<ev_prepare> and C<ev_check> calls - and is incremented between the
653	prepare and check phases.	677	prepare and check phases.
654		678
655	=item unsigned int ev_depth (loop)	679	=item unsigned int ev_depth (loop)
656		680
657	Returns the number of times C<ev_loop> was entered minus the number of	681	Returns the number of times C<ev_run> was entered minus the number of
658	times C<ev_loop> was exited, in other words, the recursion depth.	682	times C<ev_run> was exited normally, in other words, the recursion depth.
659		683
660	Outside C<ev_loop>, this number is zero. In a callback, this number is	684	Outside C<ev_run>, this number is zero. In a callback, this number is
661	C<1>, unless C<ev_loop> was invoked recursively (or from another thread),	685	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
662	in which case it is higher.	686	in which case it is higher.
663		687
664	Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread	688	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread,
665	etc.), doesn't count as "exit" - consider this as a hint to avoid such	689	throwing an exception etc.), doesn't count as "exit" - consider this
666	ungentleman behaviour unless it's really convenient.	690	as a hint to avoid such ungentleman-like behaviour unless it's really
		691	convenient, in which case it is fully supported.
667		692
668	=item unsigned int ev_backend (loop)	693	=item unsigned int ev_backend (loop)
669		694
670	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	695	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
671	use.	696	use.
…		…
680		705
681	=item ev_now_update (loop)	706	=item ev_now_update (loop)
682		707
683	Establishes the current time by querying the kernel, updating the time	708	Establishes the current time by querying the kernel, updating the time
684	returned by C<ev_now ()> in the progress. This is a costly operation and	709	returned by C<ev_now ()> in the progress. This is a costly operation and
685	is usually done automatically within C<ev_loop ()>.	710	is usually done automatically within C<ev_run ()>.
686		711
687	This function is rarely useful, but when some event callback runs for a	712	This function is rarely useful, but when some event callback runs for a
688	very long time without entering the event loop, updating libev's idea of	713	very long time without entering the event loop, updating libev's idea of
689	the current time is a good idea.	714	the current time is a good idea.
690		715
…		…
692		717
693	=item ev_suspend (loop)	718	=item ev_suspend (loop)
694		719
695	=item ev_resume (loop)	720	=item ev_resume (loop)
696		721
697	These two functions suspend and resume a loop, for use when the loop is	722	These two functions suspend and resume an event loop, for use when the
698	not used for a while and timeouts should not be processed.	723	loop is not used for a while and timeouts should not be processed.
699		724
700	A typical use case would be an interactive program such as a game: When	725	A typical use case would be an interactive program such as a game: When
701	the user presses C<^Z> to suspend the game and resumes it an hour later it	726	the user presses C<^Z> to suspend the game and resumes it an hour later it
702	would be best to handle timeouts as if no time had actually passed while	727	would be best to handle timeouts as if no time had actually passed while
703	the program was suspended. This can be achieved by calling C<ev_suspend>	728	the program was suspended. This can be achieved by calling C<ev_suspend>
…		…
714	without a previous call to C<ev_suspend>.	739	without a previous call to C<ev_suspend>.
715		740
716	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the	741	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
717	event loop time (see C<ev_now_update>).	742	event loop time (see C<ev_now_update>).
718		743
719	=item ev_loop (loop, int flags)	744	=item ev_run (loop, int flags)
720		745
721	Finally, this is it, the event handler. This function usually is called	746	Finally, this is it, the event handler. This function usually is called
722	after you have initialised all your watchers and you want to start	747	after you have initialised all your watchers and you want to start
723	handling events.	748	handling events. It will ask the operating system for any new events, call
		749	the watcher callbacks, an then repeat the whole process indefinitely: This
		750	is why event loops are called I<loops>.
724		751
725	If the flags argument is specified as C<0>, it will not return until	752	If the flags argument is specified as C<0>, it will keep handling events
726	either no event watchers are active anymore or C<ev_unloop> was called.	753	until either no event watchers are active anymore or C<ev_break> was
		754	called.
727		755
728	Please note that an explicit C<ev_unloop> is usually better than	756	Please note that an explicit C<ev_break> is usually better than
729	relying on all watchers to be stopped when deciding when a program has	757	relying on all watchers to be stopped when deciding when a program has
730	finished (especially in interactive programs), but having a program	758	finished (especially in interactive programs), but having a program
731	that automatically loops as long as it has to and no longer by virtue	759	that automatically loops as long as it has to and no longer by virtue
732	of relying on its watchers stopping correctly, that is truly a thing of	760	of relying on its watchers stopping correctly, that is truly a thing of
733	beauty.	761	beauty.
734		762
		763	This function is also I<mostly> exception-safe - you can break out of
		764	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
		765	exception and so on. This does not decrement the C<ev_depth> value, nor
		766	will it clear any outstanding C<EVBREAK_ONE> breaks.
		767
735	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	768	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
736	those events and any already outstanding ones, but will not block your	769	those events and any already outstanding ones, but will not wait and
737	process in case there are no events and will return after one iteration of	770	block your process in case there are no events and will return after one
738	the loop.	771	iteration of the loop. This is sometimes useful to poll and handle new
		772	events while doing lengthy calculations, to keep the program responsive.
739		773
740	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	774	A flags value of C<EVRUN_ONCE> will look for new events (waiting if
741	necessary) and will handle those and any already outstanding ones. It	775	necessary) and will handle those and any already outstanding ones. It
742	will block your process until at least one new event arrives (which could	776	will block your process until at least one new event arrives (which could
743	be an event internal to libev itself, so there is no guarantee that a	777	be an event internal to libev itself, so there is no guarantee that a
744	user-registered callback will be called), and will return after one	778	user-registered callback will be called), and will return after one
745	iteration of the loop.	779	iteration of the loop.
746		780
747	This is useful if you are waiting for some external event in conjunction	781	This is useful if you are waiting for some external event in conjunction
748	with something not expressible using other libev watchers (i.e. "roll your	782	with something not expressible using other libev watchers (i.e. "roll your
749	own C<ev_loop>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is	783	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
750	usually a better approach for this kind of thing.	784	usually a better approach for this kind of thing.
751		785
752	Here are the gory details of what C<ev_loop> does:	786	Here are the gory details of what C<ev_run> does:
753		787
		788	- Increment loop depth.
		789	- Reset the ev_break status.
754	- Before the first iteration, call any pending watchers.	790	- Before the first iteration, call any pending watchers.
		791	LOOP:
755	* If EVFLAG_FORKCHECK was used, check for a fork.	792	- If EVFLAG_FORKCHECK was used, check for a fork.
756	- If a fork was detected (by any means), queue and call all fork watchers.	793	- If a fork was detected (by any means), queue and call all fork watchers.
757	- Queue and call all prepare watchers.	794	- Queue and call all prepare watchers.
		795	- If ev_break was called, goto FINISH.
758	- If we have been forked, detach and recreate the kernel state	796	- If we have been forked, detach and recreate the kernel state
759	as to not disturb the other process.	797	as to not disturb the other process.
760	- Update the kernel state with all outstanding changes.	798	- Update the kernel state with all outstanding changes.
761	- Update the "event loop time" (ev_now ()).	799	- Update the "event loop time" (ev_now ()).
762	- Calculate for how long to sleep or block, if at all	800	- Calculate for how long to sleep or block, if at all
763	(active idle watchers, EVLOOP_NONBLOCK or not having	801	(active idle watchers, EVRUN_NOWAIT or not having
764	any active watchers at all will result in not sleeping).	802	any active watchers at all will result in not sleeping).
765	- Sleep if the I/O and timer collect interval say so.	803	- Sleep if the I/O and timer collect interval say so.
		804	- Increment loop iteration counter.
766	- Block the process, waiting for any events.	805	- Block the process, waiting for any events.
767	- Queue all outstanding I/O (fd) events.	806	- Queue all outstanding I/O (fd) events.
768	- Update the "event loop time" (ev_now ()), and do time jump adjustments.	807	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
769	- Queue all expired timers.	808	- Queue all expired timers.
770	- Queue all expired periodics.	809	- Queue all expired periodics.
771	- Unless any events are pending now, queue all idle watchers.	810	- Queue all idle watchers with priority higher than that of pending events.
772	- Queue all check watchers.	811	- Queue all check watchers.
773	- Call all queued watchers in reverse order (i.e. check watchers first).	812	- Call all queued watchers in reverse order (i.e. check watchers first).
774	Signals and child watchers are implemented as I/O watchers, and will	813	Signals and child watchers are implemented as I/O watchers, and will
775	be handled here by queueing them when their watcher gets executed.	814	be handled here by queueing them when their watcher gets executed.
776	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	815	- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT
777	were used, or there are no active watchers, return, otherwise	816	were used, or there are no active watchers, goto FINISH, otherwise
778	continue with step *.	817	continue with step LOOP.
		818	FINISH:
		819	- Reset the ev_break status iff it was EVBREAK_ONE.
		820	- Decrement the loop depth.
		821	- Return.
779		822
780	Example: Queue some jobs and then loop until no events are outstanding	823	Example: Queue some jobs and then loop until no events are outstanding
781	anymore.	824	anymore.
782		825
783	... queue jobs here, make sure they register event watchers as long	826	... queue jobs here, make sure they register event watchers as long
784	... as they still have work to do (even an idle watcher will do..)	827	... as they still have work to do (even an idle watcher will do..)
785	ev_loop (my_loop, 0);	828	ev_run (my_loop, 0);
786	... jobs done or somebody called unloop. yeah!	829	... jobs done or somebody called unloop. yeah!
787		830
788	=item ev_unloop (loop, how)	831	=item ev_break (loop, how)
789		832
790	Can be used to make a call to C<ev_loop> return early (but only after it	833	Can be used to make a call to C<ev_run> return early (but only after it
791	has processed all outstanding events). The C<how> argument must be either	834	has processed all outstanding events). The C<how> argument must be either
792	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	835	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
793	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	836	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
794		837
795	This "unloop state" will be cleared when entering C<ev_loop> again.	838	This "break state" will be cleared on the next call to C<ev_run>.
796		839
797	It is safe to call C<ev_unloop> from outside any C<ev_loop> calls.	840	It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in
		841	which case it will have no effect.
798		842
799	=item ev_ref (loop)	843	=item ev_ref (loop)
800		844
801	=item ev_unref (loop)	845	=item ev_unref (loop)
802		846
803	Ref/unref can be used to add or remove a reference count on the event	847	Ref/unref can be used to add or remove a reference count on the event
804	loop: Every watcher keeps one reference, and as long as the reference	848	loop: Every watcher keeps one reference, and as long as the reference
805	count is nonzero, C<ev_loop> will not return on its own.	849	count is nonzero, C<ev_run> will not return on its own.
806		850
807	This is useful when you have a watcher that you never intend to	851	This is useful when you have a watcher that you never intend to
808	unregister, but that nevertheless should not keep C<ev_loop> from	852	unregister, but that nevertheless should not keep C<ev_run> from
809	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>	853	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
810	before stopping it.	854	before stopping it.
811		855
812	As an example, libev itself uses this for its internal signal pipe: It	856	As an example, libev itself uses this for its internal signal pipe: It
813	is not visible to the libev user and should not keep C<ev_loop> from	857	is not visible to the libev user and should not keep C<ev_run> from
814	exiting if no event watchers registered by it are active. It is also an	858	exiting if no event watchers registered by it are active. It is also an
815	excellent way to do this for generic recurring timers or from within	859	excellent way to do this for generic recurring timers or from within
816	third-party libraries. Just remember to I<unref after start> and I<ref	860	third-party libraries. Just remember to I<unref after start> and I<ref
817	before stop> (but only if the watcher wasn't active before, or was active	861	before stop> (but only if the watcher wasn't active before, or was active
818	before, respectively. Note also that libev might stop watchers itself	862	before, respectively. Note also that libev might stop watchers itself
819	(e.g. non-repeating timers) in which case you have to C<ev_ref>	863	(e.g. non-repeating timers) in which case you have to C<ev_ref>
820	in the callback).	864	in the callback).
821		865
822	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	866	Example: Create a signal watcher, but keep it from keeping C<ev_run>
823	running when nothing else is active.	867	running when nothing else is active.
824		868
825	ev_signal exitsig;	869	ev_signal exitsig;
826	ev_signal_init (&exitsig, sig_cb, SIGINT);	870	ev_signal_init (&exitsig, sig_cb, SIGINT);
827	ev_signal_start (loop, &exitsig);	871	ev_signal_start (loop, &exitsig);
…		…
890	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);	934	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
891		935
892	=item ev_invoke_pending (loop)	936	=item ev_invoke_pending (loop)
893		937
894	This call will simply invoke all pending watchers while resetting their	938	This call will simply invoke all pending watchers while resetting their
895	pending state. Normally, C<ev_loop> does this automatically when required,	939	pending state. Normally, C<ev_run> does this automatically when required,
896	but when overriding the invoke callback this call comes handy.	940	but when overriding the invoke callback this call comes handy. This
		941	function can be invoked from a watcher - this can be useful for example
		942	when you want to do some lengthy calculation and want to pass further
		943	event handling to another thread (you still have to make sure only one
		944	thread executes within C<ev_invoke_pending> or C<ev_run> of course).
897		945
898	=item int ev_pending_count (loop)	946	=item int ev_pending_count (loop)
899		947
900	Returns the number of pending watchers - zero indicates that no watchers	948	Returns the number of pending watchers - zero indicates that no watchers
901	are pending.	949	are pending.
902		950
903	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))	951	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
904		952
905	This overrides the invoke pending functionality of the loop: Instead of	953	This overrides the invoke pending functionality of the loop: Instead of
906	invoking all pending watchers when there are any, C<ev_loop> will call	954	invoking all pending watchers when there are any, C<ev_run> will call
907	this callback instead. This is useful, for example, when you want to	955	this callback instead. This is useful, for example, when you want to
908	invoke the actual watchers inside another context (another thread etc.).	956	invoke the actual watchers inside another context (another thread etc.).
909		957
910	If you want to reset the callback, use C<ev_invoke_pending> as new	958	If you want to reset the callback, use C<ev_invoke_pending> as new
911	callback.	959	callback.
…		…
914		962
915	Sometimes you want to share the same loop between multiple threads. This	963	Sometimes you want to share the same loop between multiple threads. This
916	can be done relatively simply by putting mutex_lock/unlock calls around	964	can be done relatively simply by putting mutex_lock/unlock calls around
917	each call to a libev function.	965	each call to a libev function.
918		966
919	However, C<ev_loop> can run an indefinite time, so it is not feasible to	967	However, C<ev_run> can run an indefinite time, so it is not feasible
920	wait for it to return. One way around this is to wake up the loop via	968	to wait for it to return. One way around this is to wake up the event
921	C<ev_unloop> and C<av_async_send>, another way is to set these I<release>	969	loop via C<ev_break> and C<av_async_send>, another way is to set these
922	and I<acquire> callbacks on the loop.	970	I<release> and I<acquire> callbacks on the loop.
923		971
924	When set, then C<release> will be called just before the thread is	972	When set, then C<release> will be called just before the thread is
925	suspended waiting for new events, and C<acquire> is called just	973	suspended waiting for new events, and C<acquire> is called just
926	afterwards.	974	afterwards.
927		975
…		…
930		978
931	While event loop modifications are allowed between invocations of	979	While event loop modifications are allowed between invocations of
932	C<release> and C<acquire> (that's their only purpose after all), no	980	C<release> and C<acquire> (that's their only purpose after all), no
933	modifications done will affect the event loop, i.e. adding watchers will	981	modifications done will affect the event loop, i.e. adding watchers will
934	have no effect on the set of file descriptors being watched, or the time	982	have no effect on the set of file descriptors being watched, or the time
935	waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it	983	waited. Use an C<ev_async> watcher to wake up C<ev_run> when you want it
936	to take note of any changes you made.	984	to take note of any changes you made.
937		985
938	In theory, threads executing C<ev_loop> will be async-cancel safe between	986	In theory, threads executing C<ev_run> will be async-cancel safe between
939	invocations of C<release> and C<acquire>.	987	invocations of C<release> and C<acquire>.
940		988
941	See also the locking example in the C<THREADS> section later in this	989	See also the locking example in the C<THREADS> section later in this
942	document.	990	document.
943		991
…		…
945		993
946	=item ev_userdata (loop)	994	=item ev_userdata (loop)
947		995
948	Set and retrieve a single C<void *> associated with a loop. When	996	Set and retrieve a single C<void *> associated with a loop. When
949	C<ev_set_userdata> has never been called, then C<ev_userdata> returns	997	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
950	C<0.>	998	C<0>.
951		999
952	These two functions can be used to associate arbitrary data with a loop,	1000	These two functions can be used to associate arbitrary data with a loop,
953	and are intended solely for the C<invoke_pending_cb>, C<release> and	1001	and are intended solely for the C<invoke_pending_cb>, C<release> and
954	C<acquire> callbacks described above, but of course can be (ab-)used for	1002	C<acquire> callbacks described above, but of course can be (ab-)used for
955	any other purpose as well.	1003	any other purpose as well.
956		1004
957	=item ev_loop_verify (loop)	1005	=item ev_verify (loop)
958		1006
959	This function only does something when C<EV_VERIFY> support has been	1007	This function only does something when C<EV_VERIFY> support has been
960	compiled in, which is the default for non-minimal builds. It tries to go	1008	compiled in, which is the default for non-minimal builds. It tries to go
961	through all internal structures and checks them for validity. If anything	1009	through all internal structures and checks them for validity. If anything
962	is found to be inconsistent, it will print an error message to standard	1010	is found to be inconsistent, it will print an error message to standard
…		…
973		1021
974	In the following description, uppercase C<TYPE> in names stands for the	1022	In the following description, uppercase C<TYPE> in names stands for the
975	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer	1023	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
976	watchers and C<ev_io_start> for I/O watchers.	1024	watchers and C<ev_io_start> for I/O watchers.
977		1025
978	A watcher is a structure that you create and register to record your	1026	A watcher is an opaque structure that you allocate and register to record
979	interest in some event. For instance, if you want to wait for STDIN to	1027	your interest in some event. To make a concrete example, imagine you want
980	become readable, you would create an C<ev_io> watcher for that:	1028	to wait for STDIN to become readable, you would create an C<ev_io> watcher
		1029	for that:
981		1030
982	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)	1031	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
983	{	1032	{
984	ev_io_stop (w);	1033	ev_io_stop (w);
985	ev_unloop (loop, EVUNLOOP_ALL);	1034	ev_break (loop, EVBREAK_ALL);
986	}	1035	}
987		1036
988	struct ev_loop *loop = ev_default_loop (0);	1037	struct ev_loop *loop = ev_default_loop (0);
989		1038
990	ev_io stdin_watcher;	1039	ev_io stdin_watcher;
991		1040
992	ev_init (&stdin_watcher, my_cb);	1041	ev_init (&stdin_watcher, my_cb);
993	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	1042	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
994	ev_io_start (loop, &stdin_watcher);	1043	ev_io_start (loop, &stdin_watcher);
995		1044
996	ev_loop (loop, 0);	1045	ev_run (loop, 0);
997		1046
998	As you can see, you are responsible for allocating the memory for your	1047	As you can see, you are responsible for allocating the memory for your
999	watcher structures (and it is I<usually> a bad idea to do this on the	1048	watcher structures (and it is I<usually> a bad idea to do this on the
1000	stack).	1049	stack).
1001		1050
1002	Each watcher has an associated watcher structure (called C<struct ev_TYPE>	1051	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
1003	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).	1052	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
1004		1053
1005	Each watcher structure must be initialised by a call to C<ev_init	1054	Each watcher structure must be initialised by a call to C<ev_init (watcher
1006	(watcher *, callback)>, which expects a callback to be provided. This	1055	*, callback)>, which expects a callback to be provided. This callback is
1007	callback gets invoked each time the event occurs (or, in the case of I/O	1056	invoked each time the event occurs (or, in the case of I/O watchers, each
1008	watchers, each time the event loop detects that the file descriptor given	1057	time the event loop detects that the file descriptor given is readable
1009	is readable and/or writable).	1058	and/or writable).
1010		1059
1011	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>	1060	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
1012	macro to configure it, with arguments specific to the watcher type. There	1061	macro to configure it, with arguments specific to the watcher type. There
1013	is also a macro to combine initialisation and setting in one call: C<<	1062	is also a macro to combine initialisation and setting in one call: C<<
1014	ev_TYPE_init (watcher *, callback, ...) >>.	1063	ev_TYPE_init (watcher *, callback, ...) >>.
…		…
1065		1114
1066	=item C<EV_PREPARE>	1115	=item C<EV_PREPARE>
1067		1116
1068	=item C<EV_CHECK>	1117	=item C<EV_CHECK>
1069		1118
1070	All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts	1119	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts
1071	to gather new events, and all C<ev_check> watchers are invoked just after	1120	to gather new events, and all C<ev_check> watchers are invoked just after
1072	C<ev_loop> has gathered them, but before it invokes any callbacks for any	1121	C<ev_run> has gathered them, but before it invokes any callbacks for any
1073	received events. Callbacks of both watcher types can start and stop as	1122	received events. Callbacks of both watcher types can start and stop as
1074	many watchers as they want, and all of them will be taken into account	1123	many watchers as they want, and all of them will be taken into account
1075	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	1124	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
1076	C<ev_loop> from blocking).	1125	C<ev_run> from blocking).
1077		1126
1078	=item C<EV_EMBED>	1127	=item C<EV_EMBED>
1079		1128
1080	The embedded event loop specified in the C<ev_embed> watcher needs attention.	1129	The embedded event loop specified in the C<ev_embed> watcher needs attention.
1081		1130
1082	=item C<EV_FORK>	1131	=item C<EV_FORK>
1083		1132
1084	The event loop has been resumed in the child process after fork (see	1133	The event loop has been resumed in the child process after fork (see
1085	C<ev_fork>).	1134	C<ev_fork>).
		1135
		1136	=item C<EV_CLEANUP>
		1137
		1138	The event loop is about to be destroyed (see C<ev_cleanup>).
1086		1139
1087	=item C<EV_ASYNC>	1140	=item C<EV_ASYNC>
1088		1141
1089	The given async watcher has been asynchronously notified (see C<ev_async>).	1142	The given async watcher has been asynchronously notified (see C<ev_async>).
1090		1143
…		…
1262		1315
1263	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related	1316	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
1264	functions that do not need a watcher.	1317	functions that do not need a watcher.
1265		1318
1266	=back	1319	=back
1267
1268		1320
1269	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1321	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
1270		1322
1271	Each watcher has, by default, a member C<void *data> that you can change	1323	Each watcher has, by default, a member C<void *data> that you can change
1272	and read at any time: libev will completely ignore it. This can be used	1324	and read at any time: libev will completely ignore it. This can be used
…		…
1328	t2_cb (EV_P_ ev_timer *w, int revents)	1380	t2_cb (EV_P_ ev_timer *w, int revents)
1329	{	1381	{
1330	struct my_biggy big = (struct my_biggy *)	1382	struct my_biggy big = (struct my_biggy *)
1331	(((char *)w) - offsetof (struct my_biggy, t2));	1383	(((char *)w) - offsetof (struct my_biggy, t2));
1332	}	1384	}
		1385
		1386	=head2 WATCHER STATES
		1387
		1388	There are various watcher states mentioned throughout this manual -
		1389	active, pending and so on. In this section these states and the rules to
		1390	transition between them will be described in more detail - and while these
		1391	rules might look complicated, they usually do "the right thing".
		1392
		1393	=over 4
		1394
		1395	=item initialiased
		1396
		1397	Before a watcher can be registered with the event looop it has to be
		1398	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
		1399	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
		1400
		1401	In this state it is simply some block of memory that is suitable for use
		1402	in an event loop. It can be moved around, freed, reused etc. at will.
		1403
		1404	=item started/running/active
		1405
		1406	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
		1407	property of the event loop, and is actively waiting for events. While in
		1408	this state it cannot be accessed (except in a few documented ways), moved,
		1409	freed or anything else - the only legal thing is to keep a pointer to it,
		1410	and call libev functions on it that are documented to work on active watchers.
		1411
		1412	=item pending
		1413
		1414	If a watcher is active and libev determines that an event it is interested
		1415	in has occurred (such as a timer expiring), it will become pending. It will
		1416	stay in this pending state until either it is stopped or its callback is
		1417	about to be invoked, so it is not normally pending inside the watcher
		1418	callback.
		1419
		1420	The watcher might or might not be active while it is pending (for example,
		1421	an expired non-repeating timer can be pending but no longer active). If it
		1422	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
		1423	but it is still property of the event loop at this time, so cannot be
		1424	moved, freed or reused. And if it is active the rules described in the
		1425	previous item still apply.
		1426
		1427	It is also possible to feed an event on a watcher that is not active (e.g.
		1428	via C<ev_feed_event>), in which case it becomes pending without being
		1429	active.
		1430
		1431	=item stopped
		1432
		1433	A watcher can be stopped implicitly by libev (in which case it might still
		1434	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
		1435	latter will clear any pending state the watcher might be in, regardless
		1436	of whether it was active or not, so stopping a watcher explicitly before
		1437	freeing it is often a good idea.
		1438
		1439	While stopped (and not pending) the watcher is essentially in the
		1440	initialised state, that is it can be reused, moved, modified in any way
		1441	you wish.
		1442
		1443	=back
1333		1444
1334	=head2 WATCHER PRIORITY MODELS	1445	=head2 WATCHER PRIORITY MODELS
1335		1446
1336	Many event loops support I<watcher priorities>, which are usually small	1447	Many event loops support I<watcher priorities>, which are usually small
1337	integers that influence the ordering of event callback invocation	1448	integers that influence the ordering of event callback invocation
…		…
1622	...	1733	...
1623	struct ev_loop *loop = ev_default_init (0);	1734	struct ev_loop *loop = ev_default_init (0);
1624	ev_io stdin_readable;	1735	ev_io stdin_readable;
1625	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1736	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1626	ev_io_start (loop, &stdin_readable);	1737	ev_io_start (loop, &stdin_readable);
1627	ev_loop (loop, 0);	1738	ev_run (loop, 0);
1628		1739
1629		1740
1630	=head2 C<ev_timer> - relative and optionally repeating timeouts	1741	=head2 C<ev_timer> - relative and optionally repeating timeouts
1631		1742
1632	Timer watchers are simple relative timers that generate an event after a	1743	Timer watchers are simple relative timers that generate an event after a
…		…
1641	The callback is guaranteed to be invoked only I<after> its timeout has	1752	The callback is guaranteed to be invoked only I<after> its timeout has
1642	passed (not I<at>, so on systems with very low-resolution clocks this	1753	passed (not I<at>, so on systems with very low-resolution clocks this
1643	might introduce a small delay). If multiple timers become ready during the	1754	might introduce a small delay). If multiple timers become ready during the
1644	same loop iteration then the ones with earlier time-out values are invoked	1755	same loop iteration then the ones with earlier time-out values are invoked
1645	before ones of the same priority with later time-out values (but this is	1756	before ones of the same priority with later time-out values (but this is
1646	no longer true when a callback calls C<ev_loop> recursively).	1757	no longer true when a callback calls C<ev_run> recursively).
1647		1758
1648	=head3 Be smart about timeouts	1759	=head3 Be smart about timeouts
1649		1760
1650	Many real-world problems involve some kind of timeout, usually for error	1761	Many real-world problems involve some kind of timeout, usually for error
1651	recovery. A typical example is an HTTP request - if the other side hangs,	1762	recovery. A typical example is an HTTP request - if the other side hangs,
…		…
1822		1933
1823	=head3 The special problem of time updates	1934	=head3 The special problem of time updates
1824		1935
1825	Establishing the current time is a costly operation (it usually takes at	1936	Establishing the current time is a costly operation (it usually takes at
1826	least two system calls): EV therefore updates its idea of the current	1937	least two system calls): EV therefore updates its idea of the current
1827	time only before and after C<ev_loop> collects new events, which causes a	1938	time only before and after C<ev_run> collects new events, which causes a
1828	growing difference between C<ev_now ()> and C<ev_time ()> when handling	1939	growing difference between C<ev_now ()> and C<ev_time ()> when handling
1829	lots of events in one iteration.	1940	lots of events in one iteration.
1830		1941
1831	The relative timeouts are calculated relative to the C<ev_now ()>	1942	The relative timeouts are calculated relative to the C<ev_now ()>
1832	time. This is usually the right thing as this timestamp refers to the time	1943	time. This is usually the right thing as this timestamp refers to the time
…		…
1949	}	2060	}
1950		2061
1951	ev_timer mytimer;	2062	ev_timer mytimer;
1952	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	2063	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1953	ev_timer_again (&mytimer); /* start timer */	2064	ev_timer_again (&mytimer); /* start timer */
1954	ev_loop (loop, 0);	2065	ev_run (loop, 0);
1955		2066
1956	// and in some piece of code that gets executed on any "activity":	2067	// and in some piece of code that gets executed on any "activity":
1957	// reset the timeout to start ticking again at 10 seconds	2068	// reset the timeout to start ticking again at 10 seconds
1958	ev_timer_again (&mytimer);	2069	ev_timer_again (&mytimer);
1959		2070
…		…
1985		2096
1986	As with timers, the callback is guaranteed to be invoked only when the	2097	As with timers, the callback is guaranteed to be invoked only when the
1987	point in time where it is supposed to trigger has passed. If multiple	2098	point in time where it is supposed to trigger has passed. If multiple
1988	timers become ready during the same loop iteration then the ones with	2099	timers become ready during the same loop iteration then the ones with
1989	earlier time-out values are invoked before ones with later time-out values	2100	earlier time-out values are invoked before ones with later time-out values
1990	(but this is no longer true when a callback calls C<ev_loop> recursively).	2101	(but this is no longer true when a callback calls C<ev_run> recursively).
1991		2102
1992	=head3 Watcher-Specific Functions and Data Members	2103	=head3 Watcher-Specific Functions and Data Members
1993		2104
1994	=over 4	2105	=over 4
1995		2106
…		…
2123	Example: Call a callback every hour, or, more precisely, whenever the	2234	Example: Call a callback every hour, or, more precisely, whenever the
2124	system time is divisible by 3600. The callback invocation times have	2235	system time is divisible by 3600. The callback invocation times have
2125	potentially a lot of jitter, but good long-term stability.	2236	potentially a lot of jitter, but good long-term stability.
2126		2237
2127	static void	2238	static void
2128	clock_cb (struct ev_loop *loop, ev_io *w, int revents)	2239	clock_cb (struct ev_loop *loop, ev_periodic *w, int revents)
2129	{	2240	{
2130	... its now a full hour (UTC, or TAI or whatever your clock follows)	2241	... its now a full hour (UTC, or TAI or whatever your clock follows)
2131	}	2242	}
2132		2243
2133	ev_periodic hourly_tick;	2244	ev_periodic hourly_tick;
…		…
2156		2267
2157	=head2 C<ev_signal> - signal me when a signal gets signalled!	2268	=head2 C<ev_signal> - signal me when a signal gets signalled!
2158		2269
2159	Signal watchers will trigger an event when the process receives a specific	2270	Signal watchers will trigger an event when the process receives a specific
2160	signal one or more times. Even though signals are very asynchronous, libev	2271	signal one or more times. Even though signals are very asynchronous, libev
2161	will try it's best to deliver signals synchronously, i.e. as part of the	2272	will try its best to deliver signals synchronously, i.e. as part of the
2162	normal event processing, like any other event.	2273	normal event processing, like any other event.
2163		2274
2164	If you want signals to be delivered truly asynchronously, just use	2275	If you want signals to be delivered truly asynchronously, just use
2165	C<sigaction> as you would do without libev and forget about sharing	2276	C<sigaction> as you would do without libev and forget about sharing
2166	the signal. You can even use C<ev_async> from a signal handler to	2277	the signal. You can even use C<ev_async> from a signal handler to
…		…
2233	Example: Try to exit cleanly on SIGINT.	2344	Example: Try to exit cleanly on SIGINT.
2234		2345
2235	static void	2346	static void
2236	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)	2347	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
2237	{	2348	{
2238	ev_unloop (loop, EVUNLOOP_ALL);	2349	ev_break (loop, EVBREAK_ALL);
2239	}	2350	}
2240		2351
2241	ev_signal signal_watcher;	2352	ev_signal signal_watcher;
2242	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2353	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
2243	ev_signal_start (loop, &signal_watcher);	2354	ev_signal_start (loop, &signal_watcher);
…		…
2629		2740
2630	Prepare and check watchers are usually (but not always) used in pairs:	2741	Prepare and check watchers are usually (but not always) used in pairs:
2631	prepare watchers get invoked before the process blocks and check watchers	2742	prepare watchers get invoked before the process blocks and check watchers
2632	afterwards.	2743	afterwards.
2633		2744
2634	You I<must not> call C<ev_loop> or similar functions that enter	2745	You I<must not> call C<ev_run> or similar functions that enter
2635	the current event loop from either C<ev_prepare> or C<ev_check>	2746	the current event loop from either C<ev_prepare> or C<ev_check>
2636	watchers. Other loops than the current one are fine, however. The	2747	watchers. Other loops than the current one are fine, however. The
2637	rationale behind this is that you do not need to check for recursion in	2748	rationale behind this is that you do not need to check for recursion in
2638	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2749	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
2639	C<ev_check> so if you have one watcher of each kind they will always be	2750	C<ev_check> so if you have one watcher of each kind they will always be
…		…
2807		2918
2808	if (timeout >= 0)	2919	if (timeout >= 0)
2809	// create/start timer	2920	// create/start timer
2810		2921
2811	// poll	2922	// poll
2812	ev_loop (EV_A_ 0);	2923	ev_run (EV_A_ 0);
2813		2924
2814	// stop timer again	2925	// stop timer again
2815	if (timeout >= 0)	2926	if (timeout >= 0)
2816	ev_timer_stop (EV_A_ &to);	2927	ev_timer_stop (EV_A_ &to);
2817		2928
…		…
2895	if you do not want that, you need to temporarily stop the embed watcher).	3006	if you do not want that, you need to temporarily stop the embed watcher).
2896		3007
2897	=item ev_embed_sweep (loop, ev_embed *)	3008	=item ev_embed_sweep (loop, ev_embed *)
2898		3009
2899	Make a single, non-blocking sweep over the embedded loop. This works	3010	Make a single, non-blocking sweep over the embedded loop. This works
2900	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most	3011	similarly to C<ev_run (embedded_loop, EVRUN_NOWAIT)>, but in the most
2901	appropriate way for embedded loops.	3012	appropriate way for embedded loops.
2902		3013
2903	=item struct ev_loop *other [read-only]	3014	=item struct ev_loop *other [read-only]
2904		3015
2905	The embedded event loop.	3016	The embedded event loop.
…		…
2965	C<ev_default_fork> cheats and calls it in the wrong process, the fork	3076	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2966	handlers will be invoked, too, of course.	3077	handlers will be invoked, too, of course.
2967		3078
2968	=head3 The special problem of life after fork - how is it possible?	3079	=head3 The special problem of life after fork - how is it possible?
2969		3080
2970	Most uses of C<fork()> consist of forking, then some simple calls to ste	3081	Most uses of C<fork()> consist of forking, then some simple calls to set
2971	up/change the process environment, followed by a call to C<exec()>. This	3082	up/change the process environment, followed by a call to C<exec()>. This
2972	sequence should be handled by libev without any problems.	3083	sequence should be handled by libev without any problems.
2973		3084
2974	This changes when the application actually wants to do event handling	3085	This changes when the application actually wants to do event handling
2975	in the child, or both parent in child, in effect "continuing" after the	3086	in the child, or both parent in child, in effect "continuing" after the
…		…
2991	disadvantage of having to use multiple event loops (which do not support	3102	disadvantage of having to use multiple event loops (which do not support
2992	signal watchers).	3103	signal watchers).
2993		3104
2994	When this is not possible, or you want to use the default loop for	3105	When this is not possible, or you want to use the default loop for
2995	other reasons, then in the process that wants to start "fresh", call	3106	other reasons, then in the process that wants to start "fresh", call
2996	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying	3107	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
2997	the default loop will "orphan" (not stop) all registered watchers, so you	3108	Destroying the default loop will "orphan" (not stop) all registered
2998	have to be careful not to execute code that modifies those watchers. Note	3109	watchers, so you have to be careful not to execute code that modifies
2999	also that in that case, you have to re-register any signal watchers.	3110	those watchers. Note also that in that case, you have to re-register any
		3111	signal watchers.
3000		3112
3001	=head3 Watcher-Specific Functions and Data Members	3113	=head3 Watcher-Specific Functions and Data Members
3002		3114
3003	=over 4	3115	=over 4
3004		3116
3005	=item ev_fork_init (ev_signal *, callback)	3117	=item ev_fork_init (ev_fork *, callback)
3006		3118
3007	Initialises and configures the fork watcher - it has no parameters of any	3119	Initialises and configures the fork watcher - it has no parameters of any
3008	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3120	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
3009	believe me.	3121	really.
3010		3122
3011	=back	3123	=back
3012		3124
3013		3125
		3126	=head2 C<ev_cleanup> - even the best things end
		3127
		3128	Cleanup watchers are called just before the event loop is being destroyed
		3129	by a call to C<ev_loop_destroy>.
		3130
		3131	While there is no guarantee that the event loop gets destroyed, cleanup
		3132	watchers provide a convenient method to install cleanup hooks for your
		3133	program, worker threads and so on - you just to make sure to destroy the
		3134	loop when you want them to be invoked.
		3135
		3136	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3137	all other watchers, they do not keep a reference to the event loop (which
		3138	makes a lot of sense if you think about it). Like all other watchers, you
		3139	can call libev functions in the callback, except C<ev_cleanup_start>.
		3140
		3141	=head3 Watcher-Specific Functions and Data Members
		3142
		3143	=over 4
		3144
		3145	=item ev_cleanup_init (ev_cleanup *, callback)
		3146
		3147	Initialises and configures the cleanup watcher - it has no parameters of
		3148	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3149	pointless, I assure you.
		3150
		3151	=back
		3152
		3153	Example: Register an atexit handler to destroy the default loop, so any
		3154	cleanup functions are called.
		3155
		3156	static void
		3157	program_exits (void)
		3158	{
		3159	ev_loop_destroy (EV_DEFAULT_UC);
		3160	}
		3161
		3162	...
		3163	atexit (program_exits);
		3164
		3165
3014	=head2 C<ev_async> - how to wake up another event loop	3166	=head2 C<ev_async> - how to wake up an event loop
3015		3167
3016	In general, you cannot use an C<ev_loop> from multiple threads or other	3168	In general, you cannot use an C<ev_run> from multiple threads or other
3017	asynchronous sources such as signal handlers (as opposed to multiple event	3169	asynchronous sources such as signal handlers (as opposed to multiple event
3018	loops - those are of course safe to use in different threads).	3170	loops - those are of course safe to use in different threads).
3019		3171
3020	Sometimes, however, you need to wake up another event loop you do not	3172	Sometimes, however, you need to wake up an event loop you do not control,
3021	control, for example because it belongs to another thread. This is what	3173	for example because it belongs to another thread. This is what C<ev_async>
3022	C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you	3174	watchers do: as long as the C<ev_async> watcher is active, you can signal
3023	can signal it by calling C<ev_async_send>, which is thread- and signal	3175	it by calling C<ev_async_send>, which is thread- and signal safe.
3024	safe.
3025		3176
3026	This functionality is very similar to C<ev_signal> watchers, as signals,	3177	This functionality is very similar to C<ev_signal> watchers, as signals,
3027	too, are asynchronous in nature, and signals, too, will be compressed	3178	too, are asynchronous in nature, and signals, too, will be compressed
3028	(i.e. the number of callback invocations may be less than the number of	3179	(i.e. the number of callback invocations may be less than the number of
3029	C<ev_async_sent> calls).	3180	C<ev_async_sent> calls).
…		…
3237	=item * Priorities are not currently supported. Initialising priorities	3388	=item * Priorities are not currently supported. Initialising priorities
3238	will fail and all watchers will have the same priority, even though there	3389	will fail and all watchers will have the same priority, even though there
3239	is an ev_pri field.	3390	is an ev_pri field.
3240		3391
3241	=item * In libevent, the last base created gets the signals, in libev, the	3392	=item * In libevent, the last base created gets the signals, in libev, the
3242	first base created (== the default loop) gets the signals.	3393	base that registered the signal gets the signals.
3243		3394
3244	=item * Other members are not supported.	3395	=item * Other members are not supported.
3245		3396
3246	=item * The libev emulation is I<not> ABI compatible to libevent, you need	3397	=item * The libev emulation is I<not> ABI compatible to libevent, you need
3247	to use the libev header file and library.	3398	to use the libev header file and library.
…		…
3390	Associates a different C<struct ev_loop> with this watcher. You can only	3541	Associates a different C<struct ev_loop> with this watcher. You can only
3391	do this when the watcher is inactive (and not pending either).	3542	do this when the watcher is inactive (and not pending either).
3392		3543
3393	=item w->set ([arguments])	3544	=item w->set ([arguments])
3394		3545
3395	Basically the same as C<ev_TYPE_set>, with the same arguments. Must be	3546	Basically the same as C<ev_TYPE_set>, with the same arguments. Either this
3396	called at least once. Unlike the C counterpart, an active watcher gets	3547	method or a suitable start method must be called at least once. Unlike the
3397	automatically stopped and restarted when reconfiguring it with this	3548	C counterpart, an active watcher gets automatically stopped and restarted
3398	method.	3549	when reconfiguring it with this method.
3399		3550
3400	=item w->start ()	3551	=item w->start ()
3401		3552
3402	Starts the watcher. Note that there is no C<loop> argument, as the	3553	Starts the watcher. Note that there is no C<loop> argument, as the
3403	constructor already stores the event loop.	3554	constructor already stores the event loop.
3404		3555
		3556	=item w->start ([arguments])
		3557
		3558	Instead of calling C<set> and C<start> methods separately, it is often
		3559	convenient to wrap them in one call. Uses the same type of arguments as
		3560	the configure C<set> method of the watcher.
		3561
3405	=item w->stop ()	3562	=item w->stop ()
3406		3563
3407	Stops the watcher if it is active. Again, no C<loop> argument.	3564	Stops the watcher if it is active. Again, no C<loop> argument.
3408		3565
3409	=item w->again () (C<ev::timer>, C<ev::periodic> only)	3566	=item w->again () (C<ev::timer>, C<ev::periodic> only)
…		…
3421		3578
3422	=back	3579	=back
3423		3580
3424	=back	3581	=back
3425		3582
3426	Example: Define a class with an IO and idle watcher, start one of them in	3583	Example: Define a class with two I/O and idle watchers, start the I/O
3427	the constructor.	3584	watchers in the constructor.
3428		3585
3429	class myclass	3586	class myclass
3430	{	3587	{
3431	ev::io io ; void io_cb (ev::io &w, int revents);	3588	ev::io io ; void io_cb (ev::io &w, int revents);
		3589	ev::io2 io2 ; void io2_cb (ev::io &w, int revents);
3432	ev::idle idle; void idle_cb (ev::idle &w, int revents);	3590	ev::idle idle; void idle_cb (ev::idle &w, int revents);
3433		3591
3434	myclass (int fd)	3592	myclass (int fd)
3435	{	3593	{
3436	io .set <myclass, &myclass::io_cb > (this);	3594	io .set <myclass, &myclass::io_cb > (this);
		3595	io2 .set <myclass, &myclass::io2_cb > (this);
3437	idle.set <myclass, &myclass::idle_cb> (this);	3596	idle.set <myclass, &myclass::idle_cb> (this);
3438		3597
3439	io.start (fd, ev::READ);	3598	io.set (fd, ev::WRITE); // configure the watcher
		3599	io.start (); // start it whenever convenient
		3600
		3601	io2.start (fd, ev::READ); // set + start in one call
3440	}	3602	}
3441	};	3603	};
3442		3604
3443		3605
3444	=head1 OTHER LANGUAGE BINDINGS	3606	=head1 OTHER LANGUAGE BINDINGS
…		…
3518	loop argument"). The C<EV_A> form is used when this is the sole argument,	3680	loop argument"). The C<EV_A> form is used when this is the sole argument,
3519	C<EV_A_> is used when other arguments are following. Example:	3681	C<EV_A_> is used when other arguments are following. Example:
3520		3682
3521	ev_unref (EV_A);	3683	ev_unref (EV_A);
3522	ev_timer_add (EV_A_ watcher);	3684	ev_timer_add (EV_A_ watcher);
3523	ev_loop (EV_A_ 0);	3685	ev_run (EV_A_ 0);
3524		3686
3525	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,	3687	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
3526	which is often provided by the following macro.	3688	which is often provided by the following macro.
3527		3689
3528	=item C<EV_P>, C<EV_P_>	3690	=item C<EV_P>, C<EV_P_>
…		…
3568	}	3730	}
3569		3731
3570	ev_check check;	3732	ev_check check;
3571	ev_check_init (&check, check_cb);	3733	ev_check_init (&check, check_cb);
3572	ev_check_start (EV_DEFAULT_ &check);	3734	ev_check_start (EV_DEFAULT_ &check);
3573	ev_loop (EV_DEFAULT_ 0);	3735	ev_run (EV_DEFAULT_ 0);
3574		3736
3575	=head1 EMBEDDING	3737	=head1 EMBEDDING
3576		3738
3577	Libev can (and often is) directly embedded into host	3739	Libev can (and often is) directly embedded into host
3578	applications. Examples of applications that embed it include the Deliantra	3740	applications. Examples of applications that embed it include the Deliantra
…		…
3669	to a compiled library. All other symbols change the ABI, which means all	3831	to a compiled library. All other symbols change the ABI, which means all
3670	users of libev and the libev code itself must be compiled with compatible	3832	users of libev and the libev code itself must be compiled with compatible
3671	settings.	3833	settings.
3672		3834
3673	=over 4	3835	=over 4
		3836
		3837	=item EV_COMPAT3 (h)
		3838
		3839	Backwards compatibility is a major concern for libev. This is why this
		3840	release of libev comes with wrappers for the functions and symbols that
		3841	have been renamed between libev version 3 and 4.
		3842
		3843	You can disable these wrappers (to test compatibility with future
		3844	versions) by defining C<EV_COMPAT3> to C<0> when compiling your
		3845	sources. This has the additional advantage that you can drop the C<struct>
		3846	from C<struct ev_loop> declarations, as libev will provide an C<ev_loop>
		3847	typedef in that case.
		3848
		3849	In some future version, the default for C<EV_COMPAT3> will become C<0>,
		3850	and in some even more future version the compatibility code will be
		3851	removed completely.
3674		3852
3675	=item EV_STANDALONE (h)	3853	=item EV_STANDALONE (h)
3676		3854
3677	Must always be C<1> if you do not use autoconf configuration, which	3855	Must always be C<1> if you do not use autoconf configuration, which
3678	keeps libev from including F<config.h>, and it also defines dummy	3856	keeps libev from including F<config.h>, and it also defines dummy
…		…
4028	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it	4206	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
4029	will be C<0>.	4207	will be C<0>.
4030		4208
4031	=item EV_VERIFY	4209	=item EV_VERIFY
4032		4210
4033	Controls how much internal verification (see C<ev_loop_verify ()>) will	4211	Controls how much internal verification (see C<ev_verify ()>) will
4034	be done: If set to C<0>, no internal verification code will be compiled	4212	be done: If set to C<0>, no internal verification code will be compiled
4035	in. If set to C<1>, then verification code will be compiled in, but not	4213	in. If set to C<1>, then verification code will be compiled in, but not
4036	called. If set to C<2>, then the internal verification code will be	4214	called. If set to C<2>, then the internal verification code will be
4037	called once per loop, which can slow down libev. If set to C<3>, then the	4215	called once per loop, which can slow down libev. If set to C<3>, then the
4038	verification code will be called very frequently, which will slow down	4216	verification code will be called very frequently, which will slow down
…		…
4042	will be C<0>.	4220	will be C<0>.
4043		4221
4044	=item EV_COMMON	4222	=item EV_COMMON
4045		4223
4046	By default, all watchers have a C<void *data> member. By redefining	4224	By default, all watchers have a C<void *data> member. By redefining
4047	this macro to a something else you can include more and other types of	4225	this macro to something else you can include more and other types of
4048	members. You have to define it each time you include one of the files,	4226	members. You have to define it each time you include one of the files,
4049	though, and it must be identical each time.	4227	though, and it must be identical each time.
4050		4228
4051	For example, the perl EV module uses something like this:	4229	For example, the perl EV module uses something like this:
4052		4230
…		…
4253	userdata *u = ev_userdata (EV_A);	4431	userdata *u = ev_userdata (EV_A);
4254	pthread_mutex_lock (&u->lock);	4432	pthread_mutex_lock (&u->lock);
4255	}	4433	}
4256		4434
4257	The event loop thread first acquires the mutex, and then jumps straight	4435	The event loop thread first acquires the mutex, and then jumps straight
4258	into C<ev_loop>:	4436	into C<ev_run>:
4259		4437
4260	void *	4438	void *
4261	l_run (void *thr_arg)	4439	l_run (void *thr_arg)
4262	{	4440	{
4263	struct ev_loop *loop = (struct ev_loop *)thr_arg;	4441	struct ev_loop *loop = (struct ev_loop *)thr_arg;
4264		4442
4265	l_acquire (EV_A);	4443	l_acquire (EV_A);
4266	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);	4444	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
4267	ev_loop (EV_A_ 0);	4445	ev_run (EV_A_ 0);
4268	l_release (EV_A);	4446	l_release (EV_A);
4269		4447
4270	return 0;	4448	return 0;
4271	}	4449	}
4272		4450
…		…
4324		4502
4325	=head3 COROUTINES	4503	=head3 COROUTINES
4326		4504
4327	Libev is very accommodating to coroutines ("cooperative threads"):	4505	Libev is very accommodating to coroutines ("cooperative threads"):
4328	libev fully supports nesting calls to its functions from different	4506	libev fully supports nesting calls to its functions from different
4329	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4507	coroutines (e.g. you can call C<ev_run> on the same loop from two
4330	different coroutines, and switch freely between both coroutines running	4508	different coroutines, and switch freely between both coroutines running
4331	the loop, as long as you don't confuse yourself). The only exception is	4509	the loop, as long as you don't confuse yourself). The only exception is
4332	that you must not do this from C<ev_periodic> reschedule callbacks.	4510	that you must not do this from C<ev_periodic> reschedule callbacks.
4333		4511
4334	Care has been taken to ensure that libev does not keep local state inside	4512	Care has been taken to ensure that libev does not keep local state inside
4335	C<ev_loop>, and other calls do not usually allow for coroutine switches as	4513	C<ev_run>, and other calls do not usually allow for coroutine switches as
4336	they do not call any callbacks.	4514	they do not call any callbacks.
4337		4515
4338	=head2 COMPILER WARNINGS	4516	=head2 COMPILER WARNINGS
4339		4517
4340	Depending on your compiler and compiler settings, you might get no or a	4518	Depending on your compiler and compiler settings, you might get no or a
…		…
4351	maintainable.	4529	maintainable.
4352		4530
4353	And of course, some compiler warnings are just plain stupid, or simply	4531	And of course, some compiler warnings are just plain stupid, or simply
4354	wrong (because they don't actually warn about the condition their message	4532	wrong (because they don't actually warn about the condition their message
4355	seems to warn about). For example, certain older gcc versions had some	4533	seems to warn about). For example, certain older gcc versions had some
4356	warnings that resulted an extreme number of false positives. These have	4534	warnings that resulted in an extreme number of false positives. These have
4357	been fixed, but some people still insist on making code warn-free with	4535	been fixed, but some people still insist on making code warn-free with
4358	such buggy versions.	4536	such buggy versions.
4359		4537
4360	While libev is written to generate as few warnings as possible,	4538	While libev is written to generate as few warnings as possible,
4361	"warn-free" code is not a goal, and it is recommended not to build libev	4539	"warn-free" code is not a goal, and it is recommended not to build libev
…		…
4397	I suggest using suppression lists.	4575	I suggest using suppression lists.
4398		4576
4399		4577
4400	=head1 PORTABILITY NOTES	4578	=head1 PORTABILITY NOTES
4401		4579
		4580	=head2 GNU/LINUX 32 BIT LIMITATIONS
		4581
		4582	GNU/Linux is the only common platform that supports 64 bit file/large file
		4583	interfaces but I<disables> them by default.
		4584
		4585	That means that libev compiled in the default environment doesn't support
		4586	files larger than 2GiB or so, which mainly affects C<ev_stat> watchers.
		4587
		4588	Unfortunately, many programs try to work around this GNU/Linux issue
		4589	by enabling the large file API, which makes them incompatible with the
		4590	standard libev compiled for their system.
		4591
		4592	Likewise, libev cannot enable the large file API itself as this would
		4593	suddenly make it incompatible to the default compile time environment,
		4594	i.e. all programs not using special compile switches.
		4595
		4596	=head2 OS/X AND DARWIN BUGS
		4597
		4598	The whole thing is a bug if you ask me - basically any system interface
		4599	you touch is broken, whether it is locales, poll, kqueue or even the
		4600	OpenGL drivers.
		4601
		4602	=head3 C<kqueue> is buggy
		4603
		4604	The kqueue syscall is broken in all known versions - most versions support
		4605	only sockets, many support pipes.
		4606
		4607	Libev tries to work around this by not using C<kqueue> by default on this
		4608	rotten platform, but of course you can still ask for it when creating a
		4609	loop - embedding a socket-only kqueue loop into a select-based one is
		4610	probably going to work well.
		4611
		4612	=head3 C<poll> is buggy
		4613
		4614	Instead of fixing C<kqueue>, Apple replaced their (working) C<poll>
		4615	implementation by something calling C<kqueue> internally around the 10.5.6
		4616	release, so now C<kqueue> I<and> C<poll> are broken.
		4617
		4618	Libev tries to work around this by not using C<poll> by default on
		4619	this rotten platform, but of course you can still ask for it when creating
		4620	a loop.
		4621
		4622	=head3 C<select> is buggy
		4623
		4624	All that's left is C<select>, and of course Apple found a way to fuck this
		4625	one up as well: On OS/X, C<select> actively limits the number of file
		4626	descriptors you can pass in to 1024 - your program suddenly crashes when
		4627	you use more.
		4628
		4629	There is an undocumented "workaround" for this - defining
		4630	C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should>
		4631	work on OS/X.
		4632
		4633	=head2 SOLARIS PROBLEMS AND WORKAROUNDS
		4634
		4635	=head3 C<errno> reentrancy
		4636
		4637	The default compile environment on Solaris is unfortunately so
		4638	thread-unsafe that you can't even use components/libraries compiled
		4639	without C<-D_REENTRANT> in a threaded program, which, of course, isn't
		4640	defined by default. A valid, if stupid, implementation choice.
		4641
		4642	If you want to use libev in threaded environments you have to make sure
		4643	it's compiled with C<_REENTRANT> defined.
		4644
		4645	=head3 Event port backend
		4646
		4647	The scalable event interface for Solaris is called "event
		4648	ports". Unfortunately, this mechanism is very buggy in all major
		4649	releases. If you run into high CPU usage, your program freezes or you get
		4650	a large number of spurious wakeups, make sure you have all the relevant
		4651	and latest kernel patches applied. No, I don't know which ones, but there
		4652	are multiple ones to apply, and afterwards, event ports actually work
		4653	great.
		4654
		4655	If you can't get it to work, you can try running the program by setting
		4656	the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and
		4657	C<select> backends.
		4658
		4659	=head2 AIX POLL BUG
		4660
		4661	AIX unfortunately has a broken C<poll.h> header. Libev works around
		4662	this by trying to avoid the poll backend altogether (i.e. it's not even
		4663	compiled in), which normally isn't a big problem as C<select> works fine
		4664	with large bitsets on AIX, and AIX is dead anyway.
		4665
4402	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS	4666	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
		4667
		4668	=head3 General issues
4403		4669
4404	Win32 doesn't support any of the standards (e.g. POSIX) that libev	4670	Win32 doesn't support any of the standards (e.g. POSIX) that libev
4405	requires, and its I/O model is fundamentally incompatible with the POSIX	4671	requires, and its I/O model is fundamentally incompatible with the POSIX
4406	model. Libev still offers limited functionality on this platform in	4672	model. Libev still offers limited functionality on this platform in
4407	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	4673	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
4408	descriptors. This only applies when using Win32 natively, not when using	4674	descriptors. This only applies when using Win32 natively, not when using
4409	e.g. cygwin.	4675	e.g. cygwin. Actually, it only applies to the microsofts own compilers,
		4676	as every compielr comes with a slightly differently broken/incompatible
		4677	environment.
4410		4678
4411	Lifting these limitations would basically require the full	4679	Lifting these limitations would basically require the full
4412	re-implementation of the I/O system. If you are into these kinds of	4680	re-implementation of the I/O system. If you are into this kind of thing,
4413	things, then note that glib does exactly that for you in a very portable	4681	then note that glib does exactly that for you in a very portable way (note
4414	way (note also that glib is the slowest event library known to man).	4682	also that glib is the slowest event library known to man).
4415		4683
4416	There is no supported compilation method available on windows except	4684	There is no supported compilation method available on windows except
4417	embedding it into other applications.	4685	embedding it into other applications.
4418		4686
4419	Sensible signal handling is officially unsupported by Microsoft - libev	4687	Sensible signal handling is officially unsupported by Microsoft - libev
…		…
4447	you do I<not> compile the F<ev.c> or any other embedded source files!):	4715	you do I<not> compile the F<ev.c> or any other embedded source files!):
4448		4716
4449	#include "evwrap.h"	4717	#include "evwrap.h"
4450	#include "ev.c"	4718	#include "ev.c"
4451		4719
4452	=over 4
4453
4454	=item The winsocket select function	4720	=head3 The winsocket C<select> function
4455		4721
4456	The winsocket C<select> function doesn't follow POSIX in that it	4722	The winsocket C<select> function doesn't follow POSIX in that it
4457	requires socket I<handles> and not socket I<file descriptors> (it is	4723	requires socket I<handles> and not socket I<file descriptors> (it is
4458	also extremely buggy). This makes select very inefficient, and also	4724	also extremely buggy). This makes select very inefficient, and also
4459	requires a mapping from file descriptors to socket handles (the Microsoft	4725	requires a mapping from file descriptors to socket handles (the Microsoft
…		…
4468	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */	4734	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
4469		4735
4470	Note that winsockets handling of fd sets is O(n), so you can easily get a	4736	Note that winsockets handling of fd sets is O(n), so you can easily get a
4471	complexity in the O(n²) range when using win32.	4737	complexity in the O(n²) range when using win32.
4472		4738
4473	=item Limited number of file descriptors	4739	=head3 Limited number of file descriptors
4474		4740
4475	Windows has numerous arbitrary (and low) limits on things.	4741	Windows has numerous arbitrary (and low) limits on things.
4476		4742
4477	Early versions of winsocket's select only supported waiting for a maximum	4743	Early versions of winsocket's select only supported waiting for a maximum
4478	of C<64> handles (probably owning to the fact that all windows kernels	4744	of C<64> handles (probably owning to the fact that all windows kernels
…		…
4493	runtime libraries. This might get you to about C<512> or C<2048> sockets	4759	runtime libraries. This might get you to about C<512> or C<2048> sockets
4494	(depending on windows version and/or the phase of the moon). To get more,	4760	(depending on windows version and/or the phase of the moon). To get more,
4495	you need to wrap all I/O functions and provide your own fd management, but	4761	you need to wrap all I/O functions and provide your own fd management, but
4496	the cost of calling select (O(n²)) will likely make this unworkable.	4762	the cost of calling select (O(n²)) will likely make this unworkable.
4497		4763
4498	=back
4499
4500	=head2 PORTABILITY REQUIREMENTS	4764	=head2 PORTABILITY REQUIREMENTS
4501		4765
4502	In addition to a working ISO-C implementation and of course the	4766	In addition to a working ISO-C implementation and of course the
4503	backend-specific APIs, libev relies on a few additional extensions:	4767	backend-specific APIs, libev relies on a few additional extensions:
4504		4768
…		…
4510	Libev assumes not only that all watcher pointers have the same internal	4774	Libev assumes not only that all watcher pointers have the same internal
4511	structure (guaranteed by POSIX but not by ISO C for example), but it also	4775	structure (guaranteed by POSIX but not by ISO C for example), but it also
4512	assumes that the same (machine) code can be used to call any watcher	4776	assumes that the same (machine) code can be used to call any watcher
4513	callback: The watcher callbacks have different type signatures, but libev	4777	callback: The watcher callbacks have different type signatures, but libev
4514	calls them using an C<ev_watcher *> internally.	4778	calls them using an C<ev_watcher *> internally.
		4779
		4780	=item pointer accesses must be thread-atomic
		4781
		4782	Accessing a pointer value must be atomic, it must both be readable and
		4783	writable in one piece - this is the case on all current architectures.
4515		4784
4516	=item C<sig_atomic_t volatile> must be thread-atomic as well	4785	=item C<sig_atomic_t volatile> must be thread-atomic as well
4517		4786
4518	The type C<sig_atomic_t volatile> (or whatever is defined as	4787	The type C<sig_atomic_t volatile> (or whatever is defined as
4519	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different	4788	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
…		…
4542	watchers.	4811	watchers.
4543		4812
4544	=item C<double> must hold a time value in seconds with enough accuracy	4813	=item C<double> must hold a time value in seconds with enough accuracy
4545		4814
4546	The type C<double> is used to represent timestamps. It is required to	4815	The type C<double> is used to represent timestamps. It is required to
4547	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	4816	have at least 51 bits of mantissa (and 9 bits of exponent), which is
4548	enough for at least into the year 4000. This requirement is fulfilled by	4817	good enough for at least into the year 4000 with millisecond accuracy
		4818	(the design goal for libev). This requirement is overfulfilled by
4549	implementations implementing IEEE 754, which is basically all existing	4819	implementations using IEEE 754, which is basically all existing ones. With
4550	ones. With IEEE 754 doubles, you get microsecond accuracy until at least	4820	IEEE 754 doubles, you get microsecond accuracy until at least 2200.
4551	2200.
4552		4821
4553	=back	4822	=back
4554		4823
4555	If you know of other additional requirements drop me a note.	4824	If you know of other additional requirements drop me a note.
4556		4825
…		…
4626	=back	4895	=back
4627		4896
4628		4897
4629	=head1 PORTING FROM LIBEV 3.X TO 4.X	4898	=head1 PORTING FROM LIBEV 3.X TO 4.X
4630		4899
4631	The major version 4 introduced some minor incompatible changes to the API.	4900	The major version 4 introduced some incompatible changes to the API.
4632		4901
4633	At the moment, the C<ev.h> header file tries to implement superficial	4902	At the moment, the C<ev.h> header file provides compatibility definitions
4634	compatibility, so most programs should still compile. Those might be	4903	for all changes, so most programs should still compile. The compatibility
4635	removed in later versions of libev, so better update early than late.	4904	layer might be removed in later versions of libev, so better update to the
		4905	new API early than late.
4636		4906
4637	=over 4	4907	=over 4
4638		4908
4639	=item C<ev_loop_count> renamed to C<ev_iteration>	4909	=item C<EV_COMPAT3> backwards compatibility mechanism
4640		4910
4641	=item C<ev_loop_depth> renamed to C<ev_depth>	4911	The backward compatibility mechanism can be controlled by
		4912	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		4913	section.
4642		4914
4643	=item C<ev_loop_verify> renamed to C<ev_verify>	4915	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		4916
		4917	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		4918
		4919	ev_loop_destroy (EV_DEFAULT_UC);
		4920	ev_loop_fork (EV_DEFAULT);
		4921
		4922	=item function/symbol renames
		4923
		4924	A number of functions and symbols have been renamed:
		4925
		4926	ev_loop => ev_run
		4927	EVLOOP_NONBLOCK => EVRUN_NOWAIT
		4928	EVLOOP_ONESHOT => EVRUN_ONCE
		4929
		4930	ev_unloop => ev_break
		4931	EVUNLOOP_CANCEL => EVBREAK_CANCEL
		4932	EVUNLOOP_ONE => EVBREAK_ONE
		4933	EVUNLOOP_ALL => EVBREAK_ALL
		4934
		4935	EV_TIMEOUT => EV_TIMER
		4936
		4937	ev_loop_count => ev_iteration
		4938	ev_loop_depth => ev_depth
		4939	ev_loop_verify => ev_verify
4644		4940
4645	Most functions working on C<struct ev_loop> objects don't have an	4941	Most functions working on C<struct ev_loop> objects don't have an
4646	C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is	4942	C<ev_loop_> prefix, so it was removed; C<ev_loop>, C<ev_unloop> and
		4943	associated constants have been renamed to not collide with the C<struct
		4944	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
		4945	as all other watcher types. Note that C<ev_loop_fork> is still called
4647	still called C<ev_loop_fork> because it would otherwise clash with the	4946	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
4648	C<ev_fork> typedef.	4947	typedef.
4649
4650	=item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents>
4651
4652	This is a simple rename - all other watcher types use their name
4653	as revents flag, and now C<ev_timer> does, too.
4654
4655	Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions
4656	and continue to be present for the foreseeable future, so this is mostly a
4657	documentation change.
4658		4948
4659	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>	4949	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
4660		4950
4661	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different	4951	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
4662	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile	4952	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
…		…
4669		4959
4670	=over 4	4960	=over 4
4671		4961
4672	=item active	4962	=item active
4673		4963
4674	A watcher is active as long as it has been started (has been attached to	4964	A watcher is active as long as it has been started and not yet stopped.
4675	an event loop) but not yet stopped (disassociated from the event loop).	4965	See L<WATCHER STATES> for details.
4676		4966
4677	=item application	4967	=item application
4678		4968
4679	In this document, an application is whatever is using libev.	4969	In this document, an application is whatever is using libev.
		4970
		4971	=item backend
		4972
		4973	The part of the code dealing with the operating system interfaces.
4680		4974
4681	=item callback	4975	=item callback
4682		4976
4683	The address of a function that is called when some event has been	4977	The address of a function that is called when some event has been
4684	detected. Callbacks are being passed the event loop, the watcher that	4978	detected. Callbacks are being passed the event loop, the watcher that
4685	received the event, and the actual event bitset.	4979	received the event, and the actual event bitset.
4686		4980
4687	=item callback invocation	4981	=item callback/watcher invocation
4688		4982
4689	The act of calling the callback associated with a watcher.	4983	The act of calling the callback associated with a watcher.
4690		4984
4691	=item event	4985	=item event
4692		4986
…		…
4711	The model used to describe how an event loop handles and processes	5005	The model used to describe how an event loop handles and processes
4712	watchers and events.	5006	watchers and events.
4713		5007
4714	=item pending	5008	=item pending
4715		5009
4716	A watcher is pending as soon as the corresponding event has been detected,	5010	A watcher is pending as soon as the corresponding event has been
4717	and stops being pending as soon as the watcher will be invoked or its	5011	detected. See L<WATCHER STATES> for details.
4718	pending status is explicitly cleared by the application.
4719
4720	A watcher can be pending, but not active. Stopping a watcher also clears
4721	its pending status.
4722		5012
4723	=item real time	5013	=item real time
4724		5014
4725	The physical time that is observed. It is apparently strictly monotonic :)	5015	The physical time that is observed. It is apparently strictly monotonic :)
4726		5016
…		…
4733	=item watcher	5023	=item watcher
4734		5024
4735	A data structure that describes interest in certain events. Watchers need	5025	A data structure that describes interest in certain events. Watchers need
4736	to be started (attached to an event loop) before they can receive events.	5026	to be started (attached to an event loop) before they can receive events.
4737		5027
4738	=item watcher invocation
4739
4740	The act of calling the callback associated with a watcher.
4741
4742	=back	5028	=back
4743		5029
4744	=head1 AUTHOR	5030	=head1 AUTHOR
4745		5031
4746	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.	5032	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5033	Magnusson and Emanuele Giaquinta.
4747		5034

Diff Legend

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