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

Comparing libev/ev.pod (file contents):
Revision 1.55 by root, Tue Nov 27 20:38:07 2007 UTC vs.
Revision 1.67 by root, Fri Dec 7 16:44:12 2007 UTC

…		…
63	details of the event, and then hand it over to libev by I<starting> the	63	details of the event, and then hand it over to libev by I<starting> the
64	watcher.	64	watcher.
65		65
66	=head1 FEATURES	66	=head1 FEATURES
67		67
68	Libev supports C<select>, C<poll>, the linux-specific C<epoll>, the	68	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
69	bsd-specific C<kqueue> and the solaris-specific event port mechanisms	69	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
70	for file descriptor events (C<ev_io>), relative timers (C<ev_timer>),	70	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
		71	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers
71	absolute timers with customised rescheduling (C<ev_periodic>), synchronous	72	with customised rescheduling (C<ev_periodic>), synchronous signals
72	signals (C<ev_signal>), process status change events (C<ev_child>), and	73	(C<ev_signal>), process status change events (C<ev_child>), and event
73	event watchers dealing with the event loop mechanism itself (C<ev_idle>,	74	watchers dealing with the event loop mechanism itself (C<ev_idle>,
74	C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as	75	C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as
75	file watchers (C<ev_stat>) and even limited support for fork events	76	file watchers (C<ev_stat>) and even limited support for fork events
76	(C<ev_fork>).	77	(C<ev_fork>).
77		78
78	It also is quite fast (see this	79	It also is quite fast (see this
…		…
162	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	163	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for
163	recommended ones.	164	recommended ones.
164		165
165	See the description of C<ev_embed> watchers for more info.	166	See the description of C<ev_embed> watchers for more info.
166		167
167	=item ev_set_allocator (void (cb)(void *ptr, size_t size))	168	=item ev_set_allocator (void (cb)(void *ptr, long size))
168		169
169	Sets the allocation function to use (the prototype and semantics are	170	Sets the allocation function to use (the prototype is similar - the
170	identical to the realloc C function). It is used to allocate and free	171	semantics is identical - to the realloc C function). It is used to
171	memory (no surprises here). If it returns zero when memory needs to be	172	allocate and free memory (no surprises here). If it returns zero when
172	allocated, the library might abort or take some potentially destructive	173	memory needs to be allocated, the library might abort or take some
173	action. The default is your system realloc function.	174	potentially destructive action. The default is your system realloc
		175	function.
174		176
175	You could override this function in high-availability programs to, say,	177	You could override this function in high-availability programs to, say,
176	free some memory if it cannot allocate memory, to use a special allocator,	178	free some memory if it cannot allocate memory, to use a special allocator,
177	or even to sleep a while and retry until some memory is available.	179	or even to sleep a while and retry until some memory is available.
178		180
…		…
264	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will	266	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
265	override the flags completely if it is found in the environment. This is	267	override the flags completely if it is found in the environment. This is
266	useful to try out specific backends to test their performance, or to work	268	useful to try out specific backends to test their performance, or to work
267	around bugs.	269	around bugs.
268		270
		271	=item C<EVFLAG_FORKCHECK>
		272
		273	Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after
		274	a fork, you can also make libev check for a fork in each iteration by
		275	enabling this flag.
		276
		277	This works by calling C<getpid ()> on every iteration of the loop,
		278	and thus this might slow down your event loop if you do a lot of loop
		279	iterations and little real work, but is usually not noticeable (on my
		280	Linux system for example, C<getpid> is actually a simple 5-insn sequence
		281	without a syscall and thus I<very> fast, but my Linux system also has
		282	C<pthread_atfork> which is even faster).
		283
		284	The big advantage of this flag is that you can forget about fork (and
		285	forget about forgetting to tell libev about forking) when you use this
		286	flag.
		287
		288	This flag setting cannot be overriden or specified in the C<LIBEV_FLAGS>
		289	environment variable.
		290
269	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	291	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
270		292
271	This is your standard select(2) backend. Not I<completely> standard, as	293	This is your standard select(2) backend. Not I<completely> standard, as
272	libev tries to roll its own fd_set with no limits on the number of fds,	294	libev tries to roll its own fd_set with no limits on the number of fds,
273	but if that fails, expect a fairly low limit on the number of fds when	295	but if that fails, expect a fairly low limit on the number of fds when
…		…
407	=item ev_loop_fork (loop)	429	=item ev_loop_fork (loop)
408		430
409	Like C<ev_default_fork>, but acts on an event loop created by	431	Like C<ev_default_fork>, but acts on an event loop created by
410	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	432	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
411	after fork, and how you do this is entirely your own problem.	433	after fork, and how you do this is entirely your own problem.
		434
		435	=item unsigned int ev_loop_count (loop)
		436
		437	Returns the count of loop iterations for the loop, which is identical to
		438	the number of times libev did poll for new events. It starts at C<0> and
		439	happily wraps around with enough iterations.
		440
		441	This value can sometimes be useful as a generation counter of sorts (it
		442	"ticks" the number of loop iterations), as it roughly corresponds with
		443	C<ev_prepare> and C<ev_check> calls.
412		444
413	=item unsigned int ev_backend (loop)	445	=item unsigned int ev_backend (loop)
414		446
415	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	447	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
416	use.	448	use.
…		…
712	=item ev_cb_set (ev_TYPE *watcher, callback)	744	=item ev_cb_set (ev_TYPE *watcher, callback)
713		745
714	Change the callback. You can change the callback at virtually any time	746	Change the callback. You can change the callback at virtually any time
715	(modulo threads).	747	(modulo threads).
716		748
		749	=item ev_set_priority (ev_TYPE *watcher, priority)
		750
		751	=item int ev_priority (ev_TYPE *watcher)
		752
		753	Set and query the priority of the watcher. The priority is a small
		754	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
		755	(default: C<-2>). Pending watchers with higher priority will be invoked
		756	before watchers with lower priority, but priority will not keep watchers
		757	from being executed (except for C<ev_idle> watchers).
		758
		759	This means that priorities are I<only> used for ordering callback
		760	invocation after new events have been received. This is useful, for
		761	example, to reduce latency after idling, or more often, to bind two
		762	watchers on the same event and make sure one is called first.
		763
		764	If you need to suppress invocation when higher priority events are pending
		765	you need to look at C<ev_idle> watchers, which provide this functionality.
		766
		767	The default priority used by watchers when no priority has been set is
		768	always C<0>, which is supposed to not be too high and not be too low :).
		769
		770	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
		771	fine, as long as you do not mind that the priority value you query might
		772	or might not have been adjusted to be within valid range.
		773
717	=back	774	=back
718		775
719		776
720	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	777	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
721		778
…		…
914	=item ev_timer_again (loop)	971	=item ev_timer_again (loop)
915		972
916	This will act as if the timer timed out and restart it again if it is	973	This will act as if the timer timed out and restart it again if it is
917	repeating. The exact semantics are:	974	repeating. The exact semantics are:
918		975
		976	If the timer is pending, its pending status is cleared.
		977
919	If the timer is started but nonrepeating, stop it.	978	If the timer is started but nonrepeating, stop it (as if it timed out).
920		979
921	If the timer is repeating, either start it if necessary (with the repeat	980	If the timer is repeating, either start it if necessary (with the
922	value), or reset the running timer to the repeat value.	981	C<repeat> value), or reset the running timer to the C<repeat> value.
923		982
924	This sounds a bit complicated, but here is a useful and typical	983	This sounds a bit complicated, but here is a useful and typical
925	example: Imagine you have a tcp connection and you want a so-called	984	example: Imagine you have a tcp connection and you want a so-called idle
926	idle timeout, that is, you want to be called when there have been,	985	timeout, that is, you want to be called when there have been, say, 60
927	say, 60 seconds of inactivity on the socket. The easiest way to do	986	seconds of inactivity on the socket. The easiest way to do this is to
928	this is to configure an C<ev_timer> with C<after>=C<repeat>=C<60> and calling	987	configure an C<ev_timer> with a C<repeat> value of C<60> and then call
929	C<ev_timer_again> each time you successfully read or write some data. If	988	C<ev_timer_again> each time you successfully read or write some data. If
930	you go into an idle state where you do not expect data to travel on the	989	you go into an idle state where you do not expect data to travel on the
931	socket, you can stop the timer, and again will automatically restart it if	990	socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
932	need be.	991	automatically restart it if need be.
933		992
934	You can also ignore the C<after> value and C<ev_timer_start> altogether	993	That means you can ignore the C<after> value and C<ev_timer_start>
935	and only ever use the C<repeat> value:	994	altogether and only ever use the C<repeat> value and C<ev_timer_again>:
936		995
937	ev_timer_init (timer, callback, 0., 5.);	996	ev_timer_init (timer, callback, 0., 5.);
938	ev_timer_again (loop, timer);	997	ev_timer_again (loop, timer);
939	...	998	...
940	timer->again = 17.;	999	timer->again = 17.;
941	ev_timer_again (loop, timer);	1000	ev_timer_again (loop, timer);
942	...	1001	...
943	timer->again = 10.;	1002	timer->again = 10.;
944	ev_timer_again (loop, timer);	1003	ev_timer_again (loop, timer);
945		1004
946	This is more efficient then stopping/starting the timer eahc time you want	1005	This is more slightly efficient then stopping/starting the timer each time
947	to modify its timeout value.	1006	you want to modify its timeout value.
948		1007
949	=item ev_tstamp repeat [read-write]	1008	=item ev_tstamp repeat [read-write]
950		1009
951	The current C<repeat> value. Will be used each time the watcher times out	1010	The current C<repeat> value. Will be used each time the watcher times out
952	or C<ev_timer_again> is called and determines the next timeout (if any),	1011	or C<ev_timer_again> is called and determines the next timeout (if any),
…		…
1221	not exist" is a status change like any other. The condition "path does	1280	not exist" is a status change like any other. The condition "path does
1222	not exist" is signified by the C<st_nlink> field being zero (which is	1281	not exist" is signified by the C<st_nlink> field being zero (which is
1223	otherwise always forced to be at least one) and all the other fields of	1282	otherwise always forced to be at least one) and all the other fields of
1224	the stat buffer having unspecified contents.	1283	the stat buffer having unspecified contents.
1225		1284
		1285	The path I<should> be absolute and I<must not> end in a slash. If it is
		1286	relative and your working directory changes, the behaviour is undefined.
		1287
1226	Since there is no standard to do this, the portable implementation simply	1288	Since there is no standard to do this, the portable implementation simply
1227	calls C<stat (2)> regulalry on the path to see if it changed somehow. You	1289	calls C<stat (2)> regularly on the path to see if it changed somehow. You
1228	can specify a recommended polling interval for this case. If you specify	1290	can specify a recommended polling interval for this case. If you specify
1229	a polling interval of C<0> (highly recommended!) then a I<suitable,	1291	a polling interval of C<0> (highly recommended!) then a I<suitable,
1230	unspecified default> value will be used (which you can expect to be around	1292	unspecified default> value will be used (which you can expect to be around
1231	five seconds, although this might change dynamically). Libev will also	1293	five seconds, although this might change dynamically). Libev will also
1232	impose a minimum interval which is currently around C<0.1>, but thats	1294	impose a minimum interval which is currently around C<0.1>, but thats
…		…
1234		1296
1235	This watcher type is not meant for massive numbers of stat watchers,	1297	This watcher type is not meant for massive numbers of stat watchers,
1236	as even with OS-supported change notifications, this can be	1298	as even with OS-supported change notifications, this can be
1237	resource-intensive.	1299	resource-intensive.
1238		1300
1239	At the time of this writing, no specific OS backends are implemented, but	1301	At the time of this writing, only the Linux inotify interface is
1240	if demand increases, at least a kqueue and inotify backend will be added.	1302	implemented (implementing kqueue support is left as an exercise for the
		1303	reader). Inotify will be used to give hints only and should not change the
		1304	semantics of C<ev_stat> watchers, which means that libev sometimes needs
		1305	to fall back to regular polling again even with inotify, but changes are
		1306	usually detected immediately, and if the file exists there will be no
		1307	polling.
1241		1308
1242	=over 4	1309	=over 4
1243		1310
1244	=item ev_stat_init (ev_stat , callback, const char path, ev_tstamp interval)	1311	=item ev_stat_init (ev_stat , callback, const char path, ev_tstamp interval)
1245		1312
…		…
1309	ev_stat_start (loop, &passwd);	1376	ev_stat_start (loop, &passwd);
1310		1377
1311		1378
1312	=head2 C<ev_idle> - when you've got nothing better to do...	1379	=head2 C<ev_idle> - when you've got nothing better to do...
1313		1380
1314	Idle watchers trigger events when there are no other events are pending	1381	Idle watchers trigger events when no other events of the same or higher
1315	(prepare, check and other idle watchers do not count). That is, as long	1382	priority are pending (prepare, check and other idle watchers do not
1316	as your process is busy handling sockets or timeouts (or even signals,	1383	count).
1317	imagine) it will not be triggered. But when your process is idle all idle	1384
1318	watchers are being called again and again, once per event loop iteration -	1385	That is, as long as your process is busy handling sockets or timeouts
		1386	(or even signals, imagine) of the same or higher priority it will not be
		1387	triggered. But when your process is idle (or only lower-priority watchers
		1388	are pending), the idle watchers are being called once per event loop
1319	until stopped, that is, or your process receives more events and becomes	1389	iteration - until stopped, that is, or your process receives more events
1320	busy.	1390	and becomes busy again with higher priority stuff.
1321		1391
1322	The most noteworthy effect is that as long as any idle watchers are	1392	The most noteworthy effect is that as long as any idle watchers are
1323	active, the process will not block when waiting for new events.	1393	active, the process will not block when waiting for new events.
1324		1394
1325	Apart from keeping your process non-blocking (which is a useful	1395	Apart from keeping your process non-blocking (which is a useful
…		…
1425		1495
1426	// create io watchers for each fd and a timer before blocking	1496	// create io watchers for each fd and a timer before blocking
1427	static void	1497	static void
1428	adns_prepare_cb (ev_loop loop, ev_prepare w, int revents)	1498	adns_prepare_cb (ev_loop loop, ev_prepare w, int revents)
1429	{	1499	{
1430	int timeout = 3600000;truct pollfd fds [nfd];	1500	int timeout = 3600000;
		1501	struct pollfd fds [nfd];
1431	// actual code will need to loop here and realloc etc.	1502	// actual code will need to loop here and realloc etc.
1432	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	1503	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1433		1504
1434	/* the callback is illegal, but won't be called as we stop during check */	1505	/* the callback is illegal, but won't be called as we stop during check */
1435	ev_timer_init (&tw, 0, timeout * 1e-3);	1506	ev_timer_init (&tw, 0, timeout * 1e-3);
…		…
1816	Similar to the other two macros, this gives you the value of the default	1887	Similar to the other two macros, this gives you the value of the default
1817	loop, if multiple loops are supported ("ev loop default").	1888	loop, if multiple loops are supported ("ev loop default").
1818		1889
1819	=back	1890	=back
1820		1891
1821	Example: Declare and initialise a check watcher, working regardless of	1892	Example: Declare and initialise a check watcher, utilising the above
1822	wether multiple loops are supported or not.	1893	macros so it will work regardless of wether multiple loops are supported
		1894	or not.
1823		1895
1824	static void	1896	static void
1825	check_cb (EV_P_ ev_timer *w, int revents)	1897	check_cb (EV_P_ ev_timer *w, int revents)
1826	{	1898	{
1827	ev_check_stop (EV_A_ w);	1899	ev_check_stop (EV_A_ w);
…		…
1829		1901
1830	ev_check check;	1902	ev_check check;
1831	ev_check_init (&check, check_cb);	1903	ev_check_init (&check, check_cb);
1832	ev_check_start (EV_DEFAULT_ &check);	1904	ev_check_start (EV_DEFAULT_ &check);
1833	ev_loop (EV_DEFAULT_ 0);	1905	ev_loop (EV_DEFAULT_ 0);
1834
1835		1906
1836	=head1 EMBEDDING	1907	=head1 EMBEDDING
1837		1908
1838	Libev can (and often is) directly embedded into host	1909	Libev can (and often is) directly embedded into host
1839	applications. Examples of applications that embed it include the Deliantra	1910	applications. Examples of applications that embed it include the Deliantra
…		…
1879	ev_vars.h	1950	ev_vars.h
1880	ev_wrap.h	1951	ev_wrap.h
1881		1952
1882	ev_win32.c required on win32 platforms only	1953	ev_win32.c required on win32 platforms only
1883		1954
1884	ev_select.c only when select backend is enabled (which is by default)	1955	ev_select.c only when select backend is enabled (which is enabled by default)
1885	ev_poll.c only when poll backend is enabled (disabled by default)	1956	ev_poll.c only when poll backend is enabled (disabled by default)
1886	ev_epoll.c only when the epoll backend is enabled (disabled by default)	1957	ev_epoll.c only when the epoll backend is enabled (disabled by default)
1887	ev_kqueue.c only when the kqueue backend is enabled (disabled by default)	1958	ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
1888	ev_port.c only when the solaris port backend is enabled (disabled by default)	1959	ev_port.c only when the solaris port backend is enabled (disabled by default)
1889		1960
…		…
2014		2085
2015	=item EV_USE_DEVPOLL	2086	=item EV_USE_DEVPOLL
2016		2087
2017	reserved for future expansion, works like the USE symbols above.	2088	reserved for future expansion, works like the USE symbols above.
2018		2089
		2090	=item EV_USE_INOTIFY
		2091
		2092	If defined to be C<1>, libev will compile in support for the Linux inotify
		2093	interface to speed up C<ev_stat> watchers. Its actual availability will
		2094	be detected at runtime.
		2095
2019	=item EV_H	2096	=item EV_H
2020		2097
2021	The name of the F<ev.h> header file used to include it. The default if	2098	The name of the F<ev.h> header file used to include it. The default if
2022	undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This	2099	undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This
2023	can be used to virtually rename the F<ev.h> header file in case of conflicts.	2100	can be used to virtually rename the F<ev.h> header file in case of conflicts.
…		…
2052		2129
2053	If undefined or defined to be C<1>, then periodic timers are supported. If	2130	If undefined or defined to be C<1>, then periodic timers are supported. If
2054	defined to be C<0>, then they are not. Disabling them saves a few kB of	2131	defined to be C<0>, then they are not. Disabling them saves a few kB of
2055	code.	2132	code.
2056		2133
		2134	=item EV_IDLE_ENABLE
		2135
		2136	If undefined or defined to be C<1>, then idle watchers are supported. If
		2137	defined to be C<0>, then they are not. Disabling them saves a few kB of
		2138	code.
		2139
2057	=item EV_EMBED_ENABLE	2140	=item EV_EMBED_ENABLE
2058		2141
2059	If undefined or defined to be C<1>, then embed watchers are supported. If	2142	If undefined or defined to be C<1>, then embed watchers are supported. If
2060	defined to be C<0>, then they are not.	2143	defined to be C<0>, then they are not.
2061		2144
…		…
2078	=item EV_PID_HASHSIZE	2161	=item EV_PID_HASHSIZE
2079		2162
2080	C<ev_child> watchers use a small hash table to distribute workload by	2163	C<ev_child> watchers use a small hash table to distribute workload by
2081	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	2164	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more
2082	than enough. If you need to manage thousands of children you might want to	2165	than enough. If you need to manage thousands of children you might want to
2083	increase this value.	2166	increase this value (I<must> be a power of two).
		2167
		2168	=item EV_INOTIFY_HASHSIZE
		2169
		2170	C<ev_staz> watchers use a small hash table to distribute workload by
		2171	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),
		2172	usually more than enough. If you need to manage thousands of C<ev_stat>
		2173	watchers you might want to increase this value (I<must> be a power of
		2174	two).
2084		2175
2085	=item EV_COMMON	2176	=item EV_COMMON
2086		2177
2087	By default, all watchers have a C<void *data> member. By redefining	2178	By default, all watchers have a C<void *data> member. By redefining
2088	this macro to a something else you can include more and other types of	2179	this macro to a something else you can include more and other types of
…		…
2117	interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file	2208	interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file
2118	will be compiled. It is pretty complex because it provides its own header	2209	will be compiled. It is pretty complex because it provides its own header
2119	file.	2210	file.
2120		2211
2121	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	2212	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
2122	that everybody includes and which overrides some autoconf choices:	2213	that everybody includes and which overrides some configure choices:
2123		2214
		2215	#define EV_MINIMAL 1
2124	#define EV_USE_POLL 0	2216	#define EV_USE_POLL 0
2125	#define EV_MULTIPLICITY 0	2217	#define EV_MULTIPLICITY 0
2126	#define EV_PERIODICS 0	2218	#define EV_PERIODIC_ENABLE 0
		2219	#define EV_STAT_ENABLE 0
		2220	#define EV_FORK_ENABLE 0
2127	#define EV_CONFIG_H <config.h>	2221	#define EV_CONFIG_H <config.h>
		2222	#define EV_MINPRI 0
		2223	#define EV_MAXPRI 0
2128		2224
2129	#include "ev++.h"	2225	#include "ev++.h"
2130		2226
2131	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	2227	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
2132		2228
…		…
2148		2244
2149	=item Starting io/check/prepare/idle/signal/child watchers: O(1)	2245	=item Starting io/check/prepare/idle/signal/child watchers: O(1)
2150		2246
2151	=item Stopping check/prepare/idle watchers: O(1)	2247	=item Stopping check/prepare/idle watchers: O(1)
2152		2248
2153	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))	2249	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
2154		2250
2155	=item Finding the next timer per loop iteration: O(1)	2251	=item Finding the next timer per loop iteration: O(1)
2156		2252
2157	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)	2253	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
2158		2254

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.55 by root, Tue Nov 27 20:38:07 2007 UTC vs. Revision 1.67 by root, Fri Dec 7 16:44:12 2007 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.55 by root, Tue Nov 27 20:38:07 2007 UTC vs.
Revision 1.67 by root, Fri Dec 7 16:44:12 2007 UTC