Posts Tagged ‘Compiler Warnings’

  • Compiler warnings, Coding standards, Code quality…oh my! (Part 2)

    on Nov 3, 09 • by Alen Zukich • with No Comments

    In the first blog series, we discussed the value of compiler warnings and wondered why a static analysis tool would have similar error checking features. In this installment, we want to dive deeper into this question by reviewing errors that can be found by compilers, why they matter, and what limitations compilers have in this area. Let’s take an example of the “implicit int” rule: int foo() { const x = 0; return x; } This is a situation where failure to specify a type results in this compiler warning from (gcc v.3.4.4) or Microsoft

    Read More »
  • Compiler warnings, Coding standards, Code quality…oh my! (Part 1)

    on Oct 7, 09 • by Alen Zukich • with No Comments

    In this 3 part blog series I want to cover general misconceptions with static analysis coverage.  This will include a discussion about: compiler warnings available, different types of style issues including coding standards, and your available options to fit them into your formal process. Very often customers ask why we don’t cover specific checkers.  We always get great feedback on high value checkers that they would like to see.  But occasionally we get the request to find simple compiler warnings or code style issues. For the first part of this series I want to focus

    Read More »
Scroll to top