permafrost-engine VS hos-x86

Yea, bit annoying to do that, especially in a large project some vectors need to be static some need to be exposed in the API. In my mind the best solution is to add another macro parameter that lets the user change the function scope on the fly. See the vector used in the permafrost engine (a fellow redditor); when I first saw how he wrote his template macros it was a game changing trick.

And the source code for the engine is here on GitHub. I've written like 75k SLOC of C for it. It's a pretty general-purpose RTS engine that could be used for a lot of things - full conversions, remakes of classics, other RTS/citybuilder/ARPG games, and more. It has a Python scripting API for the top-level gameplay logic.

BTW, the engine is fully open-source. So if you want to take a deep dive into the code, it's here: https://github.com/eduard-permyakov/permafrost-engine

I'm into my third year of writing my own RTS game engine in C. Complete with OpenGL rendering, group pathfinding of 1k+ entities, Python scripting, yada, yada, yada.

An operating system still need to implement lot of things like paging

Here's the source code https://github.com/jaychandra6/hos-x86 and here is the stack overflow question https://stackoverflow.com/users/13775460/jaychandra

Here's the GitHub link: https://github.com/jaychandra6/hos-x86