Lines Matching refs:type

18    // every watcher type has its own typedef'd struct
133 name C<loop> (which is always of type C<struct ev_loop *>) will not have
141 ask). This type is called C<ev_tstamp>, which is what you should use
142 too. It usually aliases to the C<double> type in C. When you need to do
1091 watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
1128 Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
1129 macro to configure it, with arguments specific to the watcher type. There
1146 The received events usually include a single bit per event type received
1252 the type-specific C<ev_TYPE_set> macro afterwards to initialise the
1253 type-specific parts. For each type there is also a C<ev_TYPE_init> macro
1259 The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
1270 This macro initialises the type-specific parts of a watcher. You need to
1276 Although some watcher types do not have type-specific arguments
1515 miserably under the type of load it was designed to handle. In that case,
1567 functions and members specific to the watcher type are explained.
2645 This watcher type is not meant for massive numbers of stat watchers,
2764 The most-recently detected attributes of the file. Although the type is
3132 This is a rather advanced watcher type that lets you embed one event loop
3538 The callback has the type C<void (*cb)(int revents, void *arg)> and is
3582 data member, you can also "subclass" the watcher type and provide your own
3598 can cast it back to your own type:
3607 function type instead have been omitted.
3875    #define EV_CB_DECLARE(type)   struct my_coro *cb;
3907    #define EV_CB_DECLARE(type)   struct my_coro *cb;
4153 convenient to wrap them in one call. Uses the same type of arguments as
4289 It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
4304 It declares a parameter C<loop> of type C<struct ev_loop *>, quite
4603 out whether kqueue supports your type of fd properly and use an embedded
4640 Libev requires an integer type (suitable for storing C<0> or C<1>) whose
4642 such type is easily found in the C language, so you can provide your own
4643 type that you know is safe for your purposes. It is used both for signal
4708 the respective watcher type is supported. If defined to be C<0>, then it
4896 =item EV_CB_DECLARE (type)
5302 callback: The watcher callbacks have different type signatures, but libev
5312 The type C<sig_atomic_t volatile> (or whatever is defined as
5340 The type C<double> is used to represent timestamps. It is required to