Subject: [Boost-commit] svn:boost r68953 - trunk/libs/chrono/doc
Date: 2011-02-16 13:09:22
Date: 2011-02-16 13:09:15 EST (Wed, 16 Feb 2011)
New Revision: 68953
Chrono: update doc
Binary files modified:
Text files modified:
trunk/libs/chrono/doc/Jamfile.v2 | 3 ++-
trunk/libs/chrono/doc/chrono.qbk | 29 ++++++++++++++++++++---------
2 files changed, 22 insertions(+), 10 deletions(-)
--- trunk/libs/chrono/doc/Jamfile.v2 (original)
+++ trunk/libs/chrono/doc/Jamfile.v2 2011-02-16 13:09:15 EST (Wed, 16 Feb 2011)
@@ -68,8 +68,9 @@
# default pnd graphics are awful in PDF form,
# better use SVG's instead:
install pdf-install : standalone : <location>. <install-type>PDF ;
Binary files. No diff available.
--- trunk/libs/chrono/doc/chrono.qbk (original)
+++ trunk/libs/chrono/doc/chrono.qbk 2011-02-16 13:09:15 EST (Wed, 16 Feb 2011)
@@ -408,6 +408,14 @@
* GCC 4.6.0
* GCC 4.6.0 -std=c++0x
+* GCC 4.4.5
+* GCC 4.4.5 -std=c++0x
+* GCC 4.5.1
+* GCC 4.5.1 -std=c++0x
+* clang 2.8
Initial versions were tested on:
MacOS with GCC 4.2.4 (Some test are needed for the specific Mac files).
@@ -654,6 +662,14 @@
In summary, the author of f has quite a bit of flexibility and control in the interface he wants to provide his clients with, and easy options for manipulating that __duration internal to his function.
+[section Is it possible for the user to pass a __duration to a function with the units being ambiguous?]
+No. No matter which option the author of `f` chooses above, the following client code will not compile:
+ f(3); // Will not compile, 3 is not implicitly convertible to any __duration
[section Can Durations Overflow?]
This depend on the representation. The default typedefs uses a representation that don't handle overflows. The user can define his own representation that manage overflow as required by its application.
@@ -3854,7 +3870,7 @@
* Fix some warnings.
* Fix original errors on Mac
-* Dont fix the link with boost_system to static.
+* Don't fix the link with boost_system to static.
@@ -3864,10 +3880,11 @@
-* Removed some not useful parts as the history, the test and the tickets.
+* Removed some not useful parts as the test and the tickets.
[endsect] [/section [*Version 1.0.0, January 6, 2011] ]
[section [*Version 0.6.0, September 22, 2010] ]
@@ -4155,12 +4172,6 @@
See [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2661.htm [*N2661 - A Foundation to Sleep On]] which is very informative and provides motivation for key design decisions. This section contains some extracts from this document.
-[heading Is it possible for the user to pass a __duration to a function with the units being ambiguous?]
-No. No matter which option the author of `f` chooses above, the following client code will not compile:
- f(3); // Will not compile, 3 is not implicitly convertible to any __duration
[heading Why duration needs operator%]
This operator is convenient for computing where in a time frame a given duration lies. A motivating example is converting a duration into a "broken-down" time duration such as hours::minutes::seconds:
@@ -4530,7 +4541,7 @@
[heading For later releases]
-* Add chrono utilities as defined By Howard Hinnant in [@http://home.roadrunner.com/~hinnant/duration_io/chrono_util.html here].
+* Add chrono utilities as defined By Howard Hinnant [@http://home.roadrunner.com/~hinnant/duration_io/chrono_util.html here].
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