Not that it would eliminate security exploits caused by logical bugs, but most those exploits were already taken care of with Burroughs Algol variant (1961), Modula-2 (1978), Cedar (1981), Ada (1983), .... but oh well.
Re:A critique of "How to C in 2016"
by benbenolson on Friday January 15, 2016 @08:48AM
(#10909240)
Those are due to programmer error. The fact that C doesn't lie to you means that it takes a bit more experience to program properly; as with all things, with great power comes great responsibility. You don't blame the gun for killing people, you blame the person for shooting it.
> Those are due to programmer error.
How does that help? Almost all security vulnerabilities are due to programmer error.
> You don't blame the gun for killing people, you blame the person for shooting it.
It's more like choosing between a gun that makes it really easy to shoot yourself in the foot by accident and one that is safer.
Not even the very best C programmers will write memory safe code. When you write C you will write exploitable code, no matter who you are. Don't blame the programmer for stepping onto a mine in the minefield, blame the minefield.
http://www.cvedetails.com/vulnerability-list/year-2016/month...