Static code analysis

Have you every used Lint for C code? Or Coverity or Perl::Critic or FindBugs or PyChecker or PMD or CodePro or Clang or Checkstyle or Oink or Dehydra?

These are tools that look at source or object code and recommend bug and style fixes. On the plus, they identify profound mistakes you would never find on your own. On the minus, they consume programmer time making code conform to questionable standards while masking real bugs.

I’m a Perl::Critic developer (we’re helping people write readable Perl code!) and have experience with a few comparable tools. I’m not planning a canned presentation (but I do have a Perl::Critic talk that I can perform). Instead would like to swap real-world experiences and speculate on a bright future where code studies code.

Average: 5 (1 vote)

And transformations?

If you are doing static code analysis, it would be cool if you also covered transformation/manipulations.

grettke | 22 July 2008 - 10:15pm

transformations

I agree that transformations would be interesting. I have little experience with them, other than what Eclipse offers for Java (and that’s a lot, of course).

ChrisDolan | 23 July 2008 - 9:40pm