diff options
| author | root <root> | 2007-11-24 07:20:42 +0000 |
|---|---|---|
| committer | root <root> | 2007-11-24 07:20:42 +0000 |
| commit | b4b8cd662b359e1f3dd44b3bea5a8ab02218b461 (patch) | |
| tree | 30c2b42e350a98b4cdf34a8d09b39c38149fdb3b /ev.html | |
| parent | f3ca3041956ddaad8a69ec7f6214c25f9346f048 (diff) | |
*** empty log message ***
Diffstat (limited to 'ev.html')
| -rw-r--r-- | ev.html | 10 |
1 files changed, 7 insertions, 3 deletions
@@ -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="Sat Nov 24 08:13:46 2007" /> + <meta name="created" content="Sat Nov 24 08:20:38 2007" /> <meta name="generator" content="Pod::Xhtml 1.57" /> <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> <body> @@ -366,8 +366,12 @@ undefined behaviour (or a failed assertion if assertions are enabled).</p> <dt>ev_default_destroy ()</dt> <dd> <p>Destroys the default loop again (frees all memory and kernel state -etc.). This stops all registered event watchers (by not touching them in -any way whatsoever, although you cannot rely on this :).</p> +etc.). None of the active event watchers will be stopped in the normal +sense, so e.g. <code>ev_is_active</code> might still return true. It is your +responsibility to either stop all watchers cleanly yoursef <i>before</i> +calling this function, or cope with the fact afterwards (which is usually +the easiest thing, youc na just ignore the watchers and/or <code>free ()</code> them +for example).</p> </dd> <dt>ev_loop_destroy (loop)</dt> <dd> |