Lines Matching refs:embed

568 You still can embed kqueue into a normal poll or select backend and use it
2960 C<ev_check> watchers are often used to embed other (non-libev) event
3001 There are a number of principal ways to embed other event loops or modules
3098 want to embed is not flexible enough to support it. Instead, you can
3132 This is a rather advanced watcher type that lets you embed one event loop
3143 so nicely. In this case, you would create a kqueue-based loop and embed
3153 the rest in a second one, and embed the second one in the first.
3162 You can also set the callback to C<0>, in which case the embed watcher
3195 Configures the watcher to embed the given loop, which must be
3199 if you do not want that, you need to temporarily stop the embed watcher).
3215 Example: Try to get an embeddable event loop and embed it into the default
3223    ev_embed embed;
3231    // if we got one, then embed it, otherwise default to loop_hi
3234        ev_embed_init (&embed, 0, loop_lo);
3235        ev_embed_start (loop_hi, &embed);
3247    ev_embed embed;
3252          ev_embed_init (&embed, 0, loop_socket);
3253          ev_embed_start (loop, &embed);
3864 is still an overhead. If you embed libev, and your main usage is with some
3903 To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two
4016 to embed libev and compile libev itself as C++.
4136 Basically the same as C<ev_TYPE_set> (except for C<ev::embed> watchers>),
4142 For C<ev::embed> watchers this method is called C<set_embed>, to avoid
4165 =item w->sweep () (C<ev::embed> only)
4346 applications. Examples of applications that embed it include the Deliantra
4774 embed, async, child...) you can enable them manually by defining
4804 when you embed libev, only want to use libev functions in a single file,
5230 A typical way to use libev under windows is to embed it (see the embedding