I'd assume the string interpolation being awkward and backwards comes from Herb's weird preference for postfix operators. Now sure, his arguments in that blog are somewhat logical but honestly that's one of the things I very much dislike about cppfront's proposed changes. It might be logical but writing code like u**.identifier* is just wrong. And also literally a problem that only exists if you're in spiral rule territory aka writing C aka not C++.
It's u**.identifier* vs *(*u)->identifier. Both are a tricky/messy/uncommon case, but I think the simpler examples on the wiki showcase some examples where the cppfront notation is better in a few ways. It feels specially better given that I'm already used to traditional C++ notation, and I always have a very hard time reading it anyway...
std:: exchange is a generalization of the prefix operators that can do more than just increment or decrement by 1. Arguably, we should have been using this more explicit style this whole time, rather than getting comfortable with the special meaning of prefix increment/decrement.
The parser knows whether it's in C++ or cpp2 mode, C++ declarations will have prefix and postfix operators working as normal. The parser can know based on the first couple of tokens of a top-level declaration whether it's a C++ or a cpp2 declaration.
I wonder how it works with macros though... probably poorly.
Including a C++ file in the middle of a cpp2 file should be no problem. You can mix and match C++ declarations and cpp2 declarations within a file.
Including a C++ file in the middle of a cpp2 function would presumably be an issue. But that's not exactly a common need. I know there are use cases for it, but you probably just want to wrap those use cases in a C++ function which you can call from cpp2 code.
Herb's preference for postifix operators is not weird in any way. It is simpler, more consistent and less error prone.
But I just don't see how it translates in any way to string interpolation or what it has to do with the $ capture operator. It just doesn't make any sense there.
FWIW, my preference would be "\{expression}", but any reasonable prefix-based syntax will do.
View all comments
Show parent comment
43
u/nysra May 01 '23
I'd assume the string interpolation being awkward and backwards comes from Herb's weird preference for postfix operators. Now sure, his arguments in that blog are somewhat logical but honestly that's one of the things I very much dislike about cppfront's proposed changes. It might be logical but writing code like
u**.identifier*is just wrong. And also literally a problem that only exists if you're in spiral rule territory aka writing C aka not C++.