Comments on: Parallel Lint http://www.klocwork.com/blog/2009/06/parallel-lint/?utm_source=rss&utm_medium=rss&utm_campaign=parallel-lint >kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis. Tue, 24 Jan 2012 14:57:13 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Anneliese Gimpel http://www.klocwork.com/blog/2009/06/parallel-lint/comment-page-1/#comment-1761 Anneliese Gimpel Wed, 17 Mar 2010 15:56:53 +0000 http://www.klocwork.com/blog/?p=203#comment-1761 It seems that Andrey Karpov is not as familiar with PC-lint as he may think. Version 1.0 of PC-lint was first released in May of 1985 and at that time it supported inter-module checking of C source code. The current version of PC-lint is 9.0 and it provides inter-module checking of C and C++ code. PC-lint has been doing inter-module checking for the past 25 years and Mr. Karpov is correct when he states that "it is a very difficult task" - the developers at Gimpel Software are very aware of the difficulties and have been dealing with them for 25 years. It seems that Andrey Karpov is not as familiar with PC-lint as he may think.

Version 1.0 of PC-lint was first released in May of 1985 and at that time it supported inter-module checking of C source code. The current version of PC-lint is 9.0 and it provides inter-module checking of C and C++ code.

PC-lint has been doing inter-module checking for the past 25 years and Mr. Karpov is correct when he states that “it is a very difficult task” – the developers at Gimpel Software are very aware of the difficulties and have been dealing with them for 25 years.

]]> By: Michael Donohue http://www.klocwork.com/blog/2009/06/parallel-lint/comment-page-1/#comment-321 Michael Donohue Tue, 23 Jun 2009 14:42:40 +0000 http://www.klocwork.com/blog/?p=203#comment-321 The modern generation of static analysis tools have not done a good job of distinguishing themselves from the first generation with language. The term 'static analysis' is used commonly to mean any type of tool that looks at source code, no matter how simple the analysis is, with the result that 'grep' is a static analysis tool. I had hoped that Coverity, Klocwork, et al. would adopt a different term, like 'semantic analysis' which conveys the depth of understanding that their tools have of the software. Since grep style tools have no semantic understanding of the code, they would be dropped from such a list. The modern generation of static analysis tools have not done a good job of distinguishing themselves from the first generation with language. The term ‘static analysis’ is used commonly to mean any type of tool that looks at source code, no matter how simple the analysis is, with the result that ‘grep’ is a static analysis tool.

I had hoped that Coverity, Klocwork, et al. would adopt a different term, like ‘semantic analysis’ which conveys the depth of understanding that their tools have of the software. Since grep style tools have no semantic understanding of the code, they would be dropped from such a list.

]]>