3 ms·

Has anyone made a plugin or anything of that sort which abstracts away the grunt work of using this sort of system? It sounds like a great thing to try out were

• zedshaw 16y ago
  Not that I know of. I imagine emacs or vim has good error-line parsing which you could steal/copy and get really good results. You could then extend it to work on any language you wanted. Biggest thing I couldn't get right was automatically connecting frequency of errors to particular lines or modules. I found that I made the same mistakes over and over, and I had to just spot them and jot down what not to do or think of a ninja way to avoid it. I also found that there was a strong correlation between syntax/test failures while writing code and how bad the code was. What would have helped is if I could calculate the stats per function, line, or file and then have some pattern analysis spit out common grammatical structures that I do which are correlated with errors. It'd be something like: function/while/if/return 24% chance of defect found in blah.c:func1 and blah.c:func2 Then it'd get closer to predicting defects and letting me go check the spots it recommends. But, never got around to it since it became really insane after a year already without that level of analysis.
• windsurfer 16y ago
  Hudson AKA Jenkins? I'm not sure if that's exactly what you want, but it worked wonders at the job I had.
• torpor 16y ago
  Coverity?