so that their initialisation order ensures they have the proper values. Add
unit tests for these constants.

and simplify the Remez code accordingly.

multiplications by integers, especially powers of two.

accurate.

improved implementation of exp(), which relies on log().

addition and subtraction operators occurring when exponents were too
different.

is zero.

print() method so that it displays decimal values.

code shortcut, fix bugs in the addition and subtraction, another one in
the multiplication code, and add new unit tests for most of these.

to 32 bigits.

and add a test suite check for unary minus.

multiplication.

names with the project file.

and the OS X port.

to ios-image.cpp, but disable it on OS X because UIKit isn't available.

on errors.

According to David Turner, “it should be the only thing that NDK users
should be testing again.”

This is useful when doing several asserts in one loop, for instance: there
isn't always a way to deduce the loop index from the assert failure, so
these macros allow the user to give more context information.

we do not care about.

CPPUNIT_ASSERT_EQUAL(a, b) “expects” the value “a” and fails if “b” is
different. The logic seems backwards to me, but matching CppUnit’s
output is important so I’m doing the same in LolUnit.