qb64 VS permafrost-engine

Unpopular opinion now, but I also still think BASIC is still one of the most approachable beginner languages, even today. Late-era BASIC was way different than the old-style line-numbered BASIC that got a bad reputation for teaching bad habits, and it was possible to write well-structured programs with later dialects like QBasic. There's even a modern, open-source variant of it still being developed called qb64 that makes it possible to make standalone programs with it and I believe adds new features on top of QB (like for graphics handling, mouse, etc.) while also retaining backward compatibility with old QB code. It would even be possible to carry that knowledge forward to a platform like Xojo, which is like a continuation of VisualBASIC, though I wouldn't necessary encourage that. Would make more sense to start with QB and then take the fundamental knowledge learned there and apply it to learning new languages.

Aqui, ó, pra matar a saudade: https://github.com/QB64Team/qb64/blob/77adfc4e1a537733047fcaf638abfcdeef46db2b/programs/samples/misc/nib64.bas (só copiar e colar no QB64, F5 e alegria!).

QB64 v2.0 is now officially available, and you can get it from the official release page on GitHub: https://github.com/QB64Team/qb64/releases/latest

You might appreciate QB64 too...a 64 bit version of QBasic that is cross-platform to Windows, Mac, and Linux and 100% backwards compatible with Qbasic/QB4.5/QBX which is 90% compatible with Visual Basic 1-6 except for the OOP and extended keywords. You can find it, and the C++ source included (compiled with MinGW or GCC usually) at http://www.qb64.org

https://www.qb64.org

There’s also a GUI toolkit with an interface designer being developed for it: https://www.qb64.org/inform/

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.