Stuck
I still can’t decide how I want to handle parsing Raylib’s API. One thing I would like is to be able to use the same tool for other libraries, like Dear ImGui, or SDL. The constraint is it has to be a library that does a good job at defining it’s interface.
Maybe I’m getting ahead of myself and I should just release the weird Raylib thing I have so far.
Excludables
There’s a fair amount of stuff in Raylib that we don’t necessarily need - kind of. We already have logging facilities, I/O, compression, etc. So really, we don’t need that from Raylib. However, mixing the two can be a bit awkward. This is a general problem - how much do you push off to Raylib, and how much do you do in Elixir?
To start, let’s just shove everything to Raylib.
Instead, this
I updated the Raylib wiki to show what functions modify arguments. You can see that here: https://github.com/raysan5/raylib/wiki/raylib-data-structures#raylib-functions-that-modify-data-passed-by-reference