@[email protected] to [email protected]English • edit-22 months agoThe empire of C++ strikes back with Safe C++ blueprintwww.theregister.comexternal-linkmessage-square38fedilinkarrow-up137arrow-down12cross-posted to: [email protected][email protected]
arrow-up135arrow-down1external-linkThe empire of C++ strikes back with Safe C++ blueprintwww.theregister.com@[email protected] to [email protected]English • edit-22 months agomessage-square38fedilinkcross-posted to: [email protected][email protected]
minus-square@[email protected]linkfedilink1•2 months agoYou don’t have to use unsafe C++ functions either C++ is technically safe if you follow best practices The issue, to me, is that people learn older versions of the language first, and aren’t aware of the better ways of doing stuff. IMO people should learn the latest C++ version first, and only look at the older types of implementation when they come across them
minus-square@[email protected]linkfedilink2•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-square@[email protected]linkfedilink4•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)
You don’t have to use unsafe C++ functions either
C++ is technically safe if you follow best practices
The issue, to me, is that people learn older versions of the language first, and aren’t aware of the better ways of doing stuff.
IMO people should learn the latest C++ version first, and only look at the older types of implementation when they come across them
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)