3 ms·
"Note the emphasis on accidental memory safety violations." Good points. Of course, I'm guessing you're saying it's still really hard to write memory-safe code
by nickpsecurity 11y ago
"Note the emphasis on accidental memory safety violations."
Good points. Of course, I'm guessing you're saying it's still really hard to write memory-safe code with modern C++ constructs whereas others here suggest it's pretty easy. That point is tripping me up in these discussions. Did a quick Google on C++ safety and found you already said something about the topic:
https://news.ycombinator.com/item?id=7587978 https://news.ycombinator.com/item?id=7587978
My statement is predicated on the premise that modern C++ can be done safely without issues like that. If not, then it's false and we're back to me recommending safer, systems languages.
One thing to remember, though, is that there's tools to automatically transform C code into safe code. Softbound + CETS comes to mind. Might be able to use a C++-to-C compiler with one of those. There's also safer forms of C++ like Ironclad C++.
http://www.cs.grinnell.edu/~osera/papers/ironclad-cc.pdf http://www.cs.grinnell.edu/~osera/papers/ironclad-cc.pdf
So, the situation might be worse than people looking into C++ were hoping but not as bad as you think.