diff options
| author | root <root> | 2007-12-12 17:55:30 +0000 |
|---|---|---|
| committer | root <root> | 2007-12-12 17:55:30 +0000 |
| commit | 471c0cc622684d85d6361cc79f32e2436ad079e5 (patch) | |
| tree | 4ead64e843b6de6fbb15b12a59f942966f73ff6e | |
| parent | 3360a3869a421bc12a57dcd0a9450ef5ee8a11ec (diff) | |
*** empty log message ***
| -rw-r--r-- | ev.3 | 3 | ||||
| -rw-r--r-- | ev.html | 11 | ||||
| -rw-r--r-- | ev.pod | 2 |
3 files changed, 14 insertions, 2 deletions
@@ -1995,6 +1995,9 @@ event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being and only in the child after the fork. If whoever good citizen calling \&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork handlers will be invoked, too, of course. +.PP +\fIWatcher-Specific Functions and Data Members\fR +.IX Subsection "Watcher-Specific Functions and Data Members" .IP "ev_fork_init (ev_signal *, callback)" 4 .IX Item "ev_fork_init (ev_signal *, callback)" Initialises and configures the fork watcher \- it has no parameters of any @@ -6,7 +6,7 @@ <meta name="description" content="Pod documentation for libev" /> <meta name="inputfile" content="<standard input>" /> <meta name="outputfile" content="<standard output>" /> - <meta name="created" content="Wed Dec 12 18:55:04 2007" /> + <meta name="created" content="Wed Dec 12 18:55:28 2007" /> <meta name="generator" content="Pod::Xhtml 1.57" /> <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> <body> @@ -66,7 +66,10 @@ <ul><li><a href="#Watcher_Specific_Functions_and_Data_-9">Watcher-Specific Functions and Data Members</a></li> </ul> </li> -<li><a href="#code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</a></li> +<li><a href="#code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</a> +<ul><li><a href="#Watcher_Specific_Functions_and_Data_-10">Watcher-Specific Functions and Data Members</a></li> +</ul> +</li> </ul> </li> <li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li> @@ -1832,6 +1835,10 @@ event loop blocks next and before <code>ev_check</code> watchers are being calle and only in the child after the fork. If whoever good citizen calling <code>ev_default_fork</code> cheats and calls it in the wrong process, the fork handlers will be invoked, too, of course.</p> + +</div> +<h3 id="Watcher_Specific_Functions_and_Data_-10">Watcher-Specific Functions and Data Members</h3> +<div id="Watcher_Specific_Functions_and_Data_-2-8"> <dl> <dt>ev_fork_init (ev_signal *, callback)</dt> <dd> @@ -1794,6 +1794,8 @@ and only in the child after the fork. If whoever good citizen calling C<ev_default_fork> cheats and calls it in the wrong process, the fork handlers will be invoked, too, of course. +=head3 Watcher-Specific Functions and Data Members + =over 4 =item ev_fork_init (ev_signal *, callback) |