The issue is developers are not using the tools or following the best practices because they think they know better than 30 years worth of experience or get caught up in bikeshedding about ideology, licenses and which line the curly braces go on.
The issue is developers are not using the tools or following the best practices because they think they know better than 30 years worth of experience or get caught up in bikeshedding about ideology, licenses and which line the curly braces go on.
Nevermind the copious undefined behavior, the fact that C programmers sometimes struggle to figure out what a valid C expression actually does, the fact that C programmers have to choose between code bloat and using "goto" for finalization, the fact that there are no standard error handling constructs, the fact that strings are null terminated, the lack of a standardized way to determine array lengths at runtime, etc., etc., etc. Even something as simple as this:
int f(int x, int y) { return x + y; }
Can lead to undefined behavior in C:
https://www.securecoding.cert.org/confluence/display/seccode...
Basically C should be at the bottom of the list of languages that programmers choose for cryptography or security software.
http://www.amazon.com/The-CERT-Secure-Coding-Standard/dp/032...
Online:
https://www.securecoding.cert.org/confluence/display/seccode...
Others:
http://www.amazon.com/Secure-Coding-Edition-Software-Enginee...
http://www.amazon.com/Style-Guidelines-Programming-Professio...
http://www.amazon.com/C-Traps-Pitfalls-Andrew-Koenig/dp/0201...