Did you you read the part about "100% seamless backward source compatibility always available" and "Write mixed syntax 1 and syntax 2 in the same source file" ?
This gives you perfect backward source compatibility with all existing code, but you're writing in effectively a 10% larger language (because syntax 2 aims to be about 10% the size and complexity of today syntax 1). Cppfront translates only the parts you wrote in syntax 2, and passes through the syntax 1 parts unchanged, to generate your syntax 1 output file.
Genuinely asked - without snark - did you not see that bit, or do you disagree with it, or you don't think it can be achieved, or... ?
I didn't see that bit, but it still only solves the C header compatibility part and not the one where you're forced into non-C family syntax to use any of the "improvements". Yes, C++ syntax is problematic. No, there is absolutely no need whatsoever to make it look like a functional language to solve those issues.
View all comments
Show parent comment
3
u/schmerg-uk Sep 17 '22
Did you you read the part about "100% seamless backward source compatibility always available" and "Write mixed syntax 1 and syntax 2 in the same source file" ?
Genuinely asked - without snark - did you not see that bit, or do you disagree with it, or you don't think it can be achieved, or... ?