Criticism of the C programming language: Difference between revisions

Revision as of 18:08, 31 August 2006

Revision as of 18:11, 31 August 2006

Line 110:

It should be recognized that these tools are not a panacea. Because of C's flexibility, some types of errors involving misuse of variadic functions, out-of-bounds array indexing, and incorrect memory management cannot be detected on some architectures without incurring a significant performance penalty. However, some common cases can be recognized and accounted for.

A mention should be made that not every programmer needs a tool to deal with every concern. There are many gifted C programmers who aren't prone to memory leaks, know when to check a buffer for overflow, have no uncertainty about = vs. ==, know the prededence and associativity of operators by heart, and never use redundant parentheses, and use strtok() within its limits with ease.

==See also==