blob: 7a1ec701d37d54d0f70ec31521a98525dffdb8f0 [file] [log] [blame]
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="../css/ot.css" />
<link rel="stylesheet" type="text/css" href="../css/otjld.css" />
<title>OT/J Language Definition v1.3.1</title>
</head>
<body class="otdt">
<div id="content">
<table class="nav">
<tr>
<td class="back"><a id="top"></a><a href="s1.5.d.html" rel="prev">&lt;&lt;&nbsp;&sect;1.5.(d)&nbsp;Prohibition of name clashes</a></td>
<td class="top"><a href="index.html" rel="contents">&uarr;&nbsp;Table of Contents&nbsp;&uarr;</a></td>
<td class="next"><a href="s1.5.f.html" rel="next">&sect;1.5.(f)&nbsp;Qualified tsuper&nbsp;&gt;&gt;</a></td>
</tr>
</table>
<div class="breadcrumb"><a class="nav" href="s1.html" rel="section">&sect;1&nbsp;Teams and Roles</a>&nbsp;&gt;&nbsp;<a class="nav" href="s1.5.html" rel="section">&sect;1.5&nbsp;Team and role nesting</a></div>
<div class="subsect depth3" id="s1.5.e">
<h4 class="subsect">&sect;1.5.(e)&nbsp;<span class="title">Precedence among different supers</span><a class="img" href="s1.5.e.html"
title="PermaLink to (e)&nbsp;Precedence among different supers"><img style="vertical-align:text-top;margin-left:5px;" src="../images/permalink.png"
alt="" /></a></h4>
<p>If a role inherits the same feature from several super roles (super and tsuper),
an implicitly inherited version always overrides any explicitly inherited feature,
i.e., a role with the same simple name is closer related than one with a different name.
</p>
<p>
Also implicit inheritance alone may produce several candidate methods inherited by a role class.
This is a result of team-nesting where each level of nesting may add one more tsuper role
if outer teams also participate in an inheritance relationship.
In this case a role inherited from an <em>implicit</em> super team of the enclosing team
is closer related than a role inherited from an <em>explicit</em> super team.
If necessary this rule is applied inside out until a nesting level is found where indeed
explicit team inheritance is involved.<br />
So when comparing classes by their fully qualified names
the longest common suffix will determine the closest relationship.
E.g., <code>SuperOuter.RoleAndTeamSub.InnerRole</code>
is the closest ancestor of <code>SubOuter.RoleAndTeamSub.InnerRole</code>
because both share the name suffix <code>RoleAndTeamSub.InnerRole</code>.
</p>
<div class="codecomment">
<table>
<colgroup span="1">
<col align="left" span="1" />
<col align="center" span="1" />
</colgroup>
<tr>
<td valign="top" rowspan="1" colspan="1">
<p>In the above example (<a href="s1.html#l1.5" class="listing">Listing 1.5</a>) role <code class="small">OuterTeam.RoleAndTeamSub.InnerRole</code>
has two direct tsuper roles:
<code class="small">OuterTeam.RoleAndTeam.InnerRole</code>&nbsp;and <code class="small">SuperOuter.RoleAndTeamSub.InnerRole</code>.
Without the method <code>foo</code> defined in lines 27-30, the enclosing class <code class="small">OuterTeam.RoleAndTeamSub.InnerRole</code>
would inherit the method <code>foo</code> defined in <code>SuperOuter.RoleAndTeamSub.InnerRole</code> (line 9),
because the common name suffix <code>RoleAndTeamSub.InnerRole</code>
creates a stronger relationship making that class the closest ancestor.
</p>
</td>
<td rowspan="1" colspan="1"><img src="../images/team_nesting_hor.png" alt="Example diagram team nesting" /></td>
</tr>
</table>
</div>
</div>
<table class="nav">
<tr>
<td class="back"><a href="s1.5.d.html" rel="prev">&lt;&lt;&nbsp;&sect;1.5.(d)&nbsp;Prohibition of name clashes</a></td>
<td class="top"><a href="index.html" rel="contents">&uarr;&nbsp;Table of Contents&nbsp;&uarr;</a></td>
<td class="next"><a href="s1.5.f.html" rel="next">&sect;1.5.(f)&nbsp;Qualified tsuper&nbsp;&gt;&gt;</a></td>
</tr>
</table>
<div class="breadcrumb"><a class="nav" href="s1.html" rel="section">&sect;1&nbsp;Teams and Roles</a>&nbsp;&gt;&nbsp;<a class="nav" href="s1.5.html" rel="section">&sect;1.5&nbsp;Team and role nesting</a></div>
</div>
<div id="footer">
<hr /><a class="w3c img" href="http://jigsaw.w3.org/css-validator/check/referer"
shape="rect"><img src="../images/valid-css2-blue.png" alt="Valid CSS!" height="31" width="88" /></a><a class="w3c img" href="http://validator.w3.org/check?uri=referer" shape="rect"><img src="../images/valid-xhtml10-blue.png" alt="Valid XHTML 1.0 Strict" height="31"
width="88" /></a><address>&copy; Stephan Herrmann, Christine Hundt, Marco Mosconi</address>
OT/J version 1.3.1 &mdash; last modified: 2013-05-28
</div>
</body>
</html>