Commit 92a25f9e authored by Magnus Holmgren's avatar Magnus Holmgren
Browse files

Add filename extensions to all links. Change <a href=""> to <a href="index.html">.

parent c207d84a
......@@ -59,4 +59,4 @@ be immediately overwritten, and/or reused by subsequent calls to
<p><a name="note-realloc">*</a> <b>Compatibility note:</b> oop_realloc
is only available in version 0.7 or newer.</p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -75,6 +75,6 @@ structure as their first argument; sources are expected to include their
own data (in whatever format) with the core function pointers. Callbacks
are also C function pointers, with "void *" arguments to pass data.
For more about the liboop interface, see the <a href="ref">reference</a>.
For more about the liboop interface, see the <a href="ref.html">reference</a>.
<hr><a href="">liboop home</a></body></html>
<hr><a href="index.html">liboop home</a></body></html>
......@@ -43,11 +43,11 @@ You may also browse the Git repository for
<dt><a href="why">Extended rationale</a>
<dt><a href="why.html">Extended rationale</a>
<dd>Why everyone should be using liboop.
<dt><a href="how">Introduction and overview</a>
<dt><a href="how.html">Introduction and overview</a>
<dd>How liboop works; basic principles of operation.
<dt><a href="ref">Reference</a>
<dt><a href="ref.html">Reference</a>
<dd>Specific functions and data structures.
......@@ -72,26 +72,26 @@ system event source was fixed, the robustness of signal handling is improved,
and some minor portability problems were fixed.<p>
<dt>18 September 2001
<dd>Version 0.8 released, including a <a href="oop_tcl">source adapter</a>
<dd>Version 0.8 released, including a <a href="oop_tcl.html">source adapter</a>
for <a href="">Tcl/Tk</a>. (0.7 was never
<dt>7 October 2000
<dd>Version 0.6 released, including a <a href="oop_rl">sink adapter</a>
<dd>Version 0.6 released, including a <a href="oop_rl.html">sink adapter</a>
for the <a href="">GNU
Readline Library</a>.<p>
<dt>5 September 1999
<dd>Version 0.4 released. Besides the usual bug fixes, the
<a href="on_fd">file descriptor deregistration interface</a> changed, and we
now have a <a href="oop_glib">source adapter</a> for
<a href="">GLib</a>, and a <a href="oop_www">sink adapter</a>
<a href="on_fd.html">file descriptor deregistration interface</a> changed, and we
now have a <a href="oop_glib.html">source adapter</a> for
<a href="">GLib</a>, and a <a href="oop_www.html">sink adapter</a>
for the <a href="">W3C Protocol Library
(libwww)</a>! The test/sample program (test-oop) is also quite improved.<p>
<dt>15 August 1999
<dd>Version 0.3 released. This version includes an
<a href="oop_adns">adapter</a> for
<a href="oop_adns.html">adapter</a> for
<a href="">Ian Jackson's
asynchronous DNS resolver library</a>.<p>
......@@ -106,8 +106,8 @@ support distribution under the terms of the full GPL.</em><p>
<a href="">automake</a> and
<a href="">libtool</a>,
and includes an interface for using
<a href="alloc">alternate memory allocation functions</a>.
<a href="">Gale</a> now uses liboop!<p>
<a href="alloc.html">alternate memory allocation functions</a>.
<a href="index.html">Gale</a> now uses liboop!<p>
<dt>5 July 1999
<dd>Version 0.1 released. This is a very, very simple initial release that
......@@ -81,4 +81,4 @@ other value (including OOP_HALT) will cause termination of the event loop.
<p><a name="note-exception">*</a> <b>Compatibility note:</b> OOP_EXCEPTION
is only available in version 0.7 or newer.</p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -64,4 +64,4 @@ Should return OOP_CONTINUE if the event loop should continue operating; any
other value (including OOP_HALT) will cause termination of the event loop.
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -67,4 +67,4 @@ Should return OOP_CONTINUE if the event loop should continue operating; any
other value (including OOP_HALT) will cause termination of the event loop.
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -32,7 +32,7 @@ details.<p>
<dt><b>oop_adapter_adns *adapter</b>
<dd>An adns adapter to delete, with no outstanding
<a href="oop_adns_query">queries</a>.<p>
<a href="oop_adns_query.html">queries</a>.<p>
......@@ -55,4 +55,4 @@ callbacks registered with the event source are cancelled. The adapter can have
no active queries when it is deleted.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -28,7 +28,7 @@ void oop_adns_cancel(oop_adns_query *query);
<dt><b>oop_adapter_adns *adns</b>
<dd>The <a href="oop_adns">adns adapter</a> to use for the query.<p>
<dd>The <a href="oop_adns.html">adns adapter</a> to use for the query.<p>
<dt><b>adns_answer *answer</b>
<dd>The answer to the query (status and RR data). Refer to the adns
......@@ -91,4 +91,4 @@ Should return OOP_CONTINUE if the event loop should continue operating;
any other value (including OOP_HALT) will cause termination of the event loop.
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -45,4 +45,4 @@ This function isn't commonly used. <b>Furthermore, GLib event loop termination
does not currently work.</b> In other words, ignore this for now.
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -44,4 +44,4 @@ liboop.<p>
rl_readback_read_char() will no longer be invoked automatically.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -27,10 +27,10 @@ void oop_sys_delete(oop_source_sys *sys);
<dd>Create a new system event source. The system event source implements the
event source interface and manages a select() loop. Once the system event
source is created, use <a href="oop_sys_source">oop_sys_source()</a> to
source is created, use <a href="oop_sys_source.html">oop_sys_source()</a> to
access the event source interface (which lets you register event sinks), and
<a href="oop_sys_run">oop_sys_run()</a> or
<a href="oop_sys_run">oop_sys_run_once()</a> to actually process events.
<a href="oop_sys_run.html">oop_sys_run()</a> or
<a href="oop_sys_run.html">oop_sys_run_once()</a> to actually process events.
More than one system event source can exist, though it is rarely useful to do
so (since only one may be active at a time).<p>
......@@ -43,4 +43,4 @@ associated with the event source. The source cannot have any active callbacks
(event sinks) associated with it.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -42,4 +42,4 @@ immediately after processing any pending results. The return values are the
same as oop_sys_run(), except that a return of OOP_CONTINUE does not
necessarily mean that no event sinks are registered.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -27,4 +27,4 @@ function pointers for registering and unregistering callbacks with the event
source; you can pass it to modules which simply want an event source, without
needing to know that you use the system event source in particular.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -35,4 +35,4 @@ count of users; when oop_tcl_delete has been called as many times as
oop_tcl_new, the event source is removed.<p>
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -48,11 +48,11 @@ connections to Web servers, which may cause events to be registered even if
there are no open requests.)<p>
<dd>Set <a href="alloc">oop_malloc, oop_realloc, and oop_free</a> to
<dd>Set <a href="alloc.html">oop_malloc, oop_realloc, and oop_free</a> to
<a href="">HTMemory_malloc
and HTMemory_free</a>, respectively. You do not need to do this, but it
may help to keep your memory allocations consistent with the libwww
framework. If you do this, do so before calling any other liboop functions.
<hr><a href="ref">liboop reference</a></body></html>
<hr><a href="ref.html">liboop reference</a></body></html>
......@@ -12,23 +12,23 @@
#include &lt;oop.h&gt;
/* <em>Applications can set these; liboop libraries will use them.</em> */
extern void *(*<a href="alloc">oop_malloc</a>)(size_t); /* <em>returns NULL on failure</em> */
extern void *(*<a href="alloc">oop_realloc</a>)(void *,size_t); /* <em>returns NULL on failure</em> */
extern void (*<a href="alloc">oop_free</a>)(void *);
extern void *(*<a href="alloc.html">oop_malloc</a>)(size_t); /* <em>returns NULL on failure</em> */
extern void *(*<a href="alloc.html">oop_realloc</a>)(void *,size_t); /* <em>returns NULL on failure</em> */
extern void (*<a href="alloc.html">oop_free</a>)(void *);
typedef struct oop_source oop_source;
struct oop_source {
/* <em>File descriptor activity events.</em> */
void (*<a href="on_fd">on_fd</a>)(oop_source *,int fd,oop_event,oop_call_fd *,void *);
void (*<a href="on_fd">cancel_fd</a>)(oop_source *,int fd,oop_event);
void (*<a href="on_fd.html">on_fd</a>)(oop_source *,int fd,oop_event,oop_call_fd *,void *);
void (*<a href="on_fd.html">cancel_fd</a>)(oop_source *,int fd,oop_event);
/* <em>Timer events.</em> */
void (*<a href="on_time">on_time</a>)(oop_source *,struct timeval,oop_call_time *,void *);
void (*<a href="on_time">cancel_time</a>)(oop_source *,struct timeval,oop_call_time *,void *);
void (*<a href="on_time.html">on_time</a>)(oop_source *,struct timeval,oop_call_time *,void *);
void (*<a href="on_time.html">cancel_time</a>)(oop_source *,struct timeval,oop_call_time *,void *);
/* <em>UNIX signal events.</em> */
void (*<a href="on_signal">on_signal</a>)(oop_source *,int sig,oop_call_signal *,void *);
void (*<a href="on_signal">cancel_signal</a>)(oop_source *,int sig,oop_call_signal *,void *);
void (*<a href="on_signal.html">on_signal</a>)(oop_source *,int sig,oop_call_signal *,void *);
void (*<a href="on_signal.html">cancel_signal</a>)(oop_source *,int sig,oop_call_signal *,void *);
......@@ -38,15 +38,15 @@ struct oop_source {
typedef struct oop_source_sys oop_source_sys;
/* <em>Create and destroy a system event source.</em> */
oop_source_sys *<a href="oop_sys">oop_sys_new</a>(void); /* <em>returns NULL on failure</em> */
void <a href="oop_sys">oop_sys_delete</a>(oop_source_sys *);
oop_source_sys *<a href="oop_sys.html">oop_sys_new</a>(void); /* <em>returns NULL on failure</em> */
void <a href="oop_sys.html">oop_sys_delete</a>(oop_source_sys *);
/* <em>Run the system event loop.</em> */
void *<a href="oop_sys_run">oop_sys_run</a>(oop_source_sys *);
void *<a href="oop_sys_run">oop_sys_run_once</a>(oop_source_sys *);
void *<a href="oop_sys_run.html">oop_sys_run</a>(oop_source_sys *);
void *<a href="oop_sys_run.html">oop_sys_run_once</a>(oop_source_sys *);
/* <em>Get the standard source interface for a system event source.</em> */
oop_source *<a href="oop_sys_source">oop_sys_source</a>(oop_source_sys *);
oop_source *<a href="oop_sys_source.html">oop_sys_source</a>(oop_source_sys *);
......@@ -65,17 +65,17 @@ typedef struct oop_adapter_adns oop_adapter_adns;
typedef struct oop_adns_query oop_adns_query;
/* <em>Create and destroy a liboop adns adapter, including an instance of adns.</em> */
oop_adapter_adns *<a href="oop_adns">oop_adns_new</a>(oop_source *,adns_initflags,FILE *diag); /* <em>returns NULL on failure</em> */
void <a href="oop_adns">oop_adns_delete</a>(oop_adapter_adns *);
oop_adapter_adns *<a href="oop_adns.html">oop_adns_new</a>(oop_source *,adns_initflags,FILE *diag); /* <em>returns NULL on failure</em> */
void <a href="oop_adns.html">oop_adns_delete</a>(oop_adapter_adns *);
/* <em>Submit an asynchronous DNS query.</em> */
oop_adns_query *<a href="oop_adns_query">oop_adns_submit</a>( /* <em>returns NULL on failure</em> */
oop_adns_query *<a href="oop_adns_query.html">oop_adns_submit</a>( /* <em>returns NULL on failure</em> */
oop_adapter_adns *,
const char *owner,adns_rrtype type,adns_queryflags flags,
oop_adns_call *,void *);
/* <em>Cancel a running query.</em> */
void <a href="oop_adns_query">oop_adns_cancel</a>(oop_adns_query *);
void <a href="oop_adns_query.html">oop_adns_cancel</a>(oop_adns_query *);
......@@ -90,11 +90,11 @@ and licensed under the terms of the
#include &lt;oop-glib.h&gt;
/* <em>Create and destroy a liboop GLib adapter.</em> */
oop_source *<a href="oop_glib">oop_glib_new</a>();
void <a href="oop_glib">oop_glib_delete</a>();
oop_source *<a href="oop_glib.html">oop_glib_new</a>();
void <a href="oop_glib.html">oop_glib_delete</a>();
/* <em>Get the value used to terminate the event loop (e.g. OOP_HALT)</em>. */
void *<a href="oop_glib">oop_glib_return</a>();
void *<a href="oop_glib.html">oop_glib_return</a>();
......@@ -108,8 +108,8 @@ Sun Microsystems, Inc., and other parties.</em></p>
#include &lt;oop-tcl.h&gt;
/* <em>Create and destroy a liboop Tcl adapter.</em> */
oop_source *<a href="oop_tcl">oop_tcl_new</a>();
void <a href="oop_tcl">oop_tcl_delete</a>();
oop_source *<a href="oop_tcl.html">oop_tcl_new</a>();
void <a href="oop_tcl.html">oop_tcl_delete</a>();
......@@ -126,15 +126,15 @@ Software License</a>.</em></p>
#include &lt;oop-www.h&gt;
/* <em>Register a liboop event source as a libwww "event manager".</em> */
void <a href="oop_www">oop_www_register</a>(oop_source *);
void <a href="oop_www.html">oop_www_register</a>(oop_source *);
/* <em>Unregister the event source, leaving libwww with no event manager.
This function cannot be executed with outstanding event requests.</em> */
void <a href="oop_www">oop_www_cancel</a>();
void <a href="oop_www.html">oop_www_cancel</a>();
/* <em>Use libwww for liboop's oop_malloc, oop_realloc, and oop_free.
<b>If you use this, you must call it before any other liboop function!</b></em> */
void <a href="oop_www">oop_www_memory</a>();
void <a href="oop_www.html">oop_www_memory</a>();
......@@ -151,10 +151,10 @@ Lesser GPL, Readline is covered by the
/* <em>Use a liboop event source to call rl_callback_read_char().
It is up to you to call rl_callback_handler_install().
Note well that Readline uses malloc(), not oop_malloc().</em> */
void <a href="oop_rl">oop_readline_register</a>(oop_source *);
void <a href="oop_rl.html">oop_readline_register</a>(oop_source *);
/* <em>Stop notifying readline of input characters.</em> */
void <a href="oop_rl">oop_readline_cancel</a>(oop_source *);
void <a href="oop_rl.html">oop_readline_cancel</a>(oop_source *);
<hr><a href="">liboop home</a></body></html>
<hr><a href="index.html">liboop home</a></body></html>
......@@ -88,7 +88,7 @@ model of an application or library into liboop's model. This does require
knowledge of the code's I/O structure, but can at least keep the modules in
an application independent of each other.
For more about liboop, see the <a href="how">documentation</a>.
For more about liboop, see the <a href="how.html">documentation</a>.
......@@ -114,7 +114,7 @@ of asynchronous signals is very difficult to do properly and safely in most
existing systems (without kludges like polling).
<p>In any case, we do have a
<a href="oop_glib">GLib source adapter</a> so you can use the GLib event loop
<a href="oop_glib.html">GLib source adapter</a> so you can use the GLib event loop
with the liboop interface.</p>
<dt><em>How does liboop compare to Niels Provos' <a
......@@ -133,4 +133,4 @@ If anyone is interested in such an adapter, please contact me.</p>
<hr><a href="">liboop home</a></body></html>
<hr><a href="index.html">liboop home</a></body></html>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment