cmeerw@programming.dev to C++@programming.devEnglish · edit-22 months agoThe empire of C++ strikes back with Safe C++ blueprintwww.theregister.comexternal-linkmessage-square39fedilinkarrow-up138arrow-down12cross-posted to: programming@programming.devhackernews@lemmy.bestiver.se
arrow-up136arrow-down1external-linkThe empire of C++ strikes back with Safe C++ blueprintwww.theregister.comcmeerw@programming.dev to C++@programming.devEnglish · edit-22 months agomessage-square39fedilinkcross-posted to: programming@programming.devhackernews@lemmy.bestiver.se
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up2·2 months ago C++ is technically safe if you follow best practices Yeah but it’s virtually impossible to reliably follow best practices. The compiler won’t tell you when you’re invoking UB and there is a lot of potential UB in C++. So in practice it is not at all safe.
minus-squareFalconMirage@jlai.lulinkfedilinkarrow-up4·2 months agoI agree I was only adding my opinion (that people should try to always use the latest version of C++, which is inherently safer, but still not 100% safe)
Yeah but it’s virtually impossible to reliably follow best practices. The compiler won’t tell you when you’re invoking UB and there is a lot of potential UB in C++.
So in practice it is not at all safe.
I agree
I was only adding my opinion (that people should try to always use the latest version of C++, which is inherently safer, but still not 100% safe)