I am very happy that C3 now is part of the Handmade Network.
C3 is first and foremost a vision of what C could be if it did not need to be backwards compatible with itself. C3 is not trying to change the paradigm of C, just make it a bit more ergonomic. Regardless whether C3 succeeds as a language, I hope to show that using C to write a compiler is not particularly hard. There's no need to whip out C++ or some other language with more high level abstractions.
C3 itself takes aim at the points where C could be more user friendly: arrays and strings. Macros are made safer by explicitly marking them as well as introducing hygiene. Because the macros are semantic, rather than through a pre-processor, the resulting language is more IDE-friendly as well.
C3 is first and foremost a vision of what C could be if it did not need to be backwards compatible with itself. C3 is not trying to change the paradigm of C, just make it a bit more ergonomic. Regardless whether C3 succeeds as a language, I hope to show that using C to write a compiler is not particularly hard. There's no need to whip out C++ or some other language with more high level abstractions.
C3 itself takes aim at the points where C could be more user friendly: arrays and strings. Macros are made safer by explicitly marking them as well as introducing hygiene. Because the macros are semantic, rather than through a pre-processor, the resulting language is more IDE-friendly as well.
Edited by Christoffer Lernö
on
Reason: Initial post
Welcome.
While I'm not really interested in the language, I would be interested in reading about the creation of a compiler.
While I'm not really interested in the language, I would be interested in reading about the creation of a compiler.
I'll be blogging about more language concerns I guess. What parts of compiler writing are you interested in?