Re:Modern C++ Won't Save Us
by AnimalMuppet on Monday April 22, 2019 @11:22PM
(#19725313)
Well, it shows that there are aspects of C/C++ which are unsafe. But you don't have to use string_view or span, you know...
[ Parent
| on HN ]
It was presented to show the "just use modern c++" counterargument to discussing the unsafety of c++ isn't a great argument. There are modern parts that are still unsafe.
Re:Modern C++ Won't Save Us
by AnimalMuppet on Monday April 22, 2019 @11:36PM
(#19725384)
Fair enough. But tatersolid seems to be condemning the entire language, which is a step too far for the evidence given.
Re:Modern C++ Won't Save Us
by tatersolid on Tuesday April 23, 2019 @08:13AM
(#19727813)
40 years of security vulnerabilities in C and C++ code is plenty of evidence to condemn those languages as unfit for most purposes.
The evidence is overwhelming that it is not possible to write non-trivial C or C++ that is safe in the face of adversarial input. Microsoft, Google, Oracle, Linus, etc. have all tried for decades and failed miserably. All the resources and expertise in the world still results in unsafe software when C and C++ are used.