[Boost-commit] svn:boost r83595 - sandbox/precision/libs/precision/doc

Subject: [Boost-commit] svn:boost r83595 - sandbox/precision/libs/precision/doc
From: e_float_at_[hidden]
Date: 2013-03-26 16:41:30

Author: christopher_kormanyos
Date: 2013-03-26 16:41:29 EDT (Tue, 26 Mar 2013)
New Revision: 83595
URL: http://svn.boost.org/trac/boost/changeset/83595

Log:
Improved the expression of our motivations (in Chapter 1).
Text files modified: 
   sandbox/precision/libs/precision/doc/precision.qbk |    10 ++++++++++                              
   1 files changed, 10 insertions(+), 0 deletions(-)

Modified: sandbox/precision/libs/precision/doc/precision.qbk
==============================================================================
--- sandbox/precision/libs/precision/doc/precision.qbk	(original)
+++ sandbox/precision/libs/precision/doc/precision.qbk	2013-03-26 16:41:29 EDT (Tue, 26 Mar 2013)
@@ -181,6 +181,16 @@
   float64_t  == binary64;
   float128_t == binary128;
 
+This equivalence results in far-reaching benefits.
+
+It means that floating-point software written with
+`float16_t`, `float32_t`, `float64_t`, and `float128_t`
+should behave identically when used on any platform
+with any implementation that correctly supports the `typedef`s.
+
+It also creates the opportunity to implement quadruple-precision (__IEEE_Quad)
+in a specified, and therefore portable, fashion.
+
 One could envision two ways to name the proposed
 optional floating-point `typedef`s having specified width: