3 ms·

This isn't static analysis. Compare the output of a "real" static analysis tool that finds logic bugs[0] https://www.dropbox.com/s/md35ca9mjrny4o1/Screen%20Sh

This isn't static analysis. Compare the output of a "real" static analysis tool that finds logic bugs[0] https://www.dropbox.com/s/md35ca9mjrny4o1/Screen%20Shot%202013-02-07%20at%208.35.40%20AM.png https://www.dropbox.com/s/md35ca9mjrny4o1/Screen%20Shot%2020... With their whitespace recommendations https://codeq.io/github/tianyang-li/rna-seq-len-est-0/master/play/blat_test_0/gen.py https://codeq.io/github/tianyang-li/rna-seq-len-est-0/master... Which seem to mostly be a wrapper around autopep8: https://github.com/hhatto/autopep8 https://github.com/hhatto/autopep8. Even Pylint / Pyflakes would be more "static analyzer" than this tool, although it's a stretch. [0] In this case it trips an assert, so the bug can't "really" happen. Still, it's pretty impressive stuff.

pablasso 14y ago
I remember how impressed I was when I used clang's static analyser for the first time. I love it, more than makes up for that headache of switching from GCC on OSX.
pekk 14y ago
In what way is pylint not static analysis?
- raverbashing 14y ago
  Not sure what you mean by that, but PyLint gets errors like - calling non-existent members (including class hierarchy analysis) - reading non-existent variables See the Exxxx messages http://pylint-messages.wikidot.com/all-messages http://pylint-messages.wikidot.com/all-messages
  - pekk 14y ago
    I was referring to this quote: "Even Pylint / Pyflakes would be more "static analyzer" [...] although it's a stretch." Why is it a stretch to say that Pylint does static analysis? This is exactly what Pylint does.