From eb7909955a094de6e667e3e9f88ddbad46fc93b6 Mon Sep 17 00:00:00 2001 From: root Date: Mon, 3 Dec 2007 13:41:24 +0000 Subject: *** empty log message *** --- ev.pod | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index ed0ac1b..f372d94 100644 --- a/ev.pod +++ b/ev.pod @@ -432,6 +432,16 @@ Like C, but acts on an event loop created by C. Yes, you have to call this on every allocated event loop after fork, and how you do this is entirely your own problem. +=item unsigned int ev_loop_count (loop) + +Returns the count of loop iterations for the loop, which is identical to +the number of times libev did poll for new events. It starts at C<0> and +happily wraps around with enough iterations. + +This value can sometimes be useful as a generation counter of sorts (it +"ticks" the number of loop iterations), as it roughly corresponds with +C and C calls. + =item unsigned int ev_backend (loop) Returns one of the C flags indicating the event backend in -- cgit v1.2.3