Revision as of 03:37, 6 October 2006 edit Eyu100 (talk \| contribs) 2,682 edits m moved Criticism of C to Criticism of the C programming language ← Previous edit		Revision as of 19:28, 12 October 2006 edit undo JesseHogan (talk \| contribs) 898 edits →Tools for mitigating issues with C: It's obvious that some people are very smart and can rely on their on intellects, instead of some helpful tools, to implement technologies. Next edit →
Line 111: 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. Not every programmer needs a tool to deal with every concern. There are many C programmers who aren't prone to memory leaks, know when to check for buffer overflow, have no uncertainty about <code>=</code> vs. <code>==</code>, know the precedence and associativity of operators by heart, never resort to redundant parentheses, use strtok() within its limits, ''etc.'' ==Notes==

Criticism of the C programming language: Difference between revisions