Changes in doc/proposals/concurrency/text/together.tex [20ffcf3:cf966b5]

File:

• doc/proposals/concurrency/text/together.tex (modified) (6 diffs)

doc/proposals/concurrency/text/together.tex

@@ -7 +7 @@
 
 \section{Threads as monitors}
-As it was subtely alluded in section \ref{threads}, \code{threads} in \CFA are in fact monitors, which means that all monitor features are available when using threads. For example, here is a very simple two thread pipeline that could be used for a simulator of a game engine :
-\begin{cfacode}
+As it was subtly alluded in section \ref{threads}, \code{thread}s in \CFA are in fact monitors, which means that all monitor features are available when using threads. For example, here is a very simple two thread pipeline that could be used for a simulator of a game engine :
+\begin{figure}[H]
+\begin{cfacode}[caption={Toy simulator using \code{thread}s and \code{monitor}s.},label={lst:engine-v1}]
 // Visualization declaration
 thread Renderer {} renderer;
@@ -20 +21 @@
 void draw( Renderer & mutex this, Frame * frame );
 
-// Simualation loop
+// Simulation loop
 void main( Simulator & this ) {
         while( true ) {
@@ -36 +37 @@
 }
 \end{cfacode}
+\end{figure}
 One of the obvious complaints of the previous code snippet (other than its toy-like simplicity) is that it does not handle exit conditions and just goes on forever. Luckily, the monitor semantics can also be used to clearly enforce a shutdown order in a concise manner :
-\begin{cfacode}
+\begin{figure}[H]
+\begin{cfacode}[caption={Same toy simulator with proper termination condition.},label={lst:engine-v2}]
 // Visualization declaration
 thread Renderer {} renderer;
@@ -49 +52 @@
 void draw( Renderer & mutex this, Frame * frame );
 
-// Simualation loop
+// Simulation loop
 void main( Simulator & this ) {
         while( true ) {
@@ -76 +79 @@
 // Call destructor for renderer to signify shutdown
 \end{cfacode}
+\end{figure}
 
 \section{Fibers \& Threads}
-As mentionned in section \ref{preemption}, \CFA uses preemptive threads by default but can use fibers on demand. Currently, using fibers is done by adding the following line of code to the program~:
+As mentioned in section \ref{preemption}, \CFA uses preemptive threads by default but can use fibers on demand. Currently, using fibers is done by adding the following line of code to the program~:
 \begin{cfacode}
 unsigned int default_preemption() {
@@ -84 +88 @@
 }
 \end{cfacode}
-This function is called by the kernel to fetch the default preemption rate, where 0 signifies an infinite time-slice i.e. no preemption. However, once clusters are fully implemented, it will be possible to create fibers and uthreads in on the same system :
+This function is called by the kernel to fetch the default preemption rate, where 0 signifies an infinite time-slice, i.e., no preemption. However, once clusters are fully implemented, it will be possible to create fibers and \glspl{uthread} in the same system, as in listing \ref{lst:fiber-uthread}
 \begin{figure}
-\begin{cfacode}
+\begin{cfacode}[caption={Using fibers and \glspl{uthread} side-by-side in \CFA},label={lst:fiber-uthread}]
 //Cluster forward declaration
 struct cluster;