<?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"
	>
<channel>
	<title>Comments on: werror</title>
	<atom:link href="http://blogs.gnome.org/uraeus/2006/02/23/werror/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/uraeus/2006/02/23/werror/</link>
	<description>Just another GNOME Blogs weblog</description>
	<pubDate>Tue, 07 Oct 2008 00:08:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Sven</title>
		<link>http://blogs.gnome.org/uraeus/2006/02/23/werror/#comment-260</link>
		<dc:creator>Sven</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/02/23/werror/#comment-260</guid>
		<description>Noone can stand compiler warnings. Are you seriously saying that there are actively maintained projects in GNOME CVS that have a considerable amount of compiler warnings? How is that possible? -Wall should definitely be enough to catch all problems. Instead of forcing -Werror on people, the use of colorgcc or colormake should be encouraged so that warnings don't get unnoticed.&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>Noone can stand compiler warnings. Are you seriously saying that there are actively maintained projects in GNOME CVS that have a considerable amount of compiler warnings? How is that possible? -Wall should definitely be enough to catch all problems. Instead of forcing -Werror on people, the use of colorgcc or colormake should be encouraged so that warnings don&#8217;t get unnoticed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
