Am I the only one who doesn't understand why it's still considered "okay" to write C for security-dependent code these days? Processors have gotten order of magnitudes faster, speed is no longer the constraining resource, and certainly not one I would trade my security for...
back
2 comments
Oh my god what a revelation. I've never seen anyone bring this up before.
Outside of every single thread about C. Everyone at this point knows the shitty side of C.
Don't even need anything that drastic. Just switch the compiler to C++ mode and start using std::unique_ptr instead of malloc/free. Remember to turn off exceptions and RTTI to keep the spirit of C alive in your C++ code!