Changes in doc/theses/colby_parsons_MMAth/text/mutex_stmt.tex [80fc78f:000d68f]

File:

• doc/theses/colby_parsons_MMAth/text/mutex_stmt.tex (modified) (1 diff)

doc/theses/colby_parsons_MMAth/text/mutex_stmt.tex

@@ -83 +83 @@
 \end{figure}
 
-Like Java, \CFA monitors have \Newterm{multi-acquire} semantics so the thread in the monitor may acquire it multiple times without deadlock, allowing recursion and calling other MX functions.
+Like Java, \CFA monitors have \Newterm{multi-acquire} semantics so the thread in the monitor may acquire it multiple times without deadlock, allowing recursion and calling of other MX functions.
 For robustness, \CFA monitors ensure the monitor lock is released regardless of how an acquiring function ends, normal or exceptional, and returning a shared variable is safe via copying before the lock is released.
 Monitor objects can be passed through multiple helper functions without acquiring mutual exclusion, until a designated function associated with the object is called.
 \CFA functions are designated MX by one or more pointer/reference parameters having qualifier @mutex@.
 Java members are designated MX with \lstinline[language=java]{synchronized}, which applies only to the implicit receiver parameter.
-In the example, the increment and setter operations need mutual exclusion, while the read-only getter operation is not MX because reading an integer is atomic.
+In the example above, the increment and setter operations need mutual exclusion, while the read-only getter operation is not MX because reading an integer is atomic.
 
 As stated, the non-object-oriented nature of \CFA monitors allows a function to acquire multiple mutex objects.