yep. That's one of the analyzers we integrate with. We're expanding out portfolio to include a suite of open source and (1 or 2) proprietary static analyzers. They help to identify defects and provide information about the defect to our AI (deep learning) component that suggests fixes. Obviously its a work in progress, but if we can help people out now, that would be awesome!
In the PR, I'll supply the BR from the static analyzer upon request.
On Thu, May 11, 2017 at 5:00 PM, Matthew Brush mbrush@codebrainz.ca wrote:
On 2017-05-11 01:34 PM, Benjamin Bales wrote:
ok, I'll submit a PR with some of the fixes that I think are good. Was the format of the bug report acceptable? Our tool integrates with static analyzers, and sometimes its tricky to include their reports in a way that is clear and concise. Of course, I will provide my own summary of the issues, but I would like to know if you found them helpful.
It seems OK, though I just looked for the file/line info and studied what the code did, I didn't notice the PNG attachment until afterward. It reminds me a bit of clang static analyzer html/xcode output but without the fancy arrows.
Regards, Matthew Brush _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel