mtaskext.tex

   1 The \glspl{Task} suitable for a client are called \gls{mTask}-\gls{Task} and
   2 are written in the aforementioned \gls{mTask}-\gls{EDSL}. Some functionality of
   3 the original \gls{mTask}-\gls{EDSL} will not be used in this system.
   4 Conversely, some functionality needed was not available in the existing
   5 \gls{EDSL}. Due to the nature of class based shallow embedding this obstacle is
   6 easy to solve. A type --- housing the \gls{EDSL} --- does not have to implement
   7 all the available classes. Moreover, classes can be added at will without
   8 interfering with the existing views.
   9
  10 \section{\gls{Task} Scheduling Strategy}
  11 \input{mtaskext.taskstrat}
  12
  13 \section{\gls{SDS} Properties}
  14 \input{mtaskext.sdsprop}
  15
  16 \section{Bytecode Compilation View}\label{sec:compiler}
  17 \input{mtaskext.bytecode}
  18
  19 \section{Examples}
  20 \input{mtaskext.examples}