Author: cpage
Date: Thu Dec 22 11:07:08 2005
New Revision: 10431
Modified:
trunk/www/books/drm/Built-In_Macros_and_Special_Definitions_Overview.html
trunk/www/books/drm/Classes.html
trunk/www/books/drm/Collection_Operations.html
trunk/www/books/drm/Collections_Overview.html
trunk/www/books/drm/Constructing_and_Initializing_Instances.html
trunk/www/books/drm/Definition_Macros.html
trunk/www/books/drm/Exception_Handling.html
trunk/www/books/drm/Function_Classes.html
trunk/www/books/drm/Functions_Overview.html
trunk/www/books/drm/Glossary.html
trunk/www/books/drm/Introspective_Operations_on_Conditions.html
trunk/www/books/drm/Lexical_Syntax.html
trunk/www/books/drm/Limited_Types.html
trunk/www/books/drm/Local_Declaration_Macros.html
trunk/www/books/drm/Operations_on_Functions.html
trunk/www/books/drm/Operators.html
trunk/www/books/drm/Parameter_Lists.html
trunk/www/books/drm/Parameter_Lists_Syntax.html
trunk/www/books/drm/Patterns.html
trunk/www/books/drm/Reflective_Operations_on_Types.html
trunk/www/books/drm/Slots.html
trunk/www/books/drm/Statement_Macros.html
trunk/www/books/drm/Templates.html
trunk/www/books/drm/Type_Protocol.html
Log:
Job: website
Replaced ASCII quotes with Q quote tags.
Modified:
trunk/www/books/drm/Built-In_Macros_and_Special_Definitions_Overview.html
==============================================================================
--- trunk/www/books/drm/Built-In_Macros_and_Special_Definitions_Overview.html
(original)
+++ trunk/www/books/drm/Built-In_Macros_and_Special_Definitions_Overview.html
Thu Dec 22 11:07:08 2005
@@ -124,7 +124,7 @@
<p>This chapter contains descriptions of the built-in macros and special
definitions defined
by Dylan.</p>
<p>The syntax used in this chapter is described
- in <a href="Manual_Notation#MARKER-9-173">"Manual Notation" on page
6</a>.</p>
+ in <a href="Manual_Notation#MARKER-9-173"><q>Manual Notation</q> on
page 6</a>.</p>
</div>
Modified: trunk/www/books/drm/Classes.html
==============================================================================
--- trunk/www/books/drm/Classes.html (original)
+++ trunk/www/books/drm/Classes.html Thu Dec 22 11:07:08 2005
@@ -157,13 +157,13 @@
<li>A class can be <dfn id="MARKER-2-572">primary</dfn>
or <dfn id="MARKER-2-573">free</dfn>. This controls how a class can
be used for multiple
inheritance. For a full description of this feature,
- see <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106">"Declaring
- Characteristics of Classes" on page 134</a>.</li>
+ see <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106"><q>Declaring
+ Characteristics of Classes</q> on page 134</a>.</li>
<li>A class can be <dfn id="MARKER-2-574">sealed</dfn>
or <dfn id="MARKER-2-575">open</dfn>. This controls whether a class
can be subclassed
outside the library where it is defined. For a full description of
this feature,
- see <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106">"Declaring
- Characteristics of Classes" on page 134</a>.<a
name="MARKER-2-576"></a></li>
+ see <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106"><q>Declaring
+ Characteristics of Classes</q> on page 134</a>.<a
name="MARKER-2-576"></a></li>
</ul>
<a name="HEADING41-11"></a>
<a name="UID-Types_and_Classes-2532"></a>
@@ -228,7 +228,7 @@
lists, either <var>A</var> precedes <var>B</var> in both or <var>B</var>
precedes <var>A</var> in both.) The class precedence list is used in
determining the order
of specificity of methods based on the types they are specialized on
when dispatching; for
- details, see <a href="Method_Dispatch#MARKER-9-844">"Method Dispatch"
on page 95</a>.</p>
+ details, see <a href="Method_Dispatch#MARKER-9-844"><q>Method
Dispatch</q> on page 95</a>.</p>
<p>Sometimes there are several such consistent total orderings on
<var>C</var> and its
superclasses. Dylan uses a deterministic algorithm to compute the class
precedence list, which
chooses one of the consistent total orderings.</p>
Modified: trunk/www/books/drm/Collection_Operations.html
==============================================================================
--- trunk/www/books/drm/Collection_Operations.html (original)
+++ trunk/www/books/drm/Collection_Operations.html Thu Dec 22 11:07:08 2005
@@ -2941,9 +2941,9 @@
sequences, processing is done in the natural order.</p>
<p>When <var>mutable-collection</var> is an instance
of <code><stretchy-collection></code>, the usual alignment
requirement (described
- in <a href="Collection_Alignment#MARKER-9-1021">"Collection
Alignment" on page 120</a>)
- is relaxed. In this case, the key sequence of
<var>mutable-collection</var> is not
- considered during alignment. Rather, only the key sequences for the
+ in <a href="Collection_Alignment#MARKER-9-1021"><q>Collection
Alignment</q> on page
+ 120</a>) is relaxed. In this case, the key sequence of
<var>mutable-collection</var> is
+ not considered during alignment. Rather, only the key sequences for
the
source <var>collections</var> are aligned, with <var>function</var>
called on the
corresponding elements. The result of each call to
<var>function</var> is then stored
into <var>mutable-collection</var> with the corresponding key
(possibly
@@ -3692,11 +3692,12 @@
using the function <code>table-protocol</code>. Every concrete subclass
of <code><table></code> must provide or inherit a method
for <code>table-protocol</code>. A complete description of the table
protocol is given
- in <a href="Tables#MARKER-9-1036">"Tables" on page 122</a>.</p>
+ in <a href="Tables#MARKER-9-1036"><q>Tables</q> on page 122</a>.</p>
<a name="HEADING102-721"></a>
<h4 class="item-title"><span class="signature"><code
id="MARKER-2-1851">table-protocol</code> </span><span
class="attributes-summary">[Open Generic Function]</span></h4>
<hr class="item-title" />
- <p class="short-description"><a name="MARKER-9-1852"></a>Returns
functions used to implement the iteration protocol for tables.</p>
+ <p class="short-description"><a name="MARKER-9-1852"></a>Returns
functions used to implement
+ the iteration protocol for tables.</p>
<dl class="Cliche">
<dt><span>Signature:</span></dt>
<dd>
Modified: trunk/www/books/drm/Collections_Overview.html
==============================================================================
--- trunk/www/books/drm/Collections_Overview.html (original)
+++ trunk/www/books/drm/Collections_Overview.html Thu Dec 22 11:07:08 2005
@@ -142,11 +142,11 @@
successive non-negative integers as keys; <dfn
id="MARKER-2-991">explicit key
collections</dfn> may use any object as a key. Both of these classes
have predefined
subclasses and may be additionally subclassed by
- programmers. See <a
href="Collection_Classes#MARKER-9-1398">"Collections" on page 206</a>
- for a complete description of these classes.</p>
+ programmers. See <a
href="Collection_Classes#MARKER-9-1398"><q>Collections</q> on page
+ 206</a> for a complete description of these classes.</p>
<p>A large number of functions are available on collections, including
functions for
iteration, mapping, random access of elements, sorting, filtering,
- etc. See <a href="Collection_Operations#MARKER-9-1696">"Collection
Operations" on page
+ etc. See <a href="Collection_Operations#MARKER-9-1696"><q>Collection
Operations</q> on page
294</a> for a complete description of these functions.</p>
<a name="HEADING60-4"></a>
<a name="UID-Collections-6197"></a>
@@ -167,8 +167,8 @@
progress may cause the iteration to produce unpredictable results.</p>
<p>With notable exceptions, two or more iterations over the same
collection are not guaranteed
to produce the same values in the same order, even if the collection is
unaltered. For
- details, see <a
href="Iteration_Stability_and_Natural_Order#MARKER-9-1001">"Iteration
- Stability and Natural Order"</a> as follows.</p>
+ details, see <a
href="Iteration_Stability_and_Natural_Order#MARKER-9-1001"><q>Iteration
+ Stability and Natural Order</q></a> as follows.</p>
<p>The built-in collection functions are implemented in terms of the
iteration protocol. When
defining a new collection class, a programmer need only define the
iteration protocol for
the class. Once this is done, instances of the class can be used with
all the built-in
Modified: trunk/www/books/drm/Constructing_and_Initializing_Instances.html
==============================================================================
--- trunk/www/books/drm/Constructing_and_Initializing_Instances.html
(original)
+++ trunk/www/books/drm/Constructing_and_Initializing_Instances.html Thu Dec
22 11:07:08 2005
@@ -189,8 +189,8 @@
<p>Instance creation and initialization is performed by the open generic
functions <code>make</code> and <code>initialize</code>. For an
overview of the allocation
and initialization process,
- see <a
href="Instance_Creation_and_Initialization#MARKER-9-658">"Instance Creation and
- Initialization" beginning on page 64</a>.</p>
+ see <a
href="Instance_Creation_and_Initialization#MARKER-9-658"><q>Instance Creation
and
+ Initialization</q> beginning on page 64</a>.</p>
<a name="HEADING98-2"></a>
<a name="UID-Built-In_Functions-32090"></a>
<h2 class="subsection-title"><a name="MARKER-2-1536"></a><a
name="MARKER-2-1537"></a>General Constructor</h2>
@@ -248,8 +248,8 @@
calls <code>initialize</code> on the instance, and then returns the
instance. An error
is signaled if <var>class</var> is abstract.</p>
<p>A complete description of this method and its role in the
initialization protocol is
- given in <a
href="Instance_Creation_and_Initialization#MARKER-9-658">"Instance Creation
- and Initialization" on page 64</a>.</p>
+ given in <a
href="Instance_Creation_and_Initialization#MARKER-9-658"><q>Instance
+ Creation and Initialization</q> on page 64</a>.</p>
<a name="HEADING98-17"></a>
<h5 class="method-signature"><span class="signature"><code>make
<em>(singleton (<array>))</em><br /> #key <var>dimensions fill</var>
</code>⇒<code> <var>array</var></code> </span><span
class="attributes-summary">[Sealed G.F. Method]</span></h5>
<p class="short-description">The method on
<code>singleton(<array>)</code>
@@ -709,8 +709,8 @@
<dd>
<p>Returns a type whose instances are the instances of
<var>type1</var> and all
the <var>more-types</var>. The type returned is not instantiable. A
complete description
- of union types is given in <a
href="Union_Types#MARKER-9-701">"Union Types" on page
- 72</a>.</p>
+ of union types is given in <a
href="Union_Types#MARKER-9-701"><q>Union Types</q> on page
+ 72</a>.</p>
<pre class="code">
define constant $my-enumerated-type =
type-union(singleton(#"one"),
Modified: trunk/www/books/drm/Definition_Macros.html
==============================================================================
--- trunk/www/books/drm/Definition_Macros.html (original)
+++ trunk/www/books/drm/Definition_Macros.html Thu Dec 22 11:07:08 2005
@@ -347,14 +347,15 @@
the <var>adjectives</var>, <var>parameter-list</var> and
<var>options</var>.</p>
<p>The <var>adjectives</var> specify whether the generic function is
sealed. A complete
description of generic function sealing is given
- in <a
href="Declaring_Characteristics_of_Generic_Functions#MARKER-9-1116">"Declaring
- Characteristics of Generic Functions" on page 135</a>.</p>
+ in <a
href="Declaring_Characteristics_of_Generic_Functions#MARKER-9-1116"><q>Declaring
+ Characteristics of Generic Functions</q> on page 135</a>.</p>
<p>The <var>parameter-list</var> specifies the parameters and return
values of the generic
function and thereby constrains which methods may be added to it.
For a complete
- description of these constraints, see <a
href="Parameter_Lists#MARKER-9-837">"Parameter
- List Congruency" on page 93</a>. A generic function parameter list
may not include a
- next-method parameter, and its keyword parameters may include
neither type specializers
- nor default initial values.</p>
+ description of these constraints,
+ see <a href="Parameter_Lists#MARKER-9-837"><q>Parameter List
Congruency</q> on page
+ 93</a>. A generic function parameter list may not include a
next-method parameter, and
+ its keyword parameters may include neither type specializers nor
default initial
+ values.</p>
<p>The <var>options </var>are alternating keywords and values. No
options are defined by
the language. They may be supplied by individual
implementations.</p>
<p>The following example defines a generic function of two required
arguments and one
@@ -433,15 +434,15 @@
method</code> will create a new generic function or extend an old
one, as needed.</p>
<p>The <var>adjective</var> allows a sealing declaration to be made
about the generic
function to which the method is added. The effect of this adjective
is described
- in <a href="Define_Sealed_Domain#MARKER-9-1131">"Abbreviations for
Define Sealed Domain"
- on page 138</a>.</p>
+ in <a href="Define_Sealed_Domain#MARKER-9-1131"><q>Abbreviations
for Define Sealed
+ Domain</q> on page 138</a>.</p>
<p>The <var>parameter-list</var> describes the parameters and return
values of the method,
including their number and type. The method can be called only with
arguments that match
the types of the parameters, and the method will always return
values in the quantity
and typed declared. Methods added to a generic function must have
parameter lists that
are congruent with the generic function's parameter list. A
complete description of
- parameter lists is given in <a
href="Parameter_Lists#MARKER-9-782">"Parameter Lists" on
- page 84</a>.</p>
+ parameter lists is given in <a
href="Parameter_Lists#MARKER-9-782"><q>Parameter
+ Lists</q> on page 84</a>.</p>
<p>When the method is called, new local bindings are created for the
parameters,
initialized to the arguments of the call. The <var>body</var> is
then executed in the
environment containing these bindings.</p>
@@ -546,29 +547,29 @@
exclusive, <code>primary</code> and <code>free</code> are mutually
exclusive,
and <code>sealed</code> and <code>open</code> are mutually
exclusive. Additional
implementation-defined adjectives may be
- supported. See <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106">"Declaring
- Characteristics of Classes" on page 134</a> for a complete
description of these
+ supported. See <a
href="Declaring_Characteristics_of_Classes#MARKER-9-1106"><q>Declaring
+ Characteristics of Classes</q> on page 134</a> for a complete
description of these
adjectives.</p>
<p>The <var>superclasses</var> are the classes from which the new
class directly
inherits. The rules of inheritance are described
- in <a href="Classes#MARKER-9-583">"Class Inheritance" on page 53</a>
- and <a href="Classes#MARKER-9-590">"Computing the Class Precedence
List" on page
- 54</a>.</p>
+ in <a href="Classes#MARKER-9-583"><q>Class Inheritance</q> on page
53</a>
+ and <a href="Classes#MARKER-9-590"><q>Computing the Class
Precedence List</q> on page
+ 54</a>.</p>
<p>The <var>init-expression</var>,
<var>required-init-keyword-option</var>, <var>init-value-option</var>,
and <var>init-function-option</var> are all mutually exclusive in a
single <var>slot-spec</var>, <var>init-arg-spec</var>,
or <var>inherited-slot-spec</var>.</p>
<p>Each <var>slot-spec</var> describes a slot specification in the
class. Slot
- specifications are described in <a href="Slots#MARKER-9-610">"Slot
Specifications" on
- page 58</a></p>
+ specifications are described in <a
href="Slots#MARKER-9-610"><q>Slot Specifications</q>
+ on page 58</a></p>
<p>Each <var>init-arg-spec</var> describes the handling of an
initialization argument
specification of the class. Initialization argument specifications
are described
- in <a
href="Instance_Creation_and_Initialization#MARKER-9-680">"Initialization
Argument
- Specifications" on page 68</a>.</p>
+ in <a
href="Instance_Creation_and_Initialization#MARKER-9-680"><q>Initialization
+ Argument Specifications</q> on page 68</a>.</p>
<p>Each <var>inherited-slot-spec</var> describes an inherited slot
specification of the
class. Inherited slot specifications are described
- in <a
href="Instance_Creation_and_Initialization#MARKER-9-677">"Inherited Slot
- Specifications" on page 67</a>.</p></dd>
+ in <a
href="Instance_Creation_and_Initialization#MARKER-9-677"><q>Inherited Slot
+ Specifications</q> on page 67</a>.</p></dd>
</dl>
<a name="HEADING112-240"></a>
<h4 class="item-title"><span class="signature"><code
id="MARKER-2-2015">define module</code> </span><span
class="attributes-summary">[Definition]</span></h4>
@@ -924,8 +925,8 @@
the domain indicated by the <var>types</var>. For a complete
description of the rules
governing <code>define sealed domain</code> and the implications of
a <code>define
sealed domain</code> definition,
- see <a href="Define_Sealed_Domain#MARKER-9-1123">"Define Sealed
Domain" on page
- 135</a>.</p>
+ see <a href="Define_Sealed_Domain#MARKER-9-1123"><q>Define Sealed
Domain</q> on page
+ 135</a>.</p>
<ul>
<li><var>generic-function</var> is the name of a module binding
containing an explicitly
defined generic function.</li>
Modified: trunk/www/books/drm/Exception_Handling.html
==============================================================================
--- trunk/www/books/drm/Exception_Handling.html (original)
+++ trunk/www/books/drm/Exception_Handling.html Thu Dec 22 11:07:08 2005
@@ -131,9 +131,9 @@
<h1 class="section-title">Exception Handling</h1>
<p>A set of classes, functions, and associated conventions extend the
underlying condition
handling capabilities to provide a complete exception handling
facility.</p>
- <p>The classes are described in <a
href="Condition_Classes#MARKER-9-1472">"Conditions" on page
- 244</a>, and the functions are described
- in <a href="Operations_on_Conditions#MARKER-9-1917">"Signaling
Conditions" on page
+ <p>The classes are described in <a
href="Condition_Classes#MARKER-9-1472"><q>Conditions</q> on
+ page 244</a>, and the functions are described
+ in <a href="Operations_on_Conditions#MARKER-9-1917">"Signaling
Conditions" on page
357</a>.</p>
<a name="HEADING56-3"></a>
<a name="UID-Conditions-2155"></a>
Modified: trunk/www/books/drm/Function_Classes.html
==============================================================================
--- trunk/www/books/drm/Function_Classes.html (original)
+++ trunk/www/books/drm/Function_Classes.html Thu Dec 22 11:07:08 2005
@@ -323,9 +323,9 @@
in <a href="Functions">Chapter 6, <q>Functions.</q></a></p>
<p>The arguments describe the shape of the generic function's
parameter list, and thereby
control which methods can be added to the generic function. See the
- section <a href="Parameter_Lists#MARKER-9-800">"Kinds of Parameter
Lists" on page 86</a>
- and the section <a href="Parameter_Lists#MARKER-9-837">"Parameter
List Congruency" on
- page 93</a> for the implications of these choices.</p>
+ section <a href="Parameter_Lists#MARKER-9-800"><q>Kinds of
Parameter Lists</q> on page
+ 86</a> and the section <a
href="Parameter_Lists#MARKER-9-837"><q>Parameter List
+ Congruency</q> on page 93</a> for the implications of these
choices.</p>
<p>An error is signaled if the value of <code>rest?:</code> is true
and the value
of <code>key:</code> is a collection. While a method parameter list
may specify
both <code>#rest</code> and <code>#key</code>, a generic function
parameter list
Modified: trunk/www/books/drm/Functions_Overview.html
==============================================================================
--- trunk/www/books/drm/Functions_Overview.html (original)
+++ trunk/www/books/drm/Functions_Overview.html Thu Dec 22 11:07:08 2005
@@ -178,8 +178,8 @@
</pre>
<p>Generic functions created with <code>define generic</code> may be
sealed or open. For
details of this option,
- see <a
href="Declaring_Characteristics_of_Generic_Functions#MARKER-9-1116">"Declaring
- Characteristics of Generic Functions" on page 135</a>.<a
name="MARKER-2-761"></a></p>
+ see <a
href="Declaring_Characteristics_of_Generic_Functions#MARKER-9-1116"><q>Declaring
+ Characteristics of Generic Functions</q> on page 135</a>.<a
name="MARKER-2-761"></a></p>
<a name="HEADING48-17"></a>
<a name="UID-Functions-2162"></a>
<h2 class="subsection-title"><a name="MARKER-9-762"></a>Methods</h2>
@@ -197,7 +197,7 @@
its parameter list. The specializers in the parameter list declare the
types of the
arguments acceptable to the method. The method can be called only with
arguments that match
the specializers of the parameters. A complete description of parameter
lists is given
- in <a href="Parameter_Lists#MARKER-9-782">"Parameter Lists" on page
84</a>.</p>
+ in <a href="Parameter_Lists#MARKER-9-782"><q>Parameter Lists</q> on
page 84</a>.</p>
<p>When the method is invoked, it executes its implicit body. Statements
in the implicit body
are executed in order, in an environment that contains the parameters
bound to the
arguments.</p>
@@ -221,8 +221,8 @@
</pre>
<p><code>define method</code> allows the programmer to control aspects
of the sealing of the
generic function to which the method is added. For more details,
- see <a href="Define_Sealed_Domain#MARKER-9-1131">"Abbreviations for
Define Sealed Domain" on
- page 138</a>.</p>
+ see <a href="Define_Sealed_Domain#MARKER-9-1131"><q>Abbreviations for
Define Sealed
+ Domain</q> on page 138</a>.</p>
<p><a name="MARKER-2-769"></a>A generic function with no required
parameters can contain a
single method. Adding a new method has the effect of replacing the
existing method.</p>
<p>The complete syntax of <code>define method</code> is given
Modified: trunk/www/books/drm/Glossary.html
==============================================================================
--- trunk/www/books/drm/Glossary.html (original)
+++ trunk/www/books/drm/Glossary.html Thu Dec 22 11:07:08 2005
@@ -215,8 +215,8 @@
<dd>(of a class) A total ordering on the class and its superclasses
that is consistent with
the local precedence orders for the class and each of its
superclasses. The class
precedence list is used in determining method
- specificity. See <a href="Classes#MARKER-9-590">"Computing the Class
Precedence List" on
- page 54</a>.</dd>
+ specificity. See <a href="Classes#MARKER-9-590"><q>Computing the
Class Precedence List</q>
+ on page 54</a>.</dd>
<dt><strong>cleanup clause</strong></dt>
<dd>A clause in a <code>block</code> statement that is guaranteed to be
executed, even if
the execution of the <code>block</code> statement is terminated by
@@ -257,8 +257,8 @@
<dt><strong>congruent</strong></dt>
<dd>(two or more ~ parameter lists) Having compatible parameters. The
parameter lists of a
generic function and its methods must be
- congruent. See <a href="Parameter_Lists#MARKER-9-837">"Parameter List
Congruency" on page
- 93</a>.</dd>
+ congruent. See <a href="Parameter_Lists#MARKER-9-837"><q>Parameter
List Congruency</q> on
+ page 93</a>.</dd>
<dt><strong>constant</strong></dt>
<dd>1. A <a href="#MARKER-9-2159"><strong>constant
binding</strong></a>. 2. A <a
href="#MARKER-9-2212"><strong>literal
@@ -289,8 +289,8 @@
sequence consists of the <a href="#MARKER-9-2244"><strong>supplied
initialization
arguments</strong></a> augmented by any additional initialization
arguments for which
default values are defined by the class or any of its superclasses.
See
- also <a
href="Instance_Creation_and_Initialization#MARKER-9-658">"Instance Creation and
- Initialization" on page 64</a>.</dd>
+ also <a
href="Instance_Creation_and_Initialization#MARKER-9-658"><q>Instance Creation
and
+ Initialization</q> on page 64</a>.</dd>
<dt><strong>definition</strong></dt>
<dd>A syntax form that denotes a declarative part of a program.
Definitions are restricted
to be top level expressions, and do not return values.</dd>
@@ -313,7 +313,7 @@
<dt><strong>disjoint</strong></dt>
<dd>(of types): Informally, two types are disjoint if there can be no
object that is an
instance of both types. A formal definition is given
- in <a href="Type_Protocol#MARKER-9-553">"Type Disjointness" on page
51</a>.</dd>
+ in <a href="Type_Protocol#MARKER-9-553"><q>Type Disjointness</q> on
page 51</a>.</dd>
<dt><strong><a name="MARKER-9-2167"></a>dotted list</strong></dt>
<dd>A list that has something other than the <a
href="#MARKER-9-2170"><strong>empty
list</strong></a> as the tail of its last
@@ -332,7 +332,7 @@
<dd>(of a collection) A specification of
the <a
href="#MARKER-9-2246"><strong>type</strong></a><strong>s</strong> of objects
which
may be stored in the collection, as described
- in <a href="Element_Types#MARKER-9-1051">"Element Types" on page
124</a>.</dd>
+ in <a href="Element_Types#MARKER-9-1051"><q>Element Types</q> on page
124</a>.</dd>
<dt><strong><a name="MARKER-9-2170"></a>empty list</strong></dt>
<dd>The list that contains no elements. It is the unique instance of the
class <code><empty-list></code>.</dd>
@@ -351,7 +351,7 @@
<dd>A boolean function of two arguments that returns true if and only
if the arguments are
<q>the same</q> according to some specified criteria. For a function
to be used as an
equivalence predicate, it must be reflexive, commutative, and
transitive. See
- also <a href="Tables#MARKER-9-1036">"Tables" on page 122</a>
+ also <a href="Tables#MARKER-9-1036"><q>Tables</q> on page 122</a>
and <a href="#MARKER-9-2192"><strong>hash function</strong></a>.</dd>
<dt><strong><a name="MARKER-9-2172"></a>equivalent types</strong></dt>
<dd>Two types, each of which is a subtype of the other.</dd>
@@ -423,16 +423,19 @@
<dt><strong><a name="MARKER-9-2179"></a>format arguments</strong></dt>
<dd>A series of objects that are used to construct a message from
a <a href="#MARKER-9-2180"><strong>format string</strong></a>, as
described
- in <a href="Condition_Messages#MARKER-9-951">"Condition Messages" on
page 112</a>.</dd>
+ in <a href="Condition_Messages#MARKER-9-951"><q>Condition
Messages</q> on page
+ 112</a>.</dd>
<dt><strong>format directives</strong></dt>
<dd>Two-character sequences in a <a
href="#MARKER-9-2180"><strong>format string</strong></a>
which are replaced with representations of the <a
href="#MARKER-9-2179"><strong>format
arguments</strong></a> to construct the format message, as described
- in <a href="Condition_Messages#MARKER-9-951">"Condition Messages" on
page 112</a>.</dd>
+ in <a href="Condition_Messages#MARKER-9-951"><q>Condition
Messages</q> on page
+ 112</a>.</dd>
<dt><strong><a name="MARKER-9-2180"></a>format string</strong></dt>
<dd>A string template into which values can be inserted to construct a
message. Format
strings are used by the condition system, as described
- in <a href="Condition_Messages#MARKER-9-951">"Condition Messages" on
page 112</a>.</dd>
+ in <a href="Condition_Messages#MARKER-9-951"><q>Condition
Messages</q> on page
+ 112</a>.</dd>
<dt><strong><a name="MARKER-9-2181"></a>free class</strong></dt>
<dd>A class that may be used freely in multiple inheritance. The
opposite of a free class is
a <a href="#MARKER-9-2228"><strong>primary class</strong></a>.</dd>
@@ -510,7 +513,7 @@
<dt><strong>hygiene</strong></dt>
<dd>The property that each named value reference in a macro expansion
means the same thing
as it meant at the place in the original source code from which it
was copied into the
- macro expansion. See <a href="Hygiene#MARKER-9-1268">"Hygiene" on
page 161</a>.</dd>
+ macro expansion. See <a href="Hygiene#MARKER-9-1268"><q>Hygiene</q>
on page 161</a>.</dd>
<dt><strong>identical</strong></dt>
<dd>(of two objects) Computationally equivalent. That is, there is no
way for any portable
Dylan program to distinguish them; they are the same under
@@ -590,8 +593,8 @@
a <a href="#MARKER-9-2209"><strong>keyword initializable</strong></a>
slot.</dd>
<dt><strong>initialization protocol</strong></dt>
<dd>The protocol by which newly allocated instances are made ready for
use, as described
- in <a
href="Instance_Creation_and_Initialization#MARKER-9-658">"Instance Creation and
- Initialization" on page 64</a>.</dd>
+ in <a
href="Instance_Creation_and_Initialization#MARKER-9-658"><q>Instance Creation
and
+ Initialization</q> on page 64</a>.</dd>
<dt><strong>initialize</strong></dt>
<dd>1. (an object) To prepare an object for use, by initializing its
slots and calling the
initialize function on the object. All Dylan objects are
automatically initialized
@@ -622,8 +625,8 @@
<dd>An object used to indicate a particular element of a
collection.</dd>
<dt><strong>key test</strong></dt>
<dd>The test used to determine whether a given object matches a key in a
- collection. See <a href="Collection_Keys#MARKER-9-996">"Collection
Keys" on page
- 118</a>.</dd>
+ collection. See <a href="Collection_Keys#MARKER-9-996"><q>Collection
Keys</q> on page
+ 118</a>.</dd>
<dt><strong><a name="MARKER-9-2208"></a>keyword</strong></dt>
<dd>A symbol literal, represented in source code as a name followed by
a colon. Keywords are
used as program constants, and for naming keyword arguments in
function calls.</dd>
@@ -653,7 +656,7 @@
<dd>(~ type) A type used to indicate objects that are instances of
another type and have
additional constraints. There are several kinds of limited types. (~
collection) A limited
collection type. (~ integer) A limited integer
- type. See <a href="Limited_Types#MARKER-9-707">"Limited Types" on
page 73</a> for a
+ type. See <a href="Limited_Types#MARKER-9-707"><q>Limited Types</q>
on page 73</a> for a
complete description of limited types.</dd>
<dt><strong><a name="MARKER-9-2212"></a>literal constant</strong></dt>
<dd>An object that is specified explicitly in program text. Literal
constants are
@@ -666,9 +669,9 @@
bindings.</dd>
<dt><strong>local precedence order</strong></dt>
<dd>The ordering of a class and its direct superclasses specified by
the class
- definition. See also <a href="Classes#MARKER-9-590">"Computing the
Class Precedence List"
- on page 54</a> and <a href="#MARKER-9-2153"><strong>class precedence
- list</strong></a>.</dd>
+ definition. See also <a href="Classes#MARKER-9-590"><q>Computing the
Class Precedence
+ List</q> on page 54</a> and <a
href="#MARKER-9-2153"><strong>class precedence
+ list</strong></a>.</dd>
<dt><strong>macro</strong></dt>
<dd>An extension to the core language that can be defined by the user,
by the
implementation, or as part of the Dylan language specification. Much
of the grammatical
@@ -811,16 +814,16 @@
class</strong></a>.</dd>
<dt><strong>sealed domain</strong></dt>
<dd>A portion of a generic function and a portion of the class
hierarchy which are declared
- to be invariant. See <a
href="Define_Sealed_Domain#MARKER-9-1123">"Define Sealed Domain"
- on page 135</a> for a complete description of sealed domains.</dd>
+ to be invariant. See <a
href="Define_Sealed_Domain#MARKER-9-1123"><q>Define Sealed
+ Domain</q> on page 135</a> for a complete description of sealed
domains.</dd>
<dt><strong><a name="MARKER-9-2234"></a>sealed generic
function</strong></dt>
<dd>A generic function that cannot have methods that are not explicitly
defined in the same
library. The opposite of a sealed generic function is
an <a href="#MARKER-9-2224"><strong>open generic
function</strong></a>.</dd>
<dt><strong>sealing directive</strong></dt>
<dd>A definition or adjective within a definition that specifies a
sealing-related
- characteristic of the object being defined. See <a
href="Sealing#MARKER-9-1094">"Sealing"
- on page 133</a>.</dd>
+ characteristic of the object being
+ defined. See <a href="Sealing#MARKER-9-1094"><q>Sealing</q> on page
133</a>.</dd>
<dt><strong><a name="MARKER-9-2235"></a>sequence</strong></dt>
<dd>An instance of <code><sequence></code>, a type of collection
which uses successive
nonnegative integers as keys.</dd>
@@ -878,9 +881,9 @@
<dd>A collection that may grow or shrink to accommodate adding or
removing elements.</dd>
<dt><strong><a name="MARKER-9-2244"></a>supplied initialization
arguments</strong></dt>
<dd>The keyword arguments values supplied in a call to
<code>make</code>. See
- also <a
href="Instance_Creation_and_Initialization#MARKER-9-658">"Instance Creation and
- Initialization" on page 64</a> and <a
href="#MARKER-9-2163"><strong>defaulted
- initialization arguments</strong></a>.</dd>
+ also <a
href="Instance_Creation_and_Initialization#MARKER-9-658"><q>Instance Creation
and
+ Initialization</q> on page 64</a> and <a
href="#MARKER-9-2163"><strong>defaulted
+ initialization arguments</strong></a>.</dd>
<dt><strong><a name="MARKER-9-2245"></a>table</strong></dt>
<dd>An object, also known as a hash table, that maps arbitrary keys to
objects. Each table
has an associated <a href="#MARKER-9-2171"><strong>equivalence
predicate</strong></a> that
@@ -926,7 +929,7 @@
A modification that changes the equivalence class of the object. The
modifications that
are visible to an <a href="#MARKER-9-2171"><strong>equivalence
predicate</strong></a> are
determined by the definition of the predicate. See
- also <a href="Tables#MARKER-9-1036">"Tables" on page 122</a>.</dd>
+ also <a href="Tables#MARKER-9-1036"><q>Tables</q> on page
122</a>.</dd>
<dt><strong>whitespace</strong></dt>
<dd>Any number of contiguous space, tab, newline, and newpage
characters. Except within
string literals, the amount of contiguous whitespace is not
significant in program code.
Modified: trunk/www/books/drm/Introspective_Operations_on_Conditions.html
==============================================================================
--- trunk/www/books/drm/Introspective_Operations_on_Conditions.html
(original)
+++ trunk/www/books/drm/Introspective_Operations_on_Conditions.html Thu Dec
22 11:07:08 2005
@@ -129,8 +129,8 @@
error-recovery system to discover what restart handlers are available
before signaling a
restart.</p>
<p>Additional operations support introspection on
- conditions. See <a
href="Operations_on_Conditions#MARKER-9-1934">"Introspection on
- Conditions" on page 362</a> for a complete description of these
introspective
+ conditions. See <a
href="Operations_on_Conditions#MARKER-9-1934"><q>Introspection on
+ Conditions</q> on page 362</a> for a complete description of these
introspective
functions.<a name="MARKER-2-959"></a></p>
<a name="LINK-Conditions-lastpage"></a><a
name="LINK-CollectionsTOC-firstpage"></a><a name="UID-CollectionsTOC-615"></a>
<a name="LINK-CollectionsTOC-lastpage"></a>
Modified: trunk/www/books/drm/Lexical_Syntax.html
==============================================================================
--- trunk/www/books/drm/Lexical_Syntax.html (original)
+++ trunk/www/books/drm/Lexical_Syntax.html Thu Dec 22 11:07:08 2005
@@ -204,8 +204,8 @@
<p>A <dfn id="MARKER-2-294">number</dfn> is a decimal integer with an
optional leading sign, a
binary integer, an octal integer, a hexadecimal integer, a ratio of two
decimal integers
with an optional leading sign, or a floating-point number. The complete
syntax of numbers is
- given in <a href="Lexical_Grammar#MARKER-9-2105">"Numbers" on page
418</a>. Note that the
- ratios are not included in the Dylan language. The ratio syntax is
reserved for future
+ given in <a href="Lexical_Grammar#MARKER-9-2105"><q>Numbers</q> on page
418</a>. Note that
+ the ratios are not included in the Dylan language. The ratio syntax is
reserved for future
expansion and for implementation-specific extensions.</p>
<p>A <dfn id="MARKER-2-295">character literal</dfn> is a printing
character (including space,
but not <code>'</code> or <code>\</code>) or a backslash escape
sequence enclosed in a pair
Modified: trunk/www/books/drm/Limited_Types.html
==============================================================================
--- trunk/www/books/drm/Limited_Types.html (original)
+++ trunk/www/books/drm/Limited_Types.html Thu Dec 22 11:07:08 2005
@@ -201,8 +201,8 @@
of <code><collection></code>) that are constrained to be a
specified size and/or to
contain elements of a specified type.</p>
<p>A complete description of limited collection types is given
- in <a href="Limited_Collection_Types#MARKER-9-1060">"Limited Collection
Types" on page 126</a>
- in <a href="Collections">Chapter
+ in <a href="Limited_Collection_Types#MARKER-9-1060"><q>Limited
Collection Types</q> on page
+ 126</a> in <a href="Collections">Chapter
8, <q>Collections.</q></a><a name="MARKER-2-718"></a><a
name="MARKER-2-719"></a></p>
<a name="LINK-Types_and_Classes-lastpage"></a><a
name="LINK-FunctionsTOC-firstpage"></a><a name="UID-FunctionsTOC-557"></a>
<a name="LINK-FunctionsTOC-lastpage"></a>
Modified: trunk/www/books/drm/Local_Declaration_Macros.html
==============================================================================
--- trunk/www/books/drm/Local_Declaration_Macros.html (original)
+++ trunk/www/books/drm/Local_Declaration_Macros.html Thu Dec 22 11:07:08 2005
@@ -225,7 +225,7 @@
declaration.</p>
<p>The <var>parameter-list</var> is a standard method parameter list.
A complete
description of parameter lists is given
- in <a href="Parameter_Lists#MARKER-9-782">"Parameter Lists" on page
84</a>.</p>
+ in <a href="Parameter_Lists#MARKER-9-782"><q>Parameter Lists</q> on
page 84</a>.</p>
<p>The <var>body</var> is an implicit body.</p></dd>
</dl>
<a name="HEADING113-89"></a>
Modified: trunk/www/books/drm/Operations_on_Functions.html
==============================================================================
--- trunk/www/books/drm/Operations_on_Functions.html (original)
+++ trunk/www/books/drm/Operations_on_Functions.html Thu Dec 22 11:07:08 2005
@@ -126,11 +126,12 @@
<ul>
<li>Introspective functions take a function as an argument and return
information about
it. These are described
- in <a
href="Reflective_Operations_on_Functions#MARKER-9-1892">"Reflective Operations
on
- Functions" on page 351</a>.</li>
+ in <a
href="Reflective_Operations_on_Functions#MARKER-9-1892"><q>Reflective
Operations on
+ Functions</q> on page 351</a>.</li>
<li>Higher order functions take one or more functions as arguments and
return a new
- function. These are described in <a
href="Functional_Operations#MARKER-9-1873">"Functional
- Operations" on page 346</a>.<a name="MARKER-2-865"></a>
+ function. These are described
+ in <a href="Functional_Operations#MARKER-9-1873"><q>Functional
Operations</q> on page
+ 346</a>.<a name="MARKER-2-865"></a>
<a name="LINK-Functions-lastpage"></a><a
name="LINK-ConditionsTOC-firstpage"></a></li></ul>
<a name="UID-ConditionsTOC-446"></a>
<a name="LINK-ConditionsTOC-lastpage"></a>
Modified: trunk/www/books/drm/Operators.html
==============================================================================
--- trunk/www/books/drm/Operators.html (original)
+++ trunk/www/books/drm/Operators.html Thu Dec 22 11:07:08 2005
@@ -148,7 +148,7 @@
function call are executed in left to right order. The operands of a
binary operator call
which is shorthand for a function macro call are passed to the macro.
Their order of
execution depends on the definition of the macro. The built-in function
macros are described
- in <a href="Function_Macros#MARKER-9-2068">"Function Macros" on page
409</a>.</p>
+ in <a href="Function_Macros#MARKER-9-2068"><q>Function Macros</q> on
page 409</a>.</p>
<p><a name="MARKER-2-447"></a><a name="MARKER-2-448"></a>The operators
are listed
in <a href="#MARKER-9-427">Table 4-1</a> in descending order of
precedence. Operators within
a group share the same precedence. When a function call using slot
reference syntax appears
Modified: trunk/www/books/drm/Parameter_Lists.html
==============================================================================
--- trunk/www/books/drm/Parameter_Lists.html (original)
+++ trunk/www/books/drm/Parameter_Lists.html Thu Dec 22 11:07:08 2005
@@ -151,7 +151,7 @@
a <dfn id="MARKER-2-790">next-method parameter</dfn>. They also may
include <dfn id="MARKER-2-791">return value declarations</dfn>.</p>
<p>The complete syntax of parameter lists is given
- in <a href="Phrase_Grammar#MARKER-9-2115">"Methods" on page 426</a>.</p>
+ in <a href="Phrase_Grammar#MARKER-9-2115"><q>Methods</q> on page
426</a>.</p>
<p>Required parameters correspond to arguments that must be supplied
when a function is
called. The arguments are supplied in a fixed order and must appear
before any other
arguments.</p>
@@ -186,15 +186,15 @@
specified by the programmer, <code>define method</code> inserts one
with the
name <code>next-method</code>. If an explicit next-method parameter is
given, it must come
after the required parameters and before the rest and keyword
parameters. Details of using
- next-method are given in <a
href="Method_Dispatch#MARKER-9-858">"Calling Less Specific
- Methods" on page 98</a>.<a name="MARKER-2-799"></a></p>
+ next-method are given in <a
href="Method_Dispatch#MARKER-9-858"><q>Calling Less Specific
+ Methods</q> on page 98</a>.<a name="MARKER-2-799"></a></p>
<a name="HEADING49-14"></a>
<a name="UID-Functions-2273"></a>
<h2 class="subsection-title"><a name="MARKER-9-800"></a>Kinds of
Parameter Lists</h2>
<p><a name="MARKER-2-801"></a>Each function (generic function or method)
has an argument
passing protocol specified by its parameter list. The argument passing
protocol for a method
must be compatible with the argument passing protocol of any generic
function to which it is
- added, as described in <a href="#MARKER-9-837">"Parameter List
Congruency" on page
+ added, as described in <a href="#MARKER-9-837"><q>Parameter List
Congruency</q> on page
93</a>.</p>
<p>The argument passing protocol of a function can be described in one
of the following
ways:</p>
@@ -382,7 +382,7 @@
parameter list and are separated from the parameters by
<code>=></code>. For each return
value, a value declaration can specify a name and an operand or just a
name if the type
is <code><object></code>. The complete syntax of value
declarations is given
- in <a href="Phrase_Grammar#MARKER-9-2115">"Methods" on page 426</a>.</p>
+ in <a href="Phrase_Grammar#MARKER-9-2115"><q>Methods</q> on page
426</a>.</p>
<p>The result of executing the operand at the time the function is
defined is a type, called
a <dfn id="MARKER-2-832">value type</dfn>. The name never comes into
scope. It is included
for documentation and for syntactic consistency with parameters. It is
valid for the same
@@ -414,10 +414,10 @@
values are discarded and not returned.</li>
</ul>
<p><a name="MARKER-2-836"></a>Because of the parameter list congruency
rules for value
- declarations (see <a href="#MARKER-9-837">"Parameter List Congruency"
on page 93</a>) the
- values returned by a generic function do not have to be checked by the
generic function. The
- check inside a method will always be enough to verify that the return
values are valid for
- the generic function.</p>
+ declarations (see <a href="#MARKER-9-837"><q>Parameter List
Congruency</q> on page 93</a>)
+ the values returned by a generic function do not have to be checked by
the generic
+ function. The check inside a method will always be enough to verify
that the return values
+ are valid for the generic function.</p>
<pre class="code">
define method average (x :: <number>, y :: <number>)
=> mean :: <number>;
Modified: trunk/www/books/drm/Parameter_Lists_Syntax.html
==============================================================================
--- trunk/www/books/drm/Parameter_Lists_Syntax.html (original)
+++ trunk/www/books/drm/Parameter_Lists_Syntax.html Thu Dec 22 11:07:08 2005
@@ -138,7 +138,7 @@
the values of the arguments when the function is called. The value
names specified are only
for documentation.</p>
<p>The syntactic details of parameter lists are described
- in <a href="Phrase_Grammar#MARKER-9-2115">"Methods" on page 426</a>.</p>
+ in <a href="Phrase_Grammar#MARKER-9-2115"><q>Methods</q> on page
426</a>.</p>
</div>
Modified: trunk/www/books/drm/Patterns.html
==============================================================================
--- trunk/www/books/drm/Patterns.html (original)
+++ trunk/www/books/drm/Patterns.html Thu Dec 22 11:07:08 2005
@@ -227,10 +227,10 @@
<p>A <var id="MARKER-2-1243">pattern-variable</var> matches a fragment
as follows:</p>
<ul>
<li>When the constraint is a wildcard constraint
- (see <a href="Pattern_Variable_Constraints#MARKER-9-1256">"Pattern
Variable Constraints"
- on page 157</a>), the pattern variable consumes some initial
subsequence of the fragment,
- using a backup and retry algorithm. First, the wildcard consumes no
elementary fragments,
- and matching continues with the next <var>simple-pattern</var> in
+ (see <a href="Pattern_Variable_Constraints#MARKER-9-1256"><q>Pattern
Variable
+ Constraints</q> on page 157</a>), the pattern variable consumes
some initial subsequence
+ of the fragment, using a backup and retry algorithm. First, the
wildcard consumes no
+ elementary fragments, and matching continues with the next
<var>simple-pattern</var> in
the <var>pattern-sequence</var>. If any <var>simple-pattern</var> in
the
current <var>pattern-sequence</var> fails to match, back up to the
wildcard, consume one
more elementary fragment than before, and retry matching the rest of
@@ -242,11 +242,12 @@
a <var>pattern-sequence</var> to be a wildcard.</li>
<li>When the constraint is other than a wildcard constraint, the
pattern variable consumes
as much of the fragment as can be parsed by the grammar specified for
the constraint
- in <a href="Pattern_Variable_Constraints#MARKER-9-1256">"Pattern
Variable Constraints" on
- page 157</a>. If the parsing fails, the pattern match fails. The
pattern variable binds to
- the fragment specified in <a
href="Pattern_Variable_Constraints#MARKER-9-1256">"Pattern
- Variable Constraints."</a> This can be a parsed fragment rather
than the original
- sequence of elementary fragments.</li>
+ in <a href="Pattern_Variable_Constraints#MARKER-9-1256"><q>Pattern
Variable
+ Constraints</q> on page 157</a>. If the parsing fails, the
pattern match fails. The
+ pattern variable binds to the fragment specified
+ in <a href="Pattern_Variable_Constraints#MARKER-9-1256"><q>Pattern
Variable
+ Constraints.</q></a> This can be a parsed fragment rather than
the original sequence of
+ elementary fragments.</li>
<li>The ellipsis <var>pattern-variable</var>, <code>...</code>, can
only be used in an
auxiliary rule set. It represents a pattern variable with the same
name as the current
rule set and a wildcard constraint.</li>
@@ -270,8 +271,8 @@
has a non-wildcard constraint, parse the <var>value</var> part of
each property according
to this constraint, fail if the parsing fails or does not consume the
entire <var>value</var> part, and substitute the fragment specified
- in <a href="Pattern_Variable_Constraints#MARKER-9-1256">"Pattern
Variable Constraints" on
- page 157</a> for the <var>value</var> part.</li>
+ in <a href="Pattern_Variable_Constraints#MARKER-9-1256"><q>Pattern
Variable
+ Constraints</q> on page 157</a> for the <var>value</var>
part.</li>
<li>Each <var>pattern-keyword</var> in the
<var>property-list-pattern</var> binds a pattern
variable as follows:
<ul>
@@ -283,8 +284,8 @@
the <var>pattern-keyword</var> has a non-wildcard constraint,
parse the
property's <var>value</var> according to this constraint, fail if
the parsing fails or
does not consume the entire <var>value</var> , and bind the
pattern variable to the
- fragment specified in <a
href="Pattern_Variable_Constraints#MARKER-9-1256">"Pattern
- Variable Constraints" on page 157</a>. If the
<var>pattern-keyword</var> has a
+ fragment specified in <a
href="Pattern_Variable_Constraints#MARKER-9-1256"><q>Pattern
+ Variable Constraints</q> on page 157</a>. If the
<var>pattern-keyword</var> has a
wildcard constraint, bind the pattern variable to the
property's <var>value</var>.</li>
<li>A double <a name="MARKER-2-1248"></a>question mark finds every
property with a
Modified: trunk/www/books/drm/Reflective_Operations_on_Types.html
==============================================================================
--- trunk/www/books/drm/Reflective_Operations_on_Types.html (original)
+++ trunk/www/books/drm/Reflective_Operations_on_Types.html Thu Dec 22
11:07:08 2005
@@ -138,7 +138,8 @@
<h1 class="section-title"><a name="MARKER-9-1858"></a>Reflective
Operations on Types</h1>
<p>The following functions return information on types and test type
membership. They provide
part of the implementation of the type protocol, as described
- in <a href="Type_Protocol#MARKER-9-536">"The Type Protocol" beginning
on page 49</a>.</p>
+ in <a href="Type_Protocol#MARKER-9-536"><q>The Type Protocol</q>
beginning on page
+ 49</a>.</p>
<a name="HEADING103-2"></a>
<h4 class="item-title"><span class="signature"><code><a
name="MARKER-2-1859"></a><a name="MARKER-2-1860"></a>instance?</code>
</span><span class="attributes-summary">[Function]</span></h4>
<hr class="item-title" />
@@ -208,7 +209,7 @@
</dd>
<dt><span>Description:</span></dt>
<dd><p>Returns true if <var>type1 </var> is a subtype of
<var>type2</var>. Subtype rules are
- given in <a href="Type_Protocol#MARKER-9-536">"The Type Protocol"
on page
+ given in <a href="Type_Protocol#MARKER-9-536"><q>The Type
Protocol</q> on page
49</a>.</p></dd>
</dl>
<a name="HEADING103-16"></a>
@@ -280,7 +281,7 @@
<dd>
<p>Returns the class precedence list of <var>class</var>. This is an
ordered sequence
of<var>class</var> and all its superclasses, as described
- in <a href="Classes#MARKER-9-590">"Computing the Class Precedence
List" on page
+ in <a href="Classes#MARKER-9-590"><q>Computing the Class Precedence
List</q> on page
54</a>.</p>
<p>The result <var>sequence</var> should never be destructively
modified. Doing so may
cause unpredictable behavior. If <var>class</var> is sealed, an
implementation may
Modified: trunk/www/books/drm/Slots.html
==============================================================================
--- trunk/www/books/drm/Slots.html (original)
+++ trunk/www/books/drm/Slots.html Thu Dec 22 11:07:08 2005
@@ -133,8 +133,8 @@
the <a name="MARKER-2-600"></a>fields or instance variables of other
object-oriented
programming languages. By default, each instance of the class has
private storage for each
slot, so one instance can have one value in the slot and another
instance can have another
- value. Some slots are shared among instances, as described in <a
href="#MARKER-9-629">"Slot
- Allocation" on page 60</a>.</p>
+ value. Some slots are shared among instances, as described
+ in <a href="#MARKER-9-629"><q>Slot Allocation</q> on page 60</a>.</p>
<p><a name="MARKER-2-601"></a>All slot access is performed by function
calls.<a rel="FOOTNOTE" href="#FOOTNOTE-2"><sup>[2]</sup></a>
The method that returns the value of a slot is called the <dfn
id="MARKER-2-602">getter
method</dfn>, and the method that sets the value of a slot is called
@@ -206,8 +206,8 @@
<li><a name="MARKER-2-617"></a>A type may be specified. The value of
the slot will be
constrained to be an instance of that type.</li>
<li><a name="MARKER-2-618"></a>A sealing directive may be
- specified. See <a href="Define_Sealed_Domain#MARKER-9-1123">"Define
Sealed Domain" on page
- 135</a> for a complete description of the sealing constraints
imposed by this
+ specified. See <a href="Define_Sealed_Domain#MARKER-9-1123"><q>Define
Sealed Domain</q> on
+ page 135</a> for a complete description of the sealing constraints
imposed by this
directive.</li>
</ul>
<p>For the complete syntax of slot specifications, see the reference
entry of <code>define
@@ -334,10 +334,10 @@
<h3 class="sub-subsection-title">Overriding Slots in Subclasses</h3>
<p><a name="MARKER-2-650"></a>Some slot options related to instance
initialization can be
overridden in subclasses. The mechanisms for doing this are described
- in <a
href="Instance_Creation_and_Initialization#MARKER-9-677">"Inherited Slot
- Specifications" on page 67</a> and
- in <a
href="Instance_Creation_and_Initialization#MARKER-9-680">"Initialization
Argument
- Specifications" on page 68</a>.</p>
+ in <a
href="Instance_Creation_and_Initialization#MARKER-9-677"><q>Inherited Slot
+ Specifications</q> on page 67</a> and
+ in <a
href="Instance_Creation_and_Initialization#MARKER-9-680"><q>Initialization
Argument
+ Specifications</q> on page 68</a>.</p>
<a name="HEADING42-63"></a>
<h3 class="sub-subsection-title">Using Slots</h3>
<p><a name="MARKER-2-651"></a><a name="MARKER-2-652"></a>Because slots
are accessed through
Modified: trunk/www/books/drm/Statement_Macros.html
==============================================================================
--- trunk/www/books/drm/Statement_Macros.html (original)
+++ trunk/www/books/drm/Statement_Macros.html Thu Dec 22 11:07:08 2005
@@ -889,7 +889,7 @@
<dt><span>Description:</span></dt>
<dd><p><code>method</code> creates and returns a method specified by
the <var>parameter-list</var> and <var>body</var>. For a complete
description of
- methods, see <a href="Functions_Overview#MARKER-9-762">"Methods" on
page
+ methods, see <a
href="Functions_Overview#MARKER-9-762"><q>Methods</q> on page
80</a>.<a name="MARKER-2-2067"></a></p>
</dd>
</dl>
Modified: trunk/www/books/drm/Templates.html
==============================================================================
--- trunk/www/books/drm/Templates.html (original)
+++ trunk/www/books/drm/Templates.html Thu Dec 22 11:07:08 2005
@@ -142,7 +142,7 @@
other. This simplifies the implementation at the minor cost of
deferring some error checking
from when a macro is defined until the time when the macro is
called.</p>
<p>The grammar for templates is the definition of <var>template </var>
- in <a href="Phrase_Grammar#MARKER-9-2119">"Templates" on page
429</a>.</p>
+ in <a href="Phrase_Grammar#MARKER-9-2119"><q>Templates</q> on page
429</a>.</p>
<p>All <var>template-elements</var> other than <var>substitution</var>
are copied directly
into the macro expansion. The various kinds of <var>substitution</var>
insert something else
into the macro expansion, as follows:</p>
Modified: trunk/www/books/drm/Type_Protocol.html
==============================================================================
--- trunk/www/books/drm/Type_Protocol.html (original)
+++ trunk/www/books/drm/Type_Protocol.html Thu Dec 22 11:07:08 2005
@@ -167,17 +167,18 @@
type, <code>subtype?(singleton(<var>x</var>), <var>t</var>)</code> will
be true only
if <code>instance?(<var>x</var>, <var>t</var>)</code> is true.</p>
<p><code>subtype?</code> rules for union types are given
- in <a href="Union_Types#MARKER-9-701">"Union Types" on page 72</a>.
<code>subtype?</code>
- rules for limited integer types are given in <a
href="Limited_Types#MARKER-9-710">"Limited
- Integer Types" on page 74</a>. <code>subtype?</code> rules for
limited collection types are
- given in <a href="Limited_Collection_Types#MARKER-9-1060">"Limited
Collection Types" on page
+ in <a href="Union_Types#MARKER-9-701"><q>Union Types</q> on page
+ 72</a>. <code>subtype?</code> rules for limited integer types are
given
+ in <a href="Limited_Types#MARKER-9-710"><q>Limited Integer Types</q> on
page
+ 74</a>. <code>subtype?</code> rules for limited collection types are
given
+ in <a href="Limited_Collection_Types#MARKER-9-1060"><q>Limited
Collection Types</q> on page
126</a>.</p>
<p><code id="MARKER-2-549"><object></code> is the root of the type
hierarchy. All
objects are instances of <code><object></code>, and all types are
subtypes
of <code><object></code>.</p>
<p>A number of operations on types are described
- in <a href="Reflective_Operations_on_Types#MARKER-9-1858">"Reflective
Operations on Types"
- on page 343</a>.</p>
+ in <a href="Reflective_Operations_on_Types#MARKER-9-1858"><q>Reflective
Operations on
+ Types</q> on page 343</a>.</p>
<a name="HEADING40-14"></a>
<a name="UID-Types_and_Classes-4914"></a>
<h2 class="subsection-title"><a name="MARKER-2-550"></a>Base Types and
Pseudosubtypes</h2>
@@ -204,10 +205,11 @@
<h2 class="subsection-title"><a name="MARKER-2-552"></a><a
name="MARKER-9-553"></a>Type Disjointness</h2>
<p>Informally, two types are disjoint if there can be no object that is
an instance of both
types. Formally, the disjointness of types is specified by the
following set of rules. (Some
- of these rules reference definitions given in <a
href="Limited_Types#MARKER-9-710">"Limited
- Integer Types" on page 74</a>, <a
href="Element_Types#MARKER-9-1051">"Element Types" on page
- 124</a> and <a href="Limited_Collection_Types#MARKER-9-1060">"Limited
Collection Types" on
- page 126</a>.)</p>
+ of these rules reference definitions given
+ in <a href="Limited_Types#MARKER-9-710"><q>Limited Integer Types</q> on
page
+ 74</a>, <a href="Element_Types#MARKER-9-1051"><q>Element Types</q> on
page 124</a>
+ and <a href="Limited_Collection_Types#MARKER-9-1060"><q>Limited
Collection Types</q> on page
+ 126</a>.)</p>
<ul>
<li>Two <a name="MARKER-2-554"></a>classes are disjoint if they have no
common
subclasses.</li>
--
Gd-chatter mailing list
Gd-chatter@xxxxxxxxxxxxxxxx
https://gauss.gwydiondylan.org/mailman/listinfo/gd-chatter
|
