[ViewVC] Diff of: cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.318 by root, Fri Oct 22 09:40:22 2010 UTC vs.
Revision 1.355 by root, Tue Jan 11 01:41:56 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);
…		…
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
…		…
193	as this indicates an incompatible change. Minor versions are usually	201	as this indicates an incompatible change. Minor versions are usually
194	compatible to older versions, so a larger minor version alone is usually	202	compatible to older versions, so a larger minor version alone is usually
195	not a problem.	203	not a problem.
196		204
197	Example: Make sure we haven't accidentally been linked against the wrong	205	Example: Make sure we haven't accidentally been linked against the wrong
198	version (note, however, that this will not detect ABI mismatches :).	206	version (note, however, that this will not detect other ABI mismatches,
		207	such as LFS or reentrancy).
199		208
200	assert (("libev version mismatch",	209	assert (("libev version mismatch",
201	ev_version_major () == EV_VERSION_MAJOR	210	ev_version_major () == EV_VERSION_MAJOR
202	&& ev_version_minor () >= EV_VERSION_MINOR));	211	&& ev_version_minor () >= EV_VERSION_MINOR));
203		212
…		…
225	probe for if you specify no backends explicitly.	234	probe for if you specify no backends explicitly.
226		235
227	=item unsigned int ev_embeddable_backends ()	236	=item unsigned int ev_embeddable_backends ()
228		237
229	Returns the set of backends that are embeddable in other event loops. This	238	Returns the set of backends that are embeddable in other event loops. This
230	is the theoretical, all-platform, value. To find which backends	239	value is platform-specific but can include backends not available on the
231	might be supported on the current system, you would need to look at	240	current system. To find which embeddable backends might be supported on
232	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	241	the current system, you would need to look at C<ev_embeddable_backends ()
233	recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
234		243
235	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
236		245
237	=item ev_set_allocator (void (cb)(void *ptr, long size)) [NOT REENTRANT]	246	=item ev_set_allocator (void (cb)(void *ptr, long size))
238		247
239	Sets the allocation function to use (the prototype is similar - the	248	Sets the allocation function to use (the prototype is similar - the
240	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
241	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
242	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
…		…
268	}	277	}
269		278
270	...	279	...
271	ev_set_allocator (persistent_realloc);	280	ev_set_allocator (persistent_realloc);
272		281
273	=item ev_set_syserr_cb (void (cb)(const char msg)); [NOT REENTRANT]	282	=item ev_set_syserr_cb (void (cb)(const char msg))
274		283
275	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
276	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
277	indicating the system call or subsystem causing the problem. If this	286	indicating the system call or subsystem causing the problem. If this
278	callback is set, then libev will expect it to remedy the situation, no	287	callback is set, then libev will expect it to remedy the situation, no
…		…
290	}	299	}
291		300
292	...	301	...
293	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
294		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
295	=back	317	=back
296		318
297	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	319	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
298		320
299	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
300	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
301	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).
302		324
303	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
304	supports signals and child events, and dynamically created event loops	326	supports child process events, and dynamically created event loops which
305	which do not.	327	do not.
306		328
307	=over 4	329	=over 4
308		330
309	=item struct ev_loop *ev_default_loop (unsigned int flags)	331	=item struct ev_loop *ev_default_loop (unsigned int flags)
310		332
311	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
312	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
313	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
314	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".
315		343
316	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
317	function.	345	function (or via the C<EV_DEFAULT> macro).
318		346
319	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
320	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
321	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).
322		351
323	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,
324	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
325	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
326	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
327	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	356	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
328	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.
329		376
330	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
331	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>).
332		379
333	The following flags are supported:	380	The following flags are supported:
…		…
368	environment variable.	415	environment variable.
369		416
370	=item C<EVFLAG_NOINOTIFY>	417	=item C<EVFLAG_NOINOTIFY>
371		418
372	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
373	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
374	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
375	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.
376		423
377	=item C<EVFLAG_SIGNALFD>	424	=item C<EVFLAG_SIGNALFD>
378		425
379	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
380	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
381	delivers signals synchronously, which makes it both faster and might make	428	delivers signals synchronously, which makes it both faster and might make
382	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
383	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
384	threads that are not interested in handling them.	431	threads that are not interested in handling them.
385		432
386	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
387	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
388	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	This flag's behaviour will become the default in future versions of libev.
389		448
390	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	449	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
391		450
392	This is your standard select(2) backend. Not I<completely> standard, as	451	This is your standard select(2) backend. Not I<completely> standard, as
393	libev tries to roll its own fd_set with no limits on the number of fds,	452	libev tries to roll its own fd_set with no limits on the number of fds,
…		…
429	epoll scales either O(1) or O(active_fds).	488	epoll scales either O(1) or O(active_fds).
430		489
431	The epoll mechanism deserves honorable mention as the most misdesigned	490	The epoll mechanism deserves honorable mention as the most misdesigned
432	of the more advanced event mechanisms: mere annoyances include silently	491	of the more advanced event mechanisms: mere annoyances include silently
433	dropping file descriptors, requiring a system call per change per file	492	dropping file descriptors, requiring a system call per change per file
434	descriptor (and unnecessary guessing of parameters), problems with dup and	493	descriptor (and unnecessary guessing of parameters), problems with dup,
		494	returning before the timeout value, resulting in additional iterations
		495	(and only giving 5ms accuracy while select on the same platform gives
435	so on. The biggest issue is fork races, however - if a program forks then	496	0.1ms) and so on. The biggest issue is fork races, however - if a program
436	I<both> parent and child process have to recreate the epoll set, which can	497	forks then I<both> parent and child process have to recreate the epoll
437	take considerable time (one syscall per file descriptor) and is of course	498	set, which can take considerable time (one syscall per file descriptor)
438	hard to detect.	499	and is of course hard to detect.
439		500
440	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but	501	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
441	of course I<doesn't>, and epoll just loves to report events for totally	502	of course I<doesn't>, and epoll just loves to report events for totally
442	I<different> file descriptors (even already closed ones, so one cannot	503	I<different> file descriptors (even already closed ones, so one cannot
443	even remove them from the set) than registered in the set (especially	504	even remove them from the set) than registered in the set (especially
…		…
445	employing an additional generation counter and comparing that against the	506	employing an additional generation counter and comparing that against the
446	events to filter out spurious ones, recreating the set when required. Last	507	events to filter out spurious ones, recreating the set when required. Last
447	not least, it also refuses to work with some file descriptors which work	508	not least, it also refuses to work with some file descriptors which work
448	perfectly fine with C<select> (files, many character devices...).	509	perfectly fine with C<select> (files, many character devices...).
449		510
		511	Epoll is truly the train wreck analog among event poll mechanisms,
		512	a frankenpoll, cobbled together in a hurry, no thought to design or
		513	interaction with others.
		514
450	While stopping, setting and starting an I/O watcher in the same iteration	515	While stopping, setting and starting an I/O watcher in the same iteration
451	will result in some caching, there is still a system call per such	516	will result in some caching, there is still a system call per such
452	incident (because the same I<file descriptor> could point to a different	517	incident (because the same I<file descriptor> could point to a different
453	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed	518	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
454	file descriptors might not work very well if you register events for both	519	file descriptors might not work very well if you register events for both
…		…
519	=item C<EVBACKEND_PORT> (value 32, Solaris 10)	584	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
520		585
521	This uses the Solaris 10 event port mechanism. As with everything on Solaris,	586	This uses the Solaris 10 event port mechanism. As with everything on Solaris,
522	it's really slow, but it still scales very well (O(active_fds)).	587	it's really slow, but it still scales very well (O(active_fds)).
523		588
524	Please note that Solaris event ports can deliver a lot of spurious
525	notifications, so you need to use non-blocking I/O or other means to avoid
526	blocking when no data (or space) is available.
527
528	While this backend scales well, it requires one system call per active	589	While this backend scales well, it requires one system call per active
529	file descriptor per loop iteration. For small and medium numbers of file	590	file descriptor per loop iteration. For small and medium numbers of file
530	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	591	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
531	might perform better.	592	might perform better.
532		593
533	On the positive side, with the exception of the spurious readiness	594	On the positive side, this backend actually performed fully to
534	notifications, this backend actually performed fully to specification
535	in all tests and is fully embeddable, which is a rare feat among the	595	specification in all tests and is fully embeddable, which is a rare feat
536	OS-specific backends (I vastly prefer correctness over speed hacks).	596	among the OS-specific backends (I vastly prefer correctness over speed
		597	hacks).
		598
		599	On the negative side, the interface is I<bizarre> - so bizarre that
		600	even sun itself gets it wrong in their code examples: The event polling
		601	function sometimes returning events to the caller even though an error
		602	occurred, but with no indication whether it has done so or not (yes, it's
		603	even documented that way) - deadly for edge-triggered interfaces where
		604	you absolutely have to know whether an event occurred or not because you
		605	have to re-arm the watcher.
		606
		607	Fortunately libev seems to be able to work around these idiocies.
537		608
538	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	609	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
539	C<EVBACKEND_POLL>.	610	C<EVBACKEND_POLL>.
540		611
541	=item C<EVBACKEND_ALL>	612	=item C<EVBACKEND_ALL>
542		613
543	Try all backends (even potentially broken ones that wouldn't be tried	614	Try all backends (even potentially broken ones that wouldn't be tried
544	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as	615	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
545	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.	616	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
546		617
547	It is definitely not recommended to use this flag.	618	It is definitely not recommended to use this flag, use whatever
		619	C<ev_recommended_backends ()> returns, or simply do not specify a backend
		620	at all.
		621
		622	=item C<EVBACKEND_MASK>
		623
		624	Not a backend at all, but a mask to select all backend bits from a
		625	C<flags> value, in case you want to mask out any backends from a flags
		626	value (e.g. when modifying the C<LIBEV_FLAGS> environment variable).
548		627
549	=back	628	=back
550		629
551	If one or more of the backend flags are or'ed into the flags value,	630	If one or more of the backend flags are or'ed into the flags value,
552	then only these backends will be tried (in the reverse order as listed	631	then only these backends will be tried (in the reverse order as listed
553	here). If none are specified, all backends in C<ev_recommended_backends	632	here). If none are specified, all backends in C<ev_recommended_backends
554	()> will be tried.	633	()> will be tried.
555		634
556	Example: This is the most typical usage.
557
558	if (!ev_default_loop (0))
559	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
560
561	Example: Restrict libev to the select and poll backends, and do not allow
562	environment settings to be taken into account:
563
564	ev_default_loop (EVBACKEND_POLL \| EVBACKEND_SELECT \| EVFLAG_NOENV);
565
566	Example: Use whatever libev has to offer, but make sure that kqueue is
567	used if available (warning, breaks stuff, best use only with your own
568	private event loop and only if you know the OS supports your types of
569	fds):
570
571	ev_default_loop (ev_recommended_backends () \| EVBACKEND_KQUEUE);
572
573	=item struct ev_loop *ev_loop_new (unsigned int flags)
574
575	Similar to C<ev_default_loop>, but always creates a new event loop that is
576	always distinct from the default loop.
577
578	Note that this function I<is> thread-safe, and one common way to use
579	libev with threads is indeed to create one loop per thread, and using the
580	default loop in the "main" or "initial" thread.
581
582	Example: Try to create a event loop that uses epoll and nothing else.	635	Example: Try to create a event loop that uses epoll and nothing else.
583		636
584	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL \| EVFLAG_NOENV);	637	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL \| EVFLAG_NOENV);
585	if (!epoller)	638	if (!epoller)
586	fatal ("no epoll found here, maybe it hides under your chair");	639	fatal ("no epoll found here, maybe it hides under your chair");
587		640
		641	Example: Use whatever libev has to offer, but make sure that kqueue is
		642	used if available.
		643
		644	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () \| EVBACKEND_KQUEUE);
		645
588	=item ev_default_destroy ()	646	=item ev_loop_destroy (loop)
589		647
590	Destroys the default loop (frees all memory and kernel state etc.). None	648	Destroys an event loop object (frees all memory and kernel state
591	of the active event watchers will be stopped in the normal sense, so	649	etc.). None of the active event watchers will be stopped in the normal
592	e.g. C<ev_is_active> might still return true. It is your responsibility to	650	sense, so e.g. C<ev_is_active> might still return true. It is your
593	either stop all watchers cleanly yourself I<before> calling this function,	651	responsibility to either stop all watchers cleanly yourself I<before>
594	or cope with the fact afterwards (which is usually the easiest thing, you	652	calling this function, or cope with the fact afterwards (which is usually
595	can just ignore the watchers and/or C<free ()> them for example).	653	the easiest thing, you can just ignore the watchers and/or C<free ()> them
		654	for example).
596		655
597	Note that certain global state, such as signal state (and installed signal	656	Note that certain global state, such as signal state (and installed signal
598	handlers), will not be freed by this function, and related watchers (such	657	handlers), will not be freed by this function, and related watchers (such
599	as signal and child watchers) would need to be stopped manually.	658	as signal and child watchers) would need to be stopped manually.
600		659
601	In general it is not advisable to call this function except in the	660	This function is normally used on loop objects allocated by
602	rare occasion where you really need to free e.g. the signal handling	661	C<ev_loop_new>, but it can also be used on the default loop returned by
		662	C<ev_default_loop>, in which case it is not thread-safe.
		663
		664	Note that it is not advisable to call this function on the default loop
		665	except in the rare occasion where you really need to free its resources.
603	pipe fds. If you need dynamically allocated loops it is better to use	666	If you need dynamically allocated loops it is better to use C<ev_loop_new>
604	C<ev_loop_new> and C<ev_loop_destroy>.	667	and C<ev_loop_destroy>.
605		668
606	=item ev_loop_destroy (loop)	669	=item ev_loop_fork (loop)
607		670
608	Like C<ev_default_destroy>, but destroys an event loop created by an
609	earlier call to C<ev_loop_new>.
610
611	=item ev_default_fork ()
612
613	This function sets a flag that causes subsequent C<ev_run> iterations	671	This function sets a flag that causes subsequent C<ev_run> iterations to
614	to reinitialise the kernel state for backends that have one. Despite the	672	reinitialise the kernel state for backends that have one. Despite the
615	name, you can call it anytime, but it makes most sense after forking, in	673	name, you can call it anytime, but it makes most sense after forking, in
616	the child process (or both child and parent, but that again makes little	674	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
617	sense). You I<must> call it in the child before using any of the libev	675	child before resuming or calling C<ev_run>.
618	functions, and it will only take effect at the next C<ev_run> iteration.
619		676
620	Again, you I<have> to call it on I<any> loop that you want to re-use after	677	Again, you I<have> to call it on I<any> loop that you want to re-use after
621	a fork, I<even if you do not plan to use the loop in the parent>. This is	678	a fork, I<even if you do not plan to use the loop in the parent>. This is
622	because some kernel interfaces cough I<kqueue> cough do funny things	679	because some kernel interfaces cough I<kqueue> cough do funny things
623	during fork.	680	during fork.
…		…
628	call it at all (in fact, C<epoll> is so badly broken that it makes a	685	call it at all (in fact, C<epoll> is so badly broken that it makes a
629	difference, but libev will usually detect this case on its own and do a	686	difference, but libev will usually detect this case on its own and do a
630	costly reset of the backend).	687	costly reset of the backend).
631		688
632	The function itself is quite fast and it's usually not a problem to call	689	The function itself is quite fast and it's usually not a problem to call
633	it just in case after a fork. To make this easy, the function will fit in	690	it just in case after a fork.
634	quite nicely into a call to C<pthread_atfork>:
635		691
		692	Example: Automate calling C<ev_loop_fork> on the default loop when
		693	using pthreads.
		694
		695	static void
		696	post_fork_child (void)
		697	{
		698	ev_loop_fork (EV_DEFAULT);
		699	}
		700
		701	...
636	pthread_atfork (0, 0, ev_default_fork);	702	pthread_atfork (0, 0, post_fork_child);
637
638	=item ev_loop_fork (loop)
639
640	Like C<ev_default_fork>, but acts on an event loop created by
641	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
642	after fork that you want to re-use in the child, and how you keep track of
643	them is entirely your own problem.
644		703
645	=item int ev_is_default_loop (loop)	704	=item int ev_is_default_loop (loop)
646		705
647	Returns true when the given loop is, in fact, the default loop, and false	706	Returns true when the given loop is, in fact, the default loop, and false
648	otherwise.	707	otherwise.
…		…
659	prepare and check phases.	718	prepare and check phases.
660		719
661	=item unsigned int ev_depth (loop)	720	=item unsigned int ev_depth (loop)
662		721
663	Returns the number of times C<ev_run> was entered minus the number of	722	Returns the number of times C<ev_run> was entered minus the number of
664	times C<ev_run> was exited, in other words, the recursion depth.	723	times C<ev_run> was exited normally, in other words, the recursion depth.
665		724
666	Outside C<ev_run>, this number is zero. In a callback, this number is	725	Outside C<ev_run>, this number is zero. In a callback, this number is
667	C<1>, unless C<ev_run> was invoked recursively (or from another thread),	726	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
668	in which case it is higher.	727	in which case it is higher.
669		728
670	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread	729	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread,
671	etc.), doesn't count as "exit" - consider this as a hint to avoid such	730	throwing an exception etc.), doesn't count as "exit" - consider this
672	ungentleman-like behaviour unless it's really convenient.	731	as a hint to avoid such ungentleman-like behaviour unless it's really
		732	convenient, in which case it is fully supported.
673		733
674	=item unsigned int ev_backend (loop)	734	=item unsigned int ev_backend (loop)
675		735
676	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	736	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
677	use.	737	use.
…		…
738	relying on all watchers to be stopped when deciding when a program has	798	relying on all watchers to be stopped when deciding when a program has
739	finished (especially in interactive programs), but having a program	799	finished (especially in interactive programs), but having a program
740	that automatically loops as long as it has to and no longer by virtue	800	that automatically loops as long as it has to and no longer by virtue
741	of relying on its watchers stopping correctly, that is truly a thing of	801	of relying on its watchers stopping correctly, that is truly a thing of
742	beauty.	802	beauty.
		803
		804	This function is also I<mostly> exception-safe - you can break out of
		805	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
		806	exception and so on. This does not decrement the C<ev_depth> value, nor
		807	will it clear any outstanding C<EVBREAK_ONE> breaks.
743		808
744	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle	809	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
745	those events and any already outstanding ones, but will not wait and	810	those events and any already outstanding ones, but will not wait and
746	block your process in case there are no events and will return after one	811	block your process in case there are no events and will return after one
747	iteration of the loop. This is sometimes useful to poll and handle new	812	iteration of the loop. This is sometimes useful to poll and handle new
…		…
809	Can be used to make a call to C<ev_run> return early (but only after it	874	Can be used to make a call to C<ev_run> return early (but only after it
810	has processed all outstanding events). The C<how> argument must be either	875	has processed all outstanding events). The C<how> argument must be either
811	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or	876	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
812	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.	877	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
813		878
814	This "unloop state" will be cleared when entering C<ev_run> again.	879	This "break state" will be cleared on the next call to C<ev_run>.
815		880
816	It is safe to call C<ev_break> from outside any C<ev_run> calls. ##TODO##	881	It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in
		882	which case it will have no effect.
817		883
818	=item ev_ref (loop)	884	=item ev_ref (loop)
819		885
820	=item ev_unref (loop)	886	=item ev_unref (loop)
821		887
…		…
842	running when nothing else is active.	908	running when nothing else is active.
843		909
844	ev_signal exitsig;	910	ev_signal exitsig;
845	ev_signal_init (&exitsig, sig_cb, SIGINT);	911	ev_signal_init (&exitsig, sig_cb, SIGINT);
846	ev_signal_start (loop, &exitsig);	912	ev_signal_start (loop, &exitsig);
847	evf_unref (loop);	913	ev_unref (loop);
848		914
849	Example: For some weird reason, unregister the above signal handler again.	915	Example: For some weird reason, unregister the above signal handler again.
850		916
851	ev_ref (loop);	917	ev_ref (loop);
852	ev_signal_stop (loop, &exitsig);	918	ev_signal_stop (loop, &exitsig);
…		…
964	See also the locking example in the C<THREADS> section later in this	1030	See also the locking example in the C<THREADS> section later in this
965	document.	1031	document.
966		1032
967	=item ev_set_userdata (loop, void *data)	1033	=item ev_set_userdata (loop, void *data)
968		1034
969	=item ev_userdata (loop)	1035	=item void *ev_userdata (loop)
970		1036
971	Set and retrieve a single C<void *> associated with a loop. When	1037	Set and retrieve a single C<void *> associated with a loop. When
972	C<ev_set_userdata> has never been called, then C<ev_userdata> returns	1038	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
973	C<0.>	1039	C<0>.
974		1040
975	These two functions can be used to associate arbitrary data with a loop,	1041	These two functions can be used to associate arbitrary data with a loop,
976	and are intended solely for the C<invoke_pending_cb>, C<release> and	1042	and are intended solely for the C<invoke_pending_cb>, C<release> and
977	C<acquire> callbacks described above, but of course can be (ab-)used for	1043	C<acquire> callbacks described above, but of course can be (ab-)used for
978	any other purpose as well.	1044	any other purpose as well.
…		…
1106	=item C<EV_FORK>	1172	=item C<EV_FORK>
1107		1173
1108	The event loop has been resumed in the child process after fork (see	1174	The event loop has been resumed in the child process after fork (see
1109	C<ev_fork>).	1175	C<ev_fork>).
1110		1176
		1177	=item C<EV_CLEANUP>
		1178
		1179	The event loop is about to be destroyed (see C<ev_cleanup>).
		1180
1111	=item C<EV_ASYNC>	1181	=item C<EV_ASYNC>
1112		1182
1113	The given async watcher has been asynchronously notified (see C<ev_async>).	1183	The given async watcher has been asynchronously notified (see C<ev_async>).
1114		1184
1115	=item C<EV_CUSTOM>	1185	=item C<EV_CUSTOM>
…		…
1136	programs, though, as the fd could already be closed and reused for another	1206	programs, though, as the fd could already be closed and reused for another
1137	thing, so beware.	1207	thing, so beware.
1138		1208
1139	=back	1209	=back
1140		1210
1141	=head2 WATCHER STATES
1142
1143	There are various watcher states mentioned throughout this manual -
1144	active, pending and so on. In this section these states and the rules to
1145	transition between them will be described in more detail - and while these
1146	rules might look complicated, they usually do "the right thing".
1147
1148	=over 4
1149
1150	=item initialiased
1151
1152	Before a watcher can be registered with the event looop it has to be
1153	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
1154	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
1155
1156	In this state it is simply some block of memory that is suitable for use
1157	in an event loop. It can be moved around, freed, reused etc. at will.
1158
1159	=item started/running/active
1160
1161	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
1162	property of the event loop, and is actively waiting for events. While in
1163	this state it cannot be accessed (except in a few documented ways), moved,
1164	freed or anything else - the only legal thing is to keep a pointer to it,
1165	and call libev functions on it that are documented to work on active watchers.
1166
1167	=item pending
1168
1169	If a watcher is active and libev determines that an event it is interested
1170	in has occurred (such as a timer expiring), it will become pending. It will
1171	stay in this pending state until either it is stopped or its callback is
1172	about to be invoked, so it is not normally pending inside the watcher
1173	callback.
1174
1175	The watcher might or might not be active while it is pending (for example,
1176	an expired non-repeating timer can be pending but no longer active). If it
1177	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
1178	but it is still property of the event loop at this time, so cannot be
1179	moved, freed or reused. And if it is active the rules described in the
1180	previous item still apply.
1181
1182	It is also possible to feed an event on a watcher that is not active (e.g.
1183	via C<ev_feed_event>), in which case it becomes pending without being
1184	active.
1185
1186	=item stopped
1187
1188	A watcher can be stopped implicitly by libev (in which case it might still
1189	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
1190	latter will clear any pending state the watcher might be in, regardless
1191	of whether it was active or not, so stopping a watcher explicitly before
1192	freeing it is often a good idea.
1193
1194	While stopped (and not pending) the watcher is essentially in the
1195	initialised state, that is it can be reused, moved, modified in any way
1196	you wish.
1197
1198	=back
1199
1200	=head2 GENERIC WATCHER FUNCTIONS	1211	=head2 GENERIC WATCHER FUNCTIONS
1201		1212
1202	=over 4	1213	=over 4
1203		1214
1204	=item C<ev_init> (ev_TYPE *watcher, callback)	1215	=item C<ev_init> (ev_TYPE *watcher, callback)
…		…
1345		1356
1346	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related	1357	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
1347	functions that do not need a watcher.	1358	functions that do not need a watcher.
1348		1359
1349	=back	1360	=back
1350
1351		1361
1352	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1362	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
1353		1363
1354	Each watcher has, by default, a member C<void *data> that you can change	1364	Each watcher has, by default, a member C<void *data> that you can change
1355	and read at any time: libev will completely ignore it. This can be used	1365	and read at any time: libev will completely ignore it. This can be used
…		…
1411	t2_cb (EV_P_ ev_timer *w, int revents)	1421	t2_cb (EV_P_ ev_timer *w, int revents)
1412	{	1422	{
1413	struct my_biggy big = (struct my_biggy *)	1423	struct my_biggy big = (struct my_biggy *)
1414	(((char *)w) - offsetof (struct my_biggy, t2));	1424	(((char *)w) - offsetof (struct my_biggy, t2));
1415	}	1425	}
		1426
		1427	=head2 WATCHER STATES
		1428
		1429	There are various watcher states mentioned throughout this manual -
		1430	active, pending and so on. In this section these states and the rules to
		1431	transition between them will be described in more detail - and while these
		1432	rules might look complicated, they usually do "the right thing".
		1433
		1434	=over 4
		1435
		1436	=item initialiased
		1437
		1438	Before a watcher can be registered with the event looop it has to be
		1439	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
		1440	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
		1441
		1442	In this state it is simply some block of memory that is suitable for use
		1443	in an event loop. It can be moved around, freed, reused etc. at will.
		1444
		1445	=item started/running/active
		1446
		1447	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
		1448	property of the event loop, and is actively waiting for events. While in
		1449	this state it cannot be accessed (except in a few documented ways), moved,
		1450	freed or anything else - the only legal thing is to keep a pointer to it,
		1451	and call libev functions on it that are documented to work on active watchers.
		1452
		1453	=item pending
		1454
		1455	If a watcher is active and libev determines that an event it is interested
		1456	in has occurred (such as a timer expiring), it will become pending. It will
		1457	stay in this pending state until either it is stopped or its callback is
		1458	about to be invoked, so it is not normally pending inside the watcher
		1459	callback.
		1460
		1461	The watcher might or might not be active while it is pending (for example,
		1462	an expired non-repeating timer can be pending but no longer active). If it
		1463	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
		1464	but it is still property of the event loop at this time, so cannot be
		1465	moved, freed or reused. And if it is active the rules described in the
		1466	previous item still apply.
		1467
		1468	It is also possible to feed an event on a watcher that is not active (e.g.
		1469	via C<ev_feed_event>), in which case it becomes pending without being
		1470	active.
		1471
		1472	=item stopped
		1473
		1474	A watcher can be stopped implicitly by libev (in which case it might still
		1475	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
		1476	latter will clear any pending state the watcher might be in, regardless
		1477	of whether it was active or not, so stopping a watcher explicitly before
		1478	freeing it is often a good idea.
		1479
		1480	While stopped (and not pending) the watcher is essentially in the
		1481	initialised state, that is it can be reused, moved, modified in any way
		1482	you wish.
		1483
		1484	=back
1416		1485
1417	=head2 WATCHER PRIORITY MODELS	1486	=head2 WATCHER PRIORITY MODELS
1418		1487
1419	Many event loops support I<watcher priorities>, which are usually small	1488	Many event loops support I<watcher priorities>, which are usually small
1420	integers that influence the ordering of event callback invocation	1489	integers that influence the ordering of event callback invocation
…		…
1547	In general you can register as many read and/or write event watchers per	1616	In general you can register as many read and/or write event watchers per
1548	fd as you want (as long as you don't confuse yourself). Setting all file	1617	fd as you want (as long as you don't confuse yourself). Setting all file
1549	descriptors to non-blocking mode is also usually a good idea (but not	1618	descriptors to non-blocking mode is also usually a good idea (but not
1550	required if you know what you are doing).	1619	required if you know what you are doing).
1551		1620
1552	If you cannot use non-blocking mode, then force the use of a
1553	known-to-be-good backend (at the time of this writing, this includes only
1554	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
1555	descriptors for which non-blocking operation makes no sense (such as
1556	files) - libev doesn't guarantee any specific behaviour in that case.
1557
1558	Another thing you have to watch out for is that it is quite easy to	1621	Another thing you have to watch out for is that it is quite easy to
1559	receive "spurious" readiness notifications, that is your callback might	1622	receive "spurious" readiness notifications, that is, your callback might
1560	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1623	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1561	because there is no data. Not only are some backends known to create a	1624	because there is no data. It is very easy to get into this situation even
1562	lot of those (for example Solaris ports), it is very easy to get into	1625	with a relatively standard program structure. Thus it is best to always
1563	this situation even with a relatively standard program structure. Thus	1626	use non-blocking I/O: An extra C<read>(2) returning C<EAGAIN> is far
1564	it is best to always use non-blocking I/O: An extra C<read>(2) returning
1565	C<EAGAIN> is far preferable to a program hanging until some data arrives.	1627	preferable to a program hanging until some data arrives.
1566		1628
1567	If you cannot run the fd in non-blocking mode (for example you should	1629	If you cannot run the fd in non-blocking mode (for example you should
1568	not play around with an Xlib connection), then you have to separately	1630	not play around with an Xlib connection), then you have to separately
1569	re-test whether a file descriptor is really ready with a known-to-be good	1631	re-test whether a file descriptor is really ready with a known-to-be good
1570	interface such as poll (fortunately in our Xlib example, Xlib already	1632	interface such as poll (fortunately in the case of Xlib, it already does
1571	does this on its own, so its quite safe to use). Some people additionally	1633	this on its own, so its quite safe to use). Some people additionally
1572	use C<SIGALRM> and an interval timer, just to be sure you won't block	1634	use C<SIGALRM> and an interval timer, just to be sure you won't block
1573	indefinitely.	1635	indefinitely.
1574		1636
1575	But really, best use non-blocking mode.	1637	But really, best use non-blocking mode.
1576		1638
…		…
1604		1666
1605	There is no workaround possible except not registering events	1667	There is no workaround possible except not registering events
1606	for potentially C<dup ()>'ed file descriptors, or to resort to	1668	for potentially C<dup ()>'ed file descriptors, or to resort to
1607	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.	1669	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1608		1670
		1671	=head3 The special problem of files
		1672
		1673	Many people try to use C<select> (or libev) on file descriptors
		1674	representing files, and expect it to become ready when their program
		1675	doesn't block on disk accesses (which can take a long time on their own).
		1676
		1677	However, this cannot ever work in the "expected" way - you get a readiness
		1678	notification as soon as the kernel knows whether and how much data is
		1679	there, and in the case of open files, that's always the case, so you
		1680	always get a readiness notification instantly, and your read (or possibly
		1681	write) will still block on the disk I/O.
		1682
		1683	Another way to view it is that in the case of sockets, pipes, character
		1684	devices and so on, there is another party (the sender) that delivers data
		1685	on it's own, but in the case of files, there is no such thing: the disk
		1686	will not send data on it's own, simply because it doesn't know what you
		1687	wish to read - you would first have to request some data.
		1688
		1689	Since files are typically not-so-well supported by advanced notification
		1690	mechanism, libev tries hard to emulate POSIX behaviour with respect
		1691	to files, even though you should not use it. The reason for this is
		1692	convenience: sometimes you want to watch STDIN or STDOUT, which is
		1693	usually a tty, often a pipe, but also sometimes files or special devices
		1694	(for example, C<epoll> on Linux works with F</dev/random> but not with
		1695	F</dev/urandom>), and even though the file might better be served with
		1696	asynchronous I/O instead of with non-blocking I/O, it is still useful when
		1697	it "just works" instead of freezing.
		1698
		1699	So avoid file descriptors pointing to files when you know it (e.g. use
		1700	libeio), but use them when it is convenient, e.g. for STDIN/STDOUT, or
		1701	when you rarely read from a file instead of from a socket, and want to
		1702	reuse the same code path.
		1703
1609	=head3 The special problem of fork	1704	=head3 The special problem of fork
1610		1705
1611	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit	1706	Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit
1612	useless behaviour. Libev fully supports fork, but needs to be told about	1707	useless behaviour. Libev fully supports fork, but needs to be told about
1613	it in the child.	1708	it in the child if you want to continue to use it in the child.
1614		1709
1615	To support fork in your programs, you either have to call	1710	To support fork in your child processes, you have to call C<ev_loop_fork
1616	C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,	1711	()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to
1617	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1712	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>.
1618	C<EVBACKEND_POLL>.
1619		1713
1620	=head3 The special problem of SIGPIPE	1714	=head3 The special problem of SIGPIPE
1621		1715
1622	While not really specific to libev, it is easy to forget about C<SIGPIPE>:	1716	While not really specific to libev, it is easy to forget about C<SIGPIPE>:
1623	when writing to a pipe whose other end has been closed, your program gets	1717	when writing to a pipe whose other end has been closed, your program gets
…		…
2239		2333
2240	=head2 C<ev_signal> - signal me when a signal gets signalled!	2334	=head2 C<ev_signal> - signal me when a signal gets signalled!
2241		2335
2242	Signal watchers will trigger an event when the process receives a specific	2336	Signal watchers will trigger an event when the process receives a specific
2243	signal one or more times. Even though signals are very asynchronous, libev	2337	signal one or more times. Even though signals are very asynchronous, libev
2244	will try it's best to deliver signals synchronously, i.e. as part of the	2338	will try its best to deliver signals synchronously, i.e. as part of the
2245	normal event processing, like any other event.	2339	normal event processing, like any other event.
2246		2340
2247	If you want signals to be delivered truly asynchronously, just use	2341	If you want signals to be delivered truly asynchronously, just use
2248	C<sigaction> as you would do without libev and forget about sharing	2342	C<sigaction> as you would do without libev and forget about sharing
2249	the signal. You can even use C<ev_async> from a signal handler to	2343	the signal. You can even use C<ev_async> from a signal handler to
…		…
2291	I<has> to modify the signal mask, at least temporarily.	2385	I<has> to modify the signal mask, at least temporarily.
2292		2386
2293	So I can't stress this enough: I<If you do not reset your signal mask when	2387	So I can't stress this enough: I<If you do not reset your signal mask when
2294	you expect it to be empty, you have a race condition in your code>. This	2388	you expect it to be empty, you have a race condition in your code>. This
2295	is not a libev-specific thing, this is true for most event libraries.	2389	is not a libev-specific thing, this is true for most event libraries.
		2390
		2391	=head3 The special problem of threads signal handling
		2392
		2393	POSIX threads has problematic signal handling semantics, specifically,
		2394	a lot of functionality (sigfd, sigwait etc.) only really works if all
		2395	threads in a process block signals, which is hard to achieve.
		2396
		2397	When you want to use sigwait (or mix libev signal handling with your own
		2398	for the same signals), you can tackle this problem by globally blocking
		2399	all signals before creating any threads (or creating them with a fully set
		2400	sigprocmask) and also specifying the C<EVFLAG_NOSIGMASK> when creating
		2401	loops. Then designate one thread as "signal receiver thread" which handles
		2402	these signals. You can pass on any signals that libev might be interested
		2403	in by calling C<ev_feed_signal>.
2296		2404
2297	=head3 Watcher-Specific Functions and Data Members	2405	=head3 Watcher-Specific Functions and Data Members
2298		2406
2299	=over 4	2407	=over 4
2300		2408
…		…
3074	disadvantage of having to use multiple event loops (which do not support	3182	disadvantage of having to use multiple event loops (which do not support
3075	signal watchers).	3183	signal watchers).
3076		3184
3077	When this is not possible, or you want to use the default loop for	3185	When this is not possible, or you want to use the default loop for
3078	other reasons, then in the process that wants to start "fresh", call	3186	other reasons, then in the process that wants to start "fresh", call
3079	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying	3187	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
3080	the default loop will "orphan" (not stop) all registered watchers, so you	3188	Destroying the default loop will "orphan" (not stop) all registered
3081	have to be careful not to execute code that modifies those watchers. Note	3189	watchers, so you have to be careful not to execute code that modifies
3082	also that in that case, you have to re-register any signal watchers.	3190	those watchers. Note also that in that case, you have to re-register any
		3191	signal watchers.
3083		3192
3084	=head3 Watcher-Specific Functions and Data Members	3193	=head3 Watcher-Specific Functions and Data Members
3085		3194
3086	=over 4	3195	=over 4
3087		3196
3088	=item ev_fork_init (ev_signal *, callback)	3197	=item ev_fork_init (ev_fork *, callback)
3089		3198
3090	Initialises and configures the fork watcher - it has no parameters of any	3199	Initialises and configures the fork watcher - it has no parameters of any
3091	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3200	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
3092	believe me.	3201	really.
3093		3202
3094	=back	3203	=back
		3204
		3205
		3206	=head2 C<ev_cleanup> - even the best things end
		3207
		3208	Cleanup watchers are called just before the event loop is being destroyed
		3209	by a call to C<ev_loop_destroy>.
		3210
		3211	While there is no guarantee that the event loop gets destroyed, cleanup
		3212	watchers provide a convenient method to install cleanup hooks for your
		3213	program, worker threads and so on - you just to make sure to destroy the
		3214	loop when you want them to be invoked.
		3215
		3216	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3217	all other watchers, they do not keep a reference to the event loop (which
		3218	makes a lot of sense if you think about it). Like all other watchers, you
		3219	can call libev functions in the callback, except C<ev_cleanup_start>.
		3220
		3221	=head3 Watcher-Specific Functions and Data Members
		3222
		3223	=over 4
		3224
		3225	=item ev_cleanup_init (ev_cleanup *, callback)
		3226
		3227	Initialises and configures the cleanup watcher - it has no parameters of
		3228	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3229	pointless, I assure you.
		3230
		3231	=back
		3232
		3233	Example: Register an atexit handler to destroy the default loop, so any
		3234	cleanup functions are called.
		3235
		3236	static void
		3237	program_exits (void)
		3238	{
		3239	ev_loop_destroy (EV_DEFAULT_UC);
		3240	}
		3241
		3242	...
		3243	atexit (program_exits);
3095		3244
3096		3245
3097	=head2 C<ev_async> - how to wake up an event loop	3246	=head2 C<ev_async> - how to wake up an event loop
3098		3247
3099	In general, you cannot use an C<ev_run> from multiple threads or other	3248	In general, you cannot use an C<ev_run> from multiple threads or other
…		…
3106	it by calling C<ev_async_send>, which is thread- and signal safe.	3255	it by calling C<ev_async_send>, which is thread- and signal safe.
3107		3256
3108	This functionality is very similar to C<ev_signal> watchers, as signals,	3257	This functionality is very similar to C<ev_signal> watchers, as signals,
3109	too, are asynchronous in nature, and signals, too, will be compressed	3258	too, are asynchronous in nature, and signals, too, will be compressed
3110	(i.e. the number of callback invocations may be less than the number of	3259	(i.e. the number of callback invocations may be less than the number of
3111	C<ev_async_sent> calls).	3260	C<ev_async_sent> calls). In fact, you could use signal watchers as a kind
		3261	of "global async watchers" by using a watcher on an otherwise unused
		3262	signal, and C<ev_feed_signal> to signal this watcher from another thread,
		3263	even without knowing which loop owns the signal.
3112		3264
3113	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not	3265	Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not
3114	just the default loop.	3266	just the default loop.
3115		3267
3116	=head3 Queueing	3268	=head3 Queueing
…		…
3292	Feed an event on the given fd, as if a file descriptor backend detected	3444	Feed an event on the given fd, as if a file descriptor backend detected
3293	the given events it.	3445	the given events it.
3294		3446
3295	=item ev_feed_signal_event (loop, int signum)	3447	=item ev_feed_signal_event (loop, int signum)
3296		3448
3297	Feed an event as if the given signal occurred (C<loop> must be the default	3449	Feed an event as if the given signal occurred. See also C<ev_feed_signal>,
3298	loop!).	3450	which is async-safe.
		3451
		3452	=back
		3453
		3454
		3455	=head1 COMMON OR USEFUL IDIOMS (OR BOTH)
		3456
		3457	This section explains some common idioms that are not immediately
		3458	obvious. Note that examples are sprinkled over the whole manual, and this
		3459	section only contains stuff that wouldn't fit anywhere else.
		3460
		3461	=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS
		3462
		3463	Often (especially in GUI toolkits) there are places where you have
		3464	I<modal> interaction, which is most easily implemented by recursively
		3465	invoking C<ev_run>.
		3466
		3467	This brings the problem of exiting - a callback might want to finish the
		3468	main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but
		3469	a modal "Are you sure?" dialog is still waiting), or just the nested one
		3470	and not the main one (e.g. user clocked "Ok" in a modal dialog), or some
		3471	other combination: In these cases, C<ev_break> will not work alone.
		3472
		3473	The solution is to maintain "break this loop" variable for each C<ev_run>
		3474	invocation, and use a loop around C<ev_run> until the condition is
		3475	triggered, using C<EVRUN_ONCE>:
		3476
		3477	// main loop
		3478	int exit_main_loop = 0;
		3479
		3480	while (!exit_main_loop)
		3481	ev_run (EV_DEFAULT_ EVRUN_ONCE);
		3482
		3483	// in a model watcher
		3484	int exit_nested_loop = 0;
		3485
		3486	while (!exit_nested_loop)
		3487	ev_run (EV_A_ EVRUN_ONCE);
		3488
		3489	To exit from any of these loops, just set the corresponding exit variable:
		3490
		3491	// exit modal loop
		3492	exit_nested_loop = 1;
		3493
		3494	// exit main program, after modal loop is finished
		3495	exit_main_loop = 1;
		3496
		3497	// exit both
		3498	exit_main_loop = exit_nested_loop = 1;
		3499
		3500	=head2 THREAD LOCKING EXAMPLE
		3501
		3502	Here is a fictitious example of how to run an event loop in a different
		3503	thread than where callbacks are being invoked and watchers are
		3504	created/added/removed.
		3505
		3506	For a real-world example, see the C<EV::Loop::Async> perl module,
		3507	which uses exactly this technique (which is suited for many high-level
		3508	languages).
		3509
		3510	The example uses a pthread mutex to protect the loop data, a condition
		3511	variable to wait for callback invocations, an async watcher to notify the
		3512	event loop thread and an unspecified mechanism to wake up the main thread.
		3513
		3514	First, you need to associate some data with the event loop:
		3515
		3516	typedef struct {
		3517	mutex_t lock; /* global loop lock */
		3518	ev_async async_w;
		3519	thread_t tid;
		3520	cond_t invoke_cv;
		3521	} userdata;
		3522
		3523	void prepare_loop (EV_P)
		3524	{
		3525	// for simplicity, we use a static userdata struct.
		3526	static userdata u;
		3527
		3528	ev_async_init (&u->async_w, async_cb);
		3529	ev_async_start (EV_A_ &u->async_w);
		3530
		3531	pthread_mutex_init (&u->lock, 0);
		3532	pthread_cond_init (&u->invoke_cv, 0);
		3533
		3534	// now associate this with the loop
		3535	ev_set_userdata (EV_A_ u);
		3536	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		3537	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		3538
		3539	// then create the thread running ev_loop
		3540	pthread_create (&u->tid, 0, l_run, EV_A);
		3541	}
		3542
		3543	The callback for the C<ev_async> watcher does nothing: the watcher is used
		3544	solely to wake up the event loop so it takes notice of any new watchers
		3545	that might have been added:
		3546
		3547	static void
		3548	async_cb (EV_P_ ev_async *w, int revents)
		3549	{
		3550	// just used for the side effects
		3551	}
		3552
		3553	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		3554	protecting the loop data, respectively.
		3555
		3556	static void
		3557	l_release (EV_P)
		3558	{
		3559	userdata *u = ev_userdata (EV_A);
		3560	pthread_mutex_unlock (&u->lock);
		3561	}
		3562
		3563	static void
		3564	l_acquire (EV_P)
		3565	{
		3566	userdata *u = ev_userdata (EV_A);
		3567	pthread_mutex_lock (&u->lock);
		3568	}
		3569
		3570	The event loop thread first acquires the mutex, and then jumps straight
		3571	into C<ev_run>:
		3572
		3573	void *
		3574	l_run (void *thr_arg)
		3575	{
		3576	struct ev_loop loop = (struct ev_loop )thr_arg;
		3577
		3578	l_acquire (EV_A);
		3579	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		3580	ev_run (EV_A_ 0);
		3581	l_release (EV_A);
		3582
		3583	return 0;
		3584	}
		3585
		3586	Instead of invoking all pending watchers, the C<l_invoke> callback will
		3587	signal the main thread via some unspecified mechanism (signals? pipe
		3588	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		3589	have been called (in a while loop because a) spurious wakeups are possible
		3590	and b) skipping inter-thread-communication when there are no pending
		3591	watchers is very beneficial):
		3592
		3593	static void
		3594	l_invoke (EV_P)
		3595	{
		3596	userdata *u = ev_userdata (EV_A);
		3597
		3598	while (ev_pending_count (EV_A))
		3599	{
		3600	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		3601	pthread_cond_wait (&u->invoke_cv, &u->lock);
		3602	}
		3603	}
		3604
		3605	Now, whenever the main thread gets told to invoke pending watchers, it
		3606	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		3607	thread to continue:
		3608
		3609	static void
		3610	real_invoke_pending (EV_P)
		3611	{
		3612	userdata *u = ev_userdata (EV_A);
		3613
		3614	pthread_mutex_lock (&u->lock);
		3615	ev_invoke_pending (EV_A);
		3616	pthread_cond_signal (&u->invoke_cv);
		3617	pthread_mutex_unlock (&u->lock);
		3618	}
		3619
		3620	Whenever you want to start/stop a watcher or do other modifications to an
		3621	event loop, you will now have to lock:
		3622
		3623	ev_timer timeout_watcher;
		3624	userdata *u = ev_userdata (EV_A);
		3625
		3626	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		3627
		3628	pthread_mutex_lock (&u->lock);
		3629	ev_timer_start (EV_A_ &timeout_watcher);
		3630	ev_async_send (EV_A_ &u->async_w);
		3631	pthread_mutex_unlock (&u->lock);
		3632
		3633	Note that sending the C<ev_async> watcher is required because otherwise
		3634	an event loop currently blocking in the kernel will have no knowledge
		3635	about the newly added timer. By waking up the loop it will pick up any new
		3636	watchers in the next event loop iteration.
3299		3637
3300	=back	3638	=back
3301		3639
3302		3640
3303	=head1 LIBEVENT EMULATION	3641	=head1 LIBEVENT EMULATION
3304		3642
3305	Libev offers a compatibility emulation layer for libevent. It cannot	3643	Libev offers a compatibility emulation layer for libevent. It cannot
3306	emulate the internals of libevent, so here are some usage hints:	3644	emulate the internals of libevent, so here are some usage hints:
3307		3645
3308	=over 4	3646	=over 4
		3647
		3648	=item * Only the libevent-1.4.1-beta API is being emulated.
		3649
		3650	This was the newest libevent version available when libev was implemented,
		3651	and is still mostly unchanged in 2010.
3309		3652
3310	=item * Use it by including <event.h>, as usual.	3653	=item * Use it by including <event.h>, as usual.
3311		3654
3312	=item * The following members are fully supported: ev_base, ev_callback,	3655	=item * The following members are fully supported: ev_base, ev_callback,
3313	ev_arg, ev_fd, ev_res, ev_events.	3656	ev_arg, ev_fd, ev_res, ev_events.
…		…
3319	=item * Priorities are not currently supported. Initialising priorities	3662	=item * Priorities are not currently supported. Initialising priorities
3320	will fail and all watchers will have the same priority, even though there	3663	will fail and all watchers will have the same priority, even though there
3321	is an ev_pri field.	3664	is an ev_pri field.
3322		3665
3323	=item * In libevent, the last base created gets the signals, in libev, the	3666	=item * In libevent, the last base created gets the signals, in libev, the
3324	first base created (== the default loop) gets the signals.	3667	base that registered the signal gets the signals.
3325		3668
3326	=item * Other members are not supported.	3669	=item * Other members are not supported.
3327		3670
3328	=item * The libev emulation is I<not> ABI compatible to libevent, you need	3671	=item * The libev emulation is I<not> ABI compatible to libevent, you need
3329	to use the libev header file and library.	3672	to use the libev header file and library.
…		…
3348	Care has been taken to keep the overhead low. The only data member the C++	3691	Care has been taken to keep the overhead low. The only data member the C++
3349	classes add (compared to plain C-style watchers) is the event loop pointer	3692	classes add (compared to plain C-style watchers) is the event loop pointer
3350	that the watcher is associated with (or no additional members at all if	3693	that the watcher is associated with (or no additional members at all if
3351	you disable C<EV_MULTIPLICITY> when embedding libev).	3694	you disable C<EV_MULTIPLICITY> when embedding libev).
3352		3695
3353	Currently, functions, and static and non-static member functions can be	3696	Currently, functions, static and non-static member functions and classes
3354	used as callbacks. Other types should be easy to add as long as they only	3697	with C<operator ()> can be used as callbacks. Other types should be easy
3355	need one additional pointer for context. If you need support for other	3698	to add as long as they only need one additional pointer for context. If
3356	types of functors please contact the author (preferably after implementing	3699	you need support for other types of functors please contact the author
3357	it).	3700	(preferably after implementing it).
3358		3701
3359	Here is a list of things available in the C<ev> namespace:	3702	Here is a list of things available in the C<ev> namespace:
3360		3703
3361	=over 4	3704	=over 4
3362		3705
…		…
4291	default loop and triggering an C<ev_async> watcher from the default loop	4634	default loop and triggering an C<ev_async> watcher from the default loop
4292	watcher callback into the event loop interested in the signal.	4635	watcher callback into the event loop interested in the signal.
4293		4636
4294	=back	4637	=back
4295		4638
4296	=head4 THREAD LOCKING EXAMPLE	4639	See also L<THREAD LOCKING EXAMPLE>.
4297
4298	Here is a fictitious example of how to run an event loop in a different
4299	thread than where callbacks are being invoked and watchers are
4300	created/added/removed.
4301
4302	For a real-world example, see the C<EV::Loop::Async> perl module,
4303	which uses exactly this technique (which is suited for many high-level
4304	languages).
4305
4306	The example uses a pthread mutex to protect the loop data, a condition
4307	variable to wait for callback invocations, an async watcher to notify the
4308	event loop thread and an unspecified mechanism to wake up the main thread.
4309
4310	First, you need to associate some data with the event loop:
4311
4312	typedef struct {
4313	mutex_t lock; /* global loop lock */
4314	ev_async async_w;
4315	thread_t tid;
4316	cond_t invoke_cv;
4317	} userdata;
4318
4319	void prepare_loop (EV_P)
4320	{
4321	// for simplicity, we use a static userdata struct.
4322	static userdata u;
4323
4324	ev_async_init (&u->async_w, async_cb);
4325	ev_async_start (EV_A_ &u->async_w);
4326
4327	pthread_mutex_init (&u->lock, 0);
4328	pthread_cond_init (&u->invoke_cv, 0);
4329
4330	// now associate this with the loop
4331	ev_set_userdata (EV_A_ u);
4332	ev_set_invoke_pending_cb (EV_A_ l_invoke);
4333	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
4334
4335	// then create the thread running ev_loop
4336	pthread_create (&u->tid, 0, l_run, EV_A);
4337	}
4338
4339	The callback for the C<ev_async> watcher does nothing: the watcher is used
4340	solely to wake up the event loop so it takes notice of any new watchers
4341	that might have been added:
4342
4343	static void
4344	async_cb (EV_P_ ev_async *w, int revents)
4345	{
4346	// just used for the side effects
4347	}
4348
4349	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
4350	protecting the loop data, respectively.
4351
4352	static void
4353	l_release (EV_P)
4354	{
4355	userdata *u = ev_userdata (EV_A);
4356	pthread_mutex_unlock (&u->lock);
4357	}
4358
4359	static void
4360	l_acquire (EV_P)
4361	{
4362	userdata *u = ev_userdata (EV_A);
4363	pthread_mutex_lock (&u->lock);
4364	}
4365
4366	The event loop thread first acquires the mutex, and then jumps straight
4367	into C<ev_run>:
4368
4369	void *
4370	l_run (void *thr_arg)
4371	{
4372	struct ev_loop loop = (struct ev_loop )thr_arg;
4373
4374	l_acquire (EV_A);
4375	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
4376	ev_run (EV_A_ 0);
4377	l_release (EV_A);
4378
4379	return 0;
4380	}
4381
4382	Instead of invoking all pending watchers, the C<l_invoke> callback will
4383	signal the main thread via some unspecified mechanism (signals? pipe
4384	writes? C<Async::Interrupt>?) and then waits until all pending watchers
4385	have been called (in a while loop because a) spurious wakeups are possible
4386	and b) skipping inter-thread-communication when there are no pending
4387	watchers is very beneficial):
4388
4389	static void
4390	l_invoke (EV_P)
4391	{
4392	userdata *u = ev_userdata (EV_A);
4393
4394	while (ev_pending_count (EV_A))
4395	{
4396	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
4397	pthread_cond_wait (&u->invoke_cv, &u->lock);
4398	}
4399	}
4400
4401	Now, whenever the main thread gets told to invoke pending watchers, it
4402	will grab the lock, call C<ev_invoke_pending> and then signal the loop
4403	thread to continue:
4404
4405	static void
4406	real_invoke_pending (EV_P)
4407	{
4408	userdata *u = ev_userdata (EV_A);
4409
4410	pthread_mutex_lock (&u->lock);
4411	ev_invoke_pending (EV_A);
4412	pthread_cond_signal (&u->invoke_cv);
4413	pthread_mutex_unlock (&u->lock);
4414	}
4415
4416	Whenever you want to start/stop a watcher or do other modifications to an
4417	event loop, you will now have to lock:
4418
4419	ev_timer timeout_watcher;
4420	userdata *u = ev_userdata (EV_A);
4421
4422	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
4423
4424	pthread_mutex_lock (&u->lock);
4425	ev_timer_start (EV_A_ &timeout_watcher);
4426	ev_async_send (EV_A_ &u->async_w);
4427	pthread_mutex_unlock (&u->lock);
4428
4429	Note that sending the C<ev_async> watcher is required because otherwise
4430	an event loop currently blocking in the kernel will have no knowledge
4431	about the newly added timer. By waking up the loop it will pick up any new
4432	watchers in the next event loop iteration.
4433		4640
4434	=head3 COROUTINES	4641	=head3 COROUTINES
4435		4642
4436	Libev is very accommodating to coroutines ("cooperative threads"):	4643	Libev is very accommodating to coroutines ("cooperative threads"):
4437	libev fully supports nesting calls to its functions from different	4644	libev fully supports nesting calls to its functions from different
…		…
4706	structure (guaranteed by POSIX but not by ISO C for example), but it also	4913	structure (guaranteed by POSIX but not by ISO C for example), but it also
4707	assumes that the same (machine) code can be used to call any watcher	4914	assumes that the same (machine) code can be used to call any watcher
4708	callback: The watcher callbacks have different type signatures, but libev	4915	callback: The watcher callbacks have different type signatures, but libev
4709	calls them using an C<ev_watcher *> internally.	4916	calls them using an C<ev_watcher *> internally.
4710		4917
		4918	=item pointer accesses must be thread-atomic
		4919
		4920	Accessing a pointer value must be atomic, it must both be readable and
		4921	writable in one piece - this is the case on all current architectures.
		4922
4711	=item C<sig_atomic_t volatile> must be thread-atomic as well	4923	=item C<sig_atomic_t volatile> must be thread-atomic as well
4712		4924
4713	The type C<sig_atomic_t volatile> (or whatever is defined as	4925	The type C<sig_atomic_t volatile> (or whatever is defined as
4714	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different	4926	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
4715	threads. This is not part of the specification for C<sig_atomic_t>, but is	4927	threads. This is not part of the specification for C<sig_atomic_t>, but is
…		…
4821	=back	5033	=back
4822		5034
4823		5035
4824	=head1 PORTING FROM LIBEV 3.X TO 4.X	5036	=head1 PORTING FROM LIBEV 3.X TO 4.X
4825		5037
4826	The major version 4 introduced some minor incompatible changes to the API.	5038	The major version 4 introduced some incompatible changes to the API.
4827		5039
4828	At the moment, the C<ev.h> header file tries to implement superficial	5040	At the moment, the C<ev.h> header file provides compatibility definitions
4829	compatibility, so most programs should still compile. Those might be	5041	for all changes, so most programs should still compile. The compatibility
4830	removed in later versions of libev, so better update early than late.	5042	layer might be removed in later versions of libev, so better update to the
		5043	new API early than late.
4831		5044
4832	=over 4	5045	=over 4
		5046
		5047	=item C<EV_COMPAT3> backwards compatibility mechanism
		5048
		5049	The backward compatibility mechanism can be controlled by
		5050	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		5051	section.
		5052
		5053	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		5054
		5055	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		5056
		5057	ev_loop_destroy (EV_DEFAULT_UC);
		5058	ev_loop_fork (EV_DEFAULT);
4833		5059
4834	=item function/symbol renames	5060	=item function/symbol renames
4835		5061
4836	A number of functions and symbols have been renamed:	5062	A number of functions and symbols have been renamed:
4837		5063
…		…
4856	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme	5082	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
4857	as all other watcher types. Note that C<ev_loop_fork> is still called	5083	as all other watcher types. Note that C<ev_loop_fork> is still called
4858	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>	5084	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
4859	typedef.	5085	typedef.
4860		5086
4861	=item C<EV_COMPAT3> backwards compatibility mechanism
4862
4863	The backward compatibility mechanism can be controlled by
4864	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
4865	section.
4866
4867	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>	5087	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
4868		5088
4869	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different	5089	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
4870	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile	5090	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
4871	and work, but the library code will of course be larger.	5091	and work, but the library code will of course be larger.
…		…
4945		5165
4946	=back	5166	=back
4947		5167
4948	=head1 AUTHOR	5168	=head1 AUTHOR
4949		5169
4950	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.	5170	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5171	Magnusson and Emanuele Giaquinta.
4951		5172

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.318 by root, Fri Oct 22 09:40:22 2010 UTC vs. Revision 1.355 by root, Tue Jan 11 01:41:56 2011 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.318 by root, Fri Oct 22 09:40:22 2010 UTC vs.
Revision 1.355 by root, Tue Jan 11 01:41:56 2011 UTC