<?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: warning options</title>
	<atom:link href="http://blogs.gnome.org/otte/2008/12/22/warning-options/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/otte/2008/12/22/warning-options/</link>
	<description>Just another GNOME Blogs weblog</description>
	<lastBuildDate>Fri, 20 Nov 2009 09:10:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ariya</title>
		<link>http://blogs.gnome.org/otte/2008/12/22/warning-options/comment-page-1/#comment-908</link>
		<dc:creator>Ariya</dc:creator>
		<pubDate>Mon, 29 Dec 2008 16:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/?p=133#comment-908</guid>
		<description>An excellent treatment. Many thanks!</description>
		<content:encoded><![CDATA[<p>An excellent treatment. Many thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Nicholson</title>
		<link>http://blogs.gnome.org/otte/2008/12/22/warning-options/comment-page-1/#comment-902</link>
		<dc:creator>Dan Nicholson</dc:creator>
		<pubDate>Mon, 22 Dec 2008 23:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/?p=133#comment-902</guid>
		<description>-Wold-style-definition: You should take a look at the Xorg server and library code sometime. There&#039;s still tons of the K&amp;R style lurking around.</description>
		<content:encoded><![CDATA[<p>-Wold-style-definition: You should take a look at the Xorg server and library code sometime. There&#8217;s still tons of the K&amp;R style lurking around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Winship</title>
		<link>http://blogs.gnome.org/otte/2008/12/22/warning-options/comment-page-1/#comment-900</link>
		<dc:creator>Dan Winship</dc:creator>
		<pubDate>Mon, 22 Dec 2008 18:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/?p=133#comment-900</guid>
		<description>-Wpointer-arith is actually a GNU C vs ISO C portability thing; ISO doesn&#039;t let you do arithmetic on void pointers, GNU does, so it&#039;s good to include it to make sure your code compiles with non-GNU compilers.

The only -W flag I use that you don&#039;t list here is -Wstrict-prototypes (which warns if you have an empty function prototype, which often means &quot;C++ programmer forgot that () and (void) are different in C prototypes&quot;). But of course, you can&#039;t include that, because gtk.h triggers that warning (and must continue to do so to maintain API compatibility), so you can&#039;t use it with -Werror, which is one of the reasons why -Werror is evil.

(Actually, the real solution for -Werror [and -pedantic/-pedantic-errors] is that they should have a way to only apply it to *your own* code, not to code from system headers. That would also fix the problem where for years on Solaris, it was impossible to compile an X program with -Wall -Werror.)</description>
		<content:encoded><![CDATA[<p>-Wpointer-arith is actually a GNU C vs ISO C portability thing; ISO doesn&#8217;t let you do arithmetic on void pointers, GNU does, so it&#8217;s good to include it to make sure your code compiles with non-GNU compilers.</p>
<p>The only -W flag I use that you don&#8217;t list here is -Wstrict-prototypes (which warns if you have an empty function prototype, which often means &#8220;C++ programmer forgot that () and (void) are different in C prototypes&#8221;). But of course, you can&#8217;t include that, because gtk.h triggers that warning (and must continue to do so to maintain API compatibility), so you can&#8217;t use it with -Werror, which is one of the reasons why -Werror is evil.</p>
<p>(Actually, the real solution for -Werror [and -pedantic/-pedantic-errors] is that they should have a way to only apply it to *your own* code, not to code from system headers. That would also fix the problem where for years on Solaris, it was impossible to compile an X program with -Wall -Werror.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pádraig Brady</title>
		<link>http://blogs.gnome.org/otte/2008/12/22/warning-options/comment-page-1/#comment-899</link>
		<dc:creator>Pádraig Brady</dc:creator>
		<pubDate>Mon, 22 Dec 2008 17:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/?p=133#comment-899</guid>
		<description>Re -Wno-missing-field-initializers see:
http://www.pixelbeat.org/programming/gcc/auto_init.html

Warning are beginning to be used more in gnulib, coreutils, bison et. al. now, see:
http://lists.gnu.org/archive/html/bug-gnulib/2008-12/msg00046.html</description>
		<content:encoded><![CDATA[<p>Re -Wno-missing-field-initializers see:<br />
<a href="http://www.pixelbeat.org/programming/gcc/auto_init.html" rel="nofollow">http://www.pixelbeat.org/programming/gcc/auto_init.html</a></p>
<p>Warning are beginning to be used more in gnulib, coreutils, bison et. al. now, see:<br />
<a href="http://lists.gnu.org/archive/html/bug-gnulib/2008-12/msg00046.html" rel="nofollow">http://lists.gnu.org/archive/html/bug-gnulib/2008-12/msg00046.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
