Fix a lot of things following from Jan's comments.

[matthijs/master-project/report.git] / Chapters / Context.tex

diff --git a/Chapters/Context.tex b/Chapters/Context.tex
index 9444a6e8e78b58ea9a25ec1214398456ccedab7f..f07f1d9cd8a13da4052001a9232315fd8f4830d4 100644 (file)
--- a/Chapters/Context.tex
+++ b/Chapters/Context.tex
@@ -1,6 +1,6 @@
 \chapter[chap:context]{Context}
   An obvious question that arises when starting any research is \quote{Has
 \chapter[chap:context]{Context}
   An obvious question that arises when starting any research is \quote{Has

-  this not been done before?} Using a functional language for describing hardware
+  this not been done before?}. Using a functional language for describing hardware

   is not a new idea at all. In fact, there has been research into functional
   hardware description even before the conventional hardware description
   languages were created. \todo{Reference about early FHDLs} However,
   is not a new idea at all. In fact, there has been research into functional
   hardware description even before the conventional hardware description
   languages were created. \todo{Reference about early FHDLs} However,


@@ -86,7 +86,7 @@
       variables (\eg, using the same variable twice while only calculating it
       once) and cycles in circuits are non-trivial to properly and safely
       translate (though there is some work to fix this, but that has not been
       variables (\eg, using the same variable twice while only calculating it
       once) and cycles in circuits are non-trivial to properly and safely
       translate (though there is some work to fix this, but that has not been

-      possible in a completely reliable way yet. \cite[gill09]
+      possible in a completely reliable way yet \cite[gill09]).

       \item Some things are verbose to express. Especially ForSyDe suffers
       from a lot of notational overhead due to the Template Haskell approach
       used. Since conditional expressions are not supported, a lot of Haskell's
       \item Some things are verbose to express. Especially ForSyDe suffers
       from a lot of notational overhead due to the Template Haskell approach
       used. Since conditional expressions are not supported, a lot of Haskell's


@@ -99,10 +99,10 @@
       programmers), but the described circuits do not have any polymorphism
       or higher order functions, which can be limiting. \todo{How true or
       appropriate is this point?}
       programmers), but the described circuits do not have any polymorphism
       or higher order functions, which can be limiting. \todo{How true or
       appropriate is this point?}

-      \todo[left]{Function structure gets lost (in Lava)}
+      \todo{Function structure gets lost (in Lava)}

     \stopitemize
 
     \stopitemize
 

-    \todo[text]{Complete translation in TH is complex: Works with Haskell AST
+    \todo{Complete translation in TH is complex: Works with Haskell AST

     instead of Core}
 
 % vim: set sw=2 sts=2 expandtab:
     instead of Core}
 
 % vim: set sw=2 sts=2 expandtab: