Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r65384 - in sandbox/chrono/libs/chrono/doc: . html html/boost_chrono/appendices html/boost_chrono/reference html/boost_chrono/users_guide
From: vicente.botet_at_[hidden]
Date: 2010-09-11 08:45:38

Next message: asutton_at_[hidden]: "[Boost-commit] svn:boost r65385 - in trunk/boost/graph: . detail"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r65383 - in sandbox/chrono/libs/ratio/doc: . html"

Author: viboes
Date: 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
New Revision: 65384
URL: http://svn.boost.org/trac/boost/changeset/65384

Log:
update doc
Text files modified:
   sandbox/chrono/libs/chrono/doc/chrono.qbk | 53 ++++++++++++++++--------
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/faq.html | 12 ++--
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/rationale.html | 8 +-
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/todo.html | 4
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/cpp0x.html | 85 +++++++++++++++++++++++++++++----------
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/tutorial.html | 6 +-
   sandbox/chrono/libs/chrono/doc/html/index.html | 2
   7 files changed, 114 insertions(+), 56 deletions(-)

Modified: sandbox/chrono/libs/chrono/doc/chrono.qbk
==============================================================================
--- sandbox/chrono/libs/chrono/doc/chrono.qbk (original)
+++ sandbox/chrono/libs/chrono/doc/chrono.qbk 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -709,7 +709,7 @@
 cout << "f() took " << sec.count() << " seconds\n";
 }

-Note that if one is using the __duration__ between two clock __time_point_s__ in a way where the precision of the __duration__ matters, it is good practice to convert the clock's native __duration__ to a known __duration__. This insulates the code from future changes which may be made to the clock's native precision in the future. For example monotonic_clock could easily be based on the clock speed of the cpu. When you upgrade to a faster machine, you do not want your code that assumed a certain tick period of this clock to start experiencing run time failures because your timing code has silently changed meaning.
+Note that if one is using the __duration__ between two clock __time_point_s__ in a way where the precision of the __duration__ matters, it is good practice to convert the clock's __duration__ to a known __duration__. This insulates the code from future changes which may be made to the clock's precision in the future. For example monotonic_clock could easily be based on the clock speed of the cpu. When you upgrade to a faster machine, you do not want your code that assumed a certain tick period of this clock to start experiencing run time failures because your timing code has silently changed meaning.

A delay loop example:

@@ -1615,8 +1615,25 @@
 #include <boost/chrono/duration.hpp>
 #include <boost/chrono/time_point.hpp>
 #include <boost/chrono/system_clocks.hpp>
+ #include <boost/chrono/process_cpu_clocks.hpp>
+ #include <boost/chrono/thread_clock.hpp>
 #include <boost/chrono/typeof/boost/chrono/chrono.hpp>

+[section:limitations Limitations and Extensions]
+
+Next follows limitation respect to the C++0x recomendations:
+
+* [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3135.html#1121 Ratio values should be constexpr]: `constexpr` don't used as no compiler supports it today. `const` is used instead when appropiated.
+
+* [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3134.html#921 Rational Arithmetic should use template aliases]: In the absence of compiler support of template aliases the C++03 emulation define a nested typedef `type`.
+
+The current implementation provides in addition:
+
+* clock error handling as specified in [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3135.html#3155 clock error handling needs to be specified].
+
+
+[endsect]
+
[section:conf Configuration macros]

@@ -1670,47 +1687,47 @@
 // duration arithmetic
 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<duration<Rep1, Period1>, duration<Rep2, Period2> >::type
- operator+(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator+(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<duration<Rep1, Period1>, duration<Rep2, Period2> >::type
- operator-(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator-(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator*(const duration<Rep1, Period>& d, const Rep2& s);
+ BOOST_CHRONO_CONSTEXPR operator*(const duration<Rep1, Period>& d, const Rep2& s);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator*(const Rep1& s, const duration<Rep2, Period>& d);
+ BOOST_CHRONO_CONSTEXPR operator*(const Rep1& s, const duration<Rep2, Period>& d);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator/(const duration<Rep1, Period>& d, const Rep2& s);
+ BOOST_CHRONO_CONSTEXPR operator/(const duration<Rep1, Period>& d, const Rep2& s);

 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<Rep1, Rep2>::type
- operator/(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator/(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Rep2, class Period>
- double operator/(const Rep1& s, const duration<Rep2, Period>& d);
+ BOOST_CHRONO_CONSTEXPR double operator/(const Rep1& s, const duration<Rep2, Period>& d);

 // duration comparisons
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator!=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator!=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator< (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator< (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator<=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator<=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator> (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator> (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator>=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator>=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 // duration_cast

@@ -2235,16 +2252,16 @@

[section:clock `Clock` Requirements]

-A clock represents a bundle consisting of a native __duration__, a native __time_point__, and a function `now()` to get the current __time_point__. A clock must meet the requirements in the following Table.
+A clock represents a bundle consisting of a __duration__, a __time_point__, and a function `now()` to get the current __time_point__. A clock must meet the requirements in the following Table.

In this table `C1` and `C2` denote `clock` types. `t1` and `t2` are values returned from `C1::now()` where the call returning `t1` happens before the call returning `t2` and both of these calls happen before `C1::time_point::max()`.

[table Clock Requirements
 [[expression] [return type] [operational semantics]]
- [[`C1::rep`] [An arithmetic type or class emulating an arithmetic type. ] [The representation type of the native __duration__ and __time_point__.]]
+ [[`C1::rep`] [An arithmetic type or class emulating an arithmetic type. ] [The representation type of the __duration__ and __time_point__.]]
 [[`C1::period`] [`ratio`] [The tick period of the clock in seconds.]]
- [[`C1::duration`] [`chrono::duration<C1::rep, C1::period>`] [The native __duration__ type of the `clock`.]]
- [[`C1::time_point`] [`chrono::time_point<C1> or chrono::time_point<C2, C1::duration>`] [The native __time_point__ type of the `clock`. Different clocks are permitted to share a __time_point__ definition if it is valid to compare their time_points by comparing their respective __duration_s__. `C1` and `C2` must refer to the same epoch.]]
+ [[`C1::duration`] [`chrono::duration<C1::rep, C1::period>`] [The __duration__ type of the `clock`.]]
+ [[`C1::time_point`] [`chrono::time_point<C1> or chrono::time_point<C2, C1::duration>`] [The __time_point__ type of the `clock`. Different clocks are permitted to share a __time_point__ definition if it is valid to compare their time_points by comparing their respective __duration_s__. `C1` and `C2` must refer to the same epoch.]]
 [[`C1::is_monotonic`] [`const bool`] [`true` if `t1 <= t2` is always `true`, else `false`. *Note*: A `clock` that can be adjusted backwards is not monotonic]]
 [[`C1::now()`] [`C1::time_point`] [Returns a __time_point__ representing the current point in time.]]
]

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/faq.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/faq.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/faq.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -29,7 +29,7 @@
<a name="boost_chrono.appendices.faq"></a> Appendix D: FAQ
</h3></div></div></div>
<a name="boost_chrono.appendices.faq.how_important_is_the_order_of_the___code__phrase_role__identifier__common_type__phrase___code__lt__gt__template_arguments_"></a><h4>
-<a name="id5063392"></a>
+<a name="id5063682"></a>
 <a href="faq.html#boost_chrono.appendices.faq.how_important_is_the_order_of_the___code__phrase_role__identifier__common_type__phrase___code__lt__gt__template_arguments_">How
 important is the order of the <code class="computeroutput">common_type</code><>
 template arguments?</a>
@@ -62,7 +62,7 @@
 is also undefined.
 
<a name="boost_chrono.appendices.faq.why_does_stopwatch_reporter_only_display_millisecond_place_precision_when_the_underlying_clock_has_nanosecond_precision_"></a><h4>
-<a name="id5063890"></a>
+<a name="id5064180"></a>
 <a href="faq.html#boost_chrono.appendices.faq.why_does_stopwatch_reporter_only_display_millisecond_place_precision_when_the_underlying_clock_has_nanosecond_precision_">Why
 does stopwatch_reporter only display millisecond place precision when the
 underlying Clock has nanosecond precision?</a>
@@ -73,7 +73,7 @@
 dangerously.
 
<a name="boost_chrono.appendices.faq.why_does_stopwatch_reporter_sometimes_report_more_cpu_seconds_than_real_seconds_"></a><h4>
-<a name="id5063930"></a>
+<a name="id5064219"></a>
 <a href="faq.html#boost_chrono.appendices.faq.why_does_stopwatch_reporter_sometimes_report_more_cpu_seconds_than_real_seconds_">Why
 does stopwatch_reporter sometimes report more cpu seconds than real seconds?</a>
 </h4>
@@ -83,7 +83,7 @@
 be reporting at times.
 
<a name="boost_chrono.appendices.faq.can_i_obtain_statistics_of_the_time_elapsed_between_calls_to_a_function_"></a><h4>
-<a name="id5063963"></a>
+<a name="id5064252"></a>
 <a href="faq.html#boost_chrono.appendices.faq.can_i_obtain_statistics_of_the_time_elapsed_between_calls_to_a_function_">Can
 I obtain statistics of the time elapsed between calls to a function?</a>
 </h4>
@@ -91,13 +91,13 @@
 The library do not provides this feature.
 
<a name="boost_chrono.appendices.faq.what_happens_if_i_press_ctrl_c_and_program_terminates__what_log_would_boost_chrono_output_"></a><h4>
-<a name="id5063991"></a>
+<a name="id5064280"></a>
 <a href="faq.html#boost_chrono.appendices.faq.what_happens_if_i_press_ctrl_c_and_program_terminates__what_log_would_boost_chrono_output_">What
 happens if I press Ctrl+C and program terminates? What log would Boost.chrono
 output?</a>
 </h4>
<a name="boost_chrono.appendices.faq.can_you_explain_the_pros_cons_of___code__phrase_role__identifier__common_type__phrase___code__against_boost_typeof_"></a><h4>
-<a name="id5064019"></a>
+<a name="id5064308"></a>
 <a href="faq.html#boost_chrono.appendices.faq.can_you_explain_the_pros_cons_of___code__phrase_role__identifier__common_type__phrase___code__against_boost_typeof_">Can
 you explain the pros/cons of <code class="computeroutput">common_type</code>
 against Boost.Typeof?</a>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/rationale.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/rationale.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/rationale.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -33,7 +33,7 @@
 are an extract from this document.
 
<a name="boost_chrono.appendices.rationale.is_it_possible_for_the_user_to_pass_a___link_linkend__boost_chrono_reference_cpp0x_duration_hpp_duration___code__phrase_role__identifier__duration__phrase___code___link__to_a_function_with_the_units_being_ambiguous_"></a><h4>
-<a name="id5062089"></a>
+<a name="id5062378"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.is_it_possible_for_the_user_to_pass_a___link_linkend__boost_chrono_reference_cpp0x_duration_hpp_duration___code__phrase_role__identifier__duration__phrase___code___link__to_a_function_with_the_units_being_ambiguous_">Is
 it possible for the user to pass a <a href="../reference/cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a> to a function with the
@@ -46,7 +46,7 @@
<pre class="programlisting">f(3); // Will not compile, 3 is not implicitly convertible to any __duration__
</pre>
<a name="boost_chrono.appendices.rationale.why_duration_needs_operator_"></a><h4>
-<a name="id5062187"></a>
+<a name="id5062476"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.why_duration_needs_operator_">Why
 duration needs operator%</a>
 </h4>
@@ -74,7 +74,7 @@
};
</pre>
<a name="boost_chrono.appendices.rationale.why_ratio_needs_copyconstruction_and_assignment_from_ratios_having_the_same_normalized_form"></a><h4>
-<a name="id5062767"></a>
+<a name="id5063057"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.why_ratio_needs_copyconstruction_and_assignment_from_ratios_having_the_same_normalized_form">Why
 ratio needs CopyConstruction and Assignment from ratios having the same normalized
 form</a>
@@ -102,7 +102,7 @@
 and the compilation succeeds.
 
<a name="boost_chrono.appendices.rationale.why_ratio_needs_the_nested_normalizer_typedef_type"></a><h4>
-<a name="id5063137"></a>
+<a name="id5063426"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.why_ratio_needs_the_nested_normalizer_typedef_type">Why
 ratio needs the nested normalizer typedef type</a>
 </h4>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/todo.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/todo.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/todo.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -26,7 +26,7 @@
<a name="boost_chrono.appendices.todo"></a> Appendix H: Future plans
</h3></div></div></div>
<a name="boost_chrono.appendices.todo.tasks_to_do_before_review"></a><h4>
-<a name="id5066412"></a>
+<a name="id5066565"></a>
 <a href="todo.html#boost_chrono.appendices.todo.tasks_to_do_before_review">Tasks
 to do before review</a>
 </h4>
@@ -42,7 +42,7 @@
 </li>
</ul></div>
<a name="boost_chrono.appendices.todo.for_later_releases"></a><h4>
-<a name="id5066461"></a>
+<a name="id5066614"></a>
 <a href="todo.html#boost_chrono.appendices.todo.for_later_releases">For later
 releases</a>
 </h4>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/cpp0x.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/cpp0x.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/cpp0x.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -31,8 +31,12 @@
</h3></div></div></div>
<div class="toc"><dl>
<dt> Header <boost/chrono.hpp></dt>
-<dd><dl><dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.conf"> Configuration
- macros</a></dt></dl></dd>
+<dd><dl>
+<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.limitations">
+ Limitations and Extensions</a></dt>
+<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.conf"> Configuration
+ macros</a></dt>
+</dl></dd>
<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp"> Header
 <code class="computeroutput"><boost/chrono/duration.hpp></code></a></dt>
<dd><dl>
@@ -81,15 +85,52 @@
<div class="titlepage"><div><div><h4 class="title">
<a name="boost_chrono.reference.cpp0x.chrono_hpp"></a> Header <boost/chrono.hpp>
</h4></div></div></div>
-<div class="toc"><dl><dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.conf"> Configuration
- macros</a></dt></dl></div>
+<div class="toc"><dl>
+<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.limitations">
+ Limitations and Extensions</a></dt>
+<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.conf"> Configuration
+ macros</a></dt>
+</dl></div>
<pre class="programlisting">#include <boost/chrono/duration.hpp>
#include <boost/chrono/time_point.hpp>
#include <boost/chrono/system_clocks.hpp>
+#include <boost/chrono/process_cpu_clocks.hpp>
+#include <boost/chrono/thread_clock.hpp>
#include <boost/chrono/typeof/boost/chrono/chrono.hpp>
</pre>
<div class="section" lang="en">
<div class="titlepage"><div><div><h5 class="title">
+<a name="boost_chrono.reference.cpp0x.chrono_hpp.limitations"></a><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.limitations" title="
+ Limitations and Extensions">
+ Limitations and Extensions</a>
+</h5></div></div></div>
+
+ Next follows limitation respect to the C++0x recomendations:
+ 
+<div class="itemizedlist"><ul type="disc">
+<li>
+ <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3135.html#1121" target="_top">Ratio
+ values should be constexpr</a>: <code class="computeroutput">constexpr</code>
+ don't used as no compiler supports it today. <code class="computeroutput">const</code>
+ is used instead when appropiated.
+ </li>
+<li>
+ <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3134.html#921" target="_top">Rational
+ Arithmetic should use template aliases</a>: In the absence of
+ compiler support of template aliases the C++03 emulation define a
+ nested typedef <code class="computeroutput">type</code>.
+ </li>
+</ul></div>
+
+ The current implementation provides in addition:
+ 
+<div class="itemizedlist"><ul type="disc"><li>
+ clock error handling as specified in <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3135.html#3155" target="_top">clock
+ error handling needs to be specified</a>.
+ </li></ul></div>
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h5 class="title">
<a name="boost_chrono.reference.cpp0x.chrono_hpp.conf"></a><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_hpp.conf" title=" Configuration
 macros"> Configuration
 macros</a>
@@ -178,47 +219,47 @@
 // duration arithmetic
 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<duration<Rep1, Period1>, duration<Rep2, Period2> >::type
- operator+(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator+(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<duration<Rep1, Period1>, duration<Rep2, Period2> >::type
- operator-(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator-(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator*(const duration<Rep1, Period>& d, const Rep2& s);
+ BOOST_CHRONO_CONSTEXPR operator*(const duration<Rep1, Period>& d, const Rep2& s);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator*(const Rep1& s, const duration<Rep2, Period>& d);
+ BOOST_CHRONO_CONSTEXPR operator*(const Rep1& s, const duration<Rep2, Period>& d);

 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
- operator/(const duration<Rep1, Period>& d, const Rep2& s);
+ BOOST_CHRONO_CONSTEXPR operator/(const duration<Rep1, Period>& d, const Rep2& s);

 template <class Rep1, class Period1, class Rep2, class Period2>
 typename common_type<Rep1, Rep2>::type
- operator/(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR operator/(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Rep2, class Period>
- double operator/(const Rep1& s, const duration<Rep2, Period>& d);
+ BOOST_CHRONO_CONSTEXPR double operator/(const Rep1& s, const duration<Rep2, Period>& d);

 // duration comparisons
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator!=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator!=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator< (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator< (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator<=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator<=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator> (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator> (const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
 template <class Rep1, class Period1, class Rep2, class Period2>
- bool operator>=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
+ BOOST_CHRONO_CONSTEXPR bool operator>=(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);

 // duration_cast

@@ -1352,8 +1393,8 @@
<a name="boost_chrono.reference.cpp0x.clock"></a> Clock Requirements
</h4></div></div></div>

- A clock represents a bundle consisting of a native <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
- Class template duration<>"><code class="computeroutput">duration</code></a>, a native <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
+ A clock represents a bundle consisting of a <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
+ Class template duration<>"><code class="computeroutput">duration</code></a>, a <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
 Class template time_point<>"><code class="computeroutput">time_point</code></a>, and a function <code class="computeroutput">now()</code>
 to get the current <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
 Class template time_point<>"><code class="computeroutput">time_point</code></a>. A clock must meet
@@ -1405,7 +1446,7 @@
 </td>
<td>
 
- The representation type of the native <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
+ The representation type of the <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a> and <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
 Class template time_point<>"><code class="computeroutput">time_point</code></a>.
 
@@ -1442,7 +1483,7 @@
 </td>
<td>
 
- The native <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
+ The <a href="cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a> type of the
 <code class="computeroutput">clock</code>.
 
@@ -1462,7 +1503,7 @@
 </td>
<td>
 
- The native <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
+ The <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="
 Class template time_point<>"><code class="computeroutput">time_point</code></a> type of the
 <code class="computeroutput">clock</code>. Different
 clocks are permitted to share a <a href="cpp0x.html#boost_chrono.reference.cpp0x.time_point_hpp.time_point" title="

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/tutorial.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/tutorial.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/tutorial.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -704,11 +704,11 @@
 Class template time_point<>"><code class="computeroutput">time_point</code>'s</a> in a way where
 the precision of the <a href="../reference/cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a> matters, it is good
- practice to convert the clock's native <a href="../reference/cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
+ practice to convert the clock's <a href="../reference/cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a> to a known <a href="../reference/cpp0x.html#boost_chrono.reference.cpp0x.duration_hpp.duration" title="
 Class template duration<>"><code class="computeroutput">duration</code></a>. This insulates the
- code from future changes which may be made to the clock's native precision
- in the future. For example monotonic_clock could easily be based on the
+ code from future changes which may be made to the clock's precision in
+ the future. For example monotonic_clock could easily be based on the
 clock speed of the cpu. When you upgrade to a faster machine, you do
 not want your code that assumed a certain tick period of this clock to
 start experiencing run time failures because your timing code has silently

Modified: sandbox/chrono/libs/chrono/doc/html/index.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/index.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/index.html 2010-09-11 08:45:34 EDT (Sat, 11 Sep 2010)
@@ -94,7 +94,7 @@
</table></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: September 10, 2010 at 15:11:47 GMT</td>
+<td align="left">Last revised: September 11, 2010 at 12:40:52 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Next message: asutton_at_[hidden]: "[Boost-commit] svn:boost r65385 - in trunk/boost/graph: . detail"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r65383 - in sandbox/chrono/libs/ratio/doc: . html"

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