> On 16 apr. 2015, at 01:26, Bradley Bunk <bradbun...@gmail.com> wrote: > > Good evening, > > I am working on a school project in which I have to give a presentation on a > testing tool of choice; I chose the clang static analysis tool. Adium is one > of the few projects I have found that actively uses the tool. I am curious to > know how and or why the community chose and or chooses to use the tool and or > how you integrate it into your build/testing work flow. I apologize if this > is not the intended use of this email list, I could not find any > documentation on clang and or your testing approach in the wiki (this may be > due to my own incompetence and or ignorance.), and I am genuinely curious to > know about it and or to be able to test the code my self. > > thank you for your time, > > Bradley Bunk
Hi Bradley, In the past I’ve used the static analyzer tool a couple of times, mostly for the 1.6 branch if I remember correctly. It is not integrated into our workflow automatically, I’ve only ran it manually. I don’t actually know any other static analyzers (especially with support for Objective-C), so I can’t answer why I chose it over other things. It worked quite well for me (pros: quite fast, easy to understand the warnings it gives, easy to use), and it’s even integrated with Xcode (thought I didn’t use that myself). I hope that answers your questions, feel free to ask more, this list is definitely the right place for that. Best regards, Thijs Alkemade
