From: Matthijs Kooijman Date: Wed, 9 Dec 2009 10:42:47 +0000 (+0100) Subject: Don't put AvgStateRemoved in a float. X-Git-Tag: final-thesis~5 X-Git-Url: https://git.stderr.nl/gitweb?a=commitdiff_plain;h=23f5c33533e6ab45727c79b309751c2c25dd3327;p=matthijs%2Fmaster-project%2Freport.git Don't put AvgStateRemoved in a float. Doing this completely foobarred the strikethrough... --- diff --git a/Chapters/Prototype.tex b/Chapters/Prototype.tex index 1d87eeb..2316824 100644 --- a/Chapters/Prototype.tex +++ b/Chapters/Prototype.tex @@ -1301,11 +1301,10 @@ 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.-- @@ -1326,8 +1325,7 @@ 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