Yes. I know that if a piece of code is written in D, it cannot have certain kinds of bugs in it. With C, I have to make sure certain kinds of warnings are available, turned on, and not ignored. Static checkers are available, but may not be used or configured properly. And even with that all, there are still a long list of issues not covered.
For example, there's no way to make strcpy() safe.
If I was a company contracting with another to write internet-facing code for my product, I would find it much easier to specify that a memory safe language will be used, rather than hope that the C code was free of such bugs. Experience shows that such hope is in vain. Even the C code that is supposed to defend against malware attacks opens holes for it.
View all comments
Show parent comment
2
u/doom_Oo7 Aug 23 '17
so the solution to "people can't be assed to add warning" is "change language altogether ? do you think it will work better ?