From 61924a99a93a9f8eaaab0ab6dce11d4f6c1aa13b Mon Sep 17 00:00:00 2001 From: Dan Egnor <egnor@ofb.net> Date: Fri, 13 Jun 2003 15:40:17 +0000 Subject: [PATCH] Clarify allocation hooks --- alloc.html | 4 ++-- ref.html | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/alloc.html b/alloc.html index 1b1287d..8ae3bc4 100644 --- a/alloc.html +++ b/alloc.html @@ -29,9 +29,9 @@ extern void (*oop_free)(void *ptr); /* <em>Free allocated memory.</em> */ These are global function pointers, initialized by default to the standard C library functions <em>malloc</em>, <em>realloc</em>, and <em>free</em>. Applications using liboop may reset these pointers to allocation and -deallocation routines with a compatible interface; components should use +deallocation routines with a compatible interface; libraries should use these function pointers wherever possible to allocate and release memory. -These pointers are normally set before calling any liboop components; if they +These pointers are normally set before calling any liboop code; if they are changed during operation, the new <em>oop_free</em> and <em>oop_realloc</em> functions should be capable of handling memory obtained with the old <em>oop_malloc</em>. diff --git a/ref.html b/ref.html index b97a030..50bf9f5 100644 --- a/ref.html +++ b/ref.html @@ -11,7 +11,7 @@ <pre> #include <oop.h> -/* <em>For recommended use by oop components.</em> */ +/* <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 *); -- GitLab