X-Git-Url: https://git.ucc.asn.au/?p=ipdf%2Fsam.git;a=blobdiff_plain;f=chapters%2FBackground%2FFloats.tex;h=1be1113684ae7f2736c8761e36c289aba31b8d08;hp=65a99e4941a7527cbdc75a98301164b2b4c8aa83;hb=ae8d5f837db032eb4d9e9666f5026fab7e3e8e4a;hpb=253d241eb8279be539ad72a0283d3f1575b537ab

diff --git a/chapters/Background/Floats.tex b/chapters/Background/Floats.tex
index 65a99e4..1be1113 100644
--- a/chapters/Background/Floats.tex
+++ b/chapters/Background/Floats.tex
@@ -4,7 +4,6 @@
 
 
 \subsection{Floating Point Operations}
-{\bf FIXME:} Appendix?
 \input{chapters/Background/Floats/Operations}
 
 
@@ -12,4 +11,4 @@
 
 Arbitrary precision floating point numbers are implemented in a variety of software libraries which will dynamically allocate extra bits for the exponent or mantissa as required. An example is the GNU MPFR library discussed by Fousse in 2007\cite{fousse2007mpfr}. Although many arbitrary precision libraries already existed, MPFR intends to be fully compliant with some of the more obscure IEEE-754 requirements such as rounding rules and exceptions. 
 
-As we have seen, it is trivial to find real numbers that would require an infinite number of bits to represent exactly. Implementations of ``arbitrary'' precision must carefully determine at what point rounding should occur so as to balance performance with memory usage.
+It is trivial to find real numbers that would require an infinite number of bits to represent exactly (for example, $\frac{1}{3} = 0.333333\text{...}$). The GMP and MPFR libraries require a fixed (but arbitrarily large) precision be set; although it is possible to increase or decrease the precision of individual numbers as desired.