Content deleted Content added
Marc W. Abel (talk | contribs) |
Marc W. Abel (talk | contribs) |
||
Line 109:
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, have no uncertainty about = vs. ==, know the prededence and associativity of operators by heart, and never use redundant parentheses.
==See also==
| |||