Criticism of the C programming language: Difference between revisions

Revision as of 06:13, 1 September 2006

Revision as of 06:16, 1 September 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 notNot 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 afor buffer for overflow, have no uncertainty about = vs. ==, know the prededence and associativity of operators by heart, never useresort to redundant parentheses, and use strtok() within its limits, with ease''etc.''

==See also==