gunslinger VS buddy_alloc

Here's a framework that's cool: https://github.com/MrFrenik/gunslinger/. We have a great Discord community, too. Even if you don't end up using it, there are plenty of people who are willing to offer guidance regardless :). Invite link is on the author's YouTube channel: https://www.youtube.com/watch?v=-_HxKDNuCqA

Check out gunslinger, a pure C99 game framework, with a very clean design.

The development has been making huge strides and they have a fairly active discord channel:

https://github.com/MrFrenik/gunslinger

Make your own. If you really want to make a game in C, this may be the best option. Depending on how complex the game is that you want to make, this could be an enormous task, or not too big of a deal, in some cases it could even be easier than learning a game engine. You can use frameworks like Gunslinger to make it easier, as well. If you need guidance, the Gunslinger community is friendly and accepting of beginners :).

That being said, you may have your requirements satisfied with tagged unions which consists in implementing a struct with an anonymous union and label (like an enum) to keep track of what data is inside the union, this works really well when you know beforehand which data types you want to support. Another technique could be using macros, like the containers on the gunslinger framework, however I have never implemented something like this. Lastly you can always use void pointers, however you may need to be more clever to achieve it (I almost never use them).

Some of my favorites are: sokol/pacman.c, Gunslinger, and gb

And here is Github of his game engine of this guy: Gunslinger Game Engine

To install non exotic library from a github repo, specify just the repo-owner/repo-name or the absolute github link to the repo. E.g. to install gunslinger and stb from master branch

Looking quickly at this lib, functions of the API are not static: https://github.com/MrFrenik/gunslinger/blob/d5ebcce0647e97badc9337749d7cd9f5810eecfa/gs.h#L1415, so it might lead to ODR violation.

If you need a sub-allocator with predictable performance feel free to give it a try. The code is here and it is licensed under the 0BSD license, making it as lax and as close to public domain as possible. Comments, issues and PRs are always welcomed and appreciated. Thanks!

I maintain a project that's not technically MISRA compliant (due to being a memory allocator and MISRA disallowing the very idea) and I keep it at 100% test coverage with support for multiple compilers and operating systems. Over time I had a few users reporting back - since it's working for them I count that as success. Is it wildly popular ? Of course not, but it doesn't have to be.

You are right about the tests - they are written with 64-bit in mind. I ought to rework them to switch sizes based on arch but that will take a weekend. I've filed https://github.com/spaskalev/buddy_alloc/issues/19 to track this.

I also maintain a application-based malloc (that doesn't do obtaining and releasing memory through the OS, just managing sub-diving a larger memory block into smaller requests) at https://github.com/spaskalev/buddy_alloc - feel free to ping me with any questions about it.

I'm the author of https://github.com/spaskalev/buddy_alloc - a custom memory allocator for C (modern C11, works with C++ as well) designed for predictable and repeatable performance. It is suitable for use in embedded, games and any other system with soft or hard real-time demands. It has 100% line and branch test coverage and uses a fixed amount of space on the call stack when called. Recently the project had its first external contribution as well. Cheers!

I made a memory allocator that turned out rather neat - https://github.com/spaskalev/buddy_alloc