docs/src/features.md

Tue, 27 Jun 2023 18:24:28 +0200

author
Mike Becker <universe@uap-core.de>
date
Tue, 27 Jun 2023 18:24:28 +0200
changeset 723
c33e0ac069dd
parent 722
adc3c48dd3af
child 724
5e7b1951dc80
permissions
-rw-r--r--

add web documentation for strings

universe@720 1 ---
universe@720 2 title: UCX Features
universe@720 3 ---
universe@720 4
universe@720 5 <div id="modules">
universe@720 6
universe@720 7 ------------------------ ------------------------- ------------------- ---------------------------------
universe@720 8 [Allocator](#allocator) [String](#string) [Buffer](#buffer) [Memory&nbsp;Pool](#memory-pool)
universe@720 9 [Iterator](#iterator) [Collection](#collection) [List](#list) [Map](#map)
universe@720 10 [Utilities](#utilities)
universe@720 11 ------------------------ ------------------------- ------------------- ---------------------------------
universe@720 12
universe@720 13 </div>
universe@720 14
universe@720 15 ## Allocator
universe@720 16
universe@720 17 *Header file:* [allocator.h](api/allocator_8h.html)
universe@720 18
universe@722 19 The UCX allocator provides an interface for implementing an own memory allocation mechanism.
universe@722 20 Various function in UCX provide an additional alternative signature that takes an allocator as
universe@722 21 argument. A default allocator implementation using the stdlib memory management functions is
universe@722 22 available via the global symbol `cxDefaultAllocator`.
universe@722 23
universe@722 24 If you want to define your own allocator, you need to initialize the `CxAllocator` structure
universe@722 25 with a pointer to an allocator class (containing function pointers for the memory management
universe@722 26 functions) and an optional pointer to an arbitrary memory region that can be used to store
universe@722 27 state information for the allocator. An example is shown below:
universe@722 28
universe@722 29 ```c
universe@722 30 struct my_allocator_state {
universe@722 31 size_t total;
universe@722 32 size_t avail;
universe@722 33 char[] mem;
universe@722 34 };
universe@722 35
universe@722 36 static cx_allocator_class my_allocator_class = {
universe@722 37 my_malloc_impl,
universe@722 38 my_realloc_impl, // all these functions are somewhere defined
universe@722 39 my_calloc_impl,
universe@722 40 my_free_impl
universe@722 41 };
universe@722 42
universe@722 43 CxAllocator create_my_allocator(size_t n) {
universe@722 44 CxAllocator alloc;
universe@722 45 alloc.cl = &my_allocator_class;
universe@722 46 alloc.data = calloc(1, sizeof(struct my_allocator_state) + n);
universe@722 47 return alloc;
universe@722 48 }
universe@722 49
universe@722 50 void free_my_allocator(CxAllocator *alloc) {
universe@722 51 free(alloc.data);
universe@722 52 free(alloc);
universe@722 53 }
universe@722 54 ```
universe@722 55
universe@720 56 ## String
universe@720 57
universe@720 58 *Header file:* [string.h](api/string_8h.html)
universe@720 59
universe@723 60 UCX strings come in two variants: immutable (`cxstring`) and mutable (`cxmutstr`).
universe@723 61 The functions of UCX are designed to work with immutable strings by default but in situations where it is necessary,
universe@723 62 the API also provides alternative functions that work directly with mutable strings.
universe@723 63 Functions that change a string in-place are, of course, only accepting mutable strings.
universe@723 64
universe@723 65 When you are using UCX functions, or defining your own functions, you are sometimes facing the "problem",
universe@723 66 that the function only accepts arguments of type `cxstring` but you only have a `cxmutstr` at hand.
universe@723 67 In this case you _should not_ introduce a wrapper function that accepts the `cxmutstr`,
universe@723 68 but instead you should use the `cx_strcast()` function to cast the argument to the correct type.
universe@723 69
universe@723 70 In general, UCX strings are **not** necessarily zero-terminated. If a function guarantees to return zero-terminated
universe@723 71 string, it is explicitly mentioned in the documentation of the respective function.
universe@723 72 As a rule of thumb, you _should not_ pass the strings of a UCX string structure to another API without explicitly
universe@723 73 ensuring that the string is zero-terminated.
universe@723 74
universe@720 75 ## Buffer
universe@720 76
universe@720 77 *Header file:* [buffer.h](api/buffer_8h.html)
universe@720 78
universe@720 79 ## Memory Pool
universe@720 80
universe@720 81 *Header file:* [mempool.h](api/mempool_8h.html)
universe@720 82
universe@720 83 ### Basic Memory Pool
universe@720 84
universe@720 85 *Header file:* [basic_mempool.h](api/basic__mempool_8h.html)
universe@720 86
universe@720 87 ## Iterator
universe@720 88
universe@720 89 *Header file:* [iterator.h](api/iterator_8h.html)
universe@720 90
universe@720 91 ## Collection
universe@720 92
universe@720 93 *Header file:* [collection.h](api/collection_8h.html)
universe@720 94
universe@720 95 ## List
universe@720 96
universe@720 97 *Header file:* [list.h](api/list_8h.html)
universe@720 98
universe@720 99 ### Linked List
universe@720 100
universe@720 101 *Header file:* [linked_list.h](api/linked__list_8h.html)
universe@720 102
universe@720 103 ### Array List
universe@720 104
universe@720 105 *Header file:* [array_list.h](api/array__list_8h.html)
universe@720 106
universe@720 107 ## Map
universe@720 108
universe@720 109 *Header file:* [map.h](api/map_8h.html)
universe@720 110
universe@720 111 ### Hash Map
universe@720 112
universe@720 113 *Header file:* [hash_map.h](api/hash__map_8h.html)
universe@720 114
universe@720 115 ## Utilities
universe@720 116
universe@720 117 *Header file:* [utils.h](api/utils_8h.html)
universe@720 118
universe@720 119 ### Printf Functions
universe@720 120
universe@720 121 *Header file:* [printf.h](api/printf_8h.html)
universe@720 122
universe@720 123 ### Compare Functions
universe@720 124
universe@720 125 *Header file:* [compare.h](api/compare_8h.html)

mercurial