Lines Matching +full:in +full:- +full:functions

6 .\" copyright notice and this permission notice appear in all copies.
10 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
30 .Nd light-weight open hashing
56 These functions have been designed as a fast, extensible alternative to
57 the usual hash table functions.
59 where a key is a contiguous sequence of bytes at a fixed position in
61 Keys can either be NUL-terminated strings or fixed-size memory areas.
62 All functions take a pointer to an ohash structure as the
74 .Bd -literal -offset indent
86 field holds the position of the key in each record;
94 .Xr free 3 Ns -like
95 functions, used for managing the table internal storage;
101 Each of these functions are called similarly to their standard counterpart,
106 which can be used to communicate specific information to the functions.
124 are the basic look-up element functions.
142 handles string-like keys.
149 though the actual elements stored in the table should only contain
150 NUL-terminated keys.
157 All bytes are significant in key comparison.
164 functions.
192 can be used to access all elements in an ohash table, like this:
193 .Bd -literal -offset indent
201 Those functions are safe to use even while entries are added to/removed
202 from the table, but in such a case they don't guarantee that new entries
204 As a special case, they can safely be used to free elements in the table.
207 returns the number of elements in the hash table.
215 may call the user-supplied memory functions:
216 .Bd -literal -offset indent
217 p = (*info->calloc)(n, sizeof_record, info->data);
219 (*info->free)(old, info->data);
232 considered read-only.
241 The open hashing functions are not thread-safe by design.
242 In particular, in a threaded environment, there is no guarantee that a
253 Multi-threaded applications should explicitly protect ohash table access.
261 .%P pp 506-550
265 Those functions are completely non-standard and should be avoided in
268 Those functions were designed and written for
271 by Marc Espie in 1999.