The empire of C++ strikes back with Safe C++ blueprintwww.theregister.comexternal-linkcross-posted to: programming@programming.dev cmeerw ( @cmeerw@programming.dev ) C++@programming.devEnglish • edit-21 month ago message-square36fedilinkarrow-up124
arrow-up124external-linkThe empire of C++ strikes back with Safe C++ blueprintwww.theregister.com cmeerw ( @cmeerw@programming.dev ) C++@programming.devEnglish • edit-21 month ago message-square36fedilinkcross-posted to: programming@programming.dev
minus-square FizzyOrange ( @FizzyOrange@programming.dev ) linkfedilink0•1 month 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-square FalconMirage ( @FalconMirage@jlai.lu ) linkfedilink1•1 month 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)