From d87a4fd64d0bb48c3b42f46f7ea8806627b65c4d Mon Sep 17 00:00:00 2001 From: Mart Lubbers Date: Mon, 3 Jul 2017 16:18:02 +0200 Subject: [PATCH] camil's comment chp5 --- system.edsl.tex | 18 ++++++++++-------- system.tex | 5 +++-- 2 files changed, 13 insertions(+), 10 deletions(-) diff --git a/system.edsl.tex b/system.edsl.tex index ee783b9..afa105d 100644 --- a/system.edsl.tex +++ b/system.edsl.tex @@ -1,8 +1,8 @@ Not all \glspl{Task} are suitable to run on an \gls{IoT}-device and therefore -an \gls{EDSL} is used to offer a constrained language that expresses \glspl{Task} -for the new system. The \gls{mTask}-\gls{EDSL} shown in -Chapter~\ref{chp:mtask} provides the language to create imperative programs that -are suitable to run on microcontrollers. The \gls{EDSL}'s main view is a +an \gls{EDSL} is used to offer a constrained language that expresses +\glspl{Task} for the new system. The \gls{mTask}-\gls{EDSL} shown in +Chapter~\ref{chp:mtask} provides the language to create imperative programs +that are suitable to run on microcontrollers. The \gls{EDSL}'s main view is a \gls{C} code generator who's code compiles to \gls{Arduino} compatible microcontrollers. The big downside of this approach is the stiffness of the system. Once the code has been generated and the microcontroller has been @@ -10,9 +10,11 @@ programmed, nothing can be changed to it anymore. \gls{IoT}-devices often have a limited amount of write cycles on their program memory available and therefore it is very expensive to keep recompiling and reprogramming the chips. To solve this problem, a new view is proposed for the \gls{mTask}-\gls{EDSL} -which compiles the expressions not to \gls{C}-code, but to a bytecode format. -To achieve this, several classes have been added to the \gls{mTask}-\gls{EDSL}. -Not all of the functionality of the \gls{mTask} language is used. +which compiles the expressions not to \gls{C}-code, but to a bytecode format +which is interpetable and thus the need for reprogramming is removed. To +achieve this, several classes have been added to the \gls{mTask}-\gls{EDSL}. +Not all of the functionality of the \gls{mTask} language is needed or not +implemented. -The added functionality and implementation to the \gls{mTask}-\gls{EDSL} is +The functionality and implementation added to the \gls{mTask}-\gls{EDSL} is shown in Chapter~\ref{chp:mtaskcont}. diff --git a/system.tex b/system.tex index 87f5d5c..5800a40 100644 --- a/system.tex +++ b/system.tex @@ -1,5 +1,6 @@ -The system researched and built in this research provides a bridge between the -gap present in the current system. It provides a framework to offer +A system has been researched and built and will be described in the following +chapters. This novel system provides a bridge between to gap present in the +current system explained in the introduction. It provides a framework to offer functionality for an \gls{iTasks} server to outsource \glspl{Task} to \gls{IoT}-devices without needing to recompile the code. The \glspl{Task} targeted at \gls{IoT} devices are compiled at runtime to bytecode which is sent -- 2.20.1