<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: False positives in modern static analyzers</title>
	<atom:link href="http://www.klocwork.com/blog/2009/05/false-positives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klocwork.com/blog/2009/05/false-positives/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=false-positives</link>
	<description>&#62;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.</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:57:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Andrew</title>
		<link>http://www.klocwork.com/blog/2009/05/false-positives/comment-page-1/#comment-3043</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 18 Aug 2010 16:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=175#comment-3043</guid>
		<description>Interestingly, some organizations use &quot;false positives&quot; as an opportunity to flag code that should be rewritten.  Modern static analysis tools are pretty sophisticated and so code that trips up the analysis can be indicative of code that is overly complex and difficult to maintain.  The rocket scientists at NASA use the &quot;Power of 10&quot; rules, one of which states that not only should they fix problems coming from static analysis tools, but also &quot;fix&quot; the code so warnings/false positives go away.  This process may not be for everybody, and sometimes there are real false positives which should be ignored, but the point is that false positives may be indicative of something more than a deficiency in analysis.  For more on the power of 10 visit http://codeintegrity.blogspot.com/2010/08/power-of-10-for-safety-critical-code.html</description>
		<content:encoded><![CDATA[<p>Interestingly, some organizations use &#8220;false positives&#8221; as an opportunity to flag code that should be rewritten.  Modern static analysis tools are pretty sophisticated and so code that trips up the analysis can be indicative of code that is overly complex and difficult to maintain.  The rocket scientists at NASA use the &#8220;Power of 10&#8243; rules, one of which states that not only should they fix problems coming from static analysis tools, but also &#8220;fix&#8221; the code so warnings/false positives go away.  This process may not be for everybody, and sometimes there are real false positives which should be ignored, but the point is that false positives may be indicative of something more than a deficiency in analysis.  For more on the power of 10 visit <a href="http://codeintegrity.blogspot.com/2010/08/power-of-10-for-safety-critical-code.html" rel="nofollow">http://codeintegrity.blogspot.com/2010/08/power-of-10-for-safety-critical-code.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

