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

Comparing libev/ev.pod (file contents):
Revision 1.200 by root, Thu Oct 23 07:33:45 2008 UTC vs.
Revision 1.221 by root, Wed Dec 3 15:23:44 2008 UTC

…		…
8		8
9	=head2 EXAMPLE PROGRAM	9	=head2 EXAMPLE PROGRAM
10		10
11	// a single header file is required	11	// a single header file is required
12	#include <ev.h>	12	#include <ev.h>
		13
		14	#include <stdio.h> // for puts
13		15
14	// every watcher type has its own typedef'd struct	16	// every watcher type has its own typedef'd struct
15	// with the name ev_TYPE	17	// with the name ev_TYPE
16	ev_io stdin_watcher;	18	ev_io stdin_watcher;
17	ev_timer timeout_watcher;	19	ev_timer timeout_watcher;
…		…
41		43
42	int	44	int
43	main (void)	45	main (void)
44	{	46	{
45	// use the default event loop unless you have special needs	47	// use the default event loop unless you have special needs
46	ev_loop *loop = ev_default_loop (0);	48	struct ev_loop *loop = ev_default_loop (0);
47		49
48	// initialise an io watcher, then start it	50	// initialise an io watcher, then start it
49	// this one will watch for stdin to become readable	51	// this one will watch for stdin to become readable
50	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);
51	ev_io_start (loop, &stdin_watcher);	53	ev_io_start (loop, &stdin_watcher);
…		…
298	If you don't know what event loop to use, use the one returned from this	300	If you don't know what event loop to use, use the one returned from this
299	function.	301	function.
300		302
301	Note that this function is I<not> thread-safe, so if you want to use it	303	Note that this function is I<not> thread-safe, so if you want to use it
302	from multiple threads, you have to lock (note also that this is unlikely,	304	from multiple threads, you have to lock (note also that this is unlikely,
303	as loops cannot bes hared easily between threads anyway).	305	as loops cannot be shared easily between threads anyway).
304		306
305	The default loop is the only loop that can handle C<ev_signal> and	307	The default loop is the only loop that can handle C<ev_signal> and
306	C<ev_child> watchers, and to do this, it always registers a handler	308	C<ev_child> watchers, and to do this, it always registers a handler
307	for C<SIGCHLD>. If this is a problem for your application you can either	309	for C<SIGCHLD>. If this is a problem for your application you can either
308	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	310	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
…		…
384	=item C<EVBACKEND_EPOLL> (value 4, Linux)	386	=item C<EVBACKEND_EPOLL> (value 4, Linux)
385		387
386	For few fds, this backend is a bit little slower than poll and select,	388	For few fds, this backend is a bit little slower than poll and select,
387	but it scales phenomenally better. While poll and select usually scale	389	but it scales phenomenally better. While poll and select usually scale
388	like O(total_fds) where n is the total number of fds (or the highest fd),	390	like O(total_fds) where n is the total number of fds (or the highest fd),
389	epoll scales either O(1) or O(active_fds). The epoll design has a number	391	epoll scales either O(1) or O(active_fds).
390	of shortcomings, such as silently dropping events in some hard-to-detect	392
391	cases and requiring a system call per fd change, no fork support and bad	393	The epoll mechanism deserves honorable mention as the most misdesigned
392	support for dup.	394	of the more advanced event mechanisms: mere annoyances include silently
		395	dropping file descriptors, requiring a system call per change per file
		396	descriptor (and unnecessary guessing of parameters), problems with dup and
		397	so on. The biggest issue is fork races, however - if a program forks then
		398	I<both> parent and child process have to recreate the epoll set, which can
		399	take considerable time (one syscall per file descriptor) and is of course
		400	hard to detect.
		401
		402	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
		403	of course I<doesn't>, and epoll just loves to report events for totally
		404	I<different> file descriptors (even already closed ones, so one cannot
		405	even remove them from the set) than registered in the set (especially
		406	on SMP systems). Libev tries to counter these spurious notifications by
		407	employing an additional generation counter and comparing that against the
		408	events to filter out spurious ones, recreating the set when required.
393		409
394	While stopping, setting and starting an I/O watcher in the same iteration	410	While stopping, setting and starting an I/O watcher in the same iteration
395	will result in some caching, there is still a system call per such incident	411	will result in some caching, there is still a system call per such
396	(because the fd could point to a different file description now), so its	412	incident (because the same I<file descriptor> could point to a different
397	best to avoid that. Also, C<dup ()>'ed file descriptors might not work	413	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
398	very well if you register events for both fds.	414	file descriptors might not work very well if you register events for both
399		415	file descriptors.
400	Please note that epoll sometimes generates spurious notifications, so you
401	need to use non-blocking I/O or other means to avoid blocking when no data
402	(or space) is available.
403		416
404	Best performance from this backend is achieved by not unregistering all	417	Best performance from this backend is achieved by not unregistering all
405	watchers for a file descriptor until it has been closed, if possible,	418	watchers for a file descriptor until it has been closed, if possible,
406	i.e. keep at least one watcher active per fd at all times. Stopping and	419	i.e. keep at least one watcher active per fd at all times. Stopping and
407	starting a watcher (without re-setting it) also usually doesn't cause	420	starting a watcher (without re-setting it) also usually doesn't cause
408	extra overhead.	421	extra overhead. A fork can both result in spurious notifications as well
		422	as in libev having to destroy and recreate the epoll object, which can
		423	take considerable time and thus should be avoided.
		424
		425	All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or
		426	faster than epoll for maybe up to a hundred file descriptors, depending on
		427	the usage. So sad.
409		428
410	While nominally embeddable in other event loops, this feature is broken in	429	While nominally embeddable in other event loops, this feature is broken in
411	all kernel versions tested so far.	430	all kernel versions tested so far.
412		431
413	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	432	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
414	C<EVBACKEND_POLL>.	433	C<EVBACKEND_POLL>.
415		434
416	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	435	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
417		436
418	Kqueue deserves special mention, as at the time of this writing, it was	437	Kqueue deserves special mention, as at the time of this writing, it
419	broken on all BSDs except NetBSD (usually it doesn't work reliably with	438	was broken on all BSDs except NetBSD (usually it doesn't work reliably
420	anything but sockets and pipes, except on Darwin, where of course it's	439	with anything but sockets and pipes, except on Darwin, where of course
421	completely useless). For this reason it's not being "auto-detected" unless	440	it's completely useless). Unlike epoll, however, whose brokenness
422	you explicitly specify it in the flags (i.e. using C<EVBACKEND_KQUEUE>) or	441	is by design, these kqueue bugs can (and eventually will) be fixed
423	libev was compiled on a known-to-be-good (-enough) system like NetBSD.	442	without API changes to existing programs. For this reason it's not being
		443	"auto-detected" unless you explicitly specify it in the flags (i.e. using
		444	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
		445	system like NetBSD.
424		446
425	You still can embed kqueue into a normal poll or select backend and use it	447	You still can embed kqueue into a normal poll or select backend and use it
426	only for sockets (after having made sure that sockets work with kqueue on	448	only for sockets (after having made sure that sockets work with kqueue on
427	the target platform). See C<ev_embed> watchers for more info.	449	the target platform). See C<ev_embed> watchers for more info.
428		450
429	It scales in the same way as the epoll backend, but the interface to the	451	It scales in the same way as the epoll backend, but the interface to the
430	kernel is more efficient (which says nothing about its actual speed, of	452	kernel is more efficient (which says nothing about its actual speed, of
431	course). While stopping, setting and starting an I/O watcher does never	453	course). While stopping, setting and starting an I/O watcher does never
432	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to	454	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to
433	two event changes per incident. Support for C<fork ()> is very bad and it	455	two event changes per incident. Support for C<fork ()> is very bad (but
434	drops fds silently in similarly hard-to-detect cases.	456	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect
		457	cases
435		458
436	This backend usually performs well under most conditions.	459	This backend usually performs well under most conditions.
437		460
438	While nominally embeddable in other event loops, this doesn't work	461	While nominally embeddable in other event loops, this doesn't work
439	everywhere, so you might need to test for this. And since it is broken	462	everywhere, so you might need to test for this. And since it is broken
…		…
468	might perform better.	491	might perform better.
469		492
470	On the positive side, with the exception of the spurious readiness	493	On the positive side, with the exception of the spurious readiness
471	notifications, this backend actually performed fully to specification	494	notifications, this backend actually performed fully to specification
472	in all tests and is fully embeddable, which is a rare feat among the	495	in all tests and is fully embeddable, which is a rare feat among the
473	OS-specific backends.	496	OS-specific backends (I vastly prefer correctness over speed hacks).
474		497
475	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as	498	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
476	C<EVBACKEND_POLL>.	499	C<EVBACKEND_POLL>.
477		500
478	=item C<EVBACKEND_ALL>	501	=item C<EVBACKEND_ALL>
…		…
531	responsibility to either stop all watchers cleanly yourself I<before>	554	responsibility to either stop all watchers cleanly yourself I<before>
532	calling this function, or cope with the fact afterwards (which is usually	555	calling this function, or cope with the fact afterwards (which is usually
533	the easiest thing, you can just ignore the watchers and/or C<free ()> them	556	the easiest thing, you can just ignore the watchers and/or C<free ()> them
534	for example).	557	for example).
535		558
536	Note that certain global state, such as signal state, will not be freed by	559	Note that certain global state, such as signal state (and installed signal
537	this function, and related watchers (such as signal and child watchers)	560	handlers), will not be freed by this function, and related watchers (such
538	would need to be stopped manually.	561	as signal and child watchers) would need to be stopped manually.
539		562
540	In general it is not advisable to call this function except in the	563	In general it is not advisable to call this function except in the
541	rare occasion where you really need to free e.g. the signal handling	564	rare occasion where you really need to free e.g. the signal handling
542	pipe fds. If you need dynamically allocated loops it is better to use	565	pipe fds. If you need dynamically allocated loops it is better to use
543	C<ev_loop_new> and C<ev_loop_destroy>).	566	C<ev_loop_new> and C<ev_loop_destroy>).
…		…
635	the loop.	658	the loop.
636		659
637	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	660	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
638	necessary) and will handle those and any already outstanding ones. It	661	necessary) and will handle those and any already outstanding ones. It
639	will block your process until at least one new event arrives (which could	662	will block your process until at least one new event arrives (which could
640	be an event internal to libev itself, so there is no guarentee that a	663	be an event internal to libev itself, so there is no guarantee that a
641	user-registered callback will be called), and will return after one	664	user-registered callback will be called), and will return after one
642	iteration of the loop.	665	iteration of the loop.
643		666
644	This is useful if you are waiting for some external event in conjunction	667	This is useful if you are waiting for some external event in conjunction
645	with something not expressible using other libev watchers (i.e. "roll your	668	with something not expressible using other libev watchers (i.e. "roll your
…		…
1043	The default priority used by watchers when no priority has been set is	1066	The default priority used by watchers when no priority has been set is
1044	always C<0>, which is supposed to not be too high and not be too low :).	1067	always C<0>, which is supposed to not be too high and not be too low :).
1045		1068
1046	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1069	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
1047	fine, as long as you do not mind that the priority value you query might	1070	fine, as long as you do not mind that the priority value you query might
1048	or might not have been adjusted to be within valid range.	1071	or might not have been clamped to the valid range.
1049		1072
1050	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1073	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
1051		1074
1052	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1075	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
1053	C<loop> nor C<revents> need to be valid as long as the watcher callback	1076	C<loop> nor C<revents> need to be valid as long as the watcher callback
…		…
1398	else	1421	else
1399	{	1422	{
1400	// callback was invoked, but there was some activity, re-arm	1423	// callback was invoked, but there was some activity, re-arm
1401	// the watcher to fire in last_activity + 60, which is	1424	// the watcher to fire in last_activity + 60, which is
1402	// guaranteed to be in the future, so "again" is positive:	1425	// guaranteed to be in the future, so "again" is positive:
1403	w->again = timeout - now;	1426	w->repeat = timeout - now;
1404	ev_timer_again (EV_A_ w);	1427	ev_timer_again (EV_A_ w);
1405	}	1428	}
1406	}	1429	}
1407		1430
1408	To summarise the callback: first calculate the real timeout (defined	1431	To summarise the callback: first calculate the real timeout (defined
…		…
1910		1933
1911		1934
1912	=head2 C<ev_stat> - did the file attributes just change?	1935	=head2 C<ev_stat> - did the file attributes just change?
1913		1936
1914	This watches a file system path for attribute changes. That is, it calls	1937	This watches a file system path for attribute changes. That is, it calls
1915	C<stat> regularly (or when the OS says it changed) and sees if it changed	1938	C<stat> on that path in regular intervals (or when the OS says it changed)
1916	compared to the last time, invoking the callback if it did.	1939	and sees if it changed compared to the last time, invoking the callback if
		1940	it did.
1917		1941
1918	The path does not need to exist: changing from "path exists" to "path does	1942	The path does not need to exist: changing from "path exists" to "path does
1919	not exist" is a status change like any other. The condition "path does	1943	not exist" is a status change like any other. The condition "path does not
1920	not exist" is signified by the C<st_nlink> field being zero (which is	1944	exist" (or more correctly "path cannot be stat'ed") is signified by the
1921	otherwise always forced to be at least one) and all the other fields of	1945	C<st_nlink> field being zero (which is otherwise always forced to be at
1922	the stat buffer having unspecified contents.	1946	least one) and all the other fields of the stat buffer having unspecified
		1947	contents.
1923		1948
1924	The path I<should> be absolute and I<must not> end in a slash. If it is	1949	The path I<must not> end in a slash or contain special components such as
		1950	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1925	relative and your working directory changes, the behaviour is undefined.	1951	your working directory changes, then the behaviour is undefined.
1926		1952
1927	Since there is no standard kernel interface to do this, the portable	1953	Since there is no portable change notification interface available, the
1928	implementation simply calls C<stat (2)> regularly on the path to see if	1954	portable implementation simply calls C<stat(2)> regularly on the path
1929	it changed somehow. You can specify a recommended polling interval for	1955	to see if it changed somehow. You can specify a recommended polling
1930	this case. If you specify a polling interval of C<0> (highly recommended!)	1956	interval for this case. If you specify a polling interval of C<0> (highly
1931	then a I<suitable, unspecified default> value will be used (which	1957	recommended!) then a I<suitable, unspecified default> value will be used
1932	you can expect to be around five seconds, although this might change	1958	(which you can expect to be around five seconds, although this might
1933	dynamically). Libev will also impose a minimum interval which is currently	1959	change dynamically). Libev will also impose a minimum interval which is
1934	around C<0.1>, but thats usually overkill.	1960	currently around C<0.1>, but that's usually overkill.
1935		1961
1936	This watcher type is not meant for massive numbers of stat watchers,	1962	This watcher type is not meant for massive numbers of stat watchers,
1937	as even with OS-supported change notifications, this can be	1963	as even with OS-supported change notifications, this can be
1938	resource-intensive.	1964	resource-intensive.
1939		1965
1940	At the time of this writing, the only OS-specific interface implemented	1966	At the time of this writing, the only OS-specific interface implemented
1941	is the Linux inotify interface (implementing kqueue support is left as	1967	is the Linux inotify interface (implementing kqueue support is left as an
1942	an exercise for the reader. Note, however, that the author sees no way	1968	exercise for the reader. Note, however, that the author sees no way of
1943	of implementing C<ev_stat> semantics with kqueue).	1969	implementing C<ev_stat> semantics with kqueue, except as a hint).
1944		1970
1945	=head3 ABI Issues (Largefile Support)	1971	=head3 ABI Issues (Largefile Support)
1946		1972
1947	Libev by default (unless the user overrides this) uses the default	1973	Libev by default (unless the user overrides this) uses the default
1948	compilation environment, which means that on systems with large file	1974	compilation environment, which means that on systems with large file
1949	support disabled by default, you get the 32 bit version of the stat	1975	support disabled by default, you get the 32 bit version of the stat
1950	structure. When using the library from programs that change the ABI to	1976	structure. When using the library from programs that change the ABI to
1951	use 64 bit file offsets the programs will fail. In that case you have to	1977	use 64 bit file offsets the programs will fail. In that case you have to
1952	compile libev with the same flags to get binary compatibility. This is	1978	compile libev with the same flags to get binary compatibility. This is
1953	obviously the case with any flags that change the ABI, but the problem is	1979	obviously the case with any flags that change the ABI, but the problem is
1954	most noticeably disabled with ev_stat and large file support.	1980	most noticeably displayed with ev_stat and large file support.
1955		1981
1956	The solution for this is to lobby your distribution maker to make large	1982	The solution for this is to lobby your distribution maker to make large
1957	file interfaces available by default (as e.g. FreeBSD does) and not	1983	file interfaces available by default (as e.g. FreeBSD does) and not
1958	optional. Libev cannot simply switch on large file support because it has	1984	optional. Libev cannot simply switch on large file support because it has
1959	to exchange stat structures with application programs compiled using the	1985	to exchange stat structures with application programs compiled using the
1960	default compilation environment.	1986	default compilation environment.
1961		1987
1962	=head3 Inotify and Kqueue	1988	=head3 Inotify and Kqueue
1963		1989
1964	When C<inotify (7)> support has been compiled into libev (generally	1990	When C<inotify (7)> support has been compiled into libev and present at
1965	only available with Linux 2.6.25 or above due to bugs in earlier	1991	runtime, it will be used to speed up change detection where possible. The
1966	implementations) and present at runtime, it will be used to speed up	1992	inotify descriptor will be created lazily when the first C<ev_stat>
1967	change detection where possible. The inotify descriptor will be created	1993	watcher is being started.
1968	lazily when the first C<ev_stat> watcher is being started.
1969		1994
1970	Inotify presence does not change the semantics of C<ev_stat> watchers	1995	Inotify presence does not change the semantics of C<ev_stat> watchers
1971	except that changes might be detected earlier, and in some cases, to avoid	1996	except that changes might be detected earlier, and in some cases, to avoid
1972	making regular C<stat> calls. Even in the presence of inotify support	1997	making regular C<stat> calls. Even in the presence of inotify support
1973	there are many cases where libev has to resort to regular C<stat> polling,	1998	there are many cases where libev has to resort to regular C<stat> polling,
1974	but as long as the path exists, libev usually gets away without polling.	1999	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		2000	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		2001	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		2002	xfs are fully working) libev usually gets away without polling.
1975		2003
1976	There is no support for kqueue, as apparently it cannot be used to	2004	There is no support for kqueue, as apparently it cannot be used to
1977	implement this functionality, due to the requirement of having a file	2005	implement this functionality, due to the requirement of having a file
1978	descriptor open on the object at all times, and detecting renames, unlinks	2006	descriptor open on the object at all times, and detecting renames, unlinks
1979	etc. is difficult.	2007	etc. is difficult.
1980		2008
		2009	=head3 C<stat ()> is a synchronous operation
		2010
		2011	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2012	the process. The exception are C<ev_stat> watchers - those call C<stat
		2013	()>, which is a synchronous operation.
		2014
		2015	For local paths, this usually doesn't matter: unless the system is very
		2016	busy or the intervals between stat's are large, a stat call will be fast,
		2017	as the path data is suually in memory already (except when starting the
		2018	watcher).
		2019
		2020	For networked file systems, calling C<stat ()> can block an indefinite
		2021	time due to network issues, and even under good conditions, a stat call
		2022	often takes multiple milliseconds.
		2023
		2024	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2025	paths, although this is fully supported by libev.
		2026
1981	=head3 The special problem of stat time resolution	2027	=head3 The special problem of stat time resolution
1982		2028
1983	The C<stat ()> system call only supports full-second resolution portably, and	2029	The C<stat ()> system call only supports full-second resolution portably,
1984	even on systems where the resolution is higher, most file systems still	2030	and even on systems where the resolution is higher, most file systems
1985	only support whole seconds.	2031	still only support whole seconds.
1986		2032
1987	That means that, if the time is the only thing that changes, you can	2033	That means that, if the time is the only thing that changes, you can
1988	easily miss updates: on the first update, C<ev_stat> detects a change and	2034	easily miss updates: on the first update, C<ev_stat> detects a change and
1989	calls your callback, which does something. When there is another update	2035	calls your callback, which does something. When there is another update
1990	within the same second, C<ev_stat> will be unable to detect unless the	2036	within the same second, C<ev_stat> will be unable to detect unless the
…		…
2629	=over 4	2675	=over 4
2630		2676
2631	=item ev_async_init (ev_async *, callback)	2677	=item ev_async_init (ev_async *, callback)
2632		2678
2633	Initialises and configures the async watcher - it has no parameters of any	2679	Initialises and configures the async watcher - it has no parameters of any
2634	kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless,	2680	kind. There is a C<ev_async_set> macro, but using it is utterly pointless,
2635	trust me.	2681	trust me.
2636		2682
2637	=item ev_async_send (loop, ev_async *)	2683	=item ev_async_send (loop, ev_async *)
2638		2684
2639	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	2685	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
…		…
2845		2891
2846	myclass obj;	2892	myclass obj;
2847	ev::io iow;	2893	ev::io iow;
2848	iow.set <myclass, &myclass::io_cb> (&obj);	2894	iow.set <myclass, &myclass::io_cb> (&obj);
2849		2895
		2896	=item w->set (object *)
		2897
		2898	This is an B<experimental> feature that might go away in a future version.
		2899
		2900	This is a variation of a method callback - leaving out the method to call
		2901	will default the method to C<operator ()>, which makes it possible to use
		2902	functor objects without having to manually specify the C<operator ()> all
		2903	the time. Incidentally, you can then also leave out the template argument
		2904	list.
		2905
		2906	The C<operator ()> method prototype must be C<void operator ()(watcher &w,
		2907	int revents)>.
		2908
		2909	See the method-C<set> above for more details.
		2910
		2911	Example: use a functor object as callback.
		2912
		2913	struct myfunctor
		2914	{
		2915	void operator() (ev::io &w, int revents)
		2916	{
		2917	...
		2918	}
		2919	}
		2920
		2921	myfunctor f;
		2922
		2923	ev::io w;
		2924	w.set (&f);
		2925
2850	=item w->set<function> (void *data = 0)	2926	=item w->set<function> (void *data = 0)
2851		2927
2852	Also sets a callback, but uses a static method or plain function as	2928	Also sets a callback, but uses a static method or plain function as
2853	callback. The optional C<data> argument will be stored in the watcher's	2929	callback. The optional C<data> argument will be stored in the watcher's
2854	C<data> member and is free for you to use.	2930	C<data> member and is free for you to use.
…		…
2953	Tony Arcieri has written a ruby extension that offers access to a subset	3029	Tony Arcieri has written a ruby extension that offers access to a subset
2954	of the libev API and adds file handle abstractions, asynchronous DNS and	3030	of the libev API and adds file handle abstractions, asynchronous DNS and
2955	more on top of it. It can be found via gem servers. Its homepage is at	3031	more on top of it. It can be found via gem servers. Its homepage is at
2956	L<http://rev.rubyforge.org/>.	3032	L<http://rev.rubyforge.org/>.
2957		3033
		3034	Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190>
		3035	makes rev work even on mingw.
		3036
2958	=item D	3037	=item D
2959		3038
2960	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3039	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2961	be found at L<http://proj.llucax.com.ar/wiki/evd>.	3040	be found at L<http://proj.llucax.com.ar/wiki/evd>.
		3041
		3042	=item Ocaml
		3043
		3044	Erkki Seppala has written Ocaml bindings for libev, to be found at
		3045	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
2962		3046
2963	=back	3047	=back
2964		3048
2965		3049
2966	=head1 MACRO MAGIC	3050	=head1 MACRO MAGIC
…		…
3067		3151
3068	#define EV_STANDALONE 1	3152	#define EV_STANDALONE 1
3069	#include "ev.h"	3153	#include "ev.h"
3070		3154
3071	Both header files and implementation files can be compiled with a C++	3155	Both header files and implementation files can be compiled with a C++
3072	compiler (at least, thats a stated goal, and breakage will be treated	3156	compiler (at least, that's a stated goal, and breakage will be treated
3073	as a bug).	3157	as a bug).
3074		3158
3075	You need the following files in your source tree, or in a directory	3159	You need the following files in your source tree, or in a directory
3076	in your include path (e.g. in libev/ when using -Ilibev):	3160	in your include path (e.g. in libev/ when using -Ilibev):
3077		3161
…		…
3133	keeps libev from including F<config.h>, and it also defines dummy	3217	keeps libev from including F<config.h>, and it also defines dummy
3134	implementations for some libevent functions (such as logging, which is not	3218	implementations for some libevent functions (such as logging, which is not
3135	supported). It will also not define any of the structs usually found in	3219	supported). It will also not define any of the structs usually found in
3136	F<event.h> that are not directly supported by the libev core alone.	3220	F<event.h> that are not directly supported by the libev core alone.
3137		3221
		3222	In stanbdalone mode, libev will still try to automatically deduce the
		3223	configuration, but has to be more conservative.
		3224
3138	=item EV_USE_MONOTONIC	3225	=item EV_USE_MONOTONIC
3139		3226
3140	If defined to be C<1>, libev will try to detect the availability of the	3227	If defined to be C<1>, libev will try to detect the availability of the
3141	monotonic clock option at both compile time and runtime. Otherwise no use	3228	monotonic clock option at both compile time and runtime. Otherwise no
3142	of the monotonic clock option will be attempted. If you enable this, you	3229	use of the monotonic clock option will be attempted. If you enable this,
3143	usually have to link against librt or something similar. Enabling it when	3230	you usually have to link against librt or something similar. Enabling it
3144	the functionality isn't available is safe, though, although you have	3231	when the functionality isn't available is safe, though, although you have
3145	to make sure you link against any libraries where the C<clock_gettime>	3232	to make sure you link against any libraries where the C<clock_gettime>
3146	function is hiding in (often F<-lrt>).	3233	function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>.
3147		3234
3148	=item EV_USE_REALTIME	3235	=item EV_USE_REALTIME
3149		3236
3150	If defined to be C<1>, libev will try to detect the availability of the	3237	If defined to be C<1>, libev will try to detect the availability of the
3151	real-time clock option at compile time (and assume its availability at	3238	real-time clock option at compile time (and assume its availability at
3152	runtime if successful). Otherwise no use of the real-time clock option will	3239	runtime if successful). Otherwise no use of the real-time clock option will
3153	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	3240	be attempted. This effectively replaces C<gettimeofday> by C<clock_get
3154	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	3241	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the
3155	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	3242	note about libraries in the description of C<EV_USE_MONOTONIC>, though.
3156		3243
		3244	=item EV_USE_CLOCK_SYSCALL
		3245
		3246	If defined to be C<1>, libev will try to use a direct syscall instead
		3247	of calling the system-provided C<clock_gettime> function. This option
		3248	exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt>
		3249	unconditionally pulls in C<libpthread>, slowing down single-threaded
		3250	programs needlessly. Using a direct syscall is slightly slower (in
		3251	theory), because no optimised vdso implementation can be used, but avoids
		3252	the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or
		3253	higher, as it simplifies linking (no need for C<-lrt>).
		3254
3157	=item EV_USE_NANOSLEEP	3255	=item EV_USE_NANOSLEEP
3158		3256
3159	If defined to be C<1>, libev will assume that C<nanosleep ()> is available	3257	If defined to be C<1>, libev will assume that C<nanosleep ()> is available
3160	and will use it for delays. Otherwise it will use C<select ()>.	3258	and will use it for delays. Otherwise it will use C<select ()>.
3161		3259
…		…
3176		3274
3177	=item EV_SELECT_USE_FD_SET	3275	=item EV_SELECT_USE_FD_SET
3178		3276
3179	If defined to C<1>, then the select backend will use the system C<fd_set>	3277	If defined to C<1>, then the select backend will use the system C<fd_set>
3180	structure. This is useful if libev doesn't compile due to a missing	3278	structure. This is useful if libev doesn't compile due to a missing
3181	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on	3279	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout
3182	exotic systems. This usually limits the range of file descriptors to some	3280	on exotic systems. This usually limits the range of file descriptors to
3183	low limit such as 1024 or might have other limitations (winsocket only	3281	some low limit such as 1024 or might have other limitations (winsocket
3184	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	3282	only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
3185	influence the size of the C<fd_set> used.	3283	configures the maximum size of the C<fd_set>.
3186		3284
3187	=item EV_SELECT_IS_WINSOCKET	3285	=item EV_SELECT_IS_WINSOCKET
3188		3286
3189	When defined to C<1>, the select backend will assume that	3287	When defined to C<1>, the select backend will assume that
3190	select/socket/connect etc. don't understand file descriptors but	3288	select/socket/connect etc. don't understand file descriptors but
…		…
3549	loop, as long as you don't confuse yourself). The only exception is that	3647	loop, as long as you don't confuse yourself). The only exception is that
3550	you must not do this from C<ev_periodic> reschedule callbacks.	3648	you must not do this from C<ev_periodic> reschedule callbacks.
3551		3649
3552	Care has been taken to ensure that libev does not keep local state inside	3650	Care has been taken to ensure that libev does not keep local state inside
3553	C<ev_loop>, and other calls do not usually allow for coroutine switches as	3651	C<ev_loop>, and other calls do not usually allow for coroutine switches as
3554	they do not clal any callbacks.	3652	they do not call any callbacks.
3555		3653
3556	=head2 COMPILER WARNINGS	3654	=head2 COMPILER WARNINGS
3557		3655
3558	Depending on your compiler and compiler settings, you might get no or a	3656	Depending on your compiler and compiler settings, you might get no or a
3559	lot of warnings when compiling libev code. Some people are apparently	3657	lot of warnings when compiling libev code. Some people are apparently
…		…
3593	==2274== definitely lost: 0 bytes in 0 blocks.	3691	==2274== definitely lost: 0 bytes in 0 blocks.
3594	==2274== possibly lost: 0 bytes in 0 blocks.	3692	==2274== possibly lost: 0 bytes in 0 blocks.
3595	==2274== still reachable: 256 bytes in 1 blocks.	3693	==2274== still reachable: 256 bytes in 1 blocks.
3596		3694
3597	Then there is no memory leak, just as memory accounted to global variables	3695	Then there is no memory leak, just as memory accounted to global variables
3598	is not a memleak - the memory is still being refernced, and didn't leak.	3696	is not a memleak - the memory is still being referenced, and didn't leak.
3599		3697
3600	Similarly, under some circumstances, valgrind might report kernel bugs	3698	Similarly, under some circumstances, valgrind might report kernel bugs
3601	as if it were a bug in libev (e.g. in realloc or in the poll backend,	3699	as if it were a bug in libev (e.g. in realloc or in the poll backend,
3602	although an acceptable workaround has been found here), or it might be	3700	although an acceptable workaround has been found here), or it might be
3603	confused.	3701	confused.
…		…
3841	=back	3939	=back
3842		3940
3843		3941
3844	=head1 AUTHOR	3942	=head1 AUTHOR
3845		3943
3846	Marc Lehmann <libev@schmorp.de>.	3944	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.
3847		3945

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.200 by root, Thu Oct 23 07:33:45 2008 UTC vs. Revision 1.221 by root, Wed Dec 3 15:23:44 2008 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.200 by root, Thu Oct 23 07:33:45 2008 UTC vs.
Revision 1.221 by root, Wed Dec 3 15:23:44 2008 UTC