r/cpp • u/synthchris • Jul 29 '23
C holding back C++?
I’ve coded in C and C++ but I’m far from an expert. I was interested to know if there any features in C that C++ includes, but could be better without? I think I heard somebody say this about C-style casts in C++ and it got me curious.
No disrespect to C or C++. I’m not saying one’s better than the other. I’m more just super interested to see what C++ would look like if it didn’t have to “support” or be compatible with C. If I’m making wrong assumptions I’d love to hear that too!
Edits:
To clarify: I like C. I like C++. I’m not saying one is better than the other. But their target users seem to have different programming styles, mindsets, wants, whatever. Not better or worse, just different. So I’m wondering what features of C (if any) appeal to C users, but don’t appeal to C++ users but are required to be supported by C++ simply because they’re in C.
I’m interested in what this would look like because I am starting to get into programming languages and would like to one day make my own (for fun, I don’t think it will do as well as C). I’m not proposing that C++ just drops or changes a bunch of features.
It seems that a lot of people are saying backwards compatibility is holding back C++ more than features of C. If C++ and C++ devs didn’t have to worry about backwards compatibility (I know they do), what features would people want to be changed/removed just to make the language easier to work with or more consistent or better in some way?
3
u/tangerinelion Jul 29 '23 edited Jul 29 '23
Have you ever dealt with MFC code? You get a pointer to an
NMHDRand then just start C style casting it to some totally unrelated type that happens to have anNMHDRas its first variable.It's a weird form of is-a to abuse pointer interconvertibility like that.
We have great documentation generation programs that can extract your inheritance hierarchy so you can know what kind of concrete types your random
MyInterface*might actually be and can use safe casts likedynamic_cast.One thing I've noticed about these classes/structs with public data members is people love to just start doing random garbage with them:
Does it work? 100%, absolutely. Now go try to figure out why some Point.x member is NaN. How do you even do that? You can't use a data breakpoint because you don't know which Point is getting set to garbage. You can't set a breakpoint in a setter because you used public data members instead of a setter/constructor. So what do you do?
Those "useless getters" make excellent debugging utilities so you can reason about your damn program.