<?xml version="1.0" encoding="windows-1252"?>
<node id="1008514" title="Re^2: Four annoying warnings" created="2012-12-12 10:06:40" updated="2012-12-12 10:06:40">
<type id="11">
note</type>
<author id="163790">
dsheroh</author>
<data>
<field name="doctext">
That applies to many warnings, yes... but not necessarily to those listed here.  Personally, I can't easily recall &lt;c&gt;warnings 'undef'&lt;/c&gt; ever having caught an actual problem in my code&lt;sup&gt;1&lt;/sup&gt;, but it's constantly complaining about cases where nothing is wrong aside from my not having bothered to add an explicit default-to-zero or test-for-&lt;c&gt;defined&lt;/c&gt; whose sole purpose is to shut &lt;c&gt;warnings 'undef'&lt;/c&gt; up.
&lt;p&gt;
&lt;sup&gt;1&lt;/sup&gt; Which is not to say that it hasn't ever caught an actual problem for me.  I'm sure it has done so on at least several occasions.  But they're so rare that I can't think of any offhand.</field>
<field name="root_node">
1007936</field>
<field name="parent_node">
1008031</field>
</data>
</node>
