← Back to branch summary

~ubuntu-branches/ubuntu/hardy/transmission/hardy-updates

« back to all changes in this revision

Viewing changes to third-party/libevent/event.3

  • Committer: Bazaar Package Importer
  • Author(s): Philipp Benner
  • Date: 2008-01-05 09:16:52 UTC
  • mto: This revision was merged to the branch mainline in revision 11.
  • Revision ID: james.westby@ubuntu.com-20080105091652-8cf0z4rb3pu8d6jt
Tags: upstream-1.00
Import upstream version 1.00

Show diffs side-by-side

added added

removed removed

Lines of Context:
third-party/libevent/event.3
34
34
.Nm event_dispatch ,
35
35
.Nm event_loop ,
36
36
.Nm event_loopexit ,
 
37
.Nm event_loopbreak ,
37
38
.Nm event_set ,
38
39
.Nm event_base_dispatch ,
39
40
.Nm event_base_loop ,
40
41
.Nm event_base_loopexit ,
 
42
.Nm event_base_loopbreak ,
41
43
.Nm event_base_set ,
42
44
.Nm event_base_free ,
43
45
.Nm event_add ,
93
95
.Fn "event_loop" "int flags"
94
96
.Ft int
95
97
.Fn "event_loopexit" "struct timeval *tv"
 
98
.Ft int
 
99
.Fn "event_loopbreak" "void"
96
100
.Ft void
97
101
.Fn "event_set" "struct event *ev" "int fd" "short event" "void (*fn)(int, short, void *)" "void *arg"
98
102
.Ft int
102
106
.Ft int
103
107
.Fn "event_base_loopexit" "struct event_base *base" "struct timeval *tv"
104
108
.Ft int
 
109
.Fn "event_base_loopbreak" "struct event_base *base"
 
110
.Ft int
105
111
.Fn "event_base_set" "struct event_base *base" "struct event *"
106
112
.Ft void
107
113
.Fn "event_base_free" "struct event_base *base"
419
425
exit without blocking for events again. Subsequent invocations of
420
426
.Fn event_loop
421
427
will proceed normally.
422
 
The parameter indicates the time after which the loop should terminate.
 
428
The
 
429
.Nm event_loopbreak
 
430
function exits from the event loop immediately.
 
431
.Fn event_loop
 
432
will abort after the next event is completed;
 
433
.Fn event_loopbreak
 
434
is typically invoked from this event's callback. This behavior is analogous
 
435
to the "break;" statement. Subsequent invocations of
 
436
.Fn event_loop
 
437
will proceed normally.
423
438
.Pp
424
439
It is the responsibility of the caller to provide these functions with
425
440
pre-allocated event structures.