chrgfx VS Heady

I wrote a retro hardware, tile-based graphics conversion library a while back - chrgfx . It was my first decent-sized C++ project and looking at some the code now makes me wince, but it's pretty solid. I'd like to refactor it eventually. Any comments are certainly appreciated.

I've recently made a small update to Heady, which is a C++ library and command-line tool used to create amalgamated single-header libraries from standard C++ source files. In the readme, I also describe how to prepare your source code for header amalgamation using four rules.

If you're interested, I've made an open source utility called Heady that converts normal C++ library code into an amalgamated header file. You obviously have to follow a few rules and mark up your functions appropriately, but I've been using this successfully in my Jinx scripting library for a while now.

In of the first sections in the tutorial and on the Github landing page, I mention that Jinx requires C++ 17, because I do make use of a few C++ 17-specific features. For example, one of those techniques makes it simpler to offer an amalgamated header-only version of the library. I specifically test on the big three: MSVC, Clang, and gcc, on Windows, Mac, and Linux respectively, so I typically don't use features not available on the latest versions of those OSes and their toolchains, or else offer conditional compilation.