Thanks for the very informative response. Really helps to understand the reasoning.
To me, personally, the obsession for cryptic acronyms and mangled words is a relic of the '60ies which could need an update. It was motivated by limited RAM and CPU time for the compilers, it was never the right choice but a necessary cut. It should have ended in the '90ies. Redundant words fall in a similar category, as something looking smart now and being the reason for further criticism as they are discovered to be nothing more than dummy stubs to simplify one specific tool/task.
Java and JS showed you can have a language with keywords written in correct English (ok, except for enum) and still be part of the extended C family.
It's frankly surprising how shockingly ugly is a modern language like Rust, where literally not a single keyword is written properly. Dyslexic by design, yet requiring vast amount of resources to parse/compile.
It can be fun while it's the underdog language, but as it gains prominence, it will just flood the world with weird syllables and strings which is too late to fix. Until the next language takes over.
I hope you understand why I'd rather avoid having a new and promising language go down the same path.
I am not suggesting any modification, I respect your code, your way of thinking, your effort to create something new. I'd however like to share my concerns as constructive criticism
I usually love C and C language families, that's because they offer a familiar syntax and let you side-jump according to your curiosity and desire to learn.
This is where C3 completely fails, however. It feels like a dyslexic cross between C and Rust (the most dyslexic language ever. They felt the need to mangle/shorten every single keyword for "reasons").
fn void Stack.push() ? really? why did anyone thing "fn" in front of a procedure/function makes sense in a C language family?
not exactly 68K CPU only, but given you can easily disable the AmigaOS with a single call, you may want to install VisualStudio Code and the Amiga Assembly extension (includes FS-EAE integration and the asm/code monitor tools)
Worst case, instead of just the Motorola 68000, you'll learn the 68K in the context of a still very nice machine.
To me, personally, the obsession for cryptic acronyms and mangled words is a relic of the '60ies which could need an update. It was motivated by limited RAM and CPU time for the compilers, it was never the right choice but a necessary cut. It should have ended in the '90ies. Redundant words fall in a similar category, as something looking smart now and being the reason for further criticism as they are discovered to be nothing more than dummy stubs to simplify one specific tool/task.
Java and JS showed you can have a language with keywords written in correct English (ok, except for enum) and still be part of the extended C family.
It's frankly surprising how shockingly ugly is a modern language like Rust, where literally not a single keyword is written properly. Dyslexic by design, yet requiring vast amount of resources to parse/compile.
It can be fun while it's the underdog language, but as it gains prominence, it will just flood the world with weird syllables and strings which is too late to fix. Until the next language takes over.
I hope you understand why I'd rather avoid having a new and promising language go down the same path.
I am not suggesting any modification, I respect your code, your way of thinking, your effort to create something new. I'd however like to share my concerns as constructive criticism