Why not just use malloc ? mulle-storage can be useful as a storage for
nodes of a tree. It's likely faster and it may produce less fragmentation and
it may improve locality of reference. Freed nodes will be reused. All the tree
nodes can be "blown" away at once, without having to free each node
individually.
Why not use a mulle_structarray ? A struct array can realloc and so pointers
inside the struct array are not stable.
| Release Version | Release Notes | AI Documentation |
|---|---|---|
| RELEASENOTES | DeepWiki for mulle-storage |
Install mulle-core developer then:
mulle-sde init -d my-project -m mulle-core/c-developer executable
cd my-project
mulle-sde vibecoding on
mulle-sde runYou are done, skip the following "Add" step.
This project is a component of the mulle-core library.
As such you usually will not add or install it individually, unless you
specifically do not want to link against mulle-core.
Use mulle-sde to add mulle-storage to your project:
mulle-sde add github:mulle-c/mulle-storageTo only add the sources of mulle-storage with dependency sources use clib:
clib install --out src/mulle-c mulle-c/mulle-storageAdd -isystem src/mulle-c to your CFLAGS and compile all the sources that were downloaded with your project.
Use mulle-sde to build and install mulle-storage and all dependencies:
mulle-sde install --prefix /usr/local \
https://github.com/mulle-c/mulle-storage/archive/latest.tar.gzInstall the requirements:
| Requirements | Description |
|---|---|
| mulle-container | π Arrays, hashtables and a queue |
Download the latest tar or zip archive and unpack it.
Install mulle-storage into /usr/local with cmake:
PREFIX_DIR="/usr/local"
cmake -B build \
-DMULLE_SDK_PATH="${PREFIX_DIR}" \
-DCMAKE_INSTALL_PREFIX="${PREFIX_DIR}" \
-DCMAKE_PREFIX_PATH="${PREFIX_DIR}" \
-DCMAKE_BUILD_TYPE=Release &&
cmake --build build --config Release &&
cmake --install build --config ReleaseNat! for Mulle kybernetiK