summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorschinz <schinz@epfl.ch>2004-01-28 12:00:41 +0000
committerschinz <schinz@epfl.ch>2004-01-28 12:00:41 +0000
commit0134764630b0817a1485094c9f0e17f867e2a835 (patch)
treecb3e8a1f7b107f40134f3e289c81eff5b604a59e /doc
parentff4e27439635e45c3114e91ebddb1bf71ae92734 (diff)
downloadscala-0134764630b0817a1485094c9f0e17f867e2a835.tar.gz
scala-0134764630b0817a1485094c9f0e17f867e2a835.tar.bz2
scala-0134764630b0817a1485094c9f0e17f867e2a835.zip
- fixed a few typos in chapter 3
Diffstat (limited to 'doc')
-rw-r--r--doc/reference/ReferencePart.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/reference/ReferencePart.tex b/doc/reference/ReferencePart.tex
index 5ad42480d7..ae83813540 100644
--- a/doc/reference/ReferencePart.tex
+++ b/doc/reference/ReferencePart.tex
@@ -315,7 +315,7 @@ equivalent to the type projection \lstinline@$p$.type#$x$@.
\example
Some type designators and their expansions are listed below. We assume
-a local type parameter $t$, a value \code{mytable}
+a local type parameter $t$, a value \code{maintable}
with a type member \code{Node} and the standard class \lstinline@scala.Int@,
\begin{lstlisting}
t $\epsilon$.type#t
@@ -528,7 +528,7 @@ Types, bounds and base classes of class members depend on the way the
members are referenced. Central here are three notions, namely:
\begin{enumerate}
\item the notion of the set of base classes of a type $T$,
-\item the notion of a type $T$ in some class $C$ seem from some
+\item the notion of a type $T$ in some class $C$ seen from some
prefix type $S$,
\item the notion of a member binding of some type $T$.
\end{enumerate}
@@ -602,7 +602,7 @@ has a type instance of class $C$ as a base class, say
\begin{itemize}
\item
If $D$ is a subclass of $C$ and
- $S$ has a type instance of class $D$ among its base classes.
+ $S$ has a type instance of class $D$ among its base classes,
then $T$ in $C$ seen from $S$ is $S$.
\item
Otherwise, if $C$ is defined in a class $C'$, then
@@ -619,7 +619,7 @@ has a type instance of class $C$ as a base class, say
If $T$ is a possibly parameterized class type, where $T$'s class
is defined in some other class $D$, and $S$ is some prefix type,
then we use ``$T$ seen from $S$'' as a shorthand for
-``$T$ in $D$ seen from $S$.
+``$T$ in $D$ seen from $S$''.
3. The {\em member bindings} of a type $T$ are all bindings $d$ such that
there exists a type instance of some class $C$ among the base classes of $T$