So, can you give a concrete example where c++ is "far less safe" than C?
-
-
-
Use after free of a dangling reference. Destructors effectively implicitly call free() without you having to write that in the source.
- 6 more replies
New conversation -
-
-
That's backwards, right? You cannot write inherently safe code in C. C++17 on the other hand at least allows for it.
-
C++17 is not memory safe. You can always get use-after-free in any reasonable subset of C++.
- 3 more replies
New conversation -
-
-
Although C++ has a lot of gotchas, I did well on Stackoverflow b/c of them, I would be hard pressed to write as maintainable code in C
-
C++ may well help you write more maintainable code, but that code can be less safe.
- 11 more replies
New conversation -
-
-
Exactly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is it C++17 in particular or is that a catch-all for C++11 and C++14?
-
A catch-all.
End of conversation
New conversation -
-
-
I disagree entirely. Large projects written in modern C++ are *significantly* more safe than large projects written in C.
-
Twitter is not a good place to argue, but: the evidence does not agree with you.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.