Please, consider including CLM_LIBS.h in your list.
CLM_LIBS.h is a single file containing several code-generating macros. Each macho generates all the code and the data-types of a single library:
IMPORT_CLM_TIME: time and date related functions
time_elapsed
time_pause
time_stamp
IMPORT_CLM_RAND: random related functions
rand_int
rand_size_t
rand_double
rand_halton
rand_color
IMPORT_CLM_PRINTF:printf helper functions
printf_reset
printf_delete
printf_set_bold
printf_set_light
printf_set_strike
printf_set_underline
printf_move
printf_set_text_grey
printf_set_back_grey
printf_set_text_color
printf_set_back_color
IMPORT_CLM_DAMM: checksum functions
damm_dec
damm_hex
IMPORT_CLM_ARC4: unsafe cryptographic functions
arc4_hash
arc4_encrypt
arc4_decrypt
IMPORT_CLM_ITER: combinatorial iterator functions
iter_rand_prod
iter_next_prod
iter_rand_perm
iter_next_perm
iter_rand_comb
iter_next_comb
IMPORT_CLM_FRACTAL: spacefilling curves
fractal_van_der_corput
fractal_lebesgue_coord
fractal_lebesgue_index
fractal_hilbert_coord
fractal_hilbert_index
IMPORT_CLM_ARRAY: generic array functions
array_new
array_sort
array_shuffle
array_select
array_bisect
IMPORT_CLM_CLIST: generic singly-linked circular list container
clist_push_front
clist_push_back
clist_pop_front
clist_front
clist_back
IMPORT_CLM_STREE: generic splay tree container
stree_root
stree_min
stree_max
stree_pop
stree_next
stree_prev
stree_find
stree_insert
IMPORT_CLM_WTREE: generic weight-balanced tree container
wtree_size
wtree_find
wtree_insert
wtree_select
wtree_remove
Although everything (license, code and documentation for all the libraries) is included in a single header file, each library (indeed, each function) is independent from the others, so the final users may erase the macros (or functions!) that are not used in their code. This being said, since these are code-generating macros, no code is generated at all until you explicitly import one of these libraries, so there is no downside of including several libraries in a single header file.
CLM_LIBS.h relies just in the C standard library. CLM_LIBS.h is released into the Public Domain using the unlicense. CLM_LIBS.h has not been tested yet with C++ code but, to the best of my knowledge, nothing precludes using these libraries in C++ (although most of them make no sense in that language because there may be better alternatives in the C++'s standard library).
Please, consider including CLM_LIBS.h in your list.
CLM_LIBS.his a single file containing several code-generating macros. Each macho generates all the code and the data-types of a single library:IMPORT_CLM_TIME: time and date related functions
IMPORT_CLM_RAND: random related functions
IMPORT_CLM_PRINTF:
printfhelper functionsIMPORT_CLM_DAMM: checksum functions
IMPORT_CLM_ARC4: unsafe cryptographic functions
IMPORT_CLM_ITER: combinatorial iterator functions
IMPORT_CLM_FRACTAL: spacefilling curves
IMPORT_CLM_ARRAY: generic array functions
IMPORT_CLM_CLIST: generic singly-linked circular list container
IMPORT_CLM_STREE: generic splay tree container
IMPORT_CLM_WTREE: generic weight-balanced tree container
Although everything (license, code and documentation for all the libraries) is included in a single header file, each library (indeed, each function) is independent from the others, so the final users may erase the macros (or functions!) that are not used in their code. This being said, since these are code-generating macros, no code is generated at all until you explicitly import one of these libraries, so there is no downside of including several libraries in a single header file.
CLM_LIBS.hrelies just in the C standard library.CLM_LIBS.his released into the Public Domain using the unlicense.CLM_LIBS.hhas not been tested yet with C++ code but, to the best of my knowledge, nothing precludes using these libraries in C++ (although most of them make no sense in that language because there may be better alternatives in the C++'s standard library).