ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.320 by root, Fri Oct 22 10:48:54 2010 UTC vs.
Revision 1.370 by root, Thu Jun 2 23:42:40 2011 UTC

…		…
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);
…		…
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_run (loop, 0);	61	ev_run (loop, 0);
62		62
63	// unloop was called, so exit	63	// break was called, so exit
64	return 0;	64	return 0;
65	}	65	}
66		66
67	=head1 ABOUT THIS DOCUMENT	67	=head1 ABOUT THIS DOCUMENT
68		68
…		…
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
…		…
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. Also interetsing is the combination of	178	you actually want to know. Also interesting is the combination of
171	C<ev_update_now> and C<ev_now>.	179	C<ev_update_now> and C<ev_now>.
172		180
173	=item ev_sleep (ev_tstamp interval)	181	=item ev_sleep (ev_tstamp interval)
174		182
175	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
…		…
233	the current system, you would need to look at C<ev_embeddable_backends ()	241	the current system, you would need to look at C<ev_embeddable_backends ()
234	& ev_supported_backends ()>, likewise for recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
235		243
236	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
237		245
238	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]	246	=item ev_set_allocator (void *(*cb)(void *ptr, long size))
239		247
240	Sets the allocation function to use (the prototype is similar - the	248	Sets the allocation function to use (the prototype is similar - the
241	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
242	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
243	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
…		…
269	}	277	}
270		278
271	...	279	...
272	ev_set_allocator (persistent_realloc);	280	ev_set_allocator (persistent_realloc);
273		281
274	=item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]	282	=item ev_set_syserr_cb (void (*cb)(const char *msg))
275		283
276	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
277	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
278	indicating the system call or subsystem causing the problem. If this	286	indicating the system call or subsystem causing the problem. If this
279	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
…		…
291	}	299	}
292		300
293	...	301	...
294	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
295		303
		304	=item ev_feed_signal (int signum)
		305
		306	This function can be used to "simulate" a signal receive. It is completely
		307	safe to call this function at any time, from any context, including signal
		308	handlers or random threads.
		309
		310	Its main use is to customise signal handling in your process, especially
		311	in the presence of threads. For example, you could block signals
		312	by default in all threads (and specifying C<EVFLAG_NOSIGMASK> when
		313	creating any loops), and in one thread, use C<sigwait> or any other
		314	mechanism to wait for signals, then "deliver" them to libev by calling
		315	C<ev_feed_signal>.
		316
296	=back	317	=back
297		318
298	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	319	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
299		320
300	An event loop is described by a C<struct ev_loop *> (the C<struct> is	321	An event loop is described by a C<struct ev_loop *> (the C<struct> is
301	I<not> optional in this case unless libev 3 compatibility is disabled, as	322	I<not> optional in this case unless libev 3 compatibility is disabled, as
302	libev 3 had an C<ev_loop> function colliding with the struct name).	323	libev 3 had an C<ev_loop> function colliding with the struct name).
303		324
304	The library knows two types of such loops, the I<default> loop, which	325	The library knows two types of such loops, the I<default> loop, which
305	supports signals and child events, and dynamically created event loops	326	supports child process events, and dynamically created event loops which
306	which do not.	327	do not.
307		328
308	=over 4	329	=over 4
309		330
310	=item struct ev_loop *ev_default_loop (unsigned int flags)	331	=item struct ev_loop *ev_default_loop (unsigned int flags)
311		332
312	This will initialise the default event loop if it hasn't been initialised	333	This returns the "default" event loop object, which is what you should
313	yet and return it. If the default loop could not be initialised, returns	334	normally use when you just need "the event loop". Event loop objects and
314	false. If it already was initialised it simply returns it (and ignores the	335	the C<flags> parameter are described in more detail in the entry for
315	flags. If that is troubling you, check C<ev_backend ()> afterwards).	336	C<ev_loop_new>.
		337
		338	If the default loop is already initialised then this function simply
		339	returns it (and ignores the flags. If that is troubling you, check
		340	C<ev_backend ()> afterwards). Otherwise it will create it with the given
		341	flags, which should almost always be C<0>, unless the caller is also the
		342	one calling C<ev_run> or otherwise qualifies as "the main program".
316		343
317	If you don't know what event loop to use, use the one returned from this	344	If you don't know what event loop to use, use the one returned from this
318	function.	345	function (or via the C<EV_DEFAULT> macro).
319		346
320	Note that this function is I<not> thread-safe, so if you want to use it	347	Note that this function is I<not> thread-safe, so if you want to use it
321	from multiple threads, you have to lock (note also that this is unlikely,	348	from multiple threads, you have to employ some kind of mutex (note also
322	as loops cannot be shared easily between threads anyway).	349	that this case is unlikely, as loops cannot be shared easily between
		350	threads anyway).
323		351
324	The default loop is the only loop that can handle C<ev_signal> and	352	The default loop is the only loop that can handle C<ev_child> watchers,
325	C<ev_child> watchers, and to do this, it always registers a handler	353	and to do this, it always registers a handler for C<SIGCHLD>. If this is
326	for C<SIGCHLD>. If this is a problem for your application you can either	354	a problem for your application you can either create a dynamic loop with
327	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	355	C<ev_loop_new> which doesn't do that, or you can simply overwrite the
328	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	356	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
329	C<ev_default_init>.	357
		358	Example: This is the most typical usage.
		359
		360	if (!ev_default_loop (0))
		361	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
		362
		363	Example: Restrict libev to the select and poll backends, and do not allow
		364	environment settings to be taken into account:
		365
		366	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
		367
		368	=item struct ev_loop *ev_loop_new (unsigned int flags)
		369
		370	This will create and initialise a new event loop object. If the loop
		371	could not be initialised, returns false.
		372
		373	This function is thread-safe, and one common way to use libev with
		374	threads is indeed to create one loop per thread, and using the default
		375	loop in the "main" or "initial" thread.
330		376
331	The flags argument can be used to specify special behaviour or specific	377	The flags argument can be used to specify special behaviour or specific
332	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).	378	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
333		379
334	The following flags are supported:	380	The following flags are supported:
…		…
369	environment variable.	415	environment variable.
370		416
371	=item C<EVFLAG_NOINOTIFY>	417	=item C<EVFLAG_NOINOTIFY>
372		418
373	When this flag is specified, then libev will not attempt to use the	419	When this flag is specified, then libev will not attempt to use the
374	I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and	420	I<inotify> API for its C<ev_stat> watchers. Apart from debugging and
375	testing, this flag can be useful to conserve inotify file descriptors, as	421	testing, this flag can be useful to conserve inotify file descriptors, as
376	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.	422	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
377		423
378	=item C<EVFLAG_SIGNALFD>	424	=item C<EVFLAG_SIGNALFD>
379		425
380	When this flag is specified, then libev will attempt to use the	426	When this flag is specified, then libev will attempt to use the
381	I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API	427	I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API
382	delivers signals synchronously, which makes it both faster and might make	428	delivers signals synchronously, which makes it both faster and might make
383	it possible to get the queued signal data. It can also simplify signal	429	it possible to get the queued signal data. It can also simplify signal
384	handling with threads, as long as you properly block signals in your	430	handling with threads, as long as you properly block signals in your
385	threads that are not interested in handling them.	431	threads that are not interested in handling them.
386		432
387	Signalfd will not be used by default as this changes your signal mask, and	433	Signalfd will not be used by default as this changes your signal mask, and
388	there are a lot of shoddy libraries and programs (glib's threadpool for	434	there are a lot of shoddy libraries and programs (glib's threadpool for
389	example) that can't properly initialise their signal masks.	435	example) that can't properly initialise their signal masks.
		436
		437	=item C<EVFLAG_NOSIGMASK>
		438
		439	When this flag is specified, then libev will avoid to modify the signal
		440	mask. Specifically, this means you ahve to make sure signals are unblocked
		441	when you want to receive them.
		442
		443	This behaviour is useful when you want to do your own signal handling, or
		444	want to handle signals only in specific threads and want to avoid libev
		445	unblocking the signals.
		446
		447	It's also required by POSIX in a threaded program, as libev calls
		448	C<sigprocmask>, whose behaviour is officially unspecified.
		449
		450	This flag's behaviour will become the default in future versions of libev.
390		451
391	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	452	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
392		453
393	This is your standard select(2) backend. Not I<completely> standard, as	454	This is your standard select(2) backend. Not I<completely> standard, as
394	libev tries to roll its own fd_set with no limits on the number of fds,	455	libev tries to roll its own fd_set with no limits on the number of fds,
…		…
422	=item C<EVBACKEND_EPOLL> (value 4, Linux)	483	=item C<EVBACKEND_EPOLL> (value 4, Linux)
423		484
424	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9	485	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
425	kernels).	486	kernels).
426		487
427	For few fds, this backend is a bit little slower than poll and select,	488	For few fds, this backend is a bit little slower than poll and select, but
428	but it scales phenomenally better. While poll and select usually scale	489	it scales phenomenally better. While poll and select usually scale like
429	like O(total_fds) where n is the total number of fds (or the highest fd),	490	O(total_fds) where total_fds is the total number of fds (or the highest
430	epoll scales either O(1) or O(active_fds).	491	fd), epoll scales either O(1) or O(active_fds).
431		492
432	The epoll mechanism deserves honorable mention as the most misdesigned	493	The epoll mechanism deserves honorable mention as the most misdesigned
433	of the more advanced event mechanisms: mere annoyances include silently	494	of the more advanced event mechanisms: mere annoyances include silently
434	dropping file descriptors, requiring a system call per change per file	495	dropping file descriptors, requiring a system call per change per file
435	descriptor (and unnecessary guessing of parameters), problems with dup and	496	descriptor (and unnecessary guessing of parameters), problems with dup,
		497	returning before the timeout value, resulting in additional iterations
		498	(and only giving 5ms accuracy while select on the same platform gives
436	so on. The biggest issue is fork races, however - if a program forks then	499	0.1ms) and so on. The biggest issue is fork races, however - if a program
437	I<both> parent and child process have to recreate the epoll set, which can	500	forks then I<both> parent and child process have to recreate the epoll
438	take considerable time (one syscall per file descriptor) and is of course	501	set, which can take considerable time (one syscall per file descriptor)
439	hard to detect.	502	and is of course hard to detect.
440		503
441	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but	504	Epoll is also notoriously buggy - embedding epoll fds I<should> work,
442	of course I<doesn't>, and epoll just loves to report events for totally	505	but of course I<doesn't>, and epoll just loves to report events for
443	I<different> file descriptors (even already closed ones, so one cannot	506	totally I<different> file descriptors (even already closed ones, so
444	even remove them from the set) than registered in the set (especially	507	one cannot even remove them from the set) than registered in the set
445	on SMP systems). Libev tries to counter these spurious notifications by	508	(especially on SMP systems). Libev tries to counter these spurious
446	employing an additional generation counter and comparing that against the	509	notifications by employing an additional generation counter and comparing
447	events to filter out spurious ones, recreating the set when required. Last	510	that against the events to filter out spurious ones, recreating the set
		511	when required. Epoll also errornously rounds down timeouts, but gives you
		512	no way to know when and by how much, so sometimes you have to busy-wait
		513	because epoll returns immediately despite a nonzero timeout. And last
448	not least, it also refuses to work with some file descriptors which work	514	not least, it also refuses to work with some file descriptors which work
449	perfectly fine with C<select> (files, many character devices...).	515	perfectly fine with C<select> (files, many character devices...).
		516
		517	Epoll is truly the train wreck among event poll mechanisms, a frankenpoll,
		518	cobbled together in a hurry, no thought to design or interaction with
		519	others. Oh, the pain, will it ever stop...
450		520
451	While stopping, setting and starting an I/O watcher in the same iteration	521	While stopping, setting and starting an I/O watcher in the same iteration
452	will result in some caching, there is still a system call per such	522	will result in some caching, there is still a system call per such
453	incident (because the same I<file descriptor> could point to a different	523	incident (because the same I<file descriptor> could point to a different
454	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed	524	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
…		…
520	=item C<EVBACKEND_PORT> (value 32, Solaris 10)	590	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
521		591
522	This uses the Solaris 10 event port mechanism. As with everything on Solaris,	592	This uses the Solaris 10 event port mechanism. As with everything on Solaris,
523	it's really slow, but it still scales very well (O(active_fds)).	593	it's really slow, but it still scales very well (O(active_fds)).
524		594
525	Please note that Solaris event ports can deliver a lot of spurious
526	notifications, so you need to use non-blocking I/O or other means to avoid
527	blocking when no data (or space) is available.
528
529	While this backend scales well, it requires one system call per active	595	While this backend scales well, it requires one system call per active
530	file descriptor per loop iteration. For small and medium numbers of file	596	file descriptor per loop iteration. For small and medium numbers of file
531	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	597	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
532	might perform better.	598	might perform better.
533		599
534	On the positive side, with the exception of the spurious readiness	600	On the positive side, this backend actually performed fully to
535	notifications, this backend actually performed fully to specification
536	in all tests and is fully embeddable, which is a rare feat among the	601	specification in all tests and is fully embeddable, which is a rare feat
537	OS-specific backends (I vastly prefer correctness over speed hacks).	602	among the OS-specific backends (I vastly prefer correctness over speed
		603	hacks).
		604
		605	On the negative side, the interface is I<bizarre> - so bizarre that
		606	even sun itself gets it wrong in their code examples: The event polling
		607	function sometimes returning events to the caller even though an error
		608	occurred, but with no indication whether it has done so or not (yes, it's
		609	even documented that way) - deadly for edge-triggered interfaces where
		610	you absolutely have to know whether an event occurred or not because you
		611	have to re-arm the watcher.
		612
		613	Fortunately libev seems to be able to work around these idiocies.
538		614
539	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	615	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
540	C<EVBACKEND_POLL>.	616	C<EVBACKEND_POLL>.
541		617
542	=item C<EVBACKEND_ALL>	618	=item C<EVBACKEND_ALL>
543		619
544	Try all backends (even potentially broken ones that wouldn't be tried	620	Try all backends (even potentially broken ones that wouldn't be tried
545	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as	621	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
546	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.	622	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
547		623
548	It is definitely not recommended to use this flag.	624	It is definitely not recommended to use this flag, use whatever
		625	C<ev_recommended_backends ()> returns, or simply do not specify a backend
		626	at all.
		627
		628	=item C<EVBACKEND_MASK>
		629
		630	Not a backend at all, but a mask to select all backend bits from a
		631	C<flags> value, in case you want to mask out any backends from a flags
		632	value (e.g. when modifying the C<LIBEV_FLAGS> environment variable).
549		633
550	=back	634	=back
551		635
552	If one or more of the backend flags are or'ed into the flags value,	636	If one or more of the backend flags are or'ed into the flags value,
553	then only these backends will be tried (in the reverse order as listed	637	then only these backends will be tried (in the reverse order as listed
554	here). If none are specified, all backends in C<ev_recommended_backends	638	here). If none are specified, all backends in C<ev_recommended_backends
555	()> will be tried.	639	()> will be tried.
556		640
557	Example: This is the most typical usage.
558
559	if (!ev_default_loop (0))
560	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
561
562	Example: Restrict libev to the select and poll backends, and do not allow
563	environment settings to be taken into account:
564
565	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
566
567	Example: Use whatever libev has to offer, but make sure that kqueue is
568	used if available (warning, breaks stuff, best use only with your own
569	private event loop and only if you know the OS supports your types of
570	fds):
571
572	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
573
574	=item struct ev_loop *ev_loop_new (unsigned int flags)
575
576	Similar to C<ev_default_loop>, but always creates a new event loop that is
577	always distinct from the default loop.
578
579	Note that this function I<is> thread-safe, and one common way to use
580	libev with threads is indeed to create one loop per thread, and using the
581	default loop in the "main" or "initial" thread.
582
583	Example: Try to create a event loop that uses epoll and nothing else.	641	Example: Try to create a event loop that uses epoll and nothing else.
584		642
585	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	643	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
586	if (!epoller)	644	if (!epoller)
587	fatal ("no epoll found here, maybe it hides under your chair");	645	fatal ("no epoll found here, maybe it hides under your chair");
588		646
		647	Example: Use whatever libev has to offer, but make sure that kqueue is
		648	used if available.
		649
		650	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE);
		651
589	=item ev_default_destroy ()	652	=item ev_loop_destroy (loop)
590		653
591	Destroys the default loop (frees all memory and kernel state etc.). None	654	Destroys an event loop object (frees all memory and kernel state
592	of the active event watchers will be stopped in the normal sense, so	655	etc.). None of the active event watchers will be stopped in the normal
593	e.g. C<ev_is_active> might still return true. It is your responsibility to	656	sense, so e.g. C<ev_is_active> might still return true. It is your
594	either stop all watchers cleanly yourself I<before> calling this function,	657	responsibility to either stop all watchers cleanly yourself I<before>
595	or cope with the fact afterwards (which is usually the easiest thing, you	658	calling this function, or cope with the fact afterwards (which is usually
596	can just ignore the watchers and/or C<free ()> them for example).	659	the easiest thing, you can just ignore the watchers and/or C<free ()> them
		660	for example).
597		661
598	Note that certain global state, such as signal state (and installed signal	662	Note that certain global state, such as signal state (and installed signal
599	handlers), will not be freed by this function, and related watchers (such	663	handlers), will not be freed by this function, and related watchers (such
600	as signal and child watchers) would need to be stopped manually.	664	as signal and child watchers) would need to be stopped manually.
601		665
602	In general it is not advisable to call this function except in the	666	This function is normally used on loop objects allocated by
603	rare occasion where you really need to free e.g. the signal handling	667	C<ev_loop_new>, but it can also be used on the default loop returned by
		668	C<ev_default_loop>, in which case it is not thread-safe.
		669
		670	Note that it is not advisable to call this function on the default loop
		671	except in the rare occasion where you really need to free its resources.
604	pipe fds. If you need dynamically allocated loops it is better to use	672	If you need dynamically allocated loops it is better to use C<ev_loop_new>
605	C<ev_loop_new> and C<ev_loop_destroy>.	673	and C<ev_loop_destroy>.
606		674
607	=item ev_loop_destroy (loop)	675	=item ev_loop_fork (loop)
608		676
609	Like C<ev_default_destroy>, but destroys an event loop created by an
610	earlier call to C<ev_loop_new>.
611
612	=item ev_default_fork ()
613
614	This function sets a flag that causes subsequent C<ev_run> iterations	677	This function sets a flag that causes subsequent C<ev_run> iterations to
615	to reinitialise the kernel state for backends that have one. Despite the	678	reinitialise the kernel state for backends that have one. Despite the
616	name, you can call it anytime, but it makes most sense after forking, in	679	name, you can call it anytime, but it makes most sense after forking, in
617	the child process (or both child and parent, but that again makes little	680	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
618	sense). You I<must> call it in the child before using any of the libev	681	child before resuming or calling C<ev_run>.
619	functions, and it will only take effect at the next C<ev_run> iteration.
620		682
621	Again, you I<have> to call it on I<any> loop that you want to re-use after	683	Again, you I<have> to call it on I<any> loop that you want to re-use after
622	a fork, I<even if you do not plan to use the loop in the parent>. This is	684	a fork, I<even if you do not plan to use the loop in the parent>. This is
623	because some kernel interfaces *cough* I<kqueue> *cough* do funny things	685	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
624	during fork.	686	during fork.
…		…
629	call it at all (in fact, C<epoll> is so badly broken that it makes a	691	call it at all (in fact, C<epoll> is so badly broken that it makes a
630	difference, but libev will usually detect this case on its own and do a	692	difference, but libev will usually detect this case on its own and do a
631	costly reset of the backend).	693	costly reset of the backend).
632		694
633	The function itself is quite fast and it's usually not a problem to call	695	The function itself is quite fast and it's usually not a problem to call
634	it just in case after a fork. To make this easy, the function will fit in	696	it just in case after a fork.
635	quite nicely into a call to C<pthread_atfork>:
636		697
		698	Example: Automate calling C<ev_loop_fork> on the default loop when
		699	using pthreads.
		700
		701	static void
		702	post_fork_child (void)
		703	{
		704	ev_loop_fork (EV_DEFAULT);
		705	}
		706
		707	...
637	pthread_atfork (0, 0, ev_default_fork);	708	pthread_atfork (0, 0, post_fork_child);
638
639	=item ev_loop_fork (loop)
640
641	Like C<ev_default_fork>, but acts on an event loop created by
642	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
643	after fork that you want to re-use in the child, and how you keep track of
644	them is entirely your own problem.
645		709
646	=item int ev_is_default_loop (loop)	710	=item int ev_is_default_loop (loop)
647		711
648	Returns true when the given loop is, in fact, the default loop, and false	712	Returns true when the given loop is, in fact, the default loop, and false
649	otherwise.	713	otherwise.
…		…
660	prepare and check phases.	724	prepare and check phases.
661		725
662	=item unsigned int ev_depth (loop)	726	=item unsigned int ev_depth (loop)
663		727
664	Returns the number of times C<ev_run> was entered minus the number of	728	Returns the number of times C<ev_run> was entered minus the number of
665	times C<ev_run> was exited, in other words, the recursion depth.	729	times C<ev_run> was exited normally, in other words, the recursion depth.
666		730
667	Outside C<ev_run>, this number is zero. In a callback, this number is	731	Outside C<ev_run>, this number is zero. In a callback, this number is
668	C<1>, unless C<ev_run> was invoked recursively (or from another thread),	732	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
669	in which case it is higher.	733	in which case it is higher.
670		734
671	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread	735	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread,
672	etc.), doesn't count as "exit" - consider this as a hint to avoid such	736	throwing an exception etc.), doesn't count as "exit" - consider this
673	ungentleman-like behaviour unless it's really convenient.	737	as a hint to avoid such ungentleman-like behaviour unless it's really
		738	convenient, in which case it is fully supported.
674		739
675	=item unsigned int ev_backend (loop)	740	=item unsigned int ev_backend (loop)
676		741
677	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	742	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
678	use.	743	use.
…		…
740	finished (especially in interactive programs), but having a program	805	finished (especially in interactive programs), but having a program
741	that automatically loops as long as it has to and no longer by virtue	806	that automatically loops as long as it has to and no longer by virtue
742	of relying on its watchers stopping correctly, that is truly a thing of	807	of relying on its watchers stopping correctly, that is truly a thing of
743	beauty.	808	beauty.
744		809
		810	This function is also I<mostly> exception-safe - you can break out of
		811	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
		812	exception and so on. This does not decrement the C<ev_depth> value, nor
		813	will it clear any outstanding C<EVBREAK_ONE> breaks.
		814
745	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle	815	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
746	those events and any already outstanding ones, but will not wait and	816	those events and any already outstanding ones, but will not wait and
747	block your process in case there are no events and will return after one	817	block your process in case there are no events and will return after one
748	iteration of the loop. This is sometimes useful to poll and handle new	818	iteration of the loop. This is sometimes useful to poll and handle new
749	events while doing lengthy calculations, to keep the program responsive.	819	events while doing lengthy calculations, to keep the program responsive.
…		…
758	This is useful if you are waiting for some external event in conjunction	828	This is useful if you are waiting for some external event in conjunction
759	with something not expressible using other libev watchers (i.e. "roll your	829	with something not expressible using other libev watchers (i.e. "roll your
760	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is	830	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
761	usually a better approach for this kind of thing.	831	usually a better approach for this kind of thing.
762		832
763	Here are the gory details of what C<ev_run> does:	833	Here are the gory details of what C<ev_run> does (this is for your
		834	understanding, not a guarantee that things will work exactly like this in
		835	future versions):
764		836
765	- Increment loop depth.	837	- Increment loop depth.
766	- Reset the ev_break status.	838	- Reset the ev_break status.
767	- Before the first iteration, call any pending watchers.	839	- Before the first iteration, call any pending watchers.
768	LOOP:	840	LOOP:
…		…
801	anymore.	873	anymore.
802		874
803	... queue jobs here, make sure they register event watchers as long	875	... queue jobs here, make sure they register event watchers as long
804	... as they still have work to do (even an idle watcher will do..)	876	... as they still have work to do (even an idle watcher will do..)
805	ev_run (my_loop, 0);	877	ev_run (my_loop, 0);
806	... jobs done or somebody called unloop. yeah!	878	... jobs done or somebody called break. yeah!
807		879
808	=item ev_break (loop, how)	880	=item ev_break (loop, how)
809		881
810	Can be used to make a call to C<ev_run> return early (but only after it	882	Can be used to make a call to C<ev_run> return early (but only after it
811	has processed all outstanding events). The C<how> argument must be either	883	has processed all outstanding events). The C<how> argument must be either
812	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or	884	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
813	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.	885	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
814		886
815	This "unloop state" will be cleared when entering C<ev_run> again.	887	This "break state" will be cleared on the next call to C<ev_run>.
816		888
817	It is safe to call C<ev_break> from outside any C<ev_run> calls. ##TODO##	889	It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in
		890	which case it will have no effect.
818		891
819	=item ev_ref (loop)	892	=item ev_ref (loop)
820		893
821	=item ev_unref (loop)	894	=item ev_unref (loop)
822		895
…		…
843	running when nothing else is active.	916	running when nothing else is active.
844		917
845	ev_signal exitsig;	918	ev_signal exitsig;
846	ev_signal_init (&exitsig, sig_cb, SIGINT);	919	ev_signal_init (&exitsig, sig_cb, SIGINT);
847	ev_signal_start (loop, &exitsig);	920	ev_signal_start (loop, &exitsig);
848	evf_unref (loop);	921	ev_unref (loop);
849		922
850	Example: For some weird reason, unregister the above signal handler again.	923	Example: For some weird reason, unregister the above signal handler again.
851		924
852	ev_ref (loop);	925	ev_ref (loop);
853	ev_signal_stop (loop, &exitsig);	926	ev_signal_stop (loop, &exitsig);
…		…
965	See also the locking example in the C<THREADS> section later in this	1038	See also the locking example in the C<THREADS> section later in this
966	document.	1039	document.
967		1040
968	=item ev_set_userdata (loop, void *data)	1041	=item ev_set_userdata (loop, void *data)
969		1042
970	=item ev_userdata (loop)	1043	=item void *ev_userdata (loop)
971		1044
972	Set and retrieve a single C<void *> associated with a loop. When	1045	Set and retrieve a single C<void *> associated with a loop. When
973	C<ev_set_userdata> has never been called, then C<ev_userdata> returns	1046	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
974	C<0.>	1047	C<0>.
975		1048
976	These two functions can be used to associate arbitrary data with a loop,	1049	These two functions can be used to associate arbitrary data with a loop,
977	and are intended solely for the C<invoke_pending_cb>, C<release> and	1050	and are intended solely for the C<invoke_pending_cb>, C<release> and
978	C<acquire> callbacks described above, but of course can be (ab-)used for	1051	C<acquire> callbacks described above, but of course can be (ab-)used for
979	any other purpose as well.	1052	any other purpose as well.
…		…
1107	=item C<EV_FORK>	1180	=item C<EV_FORK>
1108		1181
1109	The event loop has been resumed in the child process after fork (see	1182	The event loop has been resumed in the child process after fork (see
1110	C<ev_fork>).	1183	C<ev_fork>).
1111		1184
		1185	=item C<EV_CLEANUP>
		1186
		1187	The event loop is about to be destroyed (see C<ev_cleanup>).
		1188
1112	=item C<EV_ASYNC>	1189	=item C<EV_ASYNC>
1113		1190
1114	The given async watcher has been asynchronously notified (see C<ev_async>).	1191	The given async watcher has been asynchronously notified (see C<ev_async>).
1115		1192
1116	=item C<EV_CUSTOM>	1193	=item C<EV_CUSTOM>
…		…
1137	programs, though, as the fd could already be closed and reused for another	1214	programs, though, as the fd could already be closed and reused for another
1138	thing, so beware.	1215	thing, so beware.
1139		1216
1140	=back	1217	=back
1141		1218
		1219	=head2 GENERIC WATCHER FUNCTIONS
		1220
		1221	=over 4
		1222
		1223	=item C<ev_init> (ev_TYPE *watcher, callback)
		1224
		1225	This macro initialises the generic portion of a watcher. The contents
		1226	of the watcher object can be arbitrary (so C<malloc> will do). Only
		1227	the generic parts of the watcher are initialised, you I<need> to call
		1228	the type-specific C<ev_TYPE_set> macro afterwards to initialise the
		1229	type-specific parts. For each type there is also a C<ev_TYPE_init> macro
		1230	which rolls both calls into one.
		1231
		1232	You can reinitialise a watcher at any time as long as it has been stopped
		1233	(or never started) and there are no pending events outstanding.
		1234
		1235	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
		1236	int revents)>.
		1237
		1238	Example: Initialise an C<ev_io> watcher in two steps.
		1239
		1240	ev_io w;
		1241	ev_init (&w, my_cb);
		1242	ev_io_set (&w, STDIN_FILENO, EV_READ);
		1243
		1244	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
		1245
		1246	This macro initialises the type-specific parts of a watcher. You need to
		1247	call C<ev_init> at least once before you call this macro, but you can
		1248	call C<ev_TYPE_set> any number of times. You must not, however, call this
		1249	macro on a watcher that is active (it can be pending, however, which is a
		1250	difference to the C<ev_init> macro).
		1251
		1252	Although some watcher types do not have type-specific arguments
		1253	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
		1254
		1255	See C<ev_init>, above, for an example.
		1256
		1257	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
		1258
		1259	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro
		1260	calls into a single call. This is the most convenient method to initialise
		1261	a watcher. The same limitations apply, of course.
		1262
		1263	Example: Initialise and set an C<ev_io> watcher in one step.
		1264
		1265	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
		1266
		1267	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
		1268
		1269	Starts (activates) the given watcher. Only active watchers will receive
		1270	events. If the watcher is already active nothing will happen.
		1271
		1272	Example: Start the C<ev_io> watcher that is being abused as example in this
		1273	whole section.
		1274
		1275	ev_io_start (EV_DEFAULT_UC, &w);
		1276
		1277	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
		1278
		1279	Stops the given watcher if active, and clears the pending status (whether
		1280	the watcher was active or not).
		1281
		1282	It is possible that stopped watchers are pending - for example,
		1283	non-repeating timers are being stopped when they become pending - but
		1284	calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
		1285	pending. If you want to free or reuse the memory used by the watcher it is
		1286	therefore a good idea to always call its C<ev_TYPE_stop> function.
		1287
		1288	=item bool ev_is_active (ev_TYPE *watcher)
		1289
		1290	Returns a true value iff the watcher is active (i.e. it has been started
		1291	and not yet been stopped). As long as a watcher is active you must not modify
		1292	it.
		1293
		1294	=item bool ev_is_pending (ev_TYPE *watcher)
		1295
		1296	Returns a true value iff the watcher is pending, (i.e. it has outstanding
		1297	events but its callback has not yet been invoked). As long as a watcher
		1298	is pending (but not active) you must not call an init function on it (but
		1299	C<ev_TYPE_set> is safe), you must not change its priority, and you must
		1300	make sure the watcher is available to libev (e.g. you cannot C<free ()>
		1301	it).
		1302
		1303	=item callback ev_cb (ev_TYPE *watcher)
		1304
		1305	Returns the callback currently set on the watcher.
		1306
		1307	=item ev_cb_set (ev_TYPE *watcher, callback)
		1308
		1309	Change the callback. You can change the callback at virtually any time
		1310	(modulo threads).
		1311
		1312	=item ev_set_priority (ev_TYPE *watcher, int priority)
		1313
		1314	=item int ev_priority (ev_TYPE *watcher)
		1315
		1316	Set and query the priority of the watcher. The priority is a small
		1317	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
		1318	(default: C<-2>). Pending watchers with higher priority will be invoked
		1319	before watchers with lower priority, but priority will not keep watchers
		1320	from being executed (except for C<ev_idle> watchers).
		1321
		1322	If you need to suppress invocation when higher priority events are pending
		1323	you need to look at C<ev_idle> watchers, which provide this functionality.
		1324
		1325	You I<must not> change the priority of a watcher as long as it is active or
		1326	pending.
		1327
		1328	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
		1329	fine, as long as you do not mind that the priority value you query might
		1330	or might not have been clamped to the valid range.
		1331
		1332	The default priority used by watchers when no priority has been set is
		1333	always C<0>, which is supposed to not be too high and not be too low :).
		1334
		1335	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
		1336	priorities.
		1337
		1338	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
		1339
		1340	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
		1341	C<loop> nor C<revents> need to be valid as long as the watcher callback
		1342	can deal with that fact, as both are simply passed through to the
		1343	callback.
		1344
		1345	=item int ev_clear_pending (loop, ev_TYPE *watcher)
		1346
		1347	If the watcher is pending, this function clears its pending status and
		1348	returns its C<revents> bitset (as if its callback was invoked). If the
		1349	watcher isn't pending it does nothing and returns C<0>.
		1350
		1351	Sometimes it can be useful to "poll" a watcher instead of waiting for its
		1352	callback to be invoked, which can be accomplished with this function.
		1353
		1354	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
		1355
		1356	Feeds the given event set into the event loop, as if the specified event
		1357	had happened for the specified watcher (which must be a pointer to an
		1358	initialised but not necessarily started event watcher). Obviously you must
		1359	not free the watcher as long as it has pending events.
		1360
		1361	Stopping the watcher, letting libev invoke it, or calling
		1362	C<ev_clear_pending> will clear the pending event, even if the watcher was
		1363	not started in the first place.
		1364
		1365	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
		1366	functions that do not need a watcher.
		1367
		1368	=back
		1369
		1370	See also the L<ASSOCIATING CUSTOM DATA WITH A WATCHER> and L<BUILDING YOUR
		1371	OWN COMPOSITE WATCHERS> idioms.
		1372
1142	=head2 WATCHER STATES	1373	=head2 WATCHER STATES
1143		1374
1144	There are various watcher states mentioned throughout this manual -	1375	There are various watcher states mentioned throughout this manual -
1145	active, pending and so on. In this section these states and the rules to	1376	active, pending and so on. In this section these states and the rules to
1146	transition between them will be described in more detail - and while these	1377	transition between them will be described in more detail - and while these
…		…
1152		1383
1153	Before a watcher can be registered with the event looop it has to be	1384	Before a watcher can be registered with the event looop it has to be
1154	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to	1385	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
1155	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.	1386	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
1156		1387
1157	In this state it is simply some block of memory that is suitable for use	1388	In this state it is simply some block of memory that is suitable for
1158	in an event loop. It can be moved around, freed, reused etc. at will.	1389	use in an event loop. It can be moved around, freed, reused etc. at
		1390	will - as long as you either keep the memory contents intact, or call
		1391	C<ev_TYPE_init> again.
1159		1392
1160	=item started/running/active	1393	=item started/running/active
1161		1394
1162	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes	1395	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
1163	property of the event loop, and is actively waiting for events. While in	1396	property of the event loop, and is actively waiting for events. While in
…		…
1191	latter will clear any pending state the watcher might be in, regardless	1424	latter will clear any pending state the watcher might be in, regardless
1192	of whether it was active or not, so stopping a watcher explicitly before	1425	of whether it was active or not, so stopping a watcher explicitly before
1193	freeing it is often a good idea.	1426	freeing it is often a good idea.
1194		1427
1195	While stopped (and not pending) the watcher is essentially in the	1428	While stopped (and not pending) the watcher is essentially in the
1196	initialised state, that is it can be reused, moved, modified in any way	1429	initialised state, that is, it can be reused, moved, modified in any way
1197	you wish.	1430	you wish (but when you trash the memory block, you need to C<ev_TYPE_init>
		1431	it again).
1198		1432
1199	=back	1433	=back
1200
1201	=head2 GENERIC WATCHER FUNCTIONS
1202
1203	=over 4
1204
1205	=item C<ev_init> (ev_TYPE *watcher, callback)
1206
1207	This macro initialises the generic portion of a watcher. The contents
1208	of the watcher object can be arbitrary (so C<malloc> will do). Only
1209	the generic parts of the watcher are initialised, you I<need> to call
1210	the type-specific C<ev_TYPE_set> macro afterwards to initialise the
1211	type-specific parts. For each type there is also a C<ev_TYPE_init> macro
1212	which rolls both calls into one.
1213
1214	You can reinitialise a watcher at any time as long as it has been stopped
1215	(or never started) and there are no pending events outstanding.
1216
1217	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
1218	int revents)>.
1219
1220	Example: Initialise an C<ev_io> watcher in two steps.
1221
1222	ev_io w;
1223	ev_init (&w, my_cb);
1224	ev_io_set (&w, STDIN_FILENO, EV_READ);
1225
1226	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
1227
1228	This macro initialises the type-specific parts of a watcher. You need to
1229	call C<ev_init> at least once before you call this macro, but you can
1230	call C<ev_TYPE_set> any number of times. You must not, however, call this
1231	macro on a watcher that is active (it can be pending, however, which is a
1232	difference to the C<ev_init> macro).
1233
1234	Although some watcher types do not have type-specific arguments
1235	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
1236
1237	See C<ev_init>, above, for an example.
1238
1239	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
1240
1241	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro
1242	calls into a single call. This is the most convenient method to initialise
1243	a watcher. The same limitations apply, of course.
1244
1245	Example: Initialise and set an C<ev_io> watcher in one step.
1246
1247	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
1248
1249	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
1250
1251	Starts (activates) the given watcher. Only active watchers will receive
1252	events. If the watcher is already active nothing will happen.
1253
1254	Example: Start the C<ev_io> watcher that is being abused as example in this
1255	whole section.
1256
1257	ev_io_start (EV_DEFAULT_UC, &w);
1258
1259	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
1260
1261	Stops the given watcher if active, and clears the pending status (whether
1262	the watcher was active or not).
1263
1264	It is possible that stopped watchers are pending - for example,
1265	non-repeating timers are being stopped when they become pending - but
1266	calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
1267	pending. If you want to free or reuse the memory used by the watcher it is
1268	therefore a good idea to always call its C<ev_TYPE_stop> function.
1269
1270	=item bool ev_is_active (ev_TYPE *watcher)
1271
1272	Returns a true value iff the watcher is active (i.e. it has been started
1273	and not yet been stopped). As long as a watcher is active you must not modify
1274	it.
1275
1276	=item bool ev_is_pending (ev_TYPE *watcher)
1277
1278	Returns a true value iff the watcher is pending, (i.e. it has outstanding
1279	events but its callback has not yet been invoked). As long as a watcher
1280	is pending (but not active) you must not call an init function on it (but
1281	C<ev_TYPE_set> is safe), you must not change its priority, and you must
1282	make sure the watcher is available to libev (e.g. you cannot C<free ()>
1283	it).
1284
1285	=item callback ev_cb (ev_TYPE *watcher)
1286
1287	Returns the callback currently set on the watcher.
1288
1289	=item ev_cb_set (ev_TYPE *watcher, callback)
1290
1291	Change the callback. You can change the callback at virtually any time
1292	(modulo threads).
1293
1294	=item ev_set_priority (ev_TYPE *watcher, int priority)
1295
1296	=item int ev_priority (ev_TYPE *watcher)
1297
1298	Set and query the priority of the watcher. The priority is a small
1299	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
1300	(default: C<-2>). Pending watchers with higher priority will be invoked
1301	before watchers with lower priority, but priority will not keep watchers
1302	from being executed (except for C<ev_idle> watchers).
1303
1304	If you need to suppress invocation when higher priority events are pending
1305	you need to look at C<ev_idle> watchers, which provide this functionality.
1306
1307	You I<must not> change the priority of a watcher as long as it is active or
1308	pending.
1309
1310	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
1311	fine, as long as you do not mind that the priority value you query might
1312	or might not have been clamped to the valid range.
1313
1314	The default priority used by watchers when no priority has been set is
1315	always C<0>, which is supposed to not be too high and not be too low :).
1316
1317	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
1318	priorities.
1319
1320	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
1321
1322	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
1323	C<loop> nor C<revents> need to be valid as long as the watcher callback
1324	can deal with that fact, as both are simply passed through to the
1325	callback.
1326
1327	=item int ev_clear_pending (loop, ev_TYPE *watcher)
1328
1329	If the watcher is pending, this function clears its pending status and
1330	returns its C<revents> bitset (as if its callback was invoked). If the
1331	watcher isn't pending it does nothing and returns C<0>.
1332
1333	Sometimes it can be useful to "poll" a watcher instead of waiting for its
1334	callback to be invoked, which can be accomplished with this function.
1335
1336	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
1337
1338	Feeds the given event set into the event loop, as if the specified event
1339	had happened for the specified watcher (which must be a pointer to an
1340	initialised but not necessarily started event watcher). Obviously you must
1341	not free the watcher as long as it has pending events.
1342
1343	Stopping the watcher, letting libev invoke it, or calling
1344	C<ev_clear_pending> will clear the pending event, even if the watcher was
1345	not started in the first place.
1346
1347	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
1348	functions that do not need a watcher.
1349
1350	=back
1351
1352
1353	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
1354
1355	Each watcher has, by default, a member C<void *data> that you can change
1356	and read at any time: libev will completely ignore it. This can be used
1357	to associate arbitrary data with your watcher. If you need more data and
1358	don't want to allocate memory and store a pointer to it in that data
1359	member, you can also "subclass" the watcher type and provide your own
1360	data:
1361
1362	struct my_io
1363	{
1364	ev_io io;
1365	int otherfd;
1366	void *somedata;
1367	struct whatever *mostinteresting;
1368	};
1369
1370	...
1371	struct my_io w;
1372	ev_io_init (&w.io, my_cb, fd, EV_READ);
1373
1374	And since your callback will be called with a pointer to the watcher, you
1375	can cast it back to your own type:
1376
1377	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1378	{
1379	struct my_io *w = (struct my_io *)w_;
1380	...
1381	}
1382
1383	More interesting and less C-conformant ways of casting your callback type
1384	instead have been omitted.
1385
1386	Another common scenario is to use some data structure with multiple
1387	embedded watchers:
1388
1389	struct my_biggy
1390	{
1391	int some_data;
1392	ev_timer t1;
1393	ev_timer t2;
1394	}
1395
1396	In this case getting the pointer to C<my_biggy> is a bit more
1397	complicated: Either you store the address of your C<my_biggy> struct
1398	in the C<data> member of the watcher (for woozies), or you need to use
1399	some pointer arithmetic using C<offsetof> inside your watchers (for real
1400	programmers):
1401
1402	#include <stddef.h>
1403
1404	static void
1405	t1_cb (EV_P_ ev_timer *w, int revents)
1406	{
1407	struct my_biggy big = (struct my_biggy *)
1408	(((char *)w) - offsetof (struct my_biggy, t1));
1409	}
1410
1411	static void
1412	t2_cb (EV_P_ ev_timer *w, int revents)
1413	{
1414	struct my_biggy big = (struct my_biggy *)
1415	(((char *)w) - offsetof (struct my_biggy, t2));
1416	}
1417		1434
1418	=head2 WATCHER PRIORITY MODELS	1435	=head2 WATCHER PRIORITY MODELS
1419		1436
1420	Many event loops support I<watcher priorities>, which are usually small	1437	Many event loops support I<watcher priorities>, which are usually small
1421	integers that influence the ordering of event callback invocation	1438	integers that influence the ordering of event callback invocation
…		…
1548	In general you can register as many read and/or write event watchers per	1565	In general you can register as many read and/or write event watchers per
1549	fd as you want (as long as you don't confuse yourself). Setting all file	1566	fd as you want (as long as you don't confuse yourself). Setting all file
1550	descriptors to non-blocking mode is also usually a good idea (but not	1567	descriptors to non-blocking mode is also usually a good idea (but not
1551	required if you know what you are doing).	1568	required if you know what you are doing).
1552		1569
1553	If you cannot use non-blocking mode, then force the use of a
1554	known-to-be-good backend (at the time of this writing, this includes only
1555	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
1556	descriptors for which non-blocking operation makes no sense (such as
1557	files) - libev doesn't guarantee any specific behaviour in that case.
1558
1559	Another thing you have to watch out for is that it is quite easy to	1570	Another thing you have to watch out for is that it is quite easy to
1560	receive "spurious" readiness notifications, that is your callback might	1571	receive "spurious" readiness notifications, that is, your callback might
1561	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1572	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1562	because there is no data. Not only are some backends known to create a	1573	because there is no data. It is very easy to get into this situation even
1563	lot of those (for example Solaris ports), it is very easy to get into	1574	with a relatively standard program structure. Thus it is best to always
1564	this situation even with a relatively standard program structure. Thus	1575	use non-blocking I/O: An extra C<read>(2) returning C<EAGAIN> is far
1565	it is best to always use non-blocking I/O: An extra C<read>(2) returning
1566	C<EAGAIN> is far preferable to a program hanging until some data arrives.	1576	preferable to a program hanging until some data arrives.
1567		1577
1568	If you cannot run the fd in non-blocking mode (for example you should	1578	If you cannot run the fd in non-blocking mode (for example you should
1569	not play around with an Xlib connection), then you have to separately	1579	not play around with an Xlib connection), then you have to separately
1570	re-test whether a file descriptor is really ready with a known-to-be good	1580	re-test whether a file descriptor is really ready with a known-to-be good
1571	interface such as poll (fortunately in our Xlib example, Xlib already	1581	interface such as poll (fortunately in the case of Xlib, it already does
1572	does this on its own, so its quite safe to use). Some people additionally	1582	this on its own, so its quite safe to use). Some people additionally
1573	use C<SIGALRM> and an interval timer, just to be sure you won't block	1583	use C<SIGALRM> and an interval timer, just to be sure you won't block
1574	indefinitely.	1584	indefinitely.
1575		1585
1576	But really, best use non-blocking mode.	1586	But really, best use non-blocking mode.
1577		1587
…		…
1605		1615
1606	There is no workaround possible except not registering events	1616	There is no workaround possible except not registering events
1607	for potentially C<dup ()>'ed file descriptors, or to resort to	1617	for potentially C<dup ()>'ed file descriptors, or to resort to
1608	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.	1618	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1609		1619
		1620	=head3 The special problem of files
		1621
		1622	Many people try to use C<select> (or libev) on file descriptors
		1623	representing files, and expect it to become ready when their program
		1624	doesn't block on disk accesses (which can take a long time on their own).
		1625
		1626	However, this cannot ever work in the "expected" way - you get a readiness
		1627	notification as soon as the kernel knows whether and how much data is
		1628	there, and in the case of open files, that's always the case, so you
		1629	always get a readiness notification instantly, and your read (or possibly
		1630	write) will still block on the disk I/O.
		1631
		1632	Another way to view it is that in the case of sockets, pipes, character
		1633	devices and so on, there is another party (the sender) that delivers data
		1634	on its own, but in the case of files, there is no such thing: the disk
		1635	will not send data on its own, simply because it doesn't know what you
		1636	wish to read - you would first have to request some data.
		1637
		1638	Since files are typically not-so-well supported by advanced notification
		1639	mechanism, libev tries hard to emulate POSIX behaviour with respect
		1640	to files, even though you should not use it. The reason for this is
		1641	convenience: sometimes you want to watch STDIN or STDOUT, which is
		1642	usually a tty, often a pipe, but also sometimes files or special devices
		1643	(for example, C<epoll> on Linux works with F</dev/random> but not with
		1644	F</dev/urandom>), and even though the file might better be served with
		1645	asynchronous I/O instead of with non-blocking I/O, it is still useful when
		1646	it "just works" instead of freezing.
		1647
		1648	So avoid file descriptors pointing to files when you know it (e.g. use
		1649	libeio), but use them when it is convenient, e.g. for STDIN/STDOUT, or
		1650	when you rarely read from a file instead of from a socket, and want to
		1651	reuse the same code path.
		1652
1610	=head3 The special problem of fork	1653	=head3 The special problem of fork
1611		1654
1612	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit	1655	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit
1613	useless behaviour. Libev fully supports fork, but needs to be told about	1656	useless behaviour. Libev fully supports fork, but needs to be told about
1614	it in the child.	1657	it in the child if you want to continue to use it in the child.
1615		1658
1616	To support fork in your programs, you either have to call	1659	To support fork in your child processes, you have to call C<ev_loop_fork
1617	C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,	1660	()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to
1618	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1661	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1619	C<EVBACKEND_POLL>.
1620		1662
1621	=head3 The special problem of SIGPIPE	1663	=head3 The special problem of SIGPIPE
1622		1664
1623	While not really specific to libev, it is easy to forget about C<SIGPIPE>:	1665	While not really specific to libev, it is easy to forget about C<SIGPIPE>:
1624	when writing to a pipe whose other end has been closed, your program gets	1666	when writing to a pipe whose other end has been closed, your program gets
…		…
2114		2156
2115	Another way to think about it (for the mathematically inclined) is that	2157	Another way to think about it (for the mathematically inclined) is that
2116	C<ev_periodic> will try to run the callback in this mode at the next possible	2158	C<ev_periodic> will try to run the callback in this mode at the next possible
2117	time where C<time = offset (mod interval)>, regardless of any time jumps.	2159	time where C<time = offset (mod interval)>, regardless of any time jumps.
2118		2160
2119	For numerical stability it is preferable that the C<offset> value is near	2161	The C<interval> I<MUST> be positive, and for numerical stability, the
2120	C<ev_now ()> (the current time), but there is no range requirement for	2162	interval value should be higher than C<1/8192> (which is around 100
2121	this value, and in fact is often specified as zero.	2163	microseconds) and C<offset> should be higher than C<0> and should have
		2164	at most a similar magnitude as the current time (say, within a factor of
		2165	ten). Typical values for offset are, in fact, C<0> or something between
		2166	C<0> and C<interval>, which is also the recommended range.
2122		2167
2123	Note also that there is an upper limit to how often a timer can fire (CPU	2168	Note also that there is an upper limit to how often a timer can fire (CPU
2124	speed for example), so if C<interval> is very small then timing stability	2169	speed for example), so if C<interval> is very small then timing stability
2125	will of course deteriorate. Libev itself tries to be exact to be about one	2170	will of course deteriorate. Libev itself tries to be exact to be about one
2126	millisecond (if the OS supports it and the machine is fast enough).	2171	millisecond (if the OS supports it and the machine is fast enough).
…		…
2240		2285
2241	=head2 C<ev_signal> - signal me when a signal gets signalled!	2286	=head2 C<ev_signal> - signal me when a signal gets signalled!
2242		2287
2243	Signal watchers will trigger an event when the process receives a specific	2288	Signal watchers will trigger an event when the process receives a specific
2244	signal one or more times. Even though signals are very asynchronous, libev	2289	signal one or more times. Even though signals are very asynchronous, libev
2245	will try it's best to deliver signals synchronously, i.e. as part of the	2290	will try its best to deliver signals synchronously, i.e. as part of the
2246	normal event processing, like any other event.	2291	normal event processing, like any other event.
2247		2292
2248	If you want signals to be delivered truly asynchronously, just use	2293	If you want signals to be delivered truly asynchronously, just use
2249	C<sigaction> as you would do without libev and forget about sharing	2294	C<sigaction> as you would do without libev and forget about sharing
2250	the signal. You can even use C<ev_async> from a signal handler to	2295	the signal. You can even use C<ev_async> from a signal handler to
…		…
2269	=head3 The special problem of inheritance over fork/execve/pthread_create	2314	=head3 The special problem of inheritance over fork/execve/pthread_create
2270		2315
2271	Both the signal mask (C<sigprocmask>) and the signal disposition	2316	Both the signal mask (C<sigprocmask>) and the signal disposition
2272	(C<sigaction>) are unspecified after starting a signal watcher (and after	2317	(C<sigaction>) are unspecified after starting a signal watcher (and after
2273	stopping it again), that is, libev might or might not block the signal,	2318	stopping it again), that is, libev might or might not block the signal,
2274	and might or might not set or restore the installed signal handler.	2319	and might or might not set or restore the installed signal handler (but
		2320	see C<EVFLAG_NOSIGMASK>).
2275		2321
2276	While this does not matter for the signal disposition (libev never	2322	While this does not matter for the signal disposition (libev never
2277	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on	2323	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
2278	C<execve>), this matters for the signal mask: many programs do not expect	2324	C<execve>), this matters for the signal mask: many programs do not expect
2279	certain signals to be blocked.	2325	certain signals to be blocked.
…		…
2292	I<has> to modify the signal mask, at least temporarily.	2338	I<has> to modify the signal mask, at least temporarily.
2293		2339
2294	So I can't stress this enough: I<If you do not reset your signal mask when	2340	So I can't stress this enough: I<If you do not reset your signal mask when
2295	you expect it to be empty, you have a race condition in your code>. This	2341	you expect it to be empty, you have a race condition in your code>. This
2296	is not a libev-specific thing, this is true for most event libraries.	2342	is not a libev-specific thing, this is true for most event libraries.
		2343
		2344	=head3 The special problem of threads signal handling
		2345
		2346	POSIX threads has problematic signal handling semantics, specifically,
		2347	a lot of functionality (sigfd, sigwait etc.) only really works if all
		2348	threads in a process block signals, which is hard to achieve.
		2349
		2350	When you want to use sigwait (or mix libev signal handling with your own
		2351	for the same signals), you can tackle this problem by globally blocking
		2352	all signals before creating any threads (or creating them with a fully set
		2353	sigprocmask) and also specifying the C<EVFLAG_NOSIGMASK> when creating
		2354	loops. Then designate one thread as "signal receiver thread" which handles
		2355	these signals. You can pass on any signals that libev might be interested
		2356	in by calling C<ev_feed_signal>.
2297		2357
2298	=head3 Watcher-Specific Functions and Data Members	2358	=head3 Watcher-Specific Functions and Data Members
2299		2359
2300	=over 4	2360	=over 4
2301		2361
…		…
3075	disadvantage of having to use multiple event loops (which do not support	3135	disadvantage of having to use multiple event loops (which do not support
3076	signal watchers).	3136	signal watchers).
3077		3137
3078	When this is not possible, or you want to use the default loop for	3138	When this is not possible, or you want to use the default loop for
3079	other reasons, then in the process that wants to start "fresh", call	3139	other reasons, then in the process that wants to start "fresh", call
3080	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying	3140	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
3081	the default loop will "orphan" (not stop) all registered watchers, so you	3141	Destroying the default loop will "orphan" (not stop) all registered
3082	have to be careful not to execute code that modifies those watchers. Note	3142	watchers, so you have to be careful not to execute code that modifies
3083	also that in that case, you have to re-register any signal watchers.	3143	those watchers. Note also that in that case, you have to re-register any
		3144	signal watchers.
3084		3145
3085	=head3 Watcher-Specific Functions and Data Members	3146	=head3 Watcher-Specific Functions and Data Members
3086		3147
3087	=over 4	3148	=over 4
3088		3149
3089	=item ev_fork_init (ev_signal *, callback)	3150	=item ev_fork_init (ev_fork *, callback)
3090		3151
3091	Initialises and configures the fork watcher - it has no parameters of any	3152	Initialises and configures the fork watcher - it has no parameters of any
3092	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3153	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
3093	believe me.	3154	really.
3094		3155
3095	=back	3156	=back
3096		3157
3097		3158
		3159	=head2 C<ev_cleanup> - even the best things end
		3160
		3161	Cleanup watchers are called just before the event loop is being destroyed
		3162	by a call to C<ev_loop_destroy>.
		3163
		3164	While there is no guarantee that the event loop gets destroyed, cleanup
		3165	watchers provide a convenient method to install cleanup hooks for your
		3166	program, worker threads and so on - you just to make sure to destroy the
		3167	loop when you want them to be invoked.
		3168
		3169	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3170	all other watchers, they do not keep a reference to the event loop (which
		3171	makes a lot of sense if you think about it). Like all other watchers, you
		3172	can call libev functions in the callback, except C<ev_cleanup_start>.
		3173
		3174	=head3 Watcher-Specific Functions and Data Members
		3175
		3176	=over 4
		3177
		3178	=item ev_cleanup_init (ev_cleanup *, callback)
		3179
		3180	Initialises and configures the cleanup watcher - it has no parameters of
		3181	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3182	pointless, I assure you.
		3183
		3184	=back
		3185
		3186	Example: Register an atexit handler to destroy the default loop, so any
		3187	cleanup functions are called.
		3188
		3189	static void
		3190	program_exits (void)
		3191	{
		3192	ev_loop_destroy (EV_DEFAULT_UC);
		3193	}
		3194
		3195	...
		3196	atexit (program_exits);
		3197
		3198
3098	=head2 C<ev_async> - how to wake up an event loop	3199	=head2 C<ev_async> - how to wake up an event loop
3099		3200
3100	In general, you cannot use an C<ev_run> from multiple threads or other	3201	In general, you cannot use an C<ev_loop> from multiple threads or other
3101	asynchronous sources such as signal handlers (as opposed to multiple event	3202	asynchronous sources such as signal handlers (as opposed to multiple event
3102	loops - those are of course safe to use in different threads).	3203	loops - those are of course safe to use in different threads).
3103		3204
3104	Sometimes, however, you need to wake up an event loop you do not control,	3205	Sometimes, however, you need to wake up an event loop you do not control,
3105	for example because it belongs to another thread. This is what C<ev_async>	3206	for example because it belongs to another thread. This is what C<ev_async>
…		…
3107	it by calling C<ev_async_send>, which is thread- and signal safe.	3208	it by calling C<ev_async_send>, which is thread- and signal safe.
3108		3209
3109	This functionality is very similar to C<ev_signal> watchers, as signals,	3210	This functionality is very similar to C<ev_signal> watchers, as signals,
3110	too, are asynchronous in nature, and signals, too, will be compressed	3211	too, are asynchronous in nature, and signals, too, will be compressed
3111	(i.e. the number of callback invocations may be less than the number of	3212	(i.e. the number of callback invocations may be less than the number of
3112	C<ev_async_sent> calls).	3213	C<ev_async_sent> calls). In fact, you could use signal watchers as a kind
		3214	of "global async watchers" by using a watcher on an otherwise unused
		3215	signal, and C<ev_feed_signal> to signal this watcher from another thread,
		3216	even without knowing which loop owns the signal.
3113		3217
3114	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not	3218	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not
3115	just the default loop.	3219	just the default loop.
3116		3220
3117	=head3 Queueing	3221	=head3 Queueing
…		…
3212	trust me.	3316	trust me.
3213		3317
3214	=item ev_async_send (loop, ev_async *)	3318	=item ev_async_send (loop, ev_async *)
3215		3319
3216	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3320	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
3217	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3321	an C<EV_ASYNC> event on the watcher into the event loop, and instantly
		3322	returns.
		3323
3218	C<ev_feed_event>, this call is safe to do from other threads, signal or	3324	Unlike C<ev_feed_event>, this call is safe to do from other threads,
3219	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3325	signal or similar contexts (see the discussion of C<EV_ATOMIC_T> in the
3220	section below on what exactly this means).	3326	embedding section below on what exactly this means).
3221		3327
3222	Note that, as with other watchers in libev, multiple events might get	3328	Note that, as with other watchers in libev, multiple events might get
3223	compressed into a single callback invocation (another way to look at this	3329	compressed into a single callback invocation (another way to look at this
3224	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,	3330	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,
3225	reset when the event loop detects that).	3331	reset when the event loop detects that).
…		…
3293	Feed an event on the given fd, as if a file descriptor backend detected	3399	Feed an event on the given fd, as if a file descriptor backend detected
3294	the given events it.	3400	the given events it.
3295		3401
3296	=item ev_feed_signal_event (loop, int signum)	3402	=item ev_feed_signal_event (loop, int signum)
3297		3403
3298	Feed an event as if the given signal occurred (C<loop> must be the default	3404	Feed an event as if the given signal occurred. See also C<ev_feed_signal>,
3299	loop!).	3405	which is async-safe.
3300		3406
3301	=back	3407	=back
		3408
		3409
		3410	=head1 COMMON OR USEFUL IDIOMS (OR BOTH)
		3411
		3412	This section explains some common idioms that are not immediately
		3413	obvious. Note that examples are sprinkled over the whole manual, and this
		3414	section only contains stuff that wouldn't fit anywhere else.
		3415
		3416	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
		3417
		3418	Each watcher has, by default, a C<void *data> member that you can read
		3419	or modify at any time: libev will completely ignore it. This can be used
		3420	to associate arbitrary data with your watcher. If you need more data and
		3421	don't want to allocate memory separately and store a pointer to it in that
		3422	data member, you can also "subclass" the watcher type and provide your own
		3423	data:
		3424
		3425	struct my_io
		3426	{
		3427	ev_io io;
		3428	int otherfd;
		3429	void *somedata;
		3430	struct whatever *mostinteresting;
		3431	};
		3432
		3433	...
		3434	struct my_io w;
		3435	ev_io_init (&w.io, my_cb, fd, EV_READ);
		3436
		3437	And since your callback will be called with a pointer to the watcher, you
		3438	can cast it back to your own type:
		3439
		3440	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
		3441	{
		3442	struct my_io *w = (struct my_io *)w_;
		3443	...
		3444	}
		3445
		3446	More interesting and less C-conformant ways of casting your callback
		3447	function type instead have been omitted.
		3448
		3449	=head2 BUILDING YOUR OWN COMPOSITE WATCHERS
		3450
		3451	Another common scenario is to use some data structure with multiple
		3452	embedded watchers, in effect creating your own watcher that combines
		3453	multiple libev event sources into one "super-watcher":
		3454
		3455	struct my_biggy
		3456	{
		3457	int some_data;
		3458	ev_timer t1;
		3459	ev_timer t2;
		3460	}
		3461
		3462	In this case getting the pointer to C<my_biggy> is a bit more
		3463	complicated: Either you store the address of your C<my_biggy> struct in
		3464	the C<data> member of the watcher (for woozies or C++ coders), or you need
		3465	to use some pointer arithmetic using C<offsetof> inside your watchers (for
		3466	real programmers):
		3467
		3468	#include <stddef.h>
		3469
		3470	static void
		3471	t1_cb (EV_P_ ev_timer *w, int revents)
		3472	{
		3473	struct my_biggy big = (struct my_biggy *)
		3474	(((char *)w) - offsetof (struct my_biggy, t1));
		3475	}
		3476
		3477	static void
		3478	t2_cb (EV_P_ ev_timer *w, int revents)
		3479	{
		3480	struct my_biggy big = (struct my_biggy *)
		3481	(((char *)w) - offsetof (struct my_biggy, t2));
		3482	}
		3483
		3484	=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS
		3485
		3486	Often (especially in GUI toolkits) there are places where you have
		3487	I<modal> interaction, which is most easily implemented by recursively
		3488	invoking C<ev_run>.
		3489
		3490	This brings the problem of exiting - a callback might want to finish the
		3491	main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but
		3492	a modal "Are you sure?" dialog is still waiting), or just the nested one
		3493	and not the main one (e.g. user clocked "Ok" in a modal dialog), or some
		3494	other combination: In these cases, C<ev_break> will not work alone.
		3495
		3496	The solution is to maintain "break this loop" variable for each C<ev_run>
		3497	invocation, and use a loop around C<ev_run> until the condition is
		3498	triggered, using C<EVRUN_ONCE>:
		3499
		3500	// main loop
		3501	int exit_main_loop = 0;
		3502
		3503	while (!exit_main_loop)
		3504	ev_run (EV_DEFAULT_ EVRUN_ONCE);
		3505
		3506	// in a model watcher
		3507	int exit_nested_loop = 0;
		3508
		3509	while (!exit_nested_loop)
		3510	ev_run (EV_A_ EVRUN_ONCE);
		3511
		3512	To exit from any of these loops, just set the corresponding exit variable:
		3513
		3514	// exit modal loop
		3515	exit_nested_loop = 1;
		3516
		3517	// exit main program, after modal loop is finished
		3518	exit_main_loop = 1;
		3519
		3520	// exit both
		3521	exit_main_loop = exit_nested_loop = 1;
		3522
		3523	=head2 THREAD LOCKING EXAMPLE
		3524
		3525	Here is a fictitious example of how to run an event loop in a different
		3526	thread from where callbacks are being invoked and watchers are
		3527	created/added/removed.
		3528
		3529	For a real-world example, see the C<EV::Loop::Async> perl module,
		3530	which uses exactly this technique (which is suited for many high-level
		3531	languages).
		3532
		3533	The example uses a pthread mutex to protect the loop data, a condition
		3534	variable to wait for callback invocations, an async watcher to notify the
		3535	event loop thread and an unspecified mechanism to wake up the main thread.
		3536
		3537	First, you need to associate some data with the event loop:
		3538
		3539	typedef struct {
		3540	mutex_t lock; /* global loop lock */
		3541	ev_async async_w;
		3542	thread_t tid;
		3543	cond_t invoke_cv;
		3544	} userdata;
		3545
		3546	void prepare_loop (EV_P)
		3547	{
		3548	// for simplicity, we use a static userdata struct.
		3549	static userdata u;
		3550
		3551	ev_async_init (&u->async_w, async_cb);
		3552	ev_async_start (EV_A_ &u->async_w);
		3553
		3554	pthread_mutex_init (&u->lock, 0);
		3555	pthread_cond_init (&u->invoke_cv, 0);
		3556
		3557	// now associate this with the loop
		3558	ev_set_userdata (EV_A_ u);
		3559	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		3560	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		3561
		3562	// then create the thread running ev_run
		3563	pthread_create (&u->tid, 0, l_run, EV_A);
		3564	}
		3565
		3566	The callback for the C<ev_async> watcher does nothing: the watcher is used
		3567	solely to wake up the event loop so it takes notice of any new watchers
		3568	that might have been added:
		3569
		3570	static void
		3571	async_cb (EV_P_ ev_async *w, int revents)
		3572	{
		3573	// just used for the side effects
		3574	}
		3575
		3576	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		3577	protecting the loop data, respectively.
		3578
		3579	static void
		3580	l_release (EV_P)
		3581	{
		3582	userdata *u = ev_userdata (EV_A);
		3583	pthread_mutex_unlock (&u->lock);
		3584	}
		3585
		3586	static void
		3587	l_acquire (EV_P)
		3588	{
		3589	userdata *u = ev_userdata (EV_A);
		3590	pthread_mutex_lock (&u->lock);
		3591	}
		3592
		3593	The event loop thread first acquires the mutex, and then jumps straight
		3594	into C<ev_run>:
		3595
		3596	void *
		3597	l_run (void *thr_arg)
		3598	{
		3599	struct ev_loop *loop = (struct ev_loop *)thr_arg;
		3600
		3601	l_acquire (EV_A);
		3602	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		3603	ev_run (EV_A_ 0);
		3604	l_release (EV_A);
		3605
		3606	return 0;
		3607	}
		3608
		3609	Instead of invoking all pending watchers, the C<l_invoke> callback will
		3610	signal the main thread via some unspecified mechanism (signals? pipe
		3611	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		3612	have been called (in a while loop because a) spurious wakeups are possible
		3613	and b) skipping inter-thread-communication when there are no pending
		3614	watchers is very beneficial):
		3615
		3616	static void
		3617	l_invoke (EV_P)
		3618	{
		3619	userdata *u = ev_userdata (EV_A);
		3620
		3621	while (ev_pending_count (EV_A))
		3622	{
		3623	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		3624	pthread_cond_wait (&u->invoke_cv, &u->lock);
		3625	}
		3626	}
		3627
		3628	Now, whenever the main thread gets told to invoke pending watchers, it
		3629	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		3630	thread to continue:
		3631
		3632	static void
		3633	real_invoke_pending (EV_P)
		3634	{
		3635	userdata *u = ev_userdata (EV_A);
		3636
		3637	pthread_mutex_lock (&u->lock);
		3638	ev_invoke_pending (EV_A);
		3639	pthread_cond_signal (&u->invoke_cv);
		3640	pthread_mutex_unlock (&u->lock);
		3641	}
		3642
		3643	Whenever you want to start/stop a watcher or do other modifications to an
		3644	event loop, you will now have to lock:
		3645
		3646	ev_timer timeout_watcher;
		3647	userdata *u = ev_userdata (EV_A);
		3648
		3649	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		3650
		3651	pthread_mutex_lock (&u->lock);
		3652	ev_timer_start (EV_A_ &timeout_watcher);
		3653	ev_async_send (EV_A_ &u->async_w);
		3654	pthread_mutex_unlock (&u->lock);
		3655
		3656	Note that sending the C<ev_async> watcher is required because otherwise
		3657	an event loop currently blocking in the kernel will have no knowledge
		3658	about the newly added timer. By waking up the loop it will pick up any new
		3659	watchers in the next event loop iteration.
		3660
		3661	=head2 THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS
		3662
		3663	While the overhead of a callback that e.g. schedules a thread is small, it
		3664	is still an overhead. If you embed libev, and your main usage is with some
		3665	kind of threads or coroutines, you might want to customise libev so that
		3666	doesn't need callbacks anymore.
		3667
		3668	Imagine you have coroutines that you can switch to using a function
		3669	C<switch_to (coro)>, that libev runs in a coroutine called C<libev_coro>
		3670	and that due to some magic, the currently active coroutine is stored in a
		3671	global called C<current_coro>. Then you can build your own "wait for libev
		3672	event" primitive by changing C<EV_CB_DECLARE> and C<EV_CB_INVOKE> (note
		3673	the differing C<;> conventions):
		3674
		3675	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3676	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb)
		3677
		3678	That means instead of having a C callback function, you store the
		3679	coroutine to switch to in each watcher, and instead of having libev call
		3680	your callback, you instead have it switch to that coroutine.
		3681
		3682	A coroutine might now wait for an event with a function called
		3683	C<wait_for_event>. (the watcher needs to be started, as always, but it doesn't
		3684	matter when, or whether the watcher is active or not when this function is
		3685	called):
		3686
		3687	void
		3688	wait_for_event (ev_watcher *w)
		3689	{
		3690	ev_cb_set (w) = current_coro;
		3691	switch_to (libev_coro);
		3692	}
		3693
		3694	That basically suspends the coroutine inside C<wait_for_event> and
		3695	continues the libev coroutine, which, when appropriate, switches back to
		3696	this or any other coroutine. I am sure if you sue this your own :)
		3697
		3698	You can do similar tricks if you have, say, threads with an event queue -
		3699	instead of storing a coroutine, you store the queue object and instead of
		3700	switching to a coroutine, you push the watcher onto the queue and notify
		3701	any waiters.
		3702
		3703	To embed libev, see L<EMBEDDING>, but in short, it's easiest to create two
		3704	files, F<my_ev.h> and F<my_ev.c> that include the respective libev files:
		3705
		3706	// my_ev.h
		3707	#define EV_CB_DECLARE(type) struct my_coro *cb;
		3708	#define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb);
		3709	#include "../libev/ev.h"
		3710
		3711	// my_ev.c
		3712	#define EV_H "my_ev.h"
		3713	#include "../libev/ev.c"
		3714
		3715	And then use F<my_ev.h> when you would normally use F<ev.h>, and compile
		3716	F<my_ev.c> into your project. When properly specifying include paths, you
		3717	can even use F<ev.h> as header file name directly.
3302		3718
3303		3719
3304	=head1 LIBEVENT EMULATION	3720	=head1 LIBEVENT EMULATION
3305		3721
3306	Libev offers a compatibility emulation layer for libevent. It cannot	3722	Libev offers a compatibility emulation layer for libevent. It cannot
3307	emulate the internals of libevent, so here are some usage hints:	3723	emulate the internals of libevent, so here are some usage hints:
3308		3724
3309	=over 4	3725	=over 4
		3726
		3727	=item * Only the libevent-1.4.1-beta API is being emulated.
		3728
		3729	This was the newest libevent version available when libev was implemented,
		3730	and is still mostly unchanged in 2010.
3310		3731
3311	=item * Use it by including <event.h>, as usual.	3732	=item * Use it by including <event.h>, as usual.
3312		3733
3313	=item * The following members are fully supported: ev_base, ev_callback,	3734	=item * The following members are fully supported: ev_base, ev_callback,
3314	ev_arg, ev_fd, ev_res, ev_events.	3735	ev_arg, ev_fd, ev_res, ev_events.
…		…
3320	=item * Priorities are not currently supported. Initialising priorities	3741	=item * Priorities are not currently supported. Initialising priorities
3321	will fail and all watchers will have the same priority, even though there	3742	will fail and all watchers will have the same priority, even though there
3322	is an ev_pri field.	3743	is an ev_pri field.
3323		3744
3324	=item * In libevent, the last base created gets the signals, in libev, the	3745	=item * In libevent, the last base created gets the signals, in libev, the
3325	first base created (== the default loop) gets the signals.	3746	base that registered the signal gets the signals.
3326		3747
3327	=item * Other members are not supported.	3748	=item * Other members are not supported.
3328		3749
3329	=item * The libev emulation is I<not> ABI compatible to libevent, you need	3750	=item * The libev emulation is I<not> ABI compatible to libevent, you need
3330	to use the libev header file and library.	3751	to use the libev header file and library.
…		…
3349	Care has been taken to keep the overhead low. The only data member the C++	3770	Care has been taken to keep the overhead low. The only data member the C++
3350	classes add (compared to plain C-style watchers) is the event loop pointer	3771	classes add (compared to plain C-style watchers) is the event loop pointer
3351	that the watcher is associated with (or no additional members at all if	3772	that the watcher is associated with (or no additional members at all if
3352	you disable C<EV_MULTIPLICITY> when embedding libev).	3773	you disable C<EV_MULTIPLICITY> when embedding libev).
3353		3774
3354	Currently, functions, and static and non-static member functions can be	3775	Currently, functions, static and non-static member functions and classes
3355	used as callbacks. Other types should be easy to add as long as they only	3776	with C<operator ()> can be used as callbacks. Other types should be easy
3356	need one additional pointer for context. If you need support for other	3777	to add as long as they only need one additional pointer for context. If
3357	types of functors please contact the author (preferably after implementing	3778	you need support for other types of functors please contact the author
3358	it).	3779	(preferably after implementing it).
3359		3780
3360	Here is a list of things available in the C<ev> namespace:	3781	Here is a list of things available in the C<ev> namespace:
3361		3782
3362	=over 4	3783	=over 4
3363		3784
…		…
3791	F<event.h> that are not directly supported by the libev core alone.	4212	F<event.h> that are not directly supported by the libev core alone.
3792		4213
3793	In standalone mode, libev will still try to automatically deduce the	4214	In standalone mode, libev will still try to automatically deduce the
3794	configuration, but has to be more conservative.	4215	configuration, but has to be more conservative.
3795		4216
		4217	=item EV_USE_FLOOR
		4218
		4219	If defined to be C<1>, libev will use the C<floor ()> function for its
		4220	periodic reschedule calculations, otherwise libev will fall back on a
		4221	portable (slower) implementation. If you enable this, you usually have to
		4222	link against libm or something equivalent. Enabling this when the C<floor>
		4223	function is not available will fail, so the safe default is to not enable
		4224	this.
		4225
3796	=item EV_USE_MONOTONIC	4226	=item EV_USE_MONOTONIC
3797		4227
3798	If defined to be C<1>, libev will try to detect the availability of the	4228	If defined to be C<1>, libev will try to detect the availability of the
3799	monotonic clock option at both compile time and runtime. Otherwise no	4229	monotonic clock option at both compile time and runtime. Otherwise no
3800	use of the monotonic clock option will be attempted. If you enable this,	4230	use of the monotonic clock option will be attempted. If you enable this,
…		…
4231	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4661	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
4232		4662
4233	#include "ev_cpp.h"	4663	#include "ev_cpp.h"
4234	#include "ev.c"	4664	#include "ev.c"
4235		4665
4236	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES	4666	=head1 INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT
4237		4667
4238	=head2 THREADS AND COROUTINES	4668	=head2 THREADS AND COROUTINES
4239		4669
4240	=head3 THREADS	4670	=head3 THREADS
4241		4671
…		…
4292	default loop and triggering an C<ev_async> watcher from the default loop	4722	default loop and triggering an C<ev_async> watcher from the default loop
4293	watcher callback into the event loop interested in the signal.	4723	watcher callback into the event loop interested in the signal.
4294		4724
4295	=back	4725	=back
4296		4726
4297	=head4 THREAD LOCKING EXAMPLE	4727	See also L<THREAD LOCKING EXAMPLE>.
4298
4299	Here is a fictitious example of how to run an event loop in a different
4300	thread than where callbacks are being invoked and watchers are
4301	created/added/removed.
4302
4303	For a real-world example, see the C<EV::Loop::Async> perl module,
4304	which uses exactly this technique (which is suited for many high-level
4305	languages).
4306
4307	The example uses a pthread mutex to protect the loop data, a condition
4308	variable to wait for callback invocations, an async watcher to notify the
4309	event loop thread and an unspecified mechanism to wake up the main thread.
4310
4311	First, you need to associate some data with the event loop:
4312
4313	typedef struct {
4314	mutex_t lock; /* global loop lock */
4315	ev_async async_w;
4316	thread_t tid;
4317	cond_t invoke_cv;
4318	} userdata;
4319
4320	void prepare_loop (EV_P)
4321	{
4322	// for simplicity, we use a static userdata struct.
4323	static userdata u;
4324
4325	ev_async_init (&u->async_w, async_cb);
4326	ev_async_start (EV_A_ &u->async_w);
4327
4328	pthread_mutex_init (&u->lock, 0);
4329	pthread_cond_init (&u->invoke_cv, 0);
4330
4331	// now associate this with the loop
4332	ev_set_userdata (EV_A_ u);
4333	ev_set_invoke_pending_cb (EV_A_ l_invoke);
4334	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
4335
4336	// then create the thread running ev_loop
4337	pthread_create (&u->tid, 0, l_run, EV_A);
4338	}
4339
4340	The callback for the C<ev_async> watcher does nothing: the watcher is used
4341	solely to wake up the event loop so it takes notice of any new watchers
4342	that might have been added:
4343
4344	static void
4345	async_cb (EV_P_ ev_async *w, int revents)
4346	{
4347	// just used for the side effects
4348	}
4349
4350	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
4351	protecting the loop data, respectively.
4352
4353	static void
4354	l_release (EV_P)
4355	{
4356	userdata *u = ev_userdata (EV_A);
4357	pthread_mutex_unlock (&u->lock);
4358	}
4359
4360	static void
4361	l_acquire (EV_P)
4362	{
4363	userdata *u = ev_userdata (EV_A);
4364	pthread_mutex_lock (&u->lock);
4365	}
4366
4367	The event loop thread first acquires the mutex, and then jumps straight
4368	into C<ev_run>:
4369
4370	void *
4371	l_run (void *thr_arg)
4372	{
4373	struct ev_loop *loop = (struct ev_loop *)thr_arg;
4374
4375	l_acquire (EV_A);
4376	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
4377	ev_run (EV_A_ 0);
4378	l_release (EV_A);
4379
4380	return 0;
4381	}
4382
4383	Instead of invoking all pending watchers, the C<l_invoke> callback will
4384	signal the main thread via some unspecified mechanism (signals? pipe
4385	writes? C<Async::Interrupt>?) and then waits until all pending watchers
4386	have been called (in a while loop because a) spurious wakeups are possible
4387	and b) skipping inter-thread-communication when there are no pending
4388	watchers is very beneficial):
4389
4390	static void
4391	l_invoke (EV_P)
4392	{
4393	userdata *u = ev_userdata (EV_A);
4394
4395	while (ev_pending_count (EV_A))
4396	{
4397	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
4398	pthread_cond_wait (&u->invoke_cv, &u->lock);
4399	}
4400	}
4401
4402	Now, whenever the main thread gets told to invoke pending watchers, it
4403	will grab the lock, call C<ev_invoke_pending> and then signal the loop
4404	thread to continue:
4405
4406	static void
4407	real_invoke_pending (EV_P)
4408	{
4409	userdata *u = ev_userdata (EV_A);
4410
4411	pthread_mutex_lock (&u->lock);
4412	ev_invoke_pending (EV_A);
4413	pthread_cond_signal (&u->invoke_cv);
4414	pthread_mutex_unlock (&u->lock);
4415	}
4416
4417	Whenever you want to start/stop a watcher or do other modifications to an
4418	event loop, you will now have to lock:
4419
4420	ev_timer timeout_watcher;
4421	userdata *u = ev_userdata (EV_A);
4422
4423	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
4424
4425	pthread_mutex_lock (&u->lock);
4426	ev_timer_start (EV_A_ &timeout_watcher);
4427	ev_async_send (EV_A_ &u->async_w);
4428	pthread_mutex_unlock (&u->lock);
4429
4430	Note that sending the C<ev_async> watcher is required because otherwise
4431	an event loop currently blocking in the kernel will have no knowledge
4432	about the newly added timer. By waking up the loop it will pick up any new
4433	watchers in the next event loop iteration.
4434		4728
4435	=head3 COROUTINES	4729	=head3 COROUTINES
4436		4730
4437	Libev is very accommodating to coroutines ("cooperative threads"):	4731	Libev is very accommodating to coroutines ("cooperative threads"):
4438	libev fully supports nesting calls to its functions from different	4732	libev fully supports nesting calls to its functions from different
…		…
4707	structure (guaranteed by POSIX but not by ISO C for example), but it also	5001	structure (guaranteed by POSIX but not by ISO C for example), but it also
4708	assumes that the same (machine) code can be used to call any watcher	5002	assumes that the same (machine) code can be used to call any watcher
4709	callback: The watcher callbacks have different type signatures, but libev	5003	callback: The watcher callbacks have different type signatures, but libev
4710	calls them using an C<ev_watcher *> internally.	5004	calls them using an C<ev_watcher *> internally.
4711		5005
		5006	=item pointer accesses must be thread-atomic
		5007
		5008	Accessing a pointer value must be atomic, it must both be readable and
		5009	writable in one piece - this is the case on all current architectures.
		5010
4712	=item C<sig_atomic_t volatile> must be thread-atomic as well	5011	=item C<sig_atomic_t volatile> must be thread-atomic as well
4713		5012
4714	The type C<sig_atomic_t volatile> (or whatever is defined as	5013	The type C<sig_atomic_t volatile> (or whatever is defined as
4715	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different	5014	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
4716	threads. This is not part of the specification for C<sig_atomic_t>, but is	5015	threads. This is not part of the specification for C<sig_atomic_t>, but is
…		…
4822	=back	5121	=back
4823		5122
4824		5123
4825	=head1 PORTING FROM LIBEV 3.X TO 4.X	5124	=head1 PORTING FROM LIBEV 3.X TO 4.X
4826		5125
4827	The major version 4 introduced some minor incompatible changes to the API.	5126	The major version 4 introduced some incompatible changes to the API.
4828		5127
4829	At the moment, the C<ev.h> header file tries to implement superficial	5128	At the moment, the C<ev.h> header file provides compatibility definitions
4830	compatibility, so most programs should still compile. Those might be	5129	for all changes, so most programs should still compile. The compatibility
4831	removed in later versions of libev, so better update early than late.	5130	layer might be removed in later versions of libev, so better update to the
		5131	new API early than late.
4832		5132
4833	=over 4	5133	=over 4
		5134
		5135	=item C<EV_COMPAT3> backwards compatibility mechanism
		5136
		5137	The backward compatibility mechanism can be controlled by
		5138	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		5139	section.
		5140
		5141	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		5142
		5143	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		5144
		5145	ev_loop_destroy (EV_DEFAULT_UC);
		5146	ev_loop_fork (EV_DEFAULT);
4834		5147
4835	=item function/symbol renames	5148	=item function/symbol renames
4836		5149
4837	A number of functions and symbols have been renamed:	5150	A number of functions and symbols have been renamed:
4838		5151
…		…
4857	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme	5170	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
4858	as all other watcher types. Note that C<ev_loop_fork> is still called	5171	as all other watcher types. Note that C<ev_loop_fork> is still called
4859	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>	5172	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
4860	typedef.	5173	typedef.
4861		5174
4862	=item C<EV_COMPAT3> backwards compatibility mechanism
4863
4864	The backward compatibility mechanism can be controlled by
4865	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
4866	section.
4867
4868	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>	5175	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
4869		5176
4870	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different	5177	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
4871	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile	5178	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
4872	and work, but the library code will of course be larger.	5179	and work, but the library code will of course be larger.
…		…
4934	The physical time that is observed. It is apparently strictly monotonic :)	5241	The physical time that is observed. It is apparently strictly monotonic :)
4935		5242
4936	=item wall-clock time	5243	=item wall-clock time
4937		5244
4938	The time and date as shown on clocks. Unlike real time, it can actually	5245	The time and date as shown on clocks. Unlike real time, it can actually
4939	be wrong and jump forwards and backwards, e.g. when the you adjust your	5246	be wrong and jump forwards and backwards, e.g. when you adjust your
4940	clock.	5247	clock.
4941		5248
4942	=item watcher	5249	=item watcher
4943		5250
4944	A data structure that describes interest in certain events. Watchers need	5251	A data structure that describes interest in certain events. Watchers need
…		…
4946		5253
4947	=back	5254	=back
4948		5255
4949	=head1 AUTHOR	5256	=head1 AUTHOR
4950		5257
4951	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.	5258	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5259	Magnusson and Emanuele Giaquinta, and minor corrections by many others.
4952		5260

Diff Legend

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