many updates

[phd-thesis.git] / top / lang.tex

diff --git a/top/lang.tex b/top/lang.tex
index 1b5735d..2a7f656 100644 (file)
--- a/top/lang.tex
+++ b/top/lang.tex
@@ -6,7 +6,7 @@
 
 \begin{document}
 \input{subfileprefix}
 
 \begin{document}
 \input{subfileprefix}

-\chapter{The \texorpdfstring{\gls{MTASK}}{mTask} language}%\texorpdfstring{\glsxtrshort{DSL}}{DSL}}%
+\chapter{The mTask language}%

 \label{chp:mtask_dsl}
 \begin{chapterabstract}
        This chapter introduces the \gls{TOP} language \gls{MTASK} by:
 \label{chp:mtask_dsl}
 \begin{chapterabstract}
        This chapter introduces the \gls{TOP} language \gls{MTASK} by:


@@ -142,14 +142,14 @@ To illustrate the structure of a \gls{MTASK} programs, \cref{lst:mtask_types} sh
 :: Main a = { main :: a }
 :: In a b = (In) infix 0 a b
 
 :: Main a = { main :: a }
 :: In a b = (In) infix 0 a b
 

-someTask :: MTask v Int | mtask v & liftsds v & sensor1 v & ...
+someTask :: MTask v Int | mtask v & lowerSds v & sensor1 v & ...

 someTask =
        sensor1 config1 \sns1->
        sensor2 config2 \sns2->
 someTask =
        sensor1 config1 \sns1->
        sensor2 config2 \sns2->

-          sds     \s1  = initialValue
-       In liftsds \s2  = someiTaskSDS
-       In fun     \fun1= ( \(a0, a1)->... )
-       In fun     \fun2= ( \a->... )
+          sds      \s1  = initialValue
+       In lowerSds \s2  = someiTaskSDS
+       In fun      \fun1= ( \(a0, a1)->... )
+       In fun      \fun2= ( \a->... )

        In { main = mainexpr }
 \end{lstClean}
 % VimTeX: SynIgnore off
        In { main = mainexpr }
 \end{lstClean}
 % VimTeX: SynIgnore off


@@ -578,7 +578,7 @@ task = declarePin A1 PMInput  \a1->
        {main = rpeat (readA a1 >>~. writeA a2 >>|. delay (lit 1000))}
 \end{lstClean}
 
        {main = rpeat (readA a1 >>~. writeA a2 >>|. delay (lit 1000))}
 \end{lstClean}
 

-\subsection{\texorpdfstring{\Glsxtrlongpl{SDS}}{Shared data sources}}
+\subsection{Shared data sources}

 For some collaborations it is cumbersome to only communicate data using task values.
 \Glspl{SDS} are a safe abstraction over any data that fill this gap.
 It allows tasks to safely and atomically read, write and update data stores in order to share data with other tasks.
 For some collaborations it is cumbersome to only communicate data using task values.
 \Glspl{SDS} are a safe abstraction over any data that fill this gap.
 It allows tasks to safely and atomically read, write and update data stores in order to share data with other tasks.