|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r83650 - in sandbox/precision/libs/precision/doc: . html html/precision
From: pbristow_at_[hidden]
Date: 2013-03-30 11:31:21
Author: pbristow
Date: 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
New Revision: 83650
URL: http://svn.boost.org/trac/boost/changeset/83650
Log:
rebuilt html and pdf - and found yet another typo.
Binary files modified:
sandbox/precision/libs/precision/doc/precision.pdf
Text files modified:
sandbox/precision/libs/precision/doc/html/index.html | 2 +-
sandbox/precision/libs/precision/doc/html/precision/abstract.html | 5 +++--
sandbox/precision/libs/precision/doc/html/precision/introduction.html | 2 +-
sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html | 3 ++-
sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html | 6 +++---
sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html | 18 ++++++++++++++++++
sandbox/precision/libs/precision/doc/html/precision/version_id.html | 2 +-
sandbox/precision/libs/precision/doc/precision.qbk | 2 +-
8 files changed, 30 insertions(+), 10 deletions(-)
Modified: sandbox/precision/libs/precision/doc/html/index.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/index.html (original)
+++ sandbox/precision/libs/precision/doc/html/index.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -72,7 +72,7 @@
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: March 29, 2013 at 12:32:13 GMT</small></p></td>
+<td align="left"><p><small>Last revised: March 30, 2013 at 15:27:44 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
Modified: sandbox/precision/libs/precision/doc/html/precision/abstract.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/abstract.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/abstract.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -39,8 +39,9 @@
</p>
<p>
The optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
- having specified widths are to be contained in a new standard library header
- <code class="computeroutput"><span class="special"><</span><span class="identifier">cstdfloat</span><span class="special">></span></code>. They will be defined in the <code class="computeroutput"><span class="identifier">std</span></code> namespace.
+ having specified widths are to be contained in a <span class="bold"><strong>new
+ standard library header <code class="computeroutput"><span class="special"><</span><span class="identifier">cstdfloat</span><span class="special">></span></code></strong></span>. They will be defined in the
+ <code class="computeroutput"><span class="identifier">std</span></code> namespace.
</p>
<p>
<span class="bold"><strong>New C-style macros to facilitate initialization</strong></span>
Modified: sandbox/precision/libs/precision/doc/html/precision/introduction.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/introduction.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/introduction.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -55,7 +55,7 @@
<p>
It is, however, emphasized that floating-point adherence to <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
floating-point format</a> is not mandated by the current C++ language standard.
- Nor does the standard specify the width, precision or lyaout of its built-in
+ Nor does the standard specify the width, precision or layout of its built-in
types <code class="computeroutput"><span class="keyword">float</span></code>, <code class="computeroutput"><span class="keyword">double</span></code>,
and <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></code>.
This can lead to portability problems, introduce poor efficiency on cost-sensitive
Modified: sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -70,7 +70,8 @@
<code class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></code>
or an implementation-dependent type) conforms with one of <code class="computeroutput"><span class="identifier">binary16</span></code>,
<code class="computeroutput"><span class="identifier">binary32</span></code>, <code class="computeroutput"><span class="identifier">binary64</span></code>,
- or <code class="computeroutput"><span class="identifier">binary128</span></code> in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ or <code class="computeroutput"><span class="identifier">binary128</span></code>, or the prescribed
+ method of precision extension in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
floating-point format</a>.
</p></td></tr>
</table></div>
Modified: sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -46,9 +46,9 @@
a 24-bit floating-point type. Here, an extension of the optional floating-point
<code class="computeroutput"><span class="keyword">typedef</span></code>s with specified widths
could include <code class="computeroutput"><span class="identifier">float24_t</span></code>. This
- would be equivalent to three-quarter precision floating-point, which is not
- specified in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
- floating-point format</a>.
+ would be equivalent to three-quarter precision floating-point, the layout of
+ which should adhere to the method of precision extension specified in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_ floating-point
+ format</a>.
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
Modified: sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -125,6 +125,24 @@
<span class="special">==</span> <span class="keyword">true</span></code>,
and the byte-order.
</p>
+<div class="note"><table border="0" summary="Note">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
+<th align="left">Note</th>
+</tr>
+<tr><td align="left" valign="top"><p>
+ <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_ floating-point
+ format</a> prescribes a method of precision extension, that allows for
+ conforming types other than <code class="computeroutput"><span class="identifier">binary16</span></code>,
+ <code class="computeroutput"><span class="identifier">binary32</span></code>, <code class="computeroutput"><span class="identifier">binary64</span></code>,
+ and <code class="computeroutput"><span class="identifier">binary128</span></code>. Furthermore,
+ paragraph 3.7 in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a> states: <span class="bold"><strong>Language standards
+ should define mechanisms supporting extendable precision for each supported
+ radix</strong></span>. This proposal embodies a potential way for C++ to adhere
+ to this requirement.
+ </p></td></tr>
+</table></div>
<p>
We will now consider several examples showing how various implementations might
introduce some of the optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
Modified: sandbox/precision/libs/precision/doc/html/precision/version_id.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/version_id.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/version_id.html 2013-03-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -26,7 +26,7 @@
<a name="precision.version_id"></a><a class="link" href="version_id.html" title="Version Info">Version Info</a>
</h2></div></div></div>
<p>
- Last edit to Quickbook file precision.qbk was at 12:32:13 PM on 2013-Mar-29.
+ Last edit to Quickbook file precision.qbk was at 03:27:44 PM on 2013-Mar-30.
</p>
<div class="tip"><table border="0" summary="Tip">
<tr>
Modified: sandbox/precision/libs/precision/doc/precision.pdf
==============================================================================
Binary files. No diff available.
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-30 11:31:20 EDT (Sat, 30 Mar 2013)
@@ -117,7 +117,7 @@
It is, however, emphasized that floating-point adherence
to __IEEE_floating_point is not mandated by the current C++ language standard.
-Nor does the standard specify the width, precision or lyaout of its built-in types
+Nor does the standard specify the width, precision or layout of its built-in types
`float`, `double`, and `long double`. This can lead to portability problems,
introduce poor efficiency on cost-sensitive microcontroller architectures,
and reduce reliability and safety.
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk