[Chrono] How to report problems?

newer
spirit and property_tree headers...

Roland Bock

15 Apr 2010 15 Apr '10

8:48 a.m.

Hi, after having received a push in the right direction by Howard yesterday, everything works fine so far, except for for the following two details: a) I get some warnings about unused parameters when using the stopclock. For instance: include/boost/chrono/stopwatch_reporter.hpp:81: warning: unused parameter ‘ec’ The fixes are trivial in all cases I encountered. b) The thread_clock part of the tutorial looks pretty broken. Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost? Thanks for this cool library! Regards, Roland

Show replies by date

Diederick C. Niehorster

15 Apr 15 Apr

8:52 a.m.

Hi Roland, I dont know if there is a tracker for boost.chrono, but i guess you can email Vincente directly, vicente.botet <at> wanadoo.fr. Best, Dee On Thu, Apr 15, 2010 at 4:48 PM, Roland Bock wrote:

...

Hi,

after having received a push in the right direction by Howard yesterday, everything works fine so far, except for for the following two details:

a) I get some warnings about unused parameters when using the stopclock. For instance:

include/boost/chrono/stopwatch_reporter.hpp:81: warning: unused parameter ‘ec’

The fixes are trivial in all cases I encountered.

b) The thread_clock part of the tutorial looks pretty broken.

Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

Thanks for this cool library!

Regards,

Roland _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

vicente.botet

16 May 16 May

5:37 p.m.

Hi, ----- Original Message ----- From: "Roland Bock" To: Sent: Thursday, April 15, 2010 10:48 AM Subject: [Boost-users] [Chrono] How to report problems?

...

Hi,

after having received a push in the right direction by Howard yesterday,

Thanks Howard.

...

everything works fine so far, except for for the following two details:

a) I get some warnings about unused parameters when using the stopclock. For instance:

include/boost/chrono/stopwatch_reporter.hpp:81: warning: unused parameter ‘ec’

The fixes are trivial in all cases I encountered.

Yes I get it. I will check the warnings on the builds I can run. On which platform and with wich compiler are you working? Could you sent me a log with the warnings you found?

...

b) The thread_clock part of the tutorial looks pretty broken.

thread_clock was one of the last features I added and has been tested only on linux with gcc-4.2.1. I need to port it to Windows, but for the moment I have had no time. Could you give more details on how this is broken?

...

Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

You can send to this ML, but as the library is under developement maybe it is better to send you mails to the boost development list boost@list.boost.org.

...

Thanks for this cool library!

Glad to hear it is useful for you. Have you run the tests onyour platform? It would be great if you can make a pre-review of the library, this will surely help to improve the library before the formal review, could you? Best, Vicente

Roland Bock

27 May 27 May

2:08 p.m.

Hi, sorry for the late reply, did not see it among all the other stuff.... vicente.botet wrote:

...

Hi, ----- Original Message ----- From: "Roland Bock" To: Sent: Thursday, April 15, 2010 10:48 AM Subject: [Boost-users] [Chrono] How to report problems?

...
Hi,

after having received a push in the right direction by Howard yesterday,

Thanks Howard.

...
everything works fine so far, except for for the following two details:

a) I get some warnings about unused parameters when using the stopclock. For instance:

include/boost/chrono/stopwatch_reporter.hpp:81: warning: unused parameter ‘ec’

The fixes are trivial in all cases I encountered.

Yes I get it. I will check the warnings on the builds I can run. On which platform and with wich compiler are you working? Could you sent me a log with the warnings you found?

Ubuntu-8.04, 64bit, gcc-4.2.4, with the following warning flags: -Wall -Wreorder -Wnon-virtual-dtor -Wno-non-template-friend -Woverloaded-virtual -Wsign-promo -Wextra Warnings are attached for the following line: boost::chrono::stopclock<> stopclock;

...

...
b) The thread_clock part of the tutorial looks pretty broken.

thread_clock was one of the last features I added and has been tested only on linux with gcc-4.2.1. I need to port it to Windows, but for the moment I have had no time. Could you give more details on how this is broken?

...
Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

You can send to this ML, but as the library is under developement maybe it is better to send you mails to the boost development list boost@list.boost.org.

...
Thanks for this cool library!

Glad to hear it is useful for you.

Have you run the tests onyour platform? It would be great if you can make a pre-review of the library, this will surely help to improve the library before the formal review, could you?

We are using boost::chrono::thread_clock boost::chrono::thread_clock::time_point boost::chrono::system_stopwatch in production now (on an Ubuntu system). All numbers I checked so far looked very reasonable :-) I have no idea what is required for a pre-review. Is there some document for that? Regards, Roland

...

Best, Vicente

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

/home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopwatch_reporter.hpp: In instantiation of `boost::chrono::basic_stopwatch_reporter::basic_stopwatch_reporter(boost::system::error_code&) [with Stopwatch = boost::chrono::stopwatchboost::chrono::process_cpu_clock, Formatter = boost::chrono::basic_time_formatter]': /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopclock.hpp:58: instantiated from `boost::chrono::basic_stopclock::basic_stopclock(boost::system::error_code&) [with Clock = boost::chrono::process_cpu_clock, Formatter = boost::chrono::basic_time_formatter]' /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopclock.hpp:127: instantiated from `boost::chrono::stopclock::stopclock(boost::system::error_code&) [with Clock = boost::chrono::process_cpu_clock, Formatter = boost::chrono::basic_time_formatter]' /home/rbock/metafeed/sources/branches/ehe-2.4.beta/sources/BoostTests/src/Chrono.cpp:14: instantiated from here /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopwatch_reporter.hpp:78: warning: unused parameter `ec' /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/scoped_suspend.hpp: In instantiation of `boost::chrono::scoped_suspend<Clock>::scoped_suspend(boost::system::error_code&) [with Clock = boost::chrono::process_cpu_clock]': /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopwatch_reporter.hpp:148: instantiated from `void boost::chrono::basic_stopwatch_reporter::report(boost::system::error_code&) [with Stopwatch = boost::chrono::stopwatchboost::chrono::process_cpu_clock, Formatter = boost::chrono::basic_time_formatter]' /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopwatch_reporter.hpp:120: instantiated from `boost::chrono::basic_stopwatch_reporter::~basic_stopwatch_reporter() [with Stopwatch = boost::chrono::stopwatchboost::chrono::process_cpu_clock, Formatter = boost::chrono::basic_time_formatter]' /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/stopclock.hpp:47: instantiated from here /home/rbock/metafeed_branches_ehe-2.4.beta_DEBUG/binaries/boost/1.41/include/boost/chrono/scoped_suspend.hpp:25: warning: unused parameter `ec'

vicente.botet

28 May 28 May

1:21 a.m.

...

Hi,

sorry for the late reply, did not see it among all the other stuff....

vicente.botet wrote:

...
Hi, ----- Original Message ----- From: "Roland Bock" To: Sent: Thursday, April 15, 2010 10:48 AM Subject: [Boost-users] [Chrono] How to report problems?

...
Hi,

after having received a push in the right direction by Howard yesterday,

Thanks Howard.

...
everything works fine so far, except for for the following two details:

a) I get some warnings about unused parameters when using the stopclock. For instance:

include/boost/chrono/stopwatch_reporter.hpp:81: warning: unused parameter ‘ec’

The fixes are trivial in all cases I encountered.

Yes I get it. I will check the warnings on the builds I can run. On which platform and with wich compiler are you working? Could you sent me a log with the warnings you found?

Ubuntu-8.04, 64bit, gcc-4.2.4, with the following warning flags: -Wall -Wreorder -Wnon-virtual-dtor -Wno-non-template-friend -Woverloaded-virtual -Wsign-promo -Wextra

Warnings are attached for the following line:

boost::chrono::stopclock<> stopclock;

----- Original Message ----- From: "Roland Bock" To: Cc: Sent: Thursday, May 27, 2010 4:08 PM Subject: Re: [Boost-users] [Chrono] How to report problems? the "unused parameter `ec'" warnings should be corrected in the sandbox http://svn.boost.org/svn/boost/sandbox/chrono/boost/chrono/stopwatch_reporte... I will release version 0.5 on the Boost Vault soon (only minor modifications).

...

...
...
b) The thread_clock part of the tutorial looks pretty broken.

thread_clock was one of the last features I added and has been tested only on linux with gcc-4.2.1. I need to port it to Windows, but for the moment I have had no time. Could you give more details on how this is broken?

...
Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

So, if I understood you, the broken part is on Windows? I will add this waring on the documentation untilI finish the Windows implementation.

...

...
You can send to this ML, but as the library is under developement maybe it is better to send you mails to the boost development list boost@list.boost.org.

...
Thanks for this cool library!

Glad to hear it is useful for you.

Have you run the tests onyour platform? It would be great if you can make a pre-review of the library, this will surely help to improve the library before the formal review, could you?

We are using

boost::chrono::thread_clock boost::chrono::thread_clock::time_point boost::chrono::system_stopwatch

in production now (on an Ubuntu system). All numbers I checked so far looked very reasonable :-)

I have no idea what is required for a pre-review. Is there some document for that?

You can start for example by reviewing the documentation. Any suggestions that can improbe it are welcome. Thanks for your interest, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

Roland Bock

7:05 a.m.

Hi, vicente.botet wrote: [...]

...

...
...
...
b) The thread_clock part of the tutorial looks pretty broken. thread_clock was one of the last features I added and has been tested only on linux with gcc-4.2.1. I need to port it to Windows, but for the moment I have had no time. Could you give more details on how this is broken?

...
Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

So, if I understood you, the broken part is on Windows? I will add this waring on the documentation untilI finish the Windows implementation.

Hmm? No, there has been a mixup: 1) I meant the tutorial page of the documentation: http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/html/boost_chr... There are long code blocks, interrupted by lines like the following formatted as text: class thread_clock { public: typedef nanoseconds duration; typedef duration::rep rep; typedef duration::period period; typedef chrono::time_point time_point; static const bool is_monotonic = true; Something went wrong during the creation of this page. 2) It might be a good addition to the FAQ page to tell where to report problems to (as you suggested: boost@list.boost.org). As for the documentation mini-review, yes, I can try to do that. May take a few days though. Regards, Roland

vicente.botet

10:35 p.m.

----- Original Message ----- From: "Roland Bock" To: Sent: Friday, May 28, 2010 9:05 AM Subject: Re: [Boost-users] [Chrono] How to report problems?

...

Hi,

vicente.botet wrote: [...]

...
...
...
...
b) The thread_clock part of the tutorial looks pretty broken. thread_clock was one of the last features I added and has been tested only on linux with gcc-4.2.1. I need to port it to Windows, but for the moment I have had no time. Could you give more details on how this is broken?

...
Not sure if more things will come up, but if so, where should I send them? Maybe this information would be a nice addition to the FAQ until chrono makes it into boost?

So, if I understood you, the broken part is on Windows? I will add this waring on the documentation untilI finish the Windows implementation.

Hmm? No, there has been a mixup:

1) I meant the tutorial page of the documentation:

http://svn.boost.org/svn/boost/sandbox/chrono/libs/chrono/doc/html/boost_chr...

There are long code blocks, interrupted by lines like the following formatted as text:

class thread_clock { public: typedef nanoseconds duration; typedef duration::rep rep; typedef duration::period period; typedef chrono::time_point time_point; static const bool is_monotonic = true;

Something went wrong during the creation of this page.

Oh I see :(

...

2) It might be a good addition to the FAQ page to tell where to report problems to (as you suggested: boost@list.boost.org).

As for the documentation mini-review, yes, I can try to do that. May take a few days though.

Thanks, Vicente

5384

Age (days ago)

5427

Last active (days ago)

List overview

Download

6 comments

3 participants

participants (3)

Diederick C. Niehorster
Roland Bock
vicente.botet