SDL VS SQLite

I don't know for sure, but could it be this?

https://github.com/libsdl-org/SDL

There is also SDL, which is a bit of a behemoth library, but gives you a lot of firepower if you want to get down to the nuts and bolts of building something from scratch with media. It provides a framework for working with graphics, sound, input hardware, etc., and is cross-platform. I haven't personally used SDL but it's a pretty well-utilized library. It's written in C so the same caveats apply as before, but works just fine with C++.

This has already been fixed in the latest SDL version, but it's likely that the game comes bundled with it's own version.

I got tired of writing C# bindings code by hand to interop with native C/C++ libraries, so I automated the process. Example for SDL: https://github.com/bottlenoselabs/SDL-cs. The repository is automated daily using Dependabot to run C2CS, generate the P/Invoke code, and push a Git commit with the code automatically when there is a change to https://github.com/libsdl-org/SDL.

Simple Directmedia Layer: a library that offers low-level access to resources like audio, video graphics, joystick, keyboard, mouse. It is mainly used for the development of video games (Stepmania and Valve's games such as Counter Strike: Source, as some examples).

Now, we'll need to source the latest SDL source tarball. You can find it [here](https://github.com/libsdl-org/SDL), but you can source the latest as of this writing with the command below. Run cd, and then run:

Game library: https://github.com/libsdl-org/SDL

If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.

https://github.com/sqlite/sqlite/tree/master/ext/lsm1

https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...

The sqlite code base is really well done. Lots of documentation.

https://github.com/sqlite/sqlite

Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...

Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c

That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.

"C in a Nutshell 2nd Ed" (O'Reilly, Prinz & Craqford, 2015) is a good reference although maybe not the best for a walk-through learning experience. It also has good chapters on tooling (gcc, make, gdb).

There's a recent book out I came across called "Bare Metal C" (No Starch Press, Oualline, 2022) which unpacks embedded programming in a very readable manner. I imagine a lot, if not most, C programming these days is done in the low-level embedded world, and this book clears up a lot of the mysteries.

https://nostarch.com/bare-metal-c

Also it never hurts to look at a good open-source codebase written in C, for example the SQLite code is worth looking at (if a bit overwhelming):

https://github.com/sqlite/sqlite/tree/master/src

> After that, 510 bytes are used for the SHARED lock. A byte range is used here to accommodate older Windows versions with mandatory locks.

I was curious how old, and... wow, that code is for Windows versions that predate the NT kernel (Win95/98/ME). I'm surprised that it's still around, but the comment does a great job of explaining it.

https://github.com/sqlite/sqlite/blob/3cf46ee508e97b46736a26...

I wouldn't rely on Google to learn good practices for technical documentation (unless they want to release their complete internal technical documents on how their recommendation algorithms work, that is).

Instead, check out a reliable open source project like SQLITE, they have great documentation:

https://www.sqlite.org/arch.html

https://github.com/sqlite/sqlite