Don't put AvgStateRemoved in a float.
authorMatthijs Kooijman <matthijs@stdin.nl>
Wed, 9 Dec 2009 10:42:47 +0000 (11:42 +0100)
committerMatthijs Kooijman <matthijs@stdin.nl>
Wed, 9 Dec 2009 10:42:47 +0000 (11:42 +0100)
Doing this completely foobarred the strikethrough...

Chapters/Prototype.tex

index 1d87eeb..2316824 100644 (file)
 
       When applying these rules to the function \lam{avg} from
       \in{example}[ex:AvgStateNormal], we be left with the description
-      in \in{example}[ex:AvgStateRemoved]. All the parts that do not
-      generate any \VHDL\ directly are crossed out, leaving just the
-      actual flow of values in the final hardware. To illustrate the
-      change of the types of \lam{s} and \lam{s'}, their types are also
-      shown.
+      below. All the parts that do not generate any \VHDL\ directly are
+      crossed out, leaving just the actual flow of values in the final
+      hardware. To illustrate the change of the types of \lam{s} and \lam{s'},
+      their types are also shown.
       
       \startbuffer[AvgStateRemoved]
         avg = iλ.λ--spacked.--
           in
             res
       \stopbuffer
-      \placeexample[here][ex:AvgStateRemoved]{Normalized version of \in{example}[ex:AvgState] with ignored parts crossed out}
-          {\typebufferlam{AvgStateRemoved}}
+      \typebufferlam{AvgStateRemoved}
               
       When we actually leave out the crossed out parts, we get a slightly
       weird program: there is a variable \lam{s} which has no value, and there