I can't overemphasize how much work the tools are doing on our behalf
Whenever we do floating-point input, we know exactly what the input is, and we also know exactly what precision the result should have. The hard problem, then, is how to specify the behavior of floating-point output.
The specs are impressive: A dual core Cortex A9 CPU that can run at 1GHZ
"At least as precise" is sometimes just a polite way of saying "loosely specified."
What's the difference between a motor, a generator, and a transformer?
Interoperating between Objective-C and C/C++ code presents several linker challenges, some of which are addressed in these recipes.
It would be useful if all conversions were as accurate as possible and, independently, were always done in exactly the same way. But complications can impede these goals.
Abstractions make things simple, but sometimes you have to dig under the abstractions and understand what really happens so you can design an embedded system that works.
Let's look at some consequences of floating-point conversion.
A simple renaming trick will get rid of all the error messages.