Changeset 7eb6eb5 for doc/theses/andrew_beach_MMath/features.tex

Timestamp:

Jan 29, 2021, 8:23:52 AM (5 years ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

ADT, arm-eh, ast-experimental, enum, forall-pointer-decay, jacob/cs343-translation, master, new-ast-unique-expr, pthread-emulation, qualifiedEnum

Children:

5669d0b

Parents:

4dcd5ea

Message:

complete first proofread of Andrew's thesis

File:

• doc/theses/andrew_beach_MMath/features.tex (modified) (8 diffs)

doc/theses/andrew_beach_MMath/features.tex

@@ -62 +62 @@
 internally for exception handling. The only user-level feature is the virtual
 cast, which is the same as the \CC \lstinline[language=C++]|dynamic_cast|.
+\label{p:VirtualCast}
 \begin{cfa}
 (virtual TYPE)EXPRESSION
@@ -89 +90 @@
 promises @exceptT@ is a virtual type and a child of the base exception-type.
 
-{\color{blue} PAB: I do not understand this paragraph.}
+\PAB{I do not understand this paragraph.}
 One odd thing about @get_exception_vtable@ is that it should always be a
 constant function, returning the same value regardless of its argument.  A
@@ -102 +103 @@
 
 \section{Raise}
-\CFA provides two kinds of exception raise: termination (see
-\VRef{s:Termination}) and resumption (see \VRef{s:Resumption}), which are
+\CFA provides two kinds of exception raise: termination
+\see{\VRef{s:Termination}} and resumption \see{\VRef{s:Resumption}}, which are
 specified with the following traits.
 \begin{cfa}
@@ -129 +130 @@
 parenthesized list of polymorphic arguments. These macros do the name mangling
 to get the virtual-table name and provide the arguments to both sides
-{\color{blue}(PAB: What's a ``side''?)}
+\PAB{What's a ``side''?}
 
 \subsection{Termination}
@@ -253 +254 @@
 current point on the stack because new try statements may have been pushed by
 the handler or functions called from the handler. If there is no match back to
-the point of the current handler, the search skips the stack frames already
+the point of the current handler, the search skips\label{p:searchskip} the stack frames already
 searched by the first resume and continues after the try statement. The default
 handler always continues from default handler associated with the point where
@@ -291 +292 @@
 continue searching the stack frames after the try statement. However, the
 current try statement is still on the stack below the handler issuing the
-reresume (see \VRef{s:Reraise}). Hence, the try statement catches the re-raise
+reresume \see{\VRef{s:Reraise}}. Hence, the try statement catches the re-raise
 again and does another re-raise \emph{ad infinitum}, which is confusing and
 difficult to debug. The \CFA resumption search-pattern skips the try statement
@@ -377 +378 @@
 \begin{description}
 \item[Main Stack:]
-
 The main stack is the one used by the program main at the start of execution,
 and is the only stack in a sequential program.  Hence, when cancellation is
@@ -401 +401 @@
 which exception has priority, the original or new exception? No matter which
 exception is selected, it is possible for the selected one to disrupt or
-destroy the context required for the other. {\color{blue} PAB: I do not
-understand the following sentences.} This loss of information can happen with
-join but as the thread destructor is always run when the stack is being unwound
-and one termination/cancellation is already active. Also since they are
-implicit they are easier to forget about.
+destroy the context required for the other. \PAB{I do not understand the
+following sentences.} This loss of information can happen with join but as the
+thread destructor is always run when the stack is being unwound and one
+termination/cancellation is already active. Also since they are implicit they
+are easier to forget about.
 
 \item[Coroutine Stack:] A coroutine stack is created for a @coroutine@ object