Lines Matching refs:set
155 set via C<ev_set_syserr_cb>, which is supposed to fix the problem or
223 Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
226 a description of the set values.
236 Return the set of all backends compiled into this binary of libev and
238 descriptor types. This set is often smaller than the one returned by
241 you know what you are doing). This is the set of backends that libev will
246 Returns the set of backends that are embeddable in other event loops. This
295 callback is set, then libev will expect it to remedy the situation, no
477 This backend maps C<EV_READ> to the C<readfds> set and C<EV_WRITE> to the
478 C<writefds> set (and to work around Microsoft Windows bugs, also onto the
479 C<exceptfds> set on that platform).
511 set, which can take considerable time (one syscall per file descriptor)
517 one cannot even remove them from the set) than registered in the set
520 that against the events to filter out spurious ones, recreating the set
984 usually doesn't make much sense to set it to a lower value than C<0.01>,
1037 loop via C<ev_break> and C<ev_async_send>, another way is to set these
1040 When set, then C<release> will be called just before the thread is
1050 have no effect on the set of file descriptors being watched, or the time
1277 (e.g. C<ev_prepare>) you still need to call its C<set> macro.
1287 Example: Initialise and set an C<ev_io> watcher in one step.
1329 Returns the callback currently set on the watcher.
1356 The default priority used by watchers when no priority has been set is
1380 Feeds the given event set into the event loop, as if the specified event
1465 In libev, Watcher priorities can be set using C<ev_set_priority>. See its
1566 information given in the last section. Any initialisation/set macros,
1710 Unfortunately, the set of errors that cause this issue differs between
1927 To start the machinery, simply initialise the watcher and set
2439 and might or might not set or restore the installed signal handler (but
2472 all signals before creating any threads (or creating them with a fully set
2525 handled at maximum priority (their priority is set to C<EV_MAXPRI> by
3055 // set the relevant poll flags
3122 // stop io watchers again - their callbacks should have set
3162 You can also set the callback to C<0>, in which case the embed watcher
3274 Most uses of C<fork ()> consist of forking, then some simple calls to set
3487 this is that C<ev_async> watchers are level-triggered: they are set on
3532 the given C<fd> and C<events> set will be created and started.
3539 passed an C<revents> set like normal event callbacks (a combination of
3664 has returned, so C<request> is not set.
3712 To exit from any of these loops, just set the corresponding exit variable:
4052 C<set> method before starting it.
4054 It will not set a callback, however: You have to call the templated C<set>
4055 method to set a callback before you can start the watcher.
4062 =item w->set<class, &class::method> (object *)
4071 callback (i.e. it is visible to it at the place of the C<set> call and
4084 iow.set <myclass, &myclass::io_cb> (&obj);
4086 =item w->set (object *)
4097 See the method-C<set> above for more details.
4112 w.set (&f);
4114 =item w->set<function> (void *data = 0)
4122 See the method-C<set> above for more details.
4127 iow.set <io_cb> ();
4129 =item w->set (loop)
4134 =item w->set ([arguments])
4143 clashing with the C<set (loop)> method.
4152 Instead of calling C<set> and C<start> methods separately, it is often
4154 the configure C<set> method of the watcher.
4188 io .set <myclass, &myclass::io_cb > (this);
4189 io2 .set <myclass, &myclass::io2_cb > (this);
4190 idle.set <myclass, &myclass::idle_cb> (this);
4192 io.set (fd, ev::WRITE); // configure the watcher
4195 io2.start (fd, ev::READ); // set + start in one call
4538 only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
4815 If this is set to C<1> at compiletime, then libev will avoid using stdio
4873 be done: If set to C<0>, no internal verification code will be compiled
4874 in. If set to C<1>, then verification code will be compiled in, but not
4875 called. If set to C<2>, then the internal verification code will be
4876 called once per loop, which can slow down libev. If set to C<3>, then the
4903 and the way callbacks are invoked and set. Must expand to a struct member