| … | |
… | |
| 1112 | =item C<EV_FORK> |
1112 | =item C<EV_FORK> |
| 1113 | |
1113 | |
| 1114 | The event loop has been resumed in the child process after fork (see |
1114 | The event loop has been resumed in the child process after fork (see |
| 1115 | C<ev_fork>). |
1115 | C<ev_fork>). |
| 1116 | |
1116 | |
|
|
1117 | =item C<EV_CLEANUP> |
|
|
1118 | |
|
|
1119 | The event loop is abotu to be destroyed (see C<ev_cleanup>). |
|
|
1120 | |
| 1117 | =item C<EV_ASYNC> |
1121 | =item C<EV_ASYNC> |
| 1118 | |
1122 | |
| 1119 | The given async watcher has been asynchronously notified (see C<ev_async>). |
1123 | The given async watcher has been asynchronously notified (see C<ev_async>). |
| 1120 | |
1124 | |
| 1121 | =item C<EV_CUSTOM> |
1125 | =item C<EV_CUSTOM> |
| … | |
… | |
| 3099 | believe me. |
3103 | believe me. |
| 3100 | |
3104 | |
| 3101 | =back |
3105 | =back |
| 3102 | |
3106 | |
| 3103 | |
3107 | |
|
|
3108 | =head2 C<ev_cleanup> - even the best things end |
|
|
3109 | |
|
|
3110 | Cleanup watchers are called just before the event loop they are registered |
|
|
3111 | with is being destroyed. |
|
|
3112 | |
|
|
3113 | While there is no guarantee that the event loop gets destroyed, cleanup |
|
|
3114 | watchers provide a convenient method to install cleanup watchers for your |
|
|
3115 | program, worker threads and so on - you just to make sure to destroy the |
|
|
3116 | loop when you want them to be invoked. |
|
|
3117 | |
|
|
3118 | =head3 Watcher-Specific Functions and Data Members |
|
|
3119 | |
|
|
3120 | =over 4 |
|
|
3121 | |
|
|
3122 | =item ev_cleanup_init (ev_signal *, callback) |
|
|
3123 | |
|
|
3124 | Initialises and configures the cleanup watcher - it has no parameters of |
|
|
3125 | any kind. There is a C<ev_cleanup_set> macro, but using it is utterly |
|
|
3126 | pointless, believe me. |
|
|
3127 | |
|
|
3128 | =back |
|
|
3129 | |
|
|
3130 | Example: Register an atexit handler to destroy the default loop, so any |
|
|
3131 | cleanup functions are called. |
|
|
3132 | |
|
|
3133 | static void |
|
|
3134 | program_exits (void) |
|
|
3135 | { |
|
|
3136 | ev_loop_destroy (EV_DEFAULT_UC); |
|
|
3137 | } |
|
|
3138 | |
|
|
3139 | ... |
|
|
3140 | atexit (program_exits); |
|
|
3141 | |
|
|
3142 | |
| 3104 | =head2 C<ev_async> - how to wake up an event loop |
3143 | =head2 C<ev_async> - how to wake up an event loop |
| 3105 | |
3144 | |
| 3106 | In general, you cannot use an C<ev_run> from multiple threads or other |
3145 | In general, you cannot use an C<ev_run> from multiple threads or other |
| 3107 | asynchronous sources such as signal handlers (as opposed to multiple event |
3146 | asynchronous sources such as signal handlers (as opposed to multiple event |
| 3108 | loops - those are of course safe to use in different threads). |
3147 | loops - those are of course safe to use in different threads). |
