diff options
author | root <root> | 2011-10-15 02:19:19 +0000 |
---|---|---|
committer | root <root> | 2011-10-15 02:19:19 +0000 |
commit | 1eb14aaa4fc3d23ce130d1a8ef3cef75c3d7d45f (patch) | |
tree | 8cc00ce140a3e2ac86f305d4ba3ca3202553fa36 | |
parent | 71c4c2467848e78e6b7098bbcb4ac30ce62a40a2 (diff) |
*** empty log message ***
-rw-r--r-- | ev.pod | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -1993,8 +1993,8 @@ late" side of things. =head3 The special problem of time updates -Establishing the current time is a costly operation (it usually takes at -least two system calls): EV therefore updates its idea of the current +Establishing the current time is a costly operation (it usually takes +at least one system call): EV therefore updates its idea of the current time only before and after C<ev_run> collects new events, which causes a growing difference between C<ev_now ()> and C<ev_time ()> when handling lots of events in one iteration. @@ -2011,7 +2011,7 @@ If the event loop is suspended for a long time, you can also force an update of the time returned by C<ev_now ()> by calling C<ev_now_update ()>. -=head3 The special problem of unsychronised clocks +=head3 The special problem of unsynchronised clocks Modern systems have a variety of clocks - libev itself uses the normal "wall clock" clock and, if available, the monotonic clock (to avoid time |