ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.pod
(Generate patch)

Comparing libev/ev.pod (file contents):
Revision 1.323 by root, Sun Oct 24 18:01:26 2010 UTC vs.
Revision 1.327 by root, Sun Oct 24 20:05:43 2010 UTC

… …
1112=item C<EV_FORK> 1112=item C<EV_FORK>
1113 1113
1114The event loop has been resumed in the child process after fork (see 1114The event loop has been resumed in the child process after fork (see
1115C<ev_fork>). 1115C<ev_fork>).
1116 1116
1117=item C<EV_CLEANUP>
1118
1119The event loop is abotu to be destroyed (see C<ev_cleanup>).
1120
1117=item C<EV_ASYNC> 1121=item C<EV_ASYNC>
1118 1122
1119The given async watcher has been asynchronously notified (see C<ev_async>). 1123The 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
3097Initialises and configures the fork watcher - it has no parameters of any 3101Initialises and configures the fork watcher - it has no parameters of any
3098kind. There is a C<ev_fork_set> macro, but using it is utterly pointless, 3102kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
3099believe me. 3103believe me.
3100 3104
3101=back 3105=back
3106
3107
3108=head2 C<ev_cleanup> - even the best things end
3109
3110Cleanup watchers are called just before the event loop they are registered
3111with is being destroyed.
3112
3113While there is no guarantee that the event loop gets destroyed, cleanup
3114watchers provide a convenient method to install cleanup hooks for your
3115program, worker threads and so on - you just to make sure to destroy the
3116loop when you want them to be invoked.
3117
3118Cleanup watchers are invoked in the same way as any other watcher. Unlike
3119all other watchers, they do not keep a reference to the event loop (which
3120makes a lot of sense if you think about it). Like all other watchers, you
3121can 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
3129Initialises and configures the cleanup watcher - it has no parameters of
3130any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
3131pointless, believe me.
3132
3133=back
3134
3135Example: Register an atexit handler to destroy the default loop, so any
3136cleanup 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
3106In general, you cannot use an C<ev_run> from multiple threads or other 3150In 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
4843These calls can be replaced easily by their C<ev_loop_xxx> counterparts: 4887These 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
4850A number of functions and symbols have been renamed: 4894A number of functions and symbols have been renamed:

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines