Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r83621 - in sandbox/precision/libs/precision/doc: . html html/precision
From: pbristow_at_[hidden]
Date: 2013-03-28 07:55:06

Next message: pbristow_at_[hidden]: "[Boost-commit] svn:boost r83622 - sandbox/precision/libs/precision/doc/html/precision"
Previous message: john_at_[hidden]: "[Boost-commit] svn:boost r83620 - trunk/libs/math/example"

Author: pbristow
Date: 2013-03-28 07:55:05 EDT (Thu, 28 Mar 2013)
New Revision: 83621
URL: http://svn.boost.org/trac/boost/changeset/83621

Log:
Bits of bolding added, no significant changes, ready for release for Boosters comments.
Binary files modified:
   sandbox/precision/libs/precision/doc/precision.pdf
Text files modified:
   sandbox/precision/libs/precision/doc/html/index.html | 14 ++++----------
   sandbox/precision/libs/precision/doc/html/precision/abstract.html | 27 ++++++++++-----------------
   sandbox/precision/libs/precision/doc/html/precision/introduction.html | 10 ++++------
   sandbox/precision/libs/precision/doc/html/precision/version_id.html | 2 +-
   sandbox/precision/libs/precision/doc/precision.qbk | 28 +++++++++++++++-------------
   5 files changed, 34 insertions(+), 47 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-28 07:55:05 EDT (Thu, 28 Mar 2013)
@@ -67,18 +67,12 @@

ISO/IEC JTC1 SC22 WG21/SG6 Numerics N??? - 2013-4-??

-<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">
- Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.
- </td></tr>
-</table></div>
+
+ Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: March 27, 2013 at 12:48:57 GMT</td>
+<td align="left">Last revised: March 28, 2013 at 11:52:10 GMT</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-28 07:55:05 EDT (Thu, 28 Mar 2013)
@@ -27,8 +27,10 @@
<a name="precision.abstract"></a><a class="link" href="abstract.html" title="Abstract">Abstract</a>
</h2></div></div></div>

- It is proposed to add to the C++ standard optional floating-point <code class="computeroutput">typedef</code>s having specified width. The optional
- <code class="computeroutput">typedef</code>s include <code class="computeroutput">float16_t</code>, <code class="computeroutput">float32_t</code>,
+ It is proposed to add to the C++ standard optional floating-point
+ <code class="computeroutput">typedef</code>s having specified width.
+ The optional <code class="computeroutput">typedef</code>s include
+ <code class="computeroutput">float16_t</code>, <code class="computeroutput">float32_t</code>,
 <code class="computeroutput">float64_t</code>, <code class="computeroutput">float128_t</code>,
 their corresponding fast and least types, and the corresponding maximum-width
 type. These are to conform with the corresponding specifications of <code class="computeroutput">binary16</code>, <code class="computeroutput">binary32</code>,
@@ -41,22 +43,13 @@
 <code class="computeroutput"><cstdfloat></code>. They will be defined in the <code class="computeroutput">std</code> namespace.
 

- It is not proposed to make any changes to <code class="computeroutput"><cmath></code>,
- special functions, <code class="computeroutput"><limits></code>, or <code class="computeroutput"><complex></code>.
- Any of the optional floating-point <code class="computeroutput">typedef</code>s
- having specified width that are <code class="computeroutput">typedef</code>ed
- from the built-in types <code class="computeroutput">float</code>,
- <code class="computeroutput">double</code>, and <code class="computeroutput">long
- double</code> should automatically be supported
- by the implementation's existing <code class="computeroutput"><cmath></code>,
- special functions, <code class="computeroutput"><limits></code>, and <code class="computeroutput"><complex></code>.
- Support for other <code class="computeroutput">typedef</code>s is
- implementation-defined.
+ New C-style macros to facilitate initialization
+ of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width from a floating-point literal constant are proposed.
 

- New C-style macros are proposed to facilitate initialization of the optional
- floating-point <code class="computeroutput">typedef</code>s having
- specified width from a floating-point literal constant.
+ It is not proposed to make any mandatory changes to <code class="computeroutput"><cmath></code>,
+ special functions, <code class="computeroutput"><limits></code>, or <code class="computeroutput"><complex></code>.
 

 The main objectives of this proposal are to:
@@ -72,7 +65,7 @@
 on all platforms.
 </li>
<li class="listitem">
- Optionally extend the range of floating-point to lower and higher precision.
+ Optionally extend the range of floating-point to lower and to higher precision.
 </li>
<li class="listitem">
 Provide a Standard way of specifying 128-bit precision.

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-28 07:55:05 EDT (Thu, 28 Mar 2013)
@@ -62,15 +62,13 @@
 microcontroller architectures, and reduce reliability and safety.
 

- This situation reveals a need for a standard way to specify floating-point
- precision in C++.
+ This situation reveals a need for a standard way to specify
+ floating-point precision in C++.
 

 It may also be desirable to extend floating-point precision to both lower and
- higher precisions. This can be done by including implementation-specific optional
- floating-point <code class="computeroutput">typedef</code>s having
- specified width that are not derived from <code class="computeroutput">float</code>,
- <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ higher precisions. This can be done by including implementation-specific <code class="computeroutput">typedef</code>s having specified width that are not
+ derived from <code class="computeroutput">float</code>, <code class="computeroutput">double</code>, and <code class="computeroutput">long
 double</code>.

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-28 07:55:05 EDT (Thu, 28 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>

- Last edit to Quickbook file precision.qbk was at 12:48:57 PM on 2013-Mar-27.
+ Last edit to Quickbook file precision.qbk was at 11:52:10 AM on 2013-Mar-28.

<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-28 07:55:05 EDT (Thu, 28 Mar 2013)
@@ -15,6 +15,8 @@

ISO/IEC JTC1 SC22 WG21/SG6 Numerics N??? - 2013-4-??

+Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.
+
[def __Boost [@http://www.boost.org/ Boost]]
[def __Boost_Math [@http://www.boost.org/doc/libs/1_53_0/libs/math/doc/html/index.html Boost.Math]]
[def __gsl [@http://www.gnu.org/software/gsl/ GSL-1.9]]
@@ -53,12 +55,12 @@

[include html4_symbols.qbk]

-[note Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.]
+[/note Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.]

[section:abstract Abstract]

It is proposed to add to the C++ standard
-optional floating-point `typedef`s having specified width.
+[*optional floating-point `typedef`s having specified width].
The optional `typedef`s include
`float16_t`, `float32_t`, `float64_t`, `float128_t`,
their corresponding fast and least types,
@@ -71,9 +73,9 @@
are to be contained in a new standard library header `<cstdfloat>`.
They will be defined in the `std` namespace.

-New C-style macros are proposed to facilitate initialization
+[*New C-style macros to facilitate initialization]
of the optional floating-point `typedef`s having specified width
-from a floating-point literal constant.
+from a floating-point literal constant are proposed.

It is not proposed to make any mandatory changes to `<cmath>`,
special functions, `<limits>`, or `<complex>`.
@@ -82,7 +84,7 @@

* Extend the benefits of specified-width typedefs for integer types to floating-point types.
* Improve floating-point safety and reliability by providing standardized `typedef`s that behave identically on all platforms.
-* Optionally extend the range of floating-point to lower and higher precision.
+* Optionally extend the range of floating-point to lower and to higher precision.
* Provide a Standard way of specifying 128-bit precision.

[endsect] [/section:abstract Abstract]
@@ -120,8 +122,8 @@
introduce poor efficiency on cost-sensitive microcontroller architectures,
and reduce reliability and safety.

-This situation reveals a need for a standard way to specify
-floating-point precision in C++.
+[*This situation reveals a need for a standard way to specify
+floating-point precision in C++.]

It may also be desirable to extend floating-point precision to
both lower and higher precisions. This can be done by including
@@ -331,7 +333,7 @@
#include <cstdfloat>

static_assert(FLOATMAX_MAX > (std::numeric_limits<float>::max)(),
- "The floating-point range is too small");
+ "The floating-point range is too small.");

[endsect] [/section:literals Handling floating-point literals]

@@ -418,8 +420,8 @@
be supported by `<cmath>` and special functions.
This is considered an implementation detail.

-[note Support of elementary functions and possibly some special functions,
-even where only optional, can be quite useful for real-life computational regimes.]
+[note Support of elementary functions (and possibly some special functions,
+even where only optional) can be very useful for real-life computational regimes.]

[endsect] [/section:cmathinterop Interoperation with <cmath> and special functions]

@@ -437,8 +439,8 @@
be supported by `<limits>`.
This is considered an implementation detail.

-[note Support for `<limits>`, even where optional, can be quite
-useful. This allows programs to query the floating-point limits
+[note Support for `<limits>`, even where optional, can be very
+useful, especially for portability. This allows programs to query the floating-point limits
at compile-time and use, among other things, `std::numeric_limits<>::is_iec559`
to verify conformance with __IEEE_floating_point.]

@@ -461,7 +463,7 @@
the implementation's existing `<complex>`.

Implementation-specific optional floating-point `typedef`s having specified width
-that are not derived from `float`, `double`, and `long double` can optionally
+that are ['not derived from `float`, `double`, and `long double`] can optionally
be supported by `<complex>`.
This is considered an implementation detail.

Next message: pbristow_at_[hidden]: "[Boost-commit] svn:boost r83622 - sandbox/precision/libs/precision/doc/html/precision"
Previous message: john_at_[hidden]: "[Boost-commit] svn:boost r83620 - trunk/libs/math/example"

Date view	Thread view	Subject view	Author view

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