<?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="Class (programming) - Page 27 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Class_(programming)&amp;p=26">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Class_%28programming%29&amp;p=28">3.Next</a>
</p>
<p>Flavors and CLOS provide a capability for more than one parent to do so at run time introduces complexity that many in the object-oriented community consider antithetical to the goals of using object classes in the first place. Understanding which class will be responsible for handling a message can get complex when dealing with more than one superclass. If used carelessly this feature can introduce some of the same system complexity and ambiguity classes were designed to avoid.</p>

<p>Most modern object-oriented languages such as Smalltalk</p><p>
<a accesskey="1" href="page.php?w=Class_(programming)&amp;p=26">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Class_%28programming%29&amp;p=28">3.Next</a>
</p>

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

</card>
</wml>
