summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2009-04-16 06:17:26 +0000
committerroot <root>2009-04-16 06:17:26 +0000
commita342811d954d19b6ca6d00c43207305d58973aac (patch)
tree2f84841b2748ec53093a7262cd72ac92a750077f /ev.pod
parent063940f2d384a70bbf0499865ca0e54e99b96f23 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod4
1 files changed, 3 insertions, 1 deletions
diff --git a/ev.pod b/ev.pod
index 467ac14..1070738 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1085,6 +1085,8 @@ integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
before watchers with lower priority, but priority will not keep watchers
from being executed (except for C<ev_idle> watchers).
+See L<
+
This means that priorities are I<only> used for ordering callback
invocation after new events have been received. This is useful, for
example, to reduce latency after idling, or more often, to bind two
@@ -1584,7 +1586,7 @@ If the timer is started but non-repeating, stop it (as if it timed out).
If the timer is repeating, either start it if necessary (with the
C<repeat> value), or reset the running timer to the C<repeat> value.
-This sounds a bit complicated, see "Be smart about timeouts", above, for a
+This sounds a bit complicated, see L<Be smart about timeouts>, above, for a
usage example.
=item ev_tstamp repeat [read-write]