Another solution to the GCC problems for Newton development is to use Assembler. Sounds crazy? Maybe, but that’s how I started programming ages ago, and at least for low level stuff like Blunt (which is mostly about moving bytes around), it might actually be quite suitable. Only interfacing with the NewtonOS and C++ requires some effort, but there’s no reason not to use clever preprocessing or macros to simplify it… this is of course no cure to port existing C or C++ code.