<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Undefined behavior - Page 5 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Undefined_behavior&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Undefined_behavior&amp;p=6">3.Next</a>
</p>
<p>standardization of the platforms has made this less of an advantage, especially in newer versions of C. Now, the cases for undefined behavior typically represent unambiguous <a href="page.php?w=software_bug">bugs</a> in the code, for example <a href="page.php?w=array_index">indexing an array</a> outside of its bounds. By definition, the <a href="page.php?w=runtime_system">runtime</a> can assume that undefined behavior never happens; therefore, some invalid conditions do not need to be checked against. For a <a href="page.php?w=compiler">compiler</a>,</p><p>
<a accesskey="1" href="page.php?w=Undefined_behavior&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Undefined_behavior&amp;p=6">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
