Do any of you professionals use either splint, under Windoze, or PC-Lint to analyse your AVR source code for errors ?
I am new to C coding and it has been suggested to me that doing static analysis is a good idea as it could stop a lot of silly mistakes and save a lot of debugging time.
Would it be worth including this or some other code analysis tool in the WinAVR distribution ?
Would it be possible to integrate it as a tool into AVRStudio 4.13, so you could just hit a button on the toolbar to run the analyser ?
Your comments please.