There is no solid standard, since it's C we're talking about. I would kind of agree that lower case is more common. More weirdly (from reading the header [1], I have not worked with raylib) the public types and function names are not namespaced so if your code already used Texture or Camera those become clobbered along with DrawPixel(), InitWindow() and hundreds more (the header is ~1,500 lines).
I'm not saying that's bad, and the API seems really nice to work with, it's just a bit odd and against the "common wisdom" on how to design C libraries.
I guess for a game there might not be a lot of need for other libraries, since raylib really does a lot of stuff.
I'm not saying that's bad, and the API seems really nice to work with, it's just a bit odd and against the "common wisdom" on how to design C libraries.
I guess for a game there might not be a lot of need for other libraries, since raylib really does a lot of stuff.
[1]: https://github.com/raysan5/raylib/blob/master/src/raylib.h