Jesus weeps

Lol.

I'm reading about storage classes in C and before that, the author discusses about scope (block scope, function scope, function prototype scope, and block scope), linkage (no linkage, external linkage, and internal linkage), and storage duration (static storage duration, thread storage duration, automatic storage duration, and allocated storage duration). Then, C uses them in combination for different storage classes (automatic variables, register variables, static with external linkage, etc.). Quite the mouthful if you ask me.

To think, the PROPER and SIMPLE method for managing this are makefiles.

Have you seen a makefile? Even in the best of cases it's a confusing mess. Thankfully the C I ended up having to work with was limited to a single file, with the only libraries required being standard. Thank god.

Makefiles can be wild. I've used them for simple stuff and even then they can be a sight to behold.

BTW, does "Manual" refer to the dynamically-allocated memory in the image?

yessir

I actually ended up not even using malloc, or even pointers, in the C work I ended up doing, I way over prepared knowledge wise for what ended up being required lol