Jump to navigation Jump to search
363 bytes added ,  09:08, 18 January 2015
→‎Motivation: Added bullet: System dependent results
* Even if the developer would be proficient, most developing environments / technologies limit floating-point arithmetic capabilities to a very limited subset of IEEE 754: Only one or two data types, no rounding modes, missing functions … []
* Results are hardly predictable. [] All operations produce the best possible accuracy ''at runtime'', this is how a floating point works. Contrariwise, financial computer systems typically use a [ fixed-point arithmetic] (COBOL, PL/I, …), where overflow and rounding can be precisely predicted ''at compile-time''.
* Results are system dependent. All but the most basic floating-point operations are not guaranteed to be accurate and produce different results depending on low level libraries and hardware. [] []
* If you do not know the technical details (cf. first bullet) you ignore the fact that the computer lies to you in many situations. For example, when looking at numerical output and the computer says “<code>ans = 0.1</code>,” this is not absolutely correct. In fact, the value is only ''close enough'' to the value 0.1. Additionally, many functions produce limit values (∞ × −∞ = −∞, ∞ ÷ 0 = ∞, ∞ ÷ −0 = −∞, log (0) = −∞), which is sometimes (but not always!) useful when overflow and underflow occur.


Navigation menu