| … | |
… | |
| 4121 | Associates a different C<struct ev_loop> with this watcher. You can only |
4121 | Associates a different C<struct ev_loop> with this watcher. You can only |
| 4122 | do this when the watcher is inactive (and not pending either). |
4122 | do this when the watcher is inactive (and not pending either). |
| 4123 | |
4123 | |
| 4124 | =item w->set ([arguments]) |
4124 | =item w->set ([arguments]) |
| 4125 | |
4125 | |
| 4126 | Basically the same as C<ev_TYPE_set>, with the same arguments. Either this |
4126 | Basically the same as C<ev_TYPE_set> (except for C<ev::embed> watchers>), |
| 4127 | method or a suitable start method must be called at least once. Unlike the |
4127 | with the same arguments. Either this method or a suitable start method |
| 4128 | C counterpart, an active watcher gets automatically stopped and restarted |
4128 | must be called at least once. Unlike the C counterpart, an active watcher |
| 4129 | when reconfiguring it with this method. |
4129 | gets automatically stopped and restarted when reconfiguring it with this |
|
|
4130 | method. |
|
|
4131 | |
|
|
4132 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
|
|
4133 | clashing with the C<set (loop)> method. |
| 4130 | |
4134 | |
| 4131 | =item w->start () |
4135 | =item w->start () |
| 4132 | |
4136 | |
| 4133 | Starts the watcher. Note that there is no C<loop> argument, as the |
4137 | Starts the watcher. Note that there is no C<loop> argument, as the |
| 4134 | constructor already stores the event loop. |
4138 | constructor already stores the event loop. |
| … | |
… | |
| 4621 | above. This reduces dependencies and makes libev faster. |
4625 | above. This reduces dependencies and makes libev faster. |
| 4622 | |
4626 | |
| 4623 | =item EV_ATOMIC_T |
4627 | =item EV_ATOMIC_T |
| 4624 | |
4628 | |
| 4625 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4629 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
| 4626 | access is atomic and serialised with respect to other threads or signal |
4630 | access is atomic with respect to other threads or signal contexts. No |
| 4627 | contexts. No such type is easily found in the C language, so you can |
4631 | such type is easily found in the C language, so you can provide your own |
| 4628 | provide your own type that you know is safe for your purposes. It is used |
4632 | type that you know is safe for your purposes. It is used both for signal |
| 4629 | both for signal handler "locking" as well as for signal and thread safety |
4633 | handler "locking" as well as for signal and thread safety in C<ev_async> |
| 4630 | in C<ev_async> watchers. |
4634 | watchers. |
| 4631 | |
4635 | |
| 4632 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
4636 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
| 4633 | (from F<signal.h>), which is usually good enough on most platforms, |
4637 | (from F<signal.h>), which is usually good enough on most platforms. |
| 4634 | although strictly speaking using a type that also implies a memory fence |
|
|
| 4635 | is required. |
|
|
| 4636 | |
4638 | |
| 4637 | =item EV_H (h) |
4639 | =item EV_H (h) |
| 4638 | |
4640 | |
| 4639 | The name of the F<ev.h> header file used to include it. The default if |
4641 | The name of the F<ev.h> header file used to include it. The default if |
| 4640 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
4642 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
