Re: Systematic Fix: Type Safe Programming Language
"it seems to me that it just needs a few tiny nudges to better rationalize and integrate the pre-processor, provide support for Objects, bring functions up to first class objects, some refinement of syntax to allow nesting of functions"
Interestingly C++ started life as an C pre-processor, and one of the requirements was that it was backward compatible with C... It sounds like you may be treading the same path - with different set of constraints. You could try working from the other direction, ie: start with BCPL and work your way through to C+Hindsight. ;)
The thing that surprises me is that you seem to have missed a huge hole in C, explicit support for parallelism. Even doing the bare minimum like supporting a subset of OCCAM constructs like ALT, PAR, PROC & CHAN could help fix an awful lot of broken/unnecessarily complex threaded code.
"I think that a good re-think of the language could allow us to toss C++, C#, Java, Objective C, golang, etc. I have a hunch that done right it would actually decrease the size of the base language."
If you go the BCPL first route I think you have a good chance of achieving that aim, it is a *very* simple language that (allegedly) informed the development of C. If it was me undertaking such a project I think I would be starting at BCPL + CSP level and clone the missing bits of C that I feel I really need. The thing about C/C++ is that the standards committees and compiler writers have actually got the languages to the point where they are actually pretty well defined - and the error checking turned up to 11 tends to weed out the majority of bone head bugs.
We have come a long way from Microsoft's early C compilers that didn't do type checking (thus begetting Hungarian notation - yuck), and compilers that didn't check arguments (anyone else remember wrangling K&R style code ?) ... ;)