A few things we focused on:
Clean, well-documented API
Modular components (pull in only what you need)
Full test coverage
Easy builds: works out of the box with Make, Autotools, or CMake
Cross-platform: Linux, macOS, and Windows (with proper DLL export handling)
New build.sh script for smoother setup, especially in environments like MSYS2
We recently rewrote the array utilities for better performance and maintainability, which felt like a good milestone to share this more broadly.
If you use C regularly (or even just occasionally), I’d really love to hear your feedback. What do you value most in a utility lib? Have you run into issues when integrating small C libraries into larger projects—especially when dealing with multiple platforms or compilers?
Also curious: if you’ve used other libraries like stb, klib, or GLib, what worked for you and what didn’t?
Feedback, ideas, bug reports, feature requests—all are welcome. Repo link is in the comments if you want to check it out or contribute.
Thanks!
Ahmen! I attend this same church.
My favorite professor in engineering school always gave open book tests.
In the real world of work, everyone has full access to all the available data and information.
Very few jobs involve paying someone simply to look up data in a book or on the internet. What they will pay for is someone who can analyze, understand, reason and apply data and information in unique ways needed to solve problems.
Doing this is called "engineering". And this is what this professor taught.