Message-ID: <0B8A3AF5-91C5-40D5-AEA3-92A2846DB5F2@r-enthusiasts.com>
Date: 2016-12-30T19:38:55Z
From: Romain Francois
Subject: [Rcpp-devel] Rcpp Timer
In-Reply-To: <22630.21795.782989.138019@max.nulle.part>
It made more sense to track times since an origin, esp when you might use several timers in case you use multiple threads.
> Le 30 d?c. 2016 ? 13:37, Dirk Eddelbuettel <edd at debian.org> a ?crit :
>
>
> On 29 December 2016 at 11:25, Jonathan Christensen wrote:
> | Hi Kaspar and Dirk,
> |
> | It is indeed cumulative. Previously (presumably when that gallery page was
> | written) it was not cumulative, but Romain Francois changed the behavior of the
> | step() function several years ago, in this commit: https://github.com/RcppCore/
> | Rcpp/commit/e295b2b178de55291e63705966368404bb0ce5e1.
>
> Nice catch.
>
> | There is no indication or reasoning about changing the behavior, so it may be
> | that making it cumulative was unintentional.
>
> Let's presume it was intentional to the author of the change -- but as you
> rightly point out, it did of course change and reverse previous behaviour.
>
> We could easily add a toggle to the constructor to get an either/or behaviour.
>
> Dirk
>
> --
> http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
> _______________________________________________
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel