Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r59262 - in sandbox/chrono/libs/chrono: doc doc/html doc/html/boost_chrono doc/html/boost_chrono/appendices doc/html/boost_chrono/overview doc/html/boost_chrono/reference doc/html/boost_chrono/users_guide example test
From: vicente.botet_at_[hidden]
Date: 2010-01-24 18:54:08

Next message: emil_at_[hidden]: "[Boost-commit] svn:boost r59263 - trunk/libs/exception/test"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r59261 - sandbox/chrono/boost/chrono"

Author: viboes
Date: 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
New Revision: 59262
URL: http://svn.boost.org/trac/boost/changeset/59262

Log:
Boost.Chrono: Version 0.3.2,
* updated documentation
* added test_thread_clock.cpp
* added suspendible_stopclock_example.cpp
Added:
   sandbox/chrono/libs/chrono/example/suspendible_stopclock_example.cpp (contents, props changed)
   sandbox/chrono/libs/chrono/test/test_thread_clock.cpp (contents, props changed)
Text files modified:
   sandbox/chrono/libs/chrono/doc/chrono.qbk | 287 ++++++++++++++++++++++++-------
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices.html | 4
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/faq.html | 14 +
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/history.html | 21 +-
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/rationale.html | 8
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/tickets.html | 56 +++++
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/todo.html | 29 --
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/overview/motivation.html | 2
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/cpp0x.html | 30 +++
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/other_clocks.html | 2
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_formatters.html | 20 +
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_reporters.html | 2
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatches.html | 2
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide.html | 10
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/getting_started.html | 22 +-
   sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/tutorial.html | 352 ++++++++++++++++++++++++++++++++++-----
   sandbox/chrono/libs/chrono/doc/html/index.html | 2
   sandbox/chrono/libs/chrono/example/specific_stopwatch_accumulator_example.cpp | 12 +
   sandbox/chrono/libs/chrono/test/Jamfile.v2 | 5
   19 files changed, 690 insertions(+), 190 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-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -436,9 +436,9 @@

Will produce the following output

-0.006s
-0.011s
-0.017s
+ 0.006s
+ 0.011s
+ 0.017s

The preceding stopwatch manage only with a measure. It is also interesting to have an statisitical view of these times, for example the sum, min, max and mean. `stopwatch_accumulator<>` associates an accumulator with a stopwatch, so we are able to retrieve any statistical feature Boost.Accumulator provides.

@@ -463,7 +463,7 @@

Will produce the following output

- 3 times, sum 0.034s, min 0.006s, max 0.017s, mean 0.011s
+ 3 times, sum=0.034s, min=0.006s, max=0.017s, mean=0.011s

It is also helpful if such timing information is broken down into real (wall clock) time, CPU time spent by the user, and CPU time spent by the operating system servicing user requests.

@@ -610,7 +610,7 @@

* MSVC 10.0
* MSVC 9.0 Express
-* MSVC 5.0
+* MSVC 8.0

[/* Intel 11.0]

@@ -656,12 +656,12 @@

Here is a complete program (stopclock_example.cpp):

- #include <boost/chrono/process_times.hpp>
+ #include <boost/chrono/stopclock.hpp>
 #include <cmath>

 int main()
 {
- boost::chrono::stopclockstopclock<> t;
+ boost::chrono::stopclock<> t;

 for ( long i = 0; i < 10000000; ++i )
 std::sqrt( 123.456L ); // burn some time
@@ -681,27 +681,57 @@

[section Tutorial]

-[section thread clock]
-[endsect]
-
[section How to define a thread clock]

+On posix systems for which the macro _POSIX_THREAD_CPUTIME is defined we can get the time associated to a specific thread.
+
 class thread_clock {
 public:
- typedef boost::intmax_t rep;
- typedef boost::chrono::nanoseconds period;
- typedef boost::chrono::duration<rep, period> duration;
- typedef boost::chrono::time_point<Clock> time_point;
- static const bool is_monotonic = true;
-
- static time_point now() {
- // get the current thread
- // get the clock_id associated to the current thread
- // get the clock_t associated to the thread clock
- // transform to nanoseconds
- }
- };
+ typedef nanoseconds duration;
+ typedef duration::rep rep;
+ typedef duration::period period;
+ typedef chrono::time_point<process_real_cpu_clock> time_point;
+ static const bool is_monotonic = true;

+ static time_point now( ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ boost::throw_exception(
+ system::system_error( errno, system::system_category, "chrono::thread_clock" ));
+ }
+
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+ static time_point now( system::error_code & ec ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ ec.assign( errno, system::system_category );
+ return time_point();
+ }
+ ec.clear();
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+ };
[endsect]

[section How can I prefix each report with `BOOST_CURRENT_FUNCTION` function signature?]
@@ -722,7 +752,7 @@
 static boost::chrono::stopclock_accumulator<> BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__)( \
 std::string(BOOST_CURRENT_FUNCTION) + ": " + boost::chrono::stopwatch_accumulator_formatter::default_format() \
 ); \
- boost::chrono::stopclock_accumulator<>::scoped_stop BOOST_JOIN(_boost_chrono_stopclock_accumulator_run_, __LINE__)(BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__))
+ boost::chrono::stopclock_accumulator<>::scoped_run BOOST_JOIN(_boost_chrono_stopclock_accumulator_run_, __LINE__)(BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__))

With this macro you will just ave
@@ -738,7 +768,7 @@

[section How can I prefix each report with `__FILE__[__LINE__]` pattern?]

-When you want to prefixx with the `__FILE__[__LINE__]` pattern you can follow the same technique as described below:
+When you want to prefix with the `__FILE__[__LINE__]` pattern you can follow the same technique as described below:

 #define REPORT_LINE_ACCUMULATED_LIFETIME \
 static stopclock_accumulator<> BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__)( \
@@ -760,6 +790,7 @@
 }

[endsect]
+
[section Can I use an stopclock accumulator which is not static?]

The typical example of stopclock_accumulator is to get statistical measures of the time a function takes for each one of its calls. You an also use stopclock_accumulator to get statistical measures of the time a given loop takes for each one of its laps.
@@ -795,14 +826,18 @@

[endsect]

-[section How get specific statistics from stopwatches accumulator]
+[section How to get specific statistics from stopwatches accumulator?]

- #include <boost/chrono/stopwatches.hpp>
- #include <cmath>
+There are two use cases that coul need to change the statistics associated to a stopwatches accumulator:
+
+# We want to reduce the default reporting and we preffer to adapt the statistics to the reporting
+# We want to report other statistics of the samples
+
+For the first case we just need to change the accumulator_set and the format we want to get. Imagin we want to get only the count, sam and mean statistics, no need to calculate the min neither the max.

- using namespace boost::chrono;
 using namespace boost::accumulators;
- typedef stopwatch_accumulator<process_real_cpu_clock, kind::running,
+
+ typedef stopwatch_accumulator<process_real_cpu_clock,
 accumulator_set<process_real_cpu_clock::rep,
 features<
 tag::count,
@@ -814,7 +849,7 @@

 int f1(long j)
 {
- static my_stopwatch_accumulator_reporter acc(BOOST_CHRONO_ACCUMULATOR_FUNCTION_FORMAT);
+ static my_stopwatch_accumulator_reporter acc("%c times, sum=%ss, mean=%as\n");
 my_stopwatch_accumulator_reporter::scoped_run _(acc);

 for ( long i = 0; i < j; ++i )
@@ -822,18 +857,104 @@

 return 0;
 }
- int main()
- {

- f1(100000);
- f1(200000);
- f1(300000);
- return 0;
- }
+But wat would hapend if we haven't forced the format:
+
+ static my_stopwatch_accumulator_reporter acc;
+ my_stopwatch_accumulator_reporter::scoped_run _(acc);
+
+Unfortunately there is no error at compile time. Fortunately, the run-time execution is not undefined and will return 0 for the missing statistics.
+

[endsect]

-[section How can I make a specific formatter when the defaul do not satisfy my expectations]
+[section How can I make a specific formatter when the default do not satisfy my expectations]
+
+Imagine then that we want to report the tag::variance(lazy). We will need to include the specific accumulator file
+
+ ...
+ #include <boost/accumulators/statistics/variance.hpp>
+ ...
+ typedef stopwatch_accumulator<process_real_cpu_clock,
+ accumulator_set<process_real_cpu_clock::rep,
+ features<
+ tag::count,
+ tag::sum,
+ tag::mean,
+ tag::variance(lazy)
+ >
+ >
+ >::reporter my_stopwatch_accumulator_reporter;
+
+But what happens if we add new statistics to the accumulator_set that are not taken in account by the default formatter? These statistics will simply be ignored. So we will need to define own own accumulator formatter.
+
+ typedef stopwatch_accumulator<process_real_cpu_clock,
+ accumulator_set<process_real_cpu_clock::rep,
+ features<
+ tag::count,
+ tag::sum,
+ tag::mean,
+ tag::variance(lazy)
+ >
+ >,
+ my_stopwatch_accumulator_formatter
+ >::reporter my_stopwatch_accumulator_reporter;
+
+Next follow the definition of a formatter taking care of count, sum, mean and variance
+
+ class my_stopwatch_accumulator_formatter {
+ public:
+ typedef std::string string_type;
+ typedef char char_type;
+ typedef std::ostream ostream_type;
+
+ static ostream_type & default_os() {return std::cout;}
+ static const char_type* default_format() {return "%c times, sum=%ss, mean=%as, variance=%vs\n";}
+ static int default_places() { return 3; }
+
+ template <class Stopwatch >
+ static void show_time( Stopwatch & stopwatch_, const char_type* format,
+ int places, ostream_type & os, system::error_code & ec)
+ {
+ typedef typename Stopwatch::duration duration_t;
+ typename Stopwatch::accumulator accumulator& acc = stopwatch_.accumulated();
+
+ boost::io::ios_flags_saver ifs( os );
+ os.setf( std::ios_base::fixed, std::ios_base::floatfield );
+ boost::io::ios_precision_saver ips( os );
+ os.precision( places );
+
+ for ( ; *format; ++format ) {
+ if ( *format != '%' || !*(format+1) || !std::strchr("acsv", *(format+1)) ) {
+ os << *format;
+ } else {
+ ++format;
+ switch ( *format ) {
+ case 's':
+ os << boost::chrono::duration<double>(duration_t(accumulators::sum(acc))).count();
+ break;
+ case 'a':
+ os << (accumulators::count(acc)>0)
+ ? boost::chrono::duration<double>(duration_t(duration_t::rep(accumulators::mean(acc)))).count()
+ : 0;
+ break;
+ case 'c':
+ os << accumulators::count(acc);
+ break;
+ case 'v':
+ os << (accumulators::count(acc)>0)
+ ? boost::chrono::duration<double>(duration_t(duration_t::rep(accumulators::variance(acc)))).count()
+ : 0;
+ break;
+ default:
+ assert(0 && "my_stopwatch_accumulator_formatter internal logic error");
+ }
+ }
+ }
+ }
+ };
+
+

[endsect]

@@ -1183,6 +1304,9 @@
 typename common_type<Rep1, Rep2>::type
 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);
+
 // duration comparisons
 template <class Rep1, class Period1, class Rep2, class Period2>
 bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
@@ -1669,8 +1793,20 @@

[endsect]

+[section:duration_operator_d_3 Non-Member function `operator/(Rep1,duration)`]
+
+ template <class Rep1, class Rep2, class Period>
+ double operator/(const Rep1& s, const duration<Rep2, Period>& d);
+
+[*Remarks:] Let `CR` represent the `common_type` of `Rep1` and `Rep2`. This function will not participate in overload resolution unless both `Rep1` and `Rep2` are implicitly convertible to `CR`, and `Rep1` is not an instantiation of `duration`.
+
+[*Returns:] `CR(s)/duration<CR, Period>(d)`.
+
+[endsect]
+

[section:duration_operator_mod_1 Non-Member function `operator%(duration,Rep2)`]
+
 template <class Rep1, class Period, class Rep2>
 duration<typename common_type<Rep1, Rep2>::type, Period>
 operator%(const duration<Rep1, Period>& d, const Rep2& s);
@@ -3281,15 +3417,18 @@

The default places is given by default_places and is 3.

-The default format is "%c times, sum=%ss, min=%ms, max=%Ms, mean=%as\\n", where
+The default format is "%c times, sum=%ss, min=%ms, max=%Ms, mean=%as, frequency=%fherzs, lifetime=%ls, percentage=%p\%\\n", where

* `%c` : the counter of the number of times the pair srat/stop has been called.
* `%s` : the sum of the samples of elapsed time between the call to start/stop.
* `%m` : the min of the samples of elapsed time between the call to start/stop.
* `%M` : the max of the samples of elapsed time between the call to start/stop.
* `%a` : the mean of the samples of elapsed time between the call to start/stop.
+* `%f` : the frequency of calls to start.
+* `%l` : the lifetime of the stopwatch_accumulator.
+* `%p` : the percentage of time spent by this stopwatch respect to its lifetime.

-The time is given using the suffix "s" following the System International d'Unites Std.
+The time is given using the suffix "s", the frequency is given using the suffix "herzs", both following the System International d'Unites Std.

[endsect]

@@ -4642,20 +4781,21 @@
[section:history Appendix A: History]
[/==================================]

-[section [*Version 0.3.2, January 24, 2010] ['New SuspendibleClock + Bug fixes]]
+[section [*Version 0.3.2, January 24, 2010] ['New SuspendibleClock, New frequency, lifetime and percentage stopwatch_accumulator features]]
[*Features:]

* Suspendible Clock concept + template class suspendible_clock<>
-* Added scope_suspend which will do nothing if the Clock is not a Suspendible Clock concept, and suspend/resume otherwise.
+* Added scope_suspend which do suspend/resume if the Clock is a model of Suspendible Clock concept, and nothing otherwise.
* Use of scope_suspend while reporting on stopwatch reporter
+* Added overloading for operator/(Integer/Duration)
+* Added frequency, lifetime and percentage to the default stopwatch_accumulator_formatter

[*Bug Fixes]
-
-* add static assertions to stopclock and stopclock_accumulator
+* Specific formatters doesn't works

[endsect]

-[section [*Version 0.3.1, January 20, 2010] ['New Allow wide characters + Bug fixes]]
+[section [*Version 0.3.1, January 20, 2010] ['New support for wide characters]]
[*Features:]

* Support for wide characters on formatters and stopclocks
@@ -4896,6 +5036,10 @@

Ask your operating system supplier. The results have been inspected with a debugger, and both for Windows and Linux, that's what the OS appears to be reporting at times.

+[heading Can I obtain statistics of the time elapsed between calls to a function?]
+
+The library do not provides this feature.
+
[endsect]

[/====================================================]
@@ -4997,6 +5141,26 @@

[table
 [[Ticket] [Description] [Resolution] [State]]
+ [[0] [ Issues raised by Michael Marcin: In the past I've seen QueryPerformanceCounter give incorrect results,
+ especially with SpeedStep processors on laptops. This was many years ago and
+ might have been fixed by service packs and drivers.
+
+ Typically you check the results of QPC against GetTickCount to see if the
+ results are reasonable.
+ http://support.microsoft.com/kb/274323
+
+ I've also heard of problems with QueryPerformanceCounter in multi-processor
+ systems.
+
+ I know some people SetThreadAffinityMask to 1 for the current thread call
+ their QueryPerformance* functions then restore SetThreadAffinityMask. This
+ seems horrible to me because it forces your program to jump to another
+ physical processor if it isn't already on cpu0 but they claim it worked well
+ in practice because they called the timing functions infrequently.
+
+ In the past I have chosen to use timeGetTime with timeBeginPeriod(1) for
+ high resolution timers to avoid these issues.
+ ] [XXXX] [Open]]
 [[1] [operator/ was ambiguous] [Disambiguate duration operator/] [Close]]
 [[2] [CLOCK_MONOTONIC is not defined with cygwin/gcc 3.4] [Disable code when BOOST_CHRONO_HAS_CLOCK_MONOTONIC is not defined.] [Close]]
 [[3] [result of metafunctions ratio_multiply and ratio_divide were not normalized ratios] [Use of the nested ratio typedef type on ratio arithmetic operations.] [Close]]
@@ -5018,12 +5182,16 @@
..\..\../boost/chrono/chrono.hpp:816: warning: suggest parentheses around '&&' within '||'
..\..\../boost/chrono/chrono.hpp:816: warning: suggest parentheses around '&&' within '||'] [???] [Open]]
 [[19] [suspendible_clock_test don't works in my windows environement (issue with tss)] [XXXX] [Open]]
- [[#] [XXXX] [XXXX] [Close]]
- [[#] [XXXX] [XXXX] [Close]]
+ [[20] [Use of Specific formatters doesn't works] [XXXX] [Close]]
+
+ [[21] [boost/chrono/scoped_suspend.hpp(31) : warning C4520: 'boost::chrono::scoped_suspend<Clock>' : multiple default constructors specified
+] [XXXX] [Open]]
 [[#] [XXXX] [XXXX] [Close]]
]

+
+
[endsect]

[/=====================================]
@@ -5032,28 +5200,9 @@

[heading Tasks to do before review]

+* Complete documentation
* Fully implement error handling, with test cases.
-* Consider issues raised by Michael Marcin:
-
- In the past I've seen QueryPerformanceCounter give incorrect results,
- especially with SpeedStep processors on laptops. This was many years ago and
- might have been fixed by service packs and drivers.
-
- Typically you check the results of QPC against GetTickCount to see if the
- results are reasonable.
- http://support.microsoft.com/kb/274323
-
- I've also heard of problems with QueryPerformanceCounter in multi-processor
- systems.
-
- I know some people SetThreadAffinityMask to 1 for the current thread call
- their QueryPerformance* functions then restore SetThreadAffinityMask. This
- seems horrible to me because it forces your program to jump to another
- physical processor if it isn't already on cpu0 but they claim it worked well
- in practice because they called the timing functions infrequently.
-
- In the past I have chosen to use timeGetTime with timeBeginPeriod(1) for
- high resolution timers to avoid these issues.
+* Fix open isues.

[heading For later releases]

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -29,8 +29,8 @@
<div class="toc"><dl>
<dt> Appendix A: History</dt>
<dd><dl>
-<dt><a href="appendices/history.html#boost_chrono.appendices.history.__version_0_3_2__january_24__2010____new_suspendibleclock___bug_fixes_">Version 0.3.2, January 24, 2010 New SuspendibleClock
- + Bug fixes</a></dt>
+<dt><a href="appendices/history.html#boost_chrono.appendices.history.__version_0_4__january_24__2010____new_suspendibleclock__new_frequency__lifetime_and_percentage_stopwatch_accumulator__features_">Version 0.4, January 24, 2010 New SuspendibleClock,
+ New frequency, lifetime and percentage stopwatch_accumulator features</a></dt>
<dt><a href="appendices/history.html#boost_chrono.appendices.history.__version_0_3_1__january_20__2010____new_allow_wide_characters___bug_fixes_">Version 0.3.1, January 20, 2010 New Allow
wide characters + Bug fixes</a></dt>
<dt><a href="appendices/history.html#boost_chrono.appendices.history.__version_0_3_0__january_17__2010____new_stopwatch_stopclock_feature___bug_fixes_">Version 0.3.0, January 17, 2010 New stopwatch/stopclock

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-01-24 18:54:05 EST (Sun, 24 Jan 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_common_type_lt__gt__template_arguments_"></a><h4>
-<a name="id4917271"></a>
+<a name="id4922665"></a>
 <a href="faq.html#boost_chrono.appendices.faq.how_important_is_the_order_of_the_common_type_lt__gt__template_arguments_">How
 important is the order of the common_type<> template arguments?</a>
 </h4>
@@ -60,7 +60,7 @@
 is also undefined.
 
<a name="boost_chrono.appendices.faq.why_does_stopwatch_reporter_only_display_millisecond_place_precision_when_the_underlying_timer_has_nanosecond_precision_"></a><h4>
-<a name="id4917681"></a>
+<a name="id4923075"></a>
 <a href="faq.html#boost_chrono.appendices.faq.why_does_stopwatch_reporter_only_display_millisecond_place_precision_when_the_underlying_timer_has_nanosecond_precision_">Why
 does stopwatch_reporter only display millisecond place precision when the
 underlying timer has nanosecond precision?</a>
@@ -71,7 +71,7 @@
 dangerously.
 
<a name="boost_chrono.appendices.faq.why_does_stopwatch_reporter_sometimes_report_more_cpu_seconds_than_real_seconds_"></a><h4>
-<a name="id4917722"></a>
+<a name="id4923116"></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>
@@ -80,6 +80,14 @@
 a debugger, and both for Windows and Linux, that's what the OS appears to
 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="id4923150"></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>
+
+ The library do not provides this feature.
+ 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/history.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/history.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/history.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -27,8 +27,8 @@
<a name="boost_chrono.appendices.history"></a> Appendix A: History
</h3></div></div></div>
<div class="toc"><dl>
-<dt><a href="history.html#boost_chrono.appendices.history.__version_0_3_2__january_24__2010____new_suspendibleclock___bug_fixes_">Version 0.3.2, January 24, 2010 New SuspendibleClock
- + Bug fixes</a></dt>
+<dt><a href="history.html#boost_chrono.appendices.history.__version_0_4__january_24__2010____new_suspendibleclock__new_frequency__lifetime_and_percentage_stopwatch_accumulator__features_">Version 0.4, January 24, 2010 New SuspendibleClock,
+ New frequency, lifetime and percentage stopwatch_accumulator features</a></dt>
<dt><a href="history.html#boost_chrono.appendices.history.__version_0_3_1__january_20__2010____new_allow_wide_characters___bug_fixes_">Version 0.3.1, January 20, 2010 New Allow
 wide characters + Bug fixes</a></dt>
<dt><a href="history.html#boost_chrono.appendices.history.__version_0_3_0__january_17__2010____new_stopwatch_stopclock_feature___bug_fixes_">Version 0.3.0, January 17, 2010 New stopwatch/stopclock
@@ -41,9 +41,9 @@
</dl></div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h4 class="title">
-<a name="boost_chrono.appendices.history.__version_0_3_2__january_24__2010____new_suspendibleclock___bug_fixes_"></a><a href="history.html#boost_chrono.appendices.history.__version_0_3_2__january_24__2010____new_suspendibleclock___bug_fixes_" title="Version 0.3.2, January 24, 2010 New SuspendibleClock
- + Bug fixes">Version 0.3.2, January 24, 2010 New SuspendibleClock
- + Bug fixes</a>
+<a name="boost_chrono.appendices.history.__version_0_4__january_24__2010____new_suspendibleclock__new_frequency__lifetime_and_percentage_stopwatch_accumulator__features_"></a><a href="history.html#boost_chrono.appendices.history.__version_0_4__january_24__2010____new_suspendibleclock__new_frequency__lifetime_and_percentage_stopwatch_accumulator__features_" title="Version 0.4, January 24, 2010 New SuspendibleClock,
+ New frequency, lifetime and percentage stopwatch_accumulator features">Version 0.4, January 24, 2010 New SuspendibleClock,
+ New frequency, lifetime and percentage stopwatch_accumulator features</a>
</h4></div></div></div>

 Features:
@@ -54,18 +54,17 @@
 </li>
<li>
 Added scope_suspend which will do nothing if the Clock is not a Suspendible
- Clock concept, and suspend/resume otherwise.
+ Clock concept, and suspendresume otherwise. * Use of scope_suspend
+ while reporting on stopwatch reporter * Added overloading for operator(Integer/Duration)
 </li>
<li>
- Use of scope_suspend while reporting on stopwatch reporter
+ Added frequency, lifetime and percentage to the default stopwatch_accumulator_formatter
 </li>
</ul></div>

- Bug Fixes
+ Bug Fixes * Specific formatters doesn't
+ works
 
-<div class="itemizedlist"><ul type="disc"><li>
- add static assertions to stopclock and stopclock_accumulator
- </li></ul></div>
</div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h4 class="title">

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-01-24 18:54:05 EST (Sun, 24 Jan 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__code__phrase_role__identifier__duration__phrase___code__to_a_function_with_the_units_being_ambiguous_"></a><h4>
-<a name="id4916055"></a>
+<a name="id4921449"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.is_it_possible_for_the_user_to_pass_a__code__phrase_role__identifier__duration__phrase___code__to_a_function_with_the_units_being_ambiguous_">Is
 it possible for the user to pass a <code class="computeroutput">duration</code>
 to a function with the units being ambiguous?</a>
@@ -45,7 +45,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="id4916144"></a>
+<a name="id4921539"></a>
 <a href="rationale.html#boost_chrono.appendices.rationale.why_duration_needs_operator_">Why
 duration needs operator%</a>
 </h4>
@@ -73,7 +73,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="id4916725"></a>
+<a name="id4922119"></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>
@@ -101,7 +101,7 @@
 ratio<1,3> and the compilation succeeds.
 
<a name="boost_chrono.appendices.rationale.why_ratio_needs_the_nested_normalizer_typedef_type"></a><h4>
-<a name="id4917038"></a>
+<a name="id4922432"></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/tickets.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/tickets.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/appendices/tickets.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -59,6 +59,51 @@
<tr>
<td>
 
+ 0
+ 
+ </td>
+<td>
+ 
+ Issues raised by Michael Marcin: In the past I've seen QueryPerformanceCounter
+ give incorrect results, especially with SpeedStep processors on laptops.
+ This was many years ago and might have been fixed by service packs
+ and drivers.
+ 
+ 
+ Typically you check the results of QPC against GetTickCount to see
+ if the results are reasonable. http://support.microsoft.com/kb/274323
+ 
+ 
+ I've also heard of problems with QueryPerformanceCounter in multi-processor
+ systems.
+ 
+ 
+ I know some people SetThreadAffinityMask to 1 for the current thread
+ call their QueryPerformance* functions then restore SetThreadAffinityMask.
+ This seems horrible to me because it forces your program to jump
+ to another physical processor if it isn't already on cpu0 but they
+ claim it worked well in practice because they called the timing functions
+ infrequently.
+ 
+ 
+ In the past I have chosen to use timeGetTime with timeBeginPeriod(1)
+ for high resolution timers to avoid these issues.
+ 
+ </td>
+<td>
+ 
+ XXXX
+ 
+ </td>
+<td>
+ 
+ Open
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
 1
 
 </td>
@@ -492,12 +537,12 @@
<tr>
<td>
 
- #
+ 20
 
 </td>
<td>
 
- XXXX
+ Use of Specific formatters doesn't works
 
 </td>
<td>
@@ -514,12 +559,13 @@
<tr>
<td>
 
- #
+ 21
 
 </td>
<td>
 
- XXXX
+ boost/chrono/scoped_suspend.hpp(31) : warning C4520: 'boost::chrono::scoped_suspend<Clock>'
+ : multiple default constructors specified
 
 </td>
<td>
@@ -529,7 +575,7 @@
 </td>
<td>
 
- Close
+ Open
 
 </td>
</tr>

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-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -26,40 +26,23 @@
<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="id4920251"></a>
+<a name="id4925742"></a>
 <a href="todo.html#boost_chrono.appendices.todo.tasks_to_do_before_review">Tasks
 to do before review</a>
 </h4>
<div class="itemizedlist"><ul type="disc">
<li>
+ Complete documentation
+ </li>
+<li>
 Fully implement error handling, with test cases.
 </li>
<li>
- Consider issues raised by Michael Marcin:
+ Fix open isues.
 </li>
</ul></div>
-<pre class="programlisting">In the past I've seen QueryPerformanceCounter give incorrect results,
-especially with SpeedStep processors on laptops. This was many years ago and
-might have been fixed by service packs and drivers.
-
-Typically you check the results of QPC against GetTickCount to see if the
-results are reasonable.
-http://support.microsoft.com/kb/274323
-
-I've also heard of problems with QueryPerformanceCounter in multi-processor
-systems.
-
-I know some people SetThreadAffinityMask to 1 for the current thread call
-their QueryPerformance* functions then restore SetThreadAffinityMask. This
-seems horrible to me because it forces your program to jump to another
-physical processor if it isn't already on cpu0 but they claim it worked well
-in practice because they called the timing functions infrequently.
-
-In the past I have chosen to use timeGetTime with timeBeginPeriod(1) for
-high resolution timers to avoid these issues.
-</pre>
<a name="boost_chrono.appendices.todo.for_later_releases"></a><h4>
-<a name="id4920855"></a>
+<a name="id4925781"></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/overview/motivation.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/overview/motivation.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/overview/motivation.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -733,7 +733,7 @@

 Will produce the following output
 
-<pre class="programlisting">3 times, sum 0.034s, min 0.006s, max 0.017s, mean 0.011s
+<pre class="programlisting">3 times, sum=0.034s, min=0.006s, max=0.017s, mean=0.011s
</pre>

 It is also helpful if such timing information is broken down into real

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-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -504,6 +504,9 @@
 typename common_type<Rep1, Rep2>::type
 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);
+
 // duration comparisons
 template <class Rep1, class Period1, class Rep2, class Period2>
 bool operator==(const duration<Rep1, Period1>& lhs, const duration<Rep2, Period2>& rhs);
@@ -605,7 +608,7 @@
 and both of these calls happen before <code class="computeroutput">C1::time_point::max()</code>.
 
<div class="table">
-<a name="id4834136"></a>Table 1. Clock Requirements
+<a name="id4839076"></a>Table 1. Clock Requirements
<table class="table" summary="Clock Requirements">
<colgroup>
<col>
@@ -1379,6 +1382,8 @@
 Non-Member function <code class="computeroutput">operator/(duration,Rep2)</code></a></dt>
<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_d_2">
 Non-Member function <code class="computeroutput">operator/(duration,duration)</code></a></dt>
+<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_d_3">
+ Non-Member function <code class="computeroutput">operator/(Rep1,duration)</code></a></dt>
<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_mod_1">
 Non-Member function <code class="computeroutput">operator%(duration,Rep2)</code></a></dt>
<dt><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_mod_2">
@@ -1495,6 +1500,29 @@
</div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h6 class="title">
+<a name="boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_d_3"></a><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_d_3" title="
+ Non-Member function operator/(Rep1,duration)">
+ Non-Member function <code class="computeroutput">operator/(Rep1,duration)</code></a>
+</h6></div></div></div>
+<pre class="programlisting">template <class Rep1, class Rep2, class Period>
+double operator/(const Rep1& s, const duration<Rep2, Period>& d);
+</pre>
+
+ Remarks: Let <code class="computeroutput">CR</code>
+ represent the <code class="computeroutput">common_type</code>
+ of <code class="computeroutput">Rep1</code> and <code class="computeroutput">Rep2</code>. This function will not participate
+ in overload resolution unless both <code class="computeroutput">Rep1</code>
+ and <code class="computeroutput">Rep2</code> are implicitly
+ convertible to <code class="computeroutput">CR</code>,
+ and <code class="computeroutput">Rep1</code> is not an
+ instantiation of <code class="computeroutput">duration</code>.
+ 
+
+ Returns: <code class="computeroutput">CR(s)/duration<CR, Period>(d)</code>.
+ 
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h6 class="title">
<a name="boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_mod_1"></a><a href="cpp0x.html#boost_chrono.reference.cpp0x.chrono_chrono_hpp.duration_non_member_arithmetic.duration_operator_mod_1" title="
 Non-Member function operator%(duration,Rep2)">
 Non-Member function <code class="computeroutput">operator%(duration,Rep2)</code></a>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/other_clocks.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/other_clocks.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/other_clocks.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -304,7 +304,7 @@
<code class="computeroutput">clock</code> types.

<div class="table">
-<a name="id4856674"></a>Table 2. SuspendibleClock Requirements
+<a name="id4861995"></a>Table 2. SuspendibleClock Requirements
<table class="table" summary="SuspendibleClock Requirements">
<colgroup>
<col>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_formatters.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_formatters.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_formatters.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -167,7 +167,8 @@
 

 The default format is "%c times, sum<code class="literal">%ss, min</code>%ms,
- max<code class="literal">%Ms, mean</code>%as\n", where
+ max<code class="literal">%Ms, mean</code>%as, frequency<code class="literal">%fherzs, lifetime</code>%ls,
+ percentage=%p%\n", where
 
<div class="itemizedlist"><ul type="disc">
<li>
@@ -190,10 +191,23 @@
<code class="computeroutput">%a</code>
 : the mean of the samples of elapsed time between the call to start/stop.
 </li>
+<li>
+<code class="computeroutput">%f</code>
+ : the frequency of calls to start.
+ </li>
+<li>
+<code class="computeroutput">%l</code>
+ : the lifetime of the stopwatch_accumulator.
+ </li>
+<li>
+<code class="computeroutput">%p</code>
+ : the percentage of time spent by this stopwatch respect to its lifetime.
+ </li>
</ul></div>

- The time is given using the suffix "s" following the System
- International d'Unites Std.
+ The time is given using the suffix "s", the frequency is given
+ using the suffix "herzs", both following the System International
+ d'Unites Std.
 
</div>
</div>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_reporters.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_reporters.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatch_reporters.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -78,7 +78,7 @@
<code class="computeroutput">std::ostream</code>, ec is a system::error_code

<div class="table">
-<a name="id4868453"></a>Table 4. Stopwatch Requirements
+<a name="id4873774"></a>Table 4. Stopwatch Requirements
<table class="table" summary="Stopwatch Requirements">
<colgroup>
<col>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatches.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatches.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/reference/stopwatches.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -135,7 +135,7 @@
is an instance of <code class="computeroutput">S</code>.

<div class="table">
-<a name="id4860199"></a>Table 3. Stopwatch Requirements
+<a name="id4865520"></a>Table 3. Stopwatch Requirements
<table class="table" summary="Stopwatch Requirements">
<colgroup>
<col>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -36,8 +36,6 @@
</dl></dd>
<dt>Tutorial</dt>
<dd><dl>
-<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.thread_clock">thread
- clock</a></dt>
<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_to_define_a_thread_clock">How
 to define a thread clock</a></dt>
<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_prefix_each_report_with__boost_current_function__function_signature_">How
@@ -49,10 +47,10 @@
 I use an stopclock accumulator which is not static?</a></dt>
<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_suspend_a_stopwatch_">How
 can I suspend a stopwatch?</a></dt>
-<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_get_specific_statistics_from_stopwatches_accumulator">How
- get specific statistics from stopwatches accumulator</a></dt>
-<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_defaul_do_not_satisfy_my_expectations">How
- can I make a specific formatter when the defaul do not satisfy my expectations</a></dt>
+<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_to_get_specific_statistics_from_stopwatches_accumulator_">How
+ to get specific statistics from stopwatches accumulator?</a></dt>
+<dt><a href="users_guide/tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_default_do_not_satisfy_my_expectations">How
+ can I make a specific formatter when the default do not satisfy my expectations</a></dt>
</dl></dd>
<dt> References</dt>
</dl></div>

Modified: sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/getting_started.html
==============================================================================
--- sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/getting_started.html (original)
+++ sandbox/chrono/libs/chrono/doc/html/boost_chrono/users_guide/getting_started.html 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -39,7 +39,7 @@
 Installing Chrono</a>
</h4></div></div></div>
<a name="boost_chrono.users_guide.getting_started.install.getting__emphasis_role__bold__boost_chrono__emphasis__"></a><h5>
-<a name="id4817366"></a>
+<a name="id4817378"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.getting__emphasis_role__bold__boost_chrono__emphasis__">Getting
 Boost.Chrono </a>
 </h5>
@@ -53,7 +53,7 @@
 Sandbox</a>.
 
<a name="boost_chrono.users_guide.getting_started.install.where_to_install__emphasis_role__bold__boost_chrono__emphasis___"></a><h5>
-<a name="id4817426"></a>
+<a name="id4817439"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.where_to_install__emphasis_role__bold__boost_chrono__emphasis___">Where
 to install Boost.Chrono? </a>
 </h5>
@@ -69,7 +69,7 @@
 variable. Any help is welcome.
 
<a name="boost_chrono.users_guide.getting_started.install.building__emphasis_role__bold__boost_chrono__emphasis__"></a><h5>
-<a name="id4817469"></a>
+<a name="id4817481"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.building__emphasis_role__bold__boost_chrono__emphasis__">Building
 Boost.Chrono </a>
 </h5>
@@ -80,7 +80,7 @@
<pre class="programlisting">bjam libs/chrono/build
</pre>
<a name="boost_chrono.users_guide.getting_started.install.requirements"></a><h5>
-<a name="id4817537"></a>
+<a name="id4817549"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.requirements">Requirements</a>
 </h5>

@@ -129,7 +129,7 @@
</dl>
</div>
<a name="boost_chrono.users_guide.getting_started.install.building_an_executable_that_uses__emphasis_role__bold__boost_chrono__emphasis__"></a><h5>
-<a name="id4817737"></a>
+<a name="id4817750"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.building_an_executable_that_uses__emphasis_role__bold__boost_chrono__emphasis__">Building
 an executable that uses Boost.Chrono
 </a>
@@ -139,7 +139,7 @@
 with the Boost System library.
 
<a name="boost_chrono.users_guide.getting_started.install.exceptions_safety_"></a><h5>
-<a name="id4817773"></a>
+<a name="id4817786"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.exceptions_safety_">Exceptions
 safety </a>
 </h5>
@@ -148,7 +148,7 @@
 of exception safety as long as the underlying parameters provide it.
 
<a name="boost_chrono.users_guide.getting_started.install.thread_safety_"></a><h5>
-<a name="id4817800"></a>
+<a name="id4817812"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.thread_safety_">Thread
 safety </a>
 </h5>
@@ -156,7 +156,7 @@
 All functions in the library are thread-unsafe except when noted explicitly.
 
<a name="boost_chrono.users_guide.getting_started.install.tested_compilers_"></a><h5>
-<a name="id4817824"></a>
+<a name="id4817837"></a>
 <a href="getting_started.html#boost_chrono.users_guide.getting_started.install.tested_compilers_">Tested
 compilers </a>
 </h5>
@@ -175,7 +175,7 @@
 MSVC 9.0 Express
 </li>
<li>
- MSVC 5.0
+ MSVC 8.0
 </li>
</ul></div>

@@ -244,12 +244,12 @@

 Here is a complete program (stopclock_example.cpp):
 
-<pre class="programlisting">#include <boost/chrono/process_times.hpp>
+<pre class="programlisting">#include <boost/chrono/stopclock.hpp>
#include <cmath>

int main()
{
- boost::chrono::stopclockstopclock<> t;
+ boost::chrono::stopclock<> t;

 for ( long i = 0; i < 10000000; ++i )
 std::sqrt( 123.456L ); // burn some time

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-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -27,8 +27,6 @@
<a name="boost_chrono.users_guide.tutorial"></a>Tutorial
</h3></div></div></div>
<div class="toc"><dl>
-<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.thread_clock">thread
- clock</a></dt>
<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_to_define_a_thread_clock">How
 to define a thread clock</a></dt>
<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_prefix_each_report_with__boost_current_function__function_signature_">How
@@ -40,38 +38,190 @@
 I use an stopclock accumulator which is not static?</a></dt>
<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_suspend_a_stopwatch_">How
 can I suspend a stopwatch?</a></dt>
-<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_get_specific_statistics_from_stopwatches_accumulator">How
- get specific statistics from stopwatches accumulator</a></dt>
-<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_defaul_do_not_satisfy_my_expectations">How
- can I make a specific formatter when the defaul do not satisfy my expectations</a></dt>
+<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_to_get_specific_statistics_from_stopwatches_accumulator_">How
+ to get specific statistics from stopwatches accumulator?</a></dt>
+<dt><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_default_do_not_satisfy_my_expectations">How
+ can I make a specific formatter when the default do not satisfy my expectations</a></dt>
</dl></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title">
-<a name="boost_chrono.users_guide.tutorial.thread_clock"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.thread_clock" title="thread
- clock">thread
- clock</a>
-</h4></div></div></div></div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="boost_chrono.users_guide.tutorial.how_to_define_a_thread_clock"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_to_define_a_thread_clock" title="How
 to define a thread clock">How
 to define a thread clock</a>
</h4></div></div></div>
+
+ On posix systems for which the macro _POSIX_THREAD_CPUTIME is defined we
+ can get the time associated to a specific thread.
+ 
<pre class="programlisting">class thread_clock {
public:
- typedef boost::intmax_t rep;
- typedef boost::chrono::nanoseconds period;
- typedef boost::chrono::duration<rep, period> duration;
- typedef boost::chrono::time_point<Clock> time_point;
- static const bool is_monotonic = true;
-
- static time_point now() {
- // get the current thread
- // get the clock_id associated to the current thread
- // get the clock_t associated to the thread clock
- // transform to nanoseconds
- }
+ typedef nanoseconds duration;
+ typedef duration::rep rep;
+ typedef duration::period period;
+ typedef chrono::time_point<process_real_cpu_clock> time_point;
+ static const bool is_monotonic = true;
+
+ static time_point now( ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ boost::throw_exception(
+ system::system_error( errno, system::system_category, "chrono::thread_clock" ));
+ }
+
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+ static time_point now( system::error_code & ec ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ ec.assign( errno, system::system_category );
+ return time_point();
+ }
+ ec.clear();
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+};
+</pre>
+
+ class thread_clock { public: typedef nanoseconds duration; typedef duration::rep
+ rep; typedef duration::period period; typedef chrono::time_point<process_real_cpu_clock>
+ time_point; static const bool is_monotonic = true;
+ 
+<pre class="programlisting"> static time_point now( ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ boost::throw_exception(
+ system::system_error( errno, system::system_category, "chrono::thread_clock" ));
+ }
+
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+ static time_point now( system::error_code & ec ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ ec.assign( errno, system::system_category );
+ return time_point();
+ }
+ ec.clear();
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+};
+</pre>
+
+ static time_point now( ) { / get the current thread pthread_t
+ pth=pthread_self(void); / get the clock_id associated to the
+ current thread clockid_t clock_id; pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) ) { boost::throw_exception( system::system_error(
+ errno, system::system_category, "chrono::thread_clock" )); }
+ 
+<pre class="programlisting"> // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+ static time_point now( system::error_code & ec ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ ec.assign( errno, system::system_category );
+ return time_point();
+ }
+ ec.clear();
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
};
</pre>
+
+ // transform to nanoseconds return time_point(duration( static_cast<thread_clock::rep>(
+ ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+ 
+<pre class="programlisting"> }
+ static time_point now( system::error_code & ec ) {
+ // get the current thread
+ pthread_t pth=pthread_self(void);
+ // get the clock_id associated to the current thread
+ clockid_t clock_id;
+ pthread_getcpuclockid(pth, clock_id);
+ // get the timespec associated to the thread clock
+ struct timespec ts;
+ if ( ::clock_gettime( clock_id, &ts ) )
+ {
+ ec.assign( errno, system::system_category );
+ return time_point();
+ }
+ ec.clear();
+ // transform to nanoseconds
+ return time_point(duration(
+ static_cast<thread_clock::rep>( ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+
+ }
+};
+</pre>
+
+ } static time_point now( system::error_code & ec ) { / get
+ the current thread pthread_t pth=pthread_self(void); / get the
+ clock_id associated to the current thread clockid_t clock_id; pthread_getcpuclockid(pth,
+ clock_id); / get the timespec associated to the thread clock
+ struct timespec ts; if ( ::clock_gettime( clock_id, &ts ) ) { ec.assign(
+ errno, system::system_category ); return time_point(); } ec.clear(); /
+ transform to nanoseconds return time_point(duration( static_cast<thread_clock::rep>(
+ ts.tv_sec ) * 1000000000 + ts.tv_nsec));
+ 
+<pre class="programlisting"> }
+};
+</pre>
+
+ } };
+ 
</div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h4 class="title">
@@ -102,7 +252,7 @@
 static boost::chrono::stopclock_accumulator<> BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__)( \
 std::string(BOOST_CURRENT_FUNCTION) + ": " + boost::chrono::stopwatch_accumulator_formatter::default_format() \
 ); \
- boost::chrono::stopclock_accumulator<>::scoped_stop BOOST_JOIN(_boost_chrono_stopclock_accumulator_run_, __LINE__)(BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__))
+ boost::chrono::stopclock_accumulator<>::scoped_run BOOST_JOIN(_boost_chrono_stopclock_accumulator_run_, __LINE__)(BOOST_JOIN(_boost_chrono_stopclock_accumulator_, __LINE__))
</pre>

 With this macro you will just ave
@@ -122,7 +272,7 @@
 can I prefix each report with <code class="computeroutput">__FILE__[__LINE__]</code> pattern?</a>
</h4></div></div></div>

- When you want to prefixx with the <code class="computeroutput">__FILE__[__LINE__]</code> pattern you can follow the same technique
+ When you want to prefix with the <code class="computeroutput">__FILE__[__LINE__]</code> pattern you can follow the same technique
 as described below:
 
<pre class="programlisting">#define REPORT_LINE_ACCUMULATED_LIFETIME \
@@ -192,16 +342,31 @@
</div>
<div class="section" lang="en">
<div class="titlepage"><div><div><h4 class="title">
-<a name="boost_chrono.users_guide.tutorial.how_get_specific_statistics_from_stopwatches_accumulator"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_get_specific_statistics_from_stopwatches_accumulator" title="How
- get specific statistics from stopwatches accumulator">How
- get specific statistics from stopwatches accumulator</a>
+<a name="boost_chrono.users_guide.tutorial.how_to_get_specific_statistics_from_stopwatches_accumulator_"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_to_get_specific_statistics_from_stopwatches_accumulator_" title="How
+ to get specific statistics from stopwatches accumulator?">How
+ to get specific statistics from stopwatches accumulator?</a>
</h4></div></div></div>
-<pre class="programlisting">#include <boost/chrono/stopwatches.hpp>
-#include <cmath>
+
+ There are two use cases that coul need to change the statistics associated
+ to a stopwatches accumulator:
+ 
+<div class="orderedlist"><ol type="1">
+<li>
+ We want to reduce the default reporting and we preffer to adapt the statistics
+ to the reporting
+ </li>
+<li>
+ We want to report other statistics of the samples
+ </li>
+</ol></div>
+
+ For the first case we just need to change the accumulator_set and the format
+ we want to get. Imagin we want to get only the count, sam and mean statistics,
+ no need to calculate the min neither the max.
+ 
+<pre class="programlisting">using namespace boost::accumulators;

-using namespace boost::chrono;
-using namespace boost::accumulators;
-typedef stopwatch_accumulator<process_real_cpu_clock, kind::running,
+typedef stopwatch_accumulator<process_real_cpu_clock,
 accumulator_set<process_real_cpu_clock::rep,
 features<
 tag::count,
@@ -213,7 +378,7 @@

int f1(long j)
{
- static my_stopwatch_accumulator_reporter acc(BOOST_CHRONO_ACCUMULATOR_FUNCTION_FORMAT);
+ static my_stopwatch_accumulator_reporter acc("%c times, sum=%ss, mean=%as\n");
 my_stopwatch_accumulator_reporter::scoped_run _(acc);

 for ( long i = 0; i < j; ++i )
@@ -221,21 +386,116 @@

 return 0;
}
-int main()
-{
+</pre>
+
+ But wat would hapend if we haven't forced the format:
+ 
+<pre class="programlisting">static my_stopwatch_accumulator_reporter acc;
+my_stopwatch_accumulator_reporter::scoped_run _(acc);
+</pre>
+
+ Unfortunately there is no error at compile time. Fortunately, the run-time
+ execution is not undefined and will return 0 for the missing statistics.
+ 
+</div>
+<div class="section" lang="en">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_default_do_not_satisfy_my_expectations"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_default_do_not_satisfy_my_expectations" title="How
+ can I make a specific formatter when the default do not satisfy my expectations">How
+ can I make a specific formatter when the default do not satisfy my expectations</a>
+</h4></div></div></div>
+
+ Imagine then that we want to report the tag::variance(lazy). We will need
+ to include the specific accumulator file
+ 
+<pre class="programlisting">...
+#include <boost/accumulators/statistics/variance.hpp>
+...
+typedef stopwatch_accumulator<process_real_cpu_clock,
+ accumulator_set<process_real_cpu_clock::rep,
+ features<
+ tag::count,
+ tag::sum,
+ tag::mean,
+ tag::variance(lazy)
+ >
+ >
+>::reporter my_stopwatch_accumulator_reporter;
+</pre>
+
+ But what happens if we add new statistics to the accumulator_set that are
+ not taken in account by the default formatter? These statistics will simply
+ be ignored. So we will need to define own own accumulator formatter.
+ 
+<pre class="programlisting">typedef stopwatch_accumulator<process_real_cpu_clock,
+ accumulator_set<process_real_cpu_clock::rep,
+ features<
+ tag::count,
+ tag::sum,
+ tag::mean,
+ tag::variance(lazy)
+ >
+ >,
+ my_stopwatch_accumulator_formatter
+>::reporter my_stopwatch_accumulator_reporter;
+</pre>
+
+ Next follow the definition of a formatter taking care of count, sum, mean
+ and variance
+ 
+<pre class="programlisting">class my_stopwatch_accumulator_formatter {
+public:
+ typedef std::string string_type;
+ typedef char char_type;
+ typedef std::ostream ostream_type;

- f1(100000);
- f1(200000);
- f1(300000);
- return 0;
-}
+ static ostream_type & default_os() {return std::cout;}
+ static const char_type* default_format() {return "%c times, sum=%ss, mean=%as, variance=%vs\n";}
+ static int default_places() { return 3; }
+
+ template <class Stopwatch >
+ static void show_time( Stopwatch & stopwatch_, const char_type* format,
+ int places, ostream_type & os, system::error_code & ec)
+ {
+ typedef typename Stopwatch::duration duration_t;
+ typename Stopwatch::accumulator accumulator& acc = stopwatch_.accumulated();
+
+ boost::io::ios_flags_saver ifs( os );
+ os.setf( std::ios_base::fixed, std::ios_base::floatfield );
+ boost::io::ios_precision_saver ips( os );
+ os.precision( places );
+
+ for ( ; *format; ++format ) {
+ if ( *format != '%' || !*(format+1) || !std::strchr("acsv", *(format+1)) ) {
+ os << *format;
+ } else {
+ ++format;
+ switch ( *format ) {
+ case 's':
+ os << boost::chrono::duration<double>(duration_t(accumulators::sum(acc))).count();
+ break;
+ case 'a':
+ os << (accumulators::count(acc)>0)
+ ? boost::chrono::duration<double>(duration_t(duration_t::rep(accumulators::mean(acc)))).count()
+ : 0;
+ break;
+ case 'c':
+ os << accumulators::count(acc);
+ break;
+ case 'v':
+ os << (accumulators::count(acc)>0)
+ ? boost::chrono::duration<double>(duration_t(duration_t::rep(accumulators::variance(acc)))).count()
+ : 0;
+ break;
+ default:
+ assert(0 && "my_stopwatch_accumulator_formatter internal logic error");
+ }
+ }
+ }
+ }
+};
</pre>
</div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title">
-<a name="boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_defaul_do_not_satisfy_my_expectations"></a><a href="tutorial.html#boost_chrono.users_guide.tutorial.how_can_i_make_a_specific_formatter_when_the_defaul_do_not_satisfy_my_expectations" title="How
- can I make a specific formatter when the defaul do not satisfy my expectations">How
- can I make a specific formatter when the defaul do not satisfy my expectations</a>
-</h4></div></div></div></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>

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-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -120,7 +120,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: January 22, 2010 at 13:09:37 GMT</td>
+<td align="left">Last revised: January 24, 2010 at 21:03:56 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: sandbox/chrono/libs/chrono/example/specific_stopwatch_accumulator_example.cpp
==============================================================================
--- sandbox/chrono/libs/chrono/example/specific_stopwatch_accumulator_example.cpp (original)
+++ sandbox/chrono/libs/chrono/example/specific_stopwatch_accumulator_example.cpp 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -78,6 +78,18 @@
, my_stopwatch_accumulator_formatter
> my_stopwatch_accumulator_reporter;

+typedef stopwatch_accumulator<process_real_cpu_clock,
+ accumulator_set<process_real_cpu_clock::rep,
+ features<
+ tag::count,
+ tag::sum,
+ tag::mean,
+ tag::variance(lazy)
+ >
+ >
+ >::get_reporter< my_stopwatch_accumulator_formatter>::type
+ my_stopwatch_accumulator_reporter2;
+
int f1(long j)
{
//static my_stopwatch_accumulator_reporter acc(BOOST_CHRONO_ACCUMULATOR_FUNCTION_FORMAT);

Added: sandbox/chrono/libs/chrono/example/suspendible_stopclock_example.cpp
==============================================================================
--- (empty file)
+++ sandbox/chrono/libs/chrono/example/suspendible_stopclock_example.cpp 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -0,0 +1,39 @@
+// stopclock_example.cpp ---------------------------------------------------//
+
+// Copyright 2009 Vicente J. Botet Escriba
+
+// Distributed under the Boost Software License, Version 1.0.
+// See http://www.boost.org/LICENSE_1_0.txt
+
+// See http://www.boost.org/libs/chrono for documentation.
+
+#include <boost/thread.hpp>
+#include <boost/chrono/stopclock.hpp>
+#include <boost/chrono/suspendible_clock.hpp>
+#include <cmath>
+
+using namespace boost::chrono;
+double res;
+
+int f1(long j)
+{
+ stopclock<suspendible_clock<process_cpu_clock> > a(9);
+ //stopclock<> b(9);
+
+ for ( long i = 0; i < j; ++i )
+ res+=std::sqrt( 123.456L ); // burn some time
+ //if (j!=0) f1(j-1);
+ //boost::this_thread::sleep(boost::posix_time::milliseconds(10));
+
+ return 0;
+}
+int main()
+{
+ //stopclock<> _(BOOST_CHRONO_TIME_FUNCTION_FORMAT);
+ stopclock<> _(9);
+
+ for (long i =1; i<= 3; ++i)
+ f1(i*100000);
+ std::cout<< res << std::endl;
+ return 0;
+}

Modified: sandbox/chrono/libs/chrono/test/Jamfile.v2
==============================================================================
--- sandbox/chrono/libs/chrono/test/Jamfile.v2 (original)
+++ sandbox/chrono/libs/chrono/test/Jamfile.v2 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -88,10 +88,13 @@
 [ run run_timer_test.cpp : : : <library>/boost/system//boost_system : run_timer_test_dll ]
 ;

- #test-suite "other_clocks"
+ # test-suite "other_clocks"
 # :
 # [ run test_suspendible_clock.cpp : : : <library>/boost/thread//boost_thread <link>static ]
 # [ run test_suspendible_clock.cpp : : : <library>/boost/thread//boost_thread <library>/boost/system//boost_system : test_suspendible_clock_dll ]
+ # [ run ../example/suspendible_stopclock_example.cpp : : : <library>/boost/thread//boost_thread <link>static ]
+ # [ run ../example/suspendible_stopclock_example.cpp : : : <library>/boost/thread//boost_thread <library>/boost/system//boost_system : suspendible_stopclock_example_dll ]
+ # [ run test_thread_clock.cpp : : : <link>static ]
 # ;

 test-suite "stopwatch"

Added: sandbox/chrono/libs/chrono/test/test_thread_clock.cpp
==============================================================================
--- (empty file)
+++ sandbox/chrono/libs/chrono/test/test_thread_clock.cpp 2010-01-24 18:54:05 EST (Sun, 24 Jan 2010)
@@ -0,0 +1,37 @@
+// test_thread_clock.cpp ----------------------------------------------------------//
+
+// Copyright 2009 Vicente J. Botet Escriba
+
+// Distributed under the Boost Software License, Version 1.0.
+// See http://www.boost.org/LICENSE_1_0.txt
+
+
+#include <boost/chrono/thread_clock.hpp>
+#include <boost/type_traits.hpp>
+
+#include <iostream>
+
+using namespace boost::chrono;
+
+void test_thread_clock()
+{
+ std::cout << "thread_clock test" << std::endl;
+ thread_clock::duration delay = milliseconds(5);
+ thread_clock::time_point start = thread_clock::now();
+ while (thread_clock::now() - start <= delay)
+ ;
+ thread_clock::time_point stop = thread_clock::now();
+ thread_clock::duration elapsed = stop - start;
+ std::cout << "paused " << nanoseconds(elapsed).count() << " nanoseconds\n";
+ start = thread_clock::now();
+ stop = thread_clock::now();
+ std::cout << "thread_clock resolution estimate: " << nanoseconds(stop-start).count() << " nanoseconds\n";
+}
+
+
+int main()
+{
+ test_thread_clock();
+ return 0;
+}
+

Next message: emil_at_[hidden]: "[Boost-commit] svn:boost r59263 - trunk/libs/exception/test"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r59261 - sandbox/chrono/boost/chrono"

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