… | |
… | |
300 | An event loop is described by a C<struct ev_loop *> (the C<struct> is |
300 | An event loop is described by a C<struct ev_loop *> (the C<struct> is |
301 | I<not> optional in this case unless libev 3 compatibility is disabled, as |
301 | I<not> optional in this case unless libev 3 compatibility is disabled, as |
302 | libev 3 had an C<ev_loop> function colliding with the struct name). |
302 | libev 3 had an C<ev_loop> function colliding with the struct name). |
303 | |
303 | |
304 | The library knows two types of such loops, the I<default> loop, which |
304 | The library knows two types of such loops, the I<default> loop, which |
305 | supports signals and child events, and dynamically created event loops |
305 | supports child process events, and dynamically created event loops which |
306 | which do not. |
306 | do not. |
307 | |
307 | |
308 | =over 4 |
308 | =over 4 |
309 | |
309 | |
310 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
310 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
311 | |
311 | |
… | |
… | |
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 about 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> |
… | |
… | |
3090 | |
3094 | |
3091 | =head3 Watcher-Specific Functions and Data Members |
3095 | =head3 Watcher-Specific Functions and Data Members |
3092 | |
3096 | |
3093 | =over 4 |
3097 | =over 4 |
3094 | |
3098 | |
3095 | =item ev_fork_init (ev_signal *, callback) |
3099 | =item ev_fork_init (ev_fork *, callback) |
3096 | |
3100 | |
3097 | Initialises and configures the fork watcher - it has no parameters of any |
3101 | Initialises and configures the fork watcher - it has no parameters of any |
3098 | kind. There is a C<ev_fork_set> macro, but using it is utterly pointless, |
3102 | kind. There is a C<ev_fork_set> macro, but using it is utterly pointless, |
3099 | believe me. |
3103 | really. |
3100 | |
3104 | |
3101 | =back |
3105 | =back |
|
|
3106 | |
|
|
3107 | |
|
|
3108 | =head2 C<ev_cleanup> - even the best things end |
|
|
3109 | |
|
|
3110 | Cleanup watchers are called just before the event loop is being destroyed |
|
|
3111 | by a call to C<ev_loop_destroy>. |
|
|
3112 | |
|
|
3113 | While there is no guarantee that the event loop gets destroyed, cleanup |
|
|
3114 | watchers provide a convenient method to install cleanup hooks 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 | Cleanup watchers are invoked in the same way as any other watcher. Unlike |
|
|
3119 | all other watchers, they do not keep a reference to the event loop (which |
|
|
3120 | makes a lot of sense if you think about it). Like all other watchers, you |
|
|
3121 | can call libev functions in the callback, except C<ev_cleanup_start>. |
|
|
3122 | |
|
|
3123 | =head3 Watcher-Specific Functions and Data Members |
|
|
3124 | |
|
|
3125 | =over 4 |
|
|
3126 | |
|
|
3127 | =item ev_cleanup_init (ev_cleanup *, callback) |
|
|
3128 | |
|
|
3129 | Initialises and configures the cleanup watcher - it has no parameters of |
|
|
3130 | any kind. There is a C<ev_cleanup_set> macro, but using it is utterly |
|
|
3131 | pointless, I assure you. |
|
|
3132 | |
|
|
3133 | =back |
|
|
3134 | |
|
|
3135 | Example: Register an atexit handler to destroy the default loop, so any |
|
|
3136 | cleanup functions are called. |
|
|
3137 | |
|
|
3138 | static void |
|
|
3139 | program_exits (void) |
|
|
3140 | { |
|
|
3141 | ev_loop_destroy (EV_DEFAULT_UC); |
|
|
3142 | } |
|
|
3143 | |
|
|
3144 | ... |
|
|
3145 | atexit (program_exits); |
3102 | |
3146 | |
3103 | |
3147 | |
3104 | =head2 C<ev_async> - how to wake up an event loop |
3148 | =head2 C<ev_async> - how to wake up an event loop |
3105 | |
3149 | |
3106 | In general, you cannot use an C<ev_run> from multiple threads or other |
3150 | In general, you cannot use an C<ev_run> from multiple threads or other |
… | |
… | |
4840 | |
4884 | |
4841 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
4885 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
4842 | |
4886 | |
4843 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
4887 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
4844 | |
4888 | |
4845 | ev_loop_destroy (EV_DEFAULT); |
4889 | ev_loop_destroy (EV_DEFAULT_UC); |
4846 | ev_loop_fork (EV_DEFAULT); |
4890 | ev_loop_fork (EV_DEFAULT); |
4847 | |
4891 | |
4848 | =item function/symbol renames |
4892 | =item function/symbol renames |
4849 | |
4893 | |
4850 | A number of functions and symbols have been renamed: |
4894 | A number of functions and symbols have been renamed: |