Context Navigation

-                      rf93c50a
+                      r166b384
 \paragraph{Hierarchy}
 A common way to organize exceptions is in a hierarchical structure.
 This pattern comes from object-orientated languages where the
+This pattern comes from object-oriented languages where the
 exception hierarchy is a natural extension of the object hierarchy.
 …
 A common feature in many programming languages is a tool to pair code
 (behaviour) with data.
 In \CFA this is done with the virtual system,
+In \CFA, this is done with the virtual system,
 which allow type information to be abstracted away, recovered and allow
 operations to be performed on the abstract objects.

doc/theses/andrew_beach_MMath/intro.tex

-                      rf93c50a
+                      r166b384
 message as a payload\cite{Ada12}.
 The modern flag-ship for termination exceptions is \Cpp,
+The modern flagship for termination exceptions -- if one exists -- is \Cpp,
 which added them in its first major wave of non-object-orientated features
 in 1990.\cite{CppHistory}
 …
 included in the \Cpp standard.
 % https://en.wikipedia.org/wiki/Exception_handling
 Since then, resumptions have been ignored in main-stream programming languages.
+Since then, resumptions have been ignored in mainstream programming languages.
 However, resumption is being revisited in the context of decades of other
 developments in programming languages.
 …
 %\subsection
 More recently exceptions, seem to be vanishing from newer programming
+More recently, exceptions seem to be vanishing from newer programming
 languages, replaced by ``panic".
 In Rust, a panic is just a program level abort that may be implemented by
 …
 Because of their cost, exceptions are rarely used for hot paths of execution.
 Hence, there is an element of self-fulfilling prophecy as implementation
 techniques have been focused on making them cheap to set-up,
+techniques have been focused on making them cheap to set up,
 happily making them expensive to use in exchange.
 This difference is less important in higher-level scripting languages,

-                      rf93c50a
+                      r166b384
 \begin{center}\textbf{Acknowledgements}\end{center}
+I would like to thank all the people who made this thesis possible.
+(I'm waiting until who is involved is finalized.)
+As is tradition and his due, I would like to begin by thanking my
+supervisor Peter Buhr. From accepting me in a first place,
+to helping me run performance tests, I would not be here without him.
+Also if there was an ``artist" field here he would be listed there as well,
+he helped me a lot with the diagrams.
+I would like to thank the readers
+Gregor Richards and Yizhou Zhang
+for their feedback and approval.
+The presentation of the thesis has definitely been improved with their
+feedback.
+I also thank the entire Cforall Team who built the rest of the
+\CFA compiler. From the existing features I used in my work, to the
+internal tooling that makes further development easier and the optimizations
+that make running tests pass by quickly.
+This includes: Aaron Moss, Rob Schluntz, Thierry Delisle, Michael Brooks,
+Mubeen Zulfieqar \& Fangren Yu.
+And thank-you Henry Xue, the co-op student who
+converted my macro implementation of exception declarations into
+the compiler features presented in this thesis.
+Finally I thank my family, who are still relieved I learned how to read.
 \cleardoublepage

Note: See TracChangeset for help on using the changeset viewer.