From e0645e1487f71512352f4fe8ace2e7a8e1e73d71 Mon Sep 17 00:00:00 2001 From: Mart Lubbers Date: Wed, 14 Jun 2017 17:07:36 +0200 Subject: [PATCH] interpr --- results.mtask.tex | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/results.mtask.tex b/results.mtask.tex index 5912801..2ad243a 100644 --- a/results.mtask.tex +++ b/results.mtask.tex @@ -62,11 +62,11 @@ class sdspub v where \section{Bytecode compilation}\label{sec:compiler} The \glspl{mTask} are sent to the device in bytecode and are saved in the memory of the device. To compile the \gls{EDSL} code to bytecode, a view is -added to the \gls{mTask}-system called \CI{ByteCode}. As shown in -Listing~\ref{lst:bcview}, the \CI{ByteCode} view is a boxed \gls{RWST} that -writes bytecode instructions (\CI{BC}) while carrying around a \CI{BCState}. -The state is kept between devices and contains fresh variable names and a -register of shares used. +added to the \gls{mTask}-system encapsulated in the type \CI{ByteCode}. As +shown in Listing~\ref{lst:bcview}, the \CI{ByteCode} view is a boxed \gls{RWST} +that writes bytecode instructions (\CI{BC}) while carrying around a +\CI{BCState}. The state is kept between compilations and is unique to a device. +The state contains fresh variable names and a register of shares used. Types implementing the \gls{mTask} classes must have two free type variables. Therefore the \gls{RWST} is wrapped with a constructor and two phantom type @@ -325,3 +325,6 @@ position in the program memory. \end{lstlisting} \todo{add more elaborate example?} + +\section{Interpretation} +\todo{details about the interpreter on the client} -- 2.20.1