logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

r10480 - trunk/www/books/drm: msg#00093

Subject: r10480 - trunk/www/books/drm
Author: cpage
Date: Tue Dec 27 09:57:33 2005
New Revision: 10480

Modified:
   trunk/www/books/drm/Errata.html
Log:
Job: website

In the Errata page, quoted text from the DRM was wrapped in list
items. I've replaced the one-item lists with BLOCKQUOTE, which is
semantically more correct and lays out better in browsers.

I also made some minor changes to the errata text to make it clearer and to
use consistent wording.



Modified: trunk/www/books/drm/Errata.html
==============================================================================
--- trunk/www/books/drm/Errata.html     (original)
+++ trunk/www/books/drm/Errata.html     Tue Dec 27 09:57:33 2005
@@ -33,35 +33,29 @@
       <li id="p73-1"><a href="Union_Types#errata-p73-1">p. 73</a>, the last 
paragraph explaining the
        subtype relationships of <tt>type-union</tt> reads
 
-       <ul>
-         <li>
-           <code>subtype?(type-union*(s<sub>1</sub>...s<sub>m</sub>)  
type-union*(t<sub>1</sub>...t<sub>n</sub>))</code>
-         </li>
-       </ul>
+       <blockquote>
+         <code>subtype?(type-union*(s<sub>1</sub>...s<sub>m</sub>)  
type-union*(t<sub>1</sub>...t<sub>n</sub>))</code>
+       </blockquote>
        
        <p>is missing a comma and should read</p>
 
-       <ul>
-         <li>
-           <code>subtype?(type-union*(s<sub>1</sub>...s<sub>m</sub>), 
type-union*(t<sub>1</sub>...t<sub>n</sub>))</code>
-         </li>
-       </ul>
-       
+       <blockquote>
+         <code>subtype?(type-union*(s<sub>1</sub>...s<sub>m</sub>), 
type-union*(t<sub>1</sub>...t<sub>n</sub>))</code>
+       </blockquote>
       </li>
       
       <li id="p73-2"><a href="Limited_Types#errata-p73-2">p. 73</a>, the 
example code illustrating
        limited types reads
 
-       <ul>
-         <li><tt>limited(&lt;integer&gt; ,min: 0 max: 255)</tt></li>
-       </ul>
+       <blockquote>
+         <tt>limited(&lt;integer&gt; ,min: 0 max: 255)</tt>
+       </blockquote>
        
        <p>it should read</p>
 
-       <ul>
-         <li><tt>limited(&lt;integer&gt;, min: 0, max: 255)</tt></li>
-       </ul>
-       
+       <blockquote>
+         <tt>limited(&lt;integer&gt;, min: 0, max: 255)</tt>
+       </blockquote>
       </li>
       
       <li id="p83-1"><a href="Functions_Overview#errata-p83-1">p. 83</a>, 
<q>Closures</q>. The
@@ -72,36 +66,35 @@
        method <tt>average</tt>, the return value declaration is incorrect; it 
contains both a
        binding name and a type
        
-       <ul>
-         <li><tt> => avg :: &lt;number&gt;;</tt></li>
-       </ul>
+       <blockquote>
+         <tt> => avg :: &lt;number&gt;;</tt>
+       </blockquote>
 
        <p>but the example is meant to illustrate how, if you do not provide 
both, the first word is
          parsed as the binding name even if it appears to be the name of a 
type. The return value
          declaration should read</p>
        
-       <ul>
-         <li><tt> => &lt;number&gt;;</tt></li>
-       </ul>
-       
+       <blockquote>
+         <tt> => &lt;number&gt;;</tt>
+       </blockquote>
       </li>
       
       <li id="p136-1"><a href="Define_Sealed_Domain#errata-p136-1">p. 136</a>, 
the illustration of
        the third constraint implied by <tt>define sealed domain</tt> should 
include open
        declarations for the initial classes and the generic function, as 
follows
        
-       <ul>
-         <li><tt>define open generic m ( x ) ;<br />
-             define open class &lt;t&gt; ( &lt;object&gt;) end class
-             &lt;t&gt;;<br />
-             define open class &lt;s&gt; ( &lt;object&gt;) end class
-             &lt;s&gt;;<br />
-             define method m ( s :: &lt;s&gt; ) end method m ;<br />
-             define sealed domain m ( &lt;t&gt; );<br />
-             &nbsp;<br />
-             define class &lt;c&gt; ( &lt;s&gt; , &lt;t&gt; ) end;
-         </tt></li>
-       </ul>
+       <blockquote>
+         <tt>define open generic m ( x ) ;<br />
+           define open class &lt;t&gt; ( &lt;object&gt;) end class
+           &lt;t&gt;;<br />
+           define open class &lt;s&gt; ( &lt;object&gt;) end class
+           &lt;s&gt;;<br />
+           define method m ( s :: &lt;s&gt; ) end method m ;<br />
+           define sealed domain m ( &lt;t&gt; );<br />
+           &nbsp;<br />
+           define class &lt;c&gt; ( &lt;s&gt; , &lt;t&gt; ) end;
+         </tt>
+       </blockquote>
        
        <p>In addition, the phrase, <q>The definition of <tt>&lt;c&gt;</tt> 
would be valid if it
            appeared in the same library as the preceding definitions or in a 
library used by
@@ -110,23 +103,23 @@
          defined. This is clearly impossible because of the prohibition 
against circular library
          use paths. Rather, this phrase refers to the following possible 
scenario:</p>
        
-       <ul>
-         <li>Library L1<br />
+       <blockquote>
+         <p>Library L1<br />
            <tt>define open class &lt;t&gt; ( .. ) ... end;<br />
-             define open class &lt;s&gt; ( .. ) ... end;</tt>
-           
-           <p>L2 (uses L1)<br />
-             <tt>define class &lt;c&gt; (&lt;s&gt;, &lt;t&gt;) end;</tt></p>
-           
-           <p>L3 (uses L1)<br />
-             <tt>define generic m (x);<br />
-               define method m (s :: &lt;s&gt;) ... end;<br />
-               define sealed domain m (&lt;t&gt;);</tt></p></li>
-       </ul>
+             define open class &lt;s&gt; ( .. ) ... end;</tt></p>
+         
+         <p>L2 (uses L1)<br />
+           <tt>define class &lt;c&gt; (&lt;s&gt;, &lt;t&gt;) end;</tt></p>
+         
+         <p>L3 (uses L1)<br />
+           <tt>define generic m (x);<br />
+             define method m (s :: &lt;s&gt;) ... end;<br />
+             define sealed domain m (&lt;t&gt;);</tt></p>
+       </blockquote>
        
        <p>These libraries can only be used together if L3 also uses (directly 
or indirectly) L2,
-         and therefore has access to the class <tt>&lt;c&gt;</tt> before the 
domain is
-         sealed.</p></li>
+         and therefore has access to the class <tt>&lt;c&gt;</tt> before the 
domain is sealed.</p>
+      </li>
       
       <li id="p140-1"><a href="Define_Sealed_Domain#errata-p140-1">p. 140</a>, 
the classes and
        generic function should be declared <tt>open</tt>.</li>
@@ -161,17 +154,18 @@
       <li id="p351-1"><a href="Function_Application#errata-p351-1">p. 351</a>, 
the second use
        of <tt>apply</tt> reads
        
-       <ul>
-         <li><tt>apply(min 5, 7 list(3, 1, 4))</tt></li>
-       </ul>
+       <blockquote>
+         <tt>apply(min 5, 7 list(3, 1, 4))</tt>
+       </blockquote>
        
        <p>it should read</p>
        
-       <ul>
-         <li><tt>apply(min, 5, 7, list(3, 1, 4))</tt></li>
-       </ul>
+       <blockquote>
+         <tt>apply(min, 5, 7, list(3, 1, 4))</tt>
+       </blockquote>
        
-       <p>(Note the additional comma after the number <tt>7</tt> in the 
correct version.)</p></li>
+       <p>(Note the additional comma after the number <tt>7</tt> in the 
correct version.)</p>
+      </li>
       
       <li id="p354-1"><a 
href="Reflective_Operations_on_Functions#errata-p354-1">p. 354</a>, in the
        description of the third value returned by <tt>function-arguments</tt>, 
the obsolete binding
@@ -182,11 +176,11 @@
        word <q>permit</q> in the last sentence describing the final example is 
incorrect. The
        word <q>recognize</q> should be used instead, yielding
        
-       <ul>
-         <li>Methods added to the generic function must have one required 
parameter, they must
-           accept keyword arguments, and they must recognize the keyword
-           argument <tt>strength:</tt>.</li>
-       </ul>
+       <blockquote>
+         Methods added to the generic function must have one required 
parameter, they must
+         accept keyword arguments, and they must recognize the keyword
+         argument <tt>strength:</tt>.
+       </blockquote>
        
        <p>This change follows the definitions of the terms <q>permit</q> and 
<q>recognize</q> as
          given on page 94, in the description of parameter list congruency.</p>
@@ -207,41 +201,39 @@
 
       <li>p. 44, the sentence describing execution order of operator calls 
reads
        
-       <ul>
-         <li>The time of the binding specified by the operand (e.g. <tt>+</tt> 
or <tt>*</tt>) is
-           unspecified.</li>
-       </ul>
+       <blockquote>
+         The time of the binding specified by the operand (e.g. <tt>+</tt> or 
<tt>*</tt>) is
+         unspecified.
+       </blockquote>
        
        <p>it should read</p>
        
-       <ul>
-         <li>The time of the binding specified by the operator (e.g. 
<tt>+</tt> or <tt>*</tt>) is
-           unspecified.</li>
-       </ul>
+       <blockquote>
+         The time of the binding specified by the operator (e.g. <tt>+</tt> or 
<tt>*</tt>) is
+         unspecified.
+       </blockquote>
       </li>
       
       <li>p. 83, the two constant definitions should end with semicolons.</li>
 
       <li>p. 88, the sentence before the enumerated list reads
        
-       <ul>
-         <li>Specialization is useful in three way:</li>
-       </ul>
-       
-       <p>it should read</p>
-       
-       <ul>
-         <li>Specialization is useful in three ways:</li>
-       </ul>
+       <blockquote>
+         Specialization is useful in three way:
+       </blockquote>
+       
+       <p>it is missing an <q>s</q> and should read</p>
+       
+       <blockquote>
+         Specialization is useful in three ways:
+       </blockquote>
       </li>
 
       <li>p. 94, there should be a colon at the end of
 
-       <ul>
-         <li>If the generic function's parameter list does not contain a rest 
value declaration,
-           then</li>
-       </ul>
-       
+       <blockquote>
+         If the generic function's parameter list does not contain a rest 
value declaration, then
+       </blockquote>
       </li>
 
       <li>p. 157, there should not be a space between <q>fragment</q> and 
<q>(4)</q>.</li>
@@ -253,17 +245,17 @@
       
       <li>p. 203, the description of <tt>&lt;extended-float&gt;</tt> reads
        
-       <ul>
-         <li>This class is intended but not required to provide more precision
-           that <tt>&lt;double-float&gt;</tt>.</li>
-       </ul>
-       
-       <p>It should read</p>
-       
-       <ul>
-         <li>This class is intended but not required to provide more precision
-           than <tt>&lt;double-float&gt;</tt>.</li>
-       </ul>
+       <blockquote>
+         This class is intended but not required to provide more precision
+         that <tt>&lt;double-float&gt;</tt>.
+       </blockquote>
+       
+       <p><q>that</q> should be <q>than</q>, yielding</p>
+       
+       <blockquote>
+         This class is intended but not required to provide more precision
+         than <tt>&lt;double-float&gt;</tt>.
+       </blockquote>
       </li>
       
       <li>p. 219, The word <q>When</q> is misspelled <q>Whe</q>.</li>
@@ -282,49 +274,48 @@
       
       <li>p. 344, the summary of <tt>all-superclasses</tt> reads
        
-       <ul>
-         <li>Returns the class precedence list a class</li>
-       </ul>
-       
-       <p>it should read</p>
-       
-       <ul>
-         <li>Returns the class precedence list of a class</li>
-       </ul>
+       <blockquote>
+         Returns the class precedence list a class
+       </blockquote>
+       
+       <p>it is missing the word <q>of</q> and should read</p>
+       
+       <blockquote>
+         Returns the class precedence list of a class
+       </blockquote>
       </li>
       
       <li>p. 389, the sentence fragment reading
        
-       <ul>
-         <li>so it cannot being excluded</li>
-       </ul>
+       <blockquote>
+         so it cannot being excluded
+       </blockquote>
        
        <p>should read</p>
        
-       <ul>
-         <li>so it cannot be excluded</li>
-       </ul>
+       <blockquote>
+         so it cannot be excluded
+       </blockquote>
       </li>
 
       <li>p. 391, there should be a space between <q><tt>let</tt></q> and 
<q><tt>(</tt></q> here:
 
-       <ul>
-         <li><tt>let(whole-part :: &lt;integer&gt;, remainder :: &lt;real&gt;) 
= truncate(amount);</tt></li>
-       </ul>
-       
+       <blockquote>
+         <tt>let(whole-part :: &lt;integer&gt;, remainder :: &lt;real&gt;) = 
truncate(amount);</tt>
+       </blockquote>
       </li>
       
       <li>p. 393, the second paragraph begins
        
-       <ul>
-         <li>The <i>handler</i> is function</li>
-       </ul>
-       
-       <p>it should read</p>
-       
-       <ul>
-         <li>The <i>handler</i> is a function</li>
-       </ul>
+       <blockquote>
+         The <i>handler</i> is function
+       </blockquote>
+       
+       <p>it is missing the word <q>a</q> and should read</p>
+       
+       <blockquote>
+         The <i>handler</i> is a function
+       </blockquote>
       </li>
 
       <li>p. 400, the text <q><tt>(</tt> <i>test</i> <tt>)</tt></q> should not 
be in
-- 
Gd-chatter mailing list
Gd-chatter@xxxxxxxxxxxxxxxx
https://gauss.gwydiondylan.org/mailman/listinfo/gd-chatter



<Prev in Thread] Current Thread [Next in Thread>