NOTE
Use of types float_t and double_t for temporary variables and arguments to internal functions is a more portable mechanism to achieve the best code.
NOTE
Until wide adoption of FPCE, isolate hexadecimal floating constants in designated header files to expedite conversion to decimal, should it become necessary.
NOTE
All CommonPoint platforms and all systems supporting at least the FPCE function library will support the comparison macros. They'll be as fast as infix comparisons if the compiler is fully FPCE-aware.
NOTE
FPCE-aware compilers will also support the names INFINITY and NAN.
Expression
evaluation pragmas
Pragmas provide a mechanism for giving a compiler leeway to produce the most expeditious code for a platform. There is no guarantee that the compiler will exploit that freedom. Hexadecimal
loating constants
Hexadecimal floating constants clarify certain format-dependent constructs, but compilers not supporting FPCE probably don't support this useful feature. Efficiency of key
macros
All CommonPoint platforms support the comparison macro functions such as IsLess and IsGreaterEqual. These macros match the built-in operators (<
and >=
) except that they don't raise the invalid flag when their operands are unordered. Support for NaNs
and infinities in I/O
In CommonPoint systems, the names kInfinity and kNaN are used for special floating-point values.
[Contents]
[Previous]
[Next]
Click the icon to mail questions or corrections about this material to Taligent personnel.
Generated with WebMaker