<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Tim,<div><br></div><div>Thanks for editing the Exceptions Hierarchy wiki page. (<a href="https://projects.cecs.pdx.edu:8443/~black/NewOOL/index.cgi/wiki/ExceptionHierarchy">https://projects.cecs.pdx.edu:8443/~black/NewOOL/index.cgi/wiki/ExceptionHierarchy</a>).</div><div>I made a few more edits, to add more information. </div><div><br></div><div>There is one section that I don’t understand. Please take a look at it and see if you can clarify it (or delete it?)</div><div><br></div><div><h2 id="MatchingExceptions" style="font-family: Arial, Verdana, 'Bitstream Vera Sans', Helvetica, sans-serif; page-break-after: avoid; font-size: 16px; margin-left: -18px; background-color: rgb(255, 255, 255);">Matching <tt>Exception</tt>s<a class="anchor" href="https://projects.cecs.pdx.edu:8443/~black/NewOOL/index.cgi/wiki/ExceptionHierarchy#MatchingExceptions" title="Link to this section" style="text-decoration: none; color: rgb(215, 215, 215); border: none; font-size: 0.8em; vertical-align: text-top; visibility: hidden;"></a></h2><p style="font-family: Verdana, Arial, 'Bitstream Vera Sans', Helvetica, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255);">Each exception is matched by its <tt>ExceptionKind</tt> and all of the ancestors of that <tt>ExceptionKind</tt> (that is, by its parent, its parent's parent, and so on). Because <tt>Exception</tt> is the top of the exception hierarchy, it matches all exceptions. <<<apb: This bit I don't grok. I don't think that it's legal grace.>>> ... and so is equivalent to the type of exceptions with an extended interface. That is:</p><pre class="wiki" style="background-color: rgb(247, 247, 247); border: 1px solid rgb(215, 215, 215); margin-right: 1.75em; margin-left: 1.75em; padding: 0.25em; overflow: auto; font-size: 13px;">def Exception = object {
inherits type { exception -> ExceptionKind; ... }
method parent { ... }
...
}
</pre><p style="font-family: Verdana, Arial, 'Bitstream Vera Sans', Helvetica, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); position: static; z-index: auto;"><<<end of don't grok.>>></p></div><div><br></div><div>The page still says nothing about capitalization of the names — in fact, it’s inconsistent. We agreed that Types should be Capitalized, and other objects should be lower case. You were arguing that Patters should also be Capitalized. What — although presumably not Patterns that are single objects that match only themselves.</div><div><br></div><div>This is really a separate discussion. What is the argument for capitalizing Patterns?</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Andrew</div><div><br></div></body></html>