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

Comparing libev/ev.pod (file contents):
Revision 1.325 by root, Sun Oct 24 19:44:08 2010 UTC vs.
Revision 1.330 by sf-exg, Sun Oct 24 21:01:58 2010 UTC

… …
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> 1117=item C<EV_CLEANUP>
1118 1118
1119The event loop is abotu to be destroyed (see C<ev_cleanup>). 1119The event loop is about to be destroyed (see C<ev_cleanup>).
1120 1120
1121=item C<EV_ASYNC> 1121=item C<EV_ASYNC>
1122 1122
1123The given async watcher has been asynchronously notified (see C<ev_async>). 1123The given async watcher has been asynchronously notified (see C<ev_async>).
1124 1124
… …
3098 3098
3099=item ev_fork_init (ev_fork *, callback) 3099=item ev_fork_init (ev_fork *, callback)
3100 3100
3101Initialises and configures the fork watcher - it has no parameters of any 3101Initialises and configures the fork watcher - it has no parameters of any
3102kind. 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,
3103believe me. 3103really.
3104 3104
3105=back 3105=back
3106 3106
3107 3107
3108=head2 C<ev_cleanup> - even the best things end 3108=head2 C<ev_cleanup> - even the best things end
3109 3109
3110Cleanup watchers are called just before the event loop they are registered 3110Cleanup watchers are called just before the event loop is being destroyed
3111with is being destroyed. 3111by a call to C<ev_loop_destroy>.
3112 3112
3113While there is no guarantee that the event loop gets destroyed, cleanup 3113While there is no guarantee that the event loop gets destroyed, cleanup
3114watchers provide a convenient method to install cleanup watchers for your 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 3115program, worker threads and so on - you just to make sure to destroy the
3116loop when you want them to be invoked. 3116loop when you want them to be invoked.
3117 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
3118=head3 Watcher-Specific Functions and Data Members 3123=head3 Watcher-Specific Functions and Data Members
3119 3124
3120=over 4 3125=over 4
3121 3126
3122=item ev_cleanup_init (ev_cleanup *, callback) 3127=item ev_cleanup_init (ev_cleanup *, callback)
3123 3128
3124Initialises and configures the cleanup watcher - it has no parameters of 3129Initialises and configures the cleanup watcher - it has no parameters of
3125any kind. There is a C<ev_cleanup_set> macro, but using it is utterly 3130any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
3126pointless, believe me. 3131pointless, I assure you.
3127 3132
3128=back 3133=back
3129 3134
3130Example: Register an atexit handler to destroy the default loop, so any 3135Example: Register an atexit handler to destroy the default loop, so any
3131cleanup functions are called. 3136cleanup functions are called.

Diff Legend

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