A simple stop watch which I want to extendSimple stop watchStop Watch applicationStop Watch Application 2.0A thread-safe stop watch utility classTimer stop watch in AngularJSA low tech approach to measuring game speedSimple timer start and stop from consoleExtremely simple timer class in C++A simple Java class for implementing code stop watchesA simple Java class for implementing code stop watches - follow-up

In a 2 layer PCB with a top layer densely populated, from an EMI & EMC point of view should the ground plane be on top, bottom or both and why?

Te-form and かつ and も?

Three legged NOT gate? What is this symbol?

Not going forward with internship interview process

function evaluation - I don't get it

DeclareMathOperator and widearcarrow with kpfonts

On the Rømer experiments and the speed if light

In SQL Server, why does backward scan of clustered index cannot use parallelism?

How are you supposed to know the strumming pattern for a song from the "chord sheet music"?

A simple stop watch which I want to extend

Dropdowns & Chevrons for Right to Left languages

How to take the beginning and end parts of a list with simpler syntax?

try/finally with bash shell

Who are these characters/superheroes in the posters from Chris's room in Family Guy?

Double redundancy for the Saturn V LVDC computer memory, how were disagreements resolved?

CTCI Chapter 1 : Palindrome Permutation

Is it okay for a ticket seller to grab a tip in the USA?

Why did Gandalf use a sword against the Balrog?

How to avoid the "need" to learn more before conducting research?

What is the difference between 型 and 形?

What are the uses and limitations of Persuasion, Insight, and Deception against other PCs?

Are differences between uniformly distributed numbers uniformly distributed?

Understanding the point of a kölsche Witz

Acceptable to cut steak before searing?



A simple stop watch which I want to extend


Simple stop watchStop Watch applicationStop Watch Application 2.0A thread-safe stop watch utility classTimer stop watch in AngularJSA low tech approach to measuring game speedSimple timer start and stop from consoleExtremely simple timer class in C++A simple Java class for implementing code stop watchesA simple Java class for implementing code stop watches - follow-up






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2












$begingroup$


I am making a very simple stopwatch functionality as below.



New will start the timer.

Pause will suspend the watch.

Start will restart again.

Session will return the duration.



#include<chrono>
#include<vector>

class Timer
using cppTimer = std::chrono::high_resolution_clock;
using seconds = std::chrono::seconds;
std::vector< int64_t > mvSession;
cppTimer::time_point mtpNow;
cppTimer::time_point mtPause;
seconds mtRestart;
bool mbIsPause;
public:

enum Units
sec,
min,
hrs,
end
;

Timer() noexcept: mbIsPause(false), mtRestart ,mvSession(3)


inline void Now() noexcept
mtpNow = cppTimer::now();
mbIsPause = false;
mtRestart = seconds(0);


inline void Pause() noexcept
if(!mbIsPause)
mtPause = cppTimer::now();
mbIsPause = true;




inline void Start() noexcept
if(mbIsPause)
mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);
mbIsPause = false;





std::vector< int64_t > SessionTime()

auto now = cppTimer::now();
auto delay = std::chrono::duration_cast<std::chrono::seconds>(now - mtpNow);

if(mbIsPause)
mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);


auto tp = std::chrono::duration_cast<std::chrono::seconds>(delay - mtRestart); //+ mtRestart ;// SecondsTp(cppTimer::now()) - SecondsTp(mtpNow) + SecondsTp(mtRestart);

mvSession[sec] = tp.count()%60;
mvSession[min] = std::chrono::duration_cast<std::chrono::minutes>(tp).count()%60;
mvSession[hrs] = std::chrono::duration_cast<std::chrono::hours>(tp).count();

return mvSession;


;









share|improve this question









New contributor



Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






$endgroup$




















    2












    $begingroup$


    I am making a very simple stopwatch functionality as below.



    New will start the timer.

    Pause will suspend the watch.

    Start will restart again.

    Session will return the duration.



    #include<chrono>
    #include<vector>

    class Timer
    using cppTimer = std::chrono::high_resolution_clock;
    using seconds = std::chrono::seconds;
    std::vector< int64_t > mvSession;
    cppTimer::time_point mtpNow;
    cppTimer::time_point mtPause;
    seconds mtRestart;
    bool mbIsPause;
    public:

    enum Units
    sec,
    min,
    hrs,
    end
    ;

    Timer() noexcept: mbIsPause(false), mtRestart ,mvSession(3)


    inline void Now() noexcept
    mtpNow = cppTimer::now();
    mbIsPause = false;
    mtRestart = seconds(0);


    inline void Pause() noexcept
    if(!mbIsPause)
    mtPause = cppTimer::now();
    mbIsPause = true;




    inline void Start() noexcept
    if(mbIsPause)
    mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);
    mbIsPause = false;





    std::vector< int64_t > SessionTime()

    auto now = cppTimer::now();
    auto delay = std::chrono::duration_cast<std::chrono::seconds>(now - mtpNow);

    if(mbIsPause)
    mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);


    auto tp = std::chrono::duration_cast<std::chrono::seconds>(delay - mtRestart); //+ mtRestart ;// SecondsTp(cppTimer::now()) - SecondsTp(mtpNow) + SecondsTp(mtRestart);

    mvSession[sec] = tp.count()%60;
    mvSession[min] = std::chrono::duration_cast<std::chrono::minutes>(tp).count()%60;
    mvSession[hrs] = std::chrono::duration_cast<std::chrono::hours>(tp).count();

    return mvSession;


    ;









    share|improve this question









    New contributor



    Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






    $endgroup$
















      2












      2








      2


      1



      $begingroup$


      I am making a very simple stopwatch functionality as below.



      New will start the timer.

      Pause will suspend the watch.

      Start will restart again.

      Session will return the duration.



      #include<chrono>
      #include<vector>

      class Timer
      using cppTimer = std::chrono::high_resolution_clock;
      using seconds = std::chrono::seconds;
      std::vector< int64_t > mvSession;
      cppTimer::time_point mtpNow;
      cppTimer::time_point mtPause;
      seconds mtRestart;
      bool mbIsPause;
      public:

      enum Units
      sec,
      min,
      hrs,
      end
      ;

      Timer() noexcept: mbIsPause(false), mtRestart ,mvSession(3)


      inline void Now() noexcept
      mtpNow = cppTimer::now();
      mbIsPause = false;
      mtRestart = seconds(0);


      inline void Pause() noexcept
      if(!mbIsPause)
      mtPause = cppTimer::now();
      mbIsPause = true;




      inline void Start() noexcept
      if(mbIsPause)
      mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);
      mbIsPause = false;





      std::vector< int64_t > SessionTime()

      auto now = cppTimer::now();
      auto delay = std::chrono::duration_cast<std::chrono::seconds>(now - mtpNow);

      if(mbIsPause)
      mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);


      auto tp = std::chrono::duration_cast<std::chrono::seconds>(delay - mtRestart); //+ mtRestart ;// SecondsTp(cppTimer::now()) - SecondsTp(mtpNow) + SecondsTp(mtRestart);

      mvSession[sec] = tp.count()%60;
      mvSession[min] = std::chrono::duration_cast<std::chrono::minutes>(tp).count()%60;
      mvSession[hrs] = std::chrono::duration_cast<std::chrono::hours>(tp).count();

      return mvSession;


      ;









      share|improve this question









      New contributor



      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      $endgroup$




      I am making a very simple stopwatch functionality as below.



      New will start the timer.

      Pause will suspend the watch.

      Start will restart again.

      Session will return the duration.



      #include<chrono>
      #include<vector>

      class Timer
      using cppTimer = std::chrono::high_resolution_clock;
      using seconds = std::chrono::seconds;
      std::vector< int64_t > mvSession;
      cppTimer::time_point mtpNow;
      cppTimer::time_point mtPause;
      seconds mtRestart;
      bool mbIsPause;
      public:

      enum Units
      sec,
      min,
      hrs,
      end
      ;

      Timer() noexcept: mbIsPause(false), mtRestart ,mvSession(3)


      inline void Now() noexcept
      mtpNow = cppTimer::now();
      mbIsPause = false;
      mtRestart = seconds(0);


      inline void Pause() noexcept
      if(!mbIsPause)
      mtPause = cppTimer::now();
      mbIsPause = true;




      inline void Start() noexcept
      if(mbIsPause)
      mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);
      mbIsPause = false;





      std::vector< int64_t > SessionTime()

      auto now = cppTimer::now();
      auto delay = std::chrono::duration_cast<std::chrono::seconds>(now - mtpNow);

      if(mbIsPause)
      mtRestart += std::chrono::duration_cast<std::chrono::seconds>(cppTimer::now() - mtPause);


      auto tp = std::chrono::duration_cast<std::chrono::seconds>(delay - mtRestart); //+ mtRestart ;// SecondsTp(cppTimer::now()) - SecondsTp(mtpNow) + SecondsTp(mtRestart);

      mvSession[sec] = tp.count()%60;
      mvSession[min] = std::chrono::duration_cast<std::chrono::minutes>(tp).count()%60;
      mvSession[hrs] = std::chrono::duration_cast<std::chrono::hours>(tp).count();

      return mvSession;


      ;






      c++ timer






      share|improve this question









      New contributor



      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share|improve this question









      New contributor



      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share|improve this question




      share|improve this question








      edited 1 hour ago









      Peter Mortensen

      2621 silver badge7 bronze badges




      2621 silver badge7 bronze badges






      New contributor



      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      asked 18 hours ago









      MohitMohit

      111 bronze badge




      111 bronze badge




      New contributor



      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




      New contributor




      Mohit is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.

























          2 Answers
          2






          active

          oldest

          votes


















          6












          $begingroup$

          Don't use member variables for temporary storage



          Your class Timer has a member variable mvSession, which is unnecessary. It is only used in SessionTime(), where it is filled in and returned. No other functions use it. Instead, just declare std::vector<int64_t> mvSession(3) inside SessionTime().



          By making it a member variable, you introduced two problems: first, your class now uses more memory than necessary. Second, the function SessionTime() is now no longer reentrant; if two threads would call SessionTime() simultaneously, they would both write to the same mvSession variable, potentially corrupting it.



          Use std::chrono::steady_clock for timers



          The problem with std::chrono::high_resolution_clock() is that it is not guaranteed what kind of clock it is. It can represent wall clock time, which can jump ahead or forwards because of summer and winter time, leap seconds, the computer suspending and resuming. This is not something you want for a timer where you are interested in a simple duration. For this, you want to use std::chrono::steady_clock, which is guaranteed to be a monotonically increasing clock. Also, your function SessionTime() returns the time in a resolution of seconds, so you don't need a high resolution clock anyway.



          Don't use Hungarian notation



          There might be some merits to Hungarian notation, but it really isn't necessary to use it for C++, since the compiler will do type checking for you. Moreover, it's easy to use the wrong prefix, and it's hard to come up with a reasonable prefix when you can have complex types.



          You are already making mistakes in your code. For example, mtpNow and mtPause are both of type cppTimer::time_point. So the prefix should have been the same. And mtRestart has a different type than mtPause, so their prefixes should have been different. I recommend that you just avoid using Hungarian notation altoghether.



          Be consistent with using



          You are declaring using seconds = std::chrono::seconds, and use seconds in a few places, but you also use std::chrono::seconds in a lot of places. Furthermore, you also use std::chrono::minutes and std::chrono::hours, but have not declared an alias for them. In this case, I suggest you don't declare using seconds at all.



          I would keep using cppTimer though, since it basically selects which clock to use. That makes it easier to change the clock later by just changing one line of code. I would write using clock = ... though, to be consistent with the C++ library itself.



          Don't cast to seconds too early



          Instead of seconds mtRestart, use cppTimer::duration mtRestart. This will keep the accuracy of the duration to the same as the clock itself. Only cast durations to seconds or other time intervals until the last moment possible. The same goes for the calculation of delay in SessionTime(), just write:



          auto delay = now - mtpNow;


          Use nouns for variable names, verbs for function names



          A variable holds (the value of) a thing, so its name should naturally be a noun. Functions do stuff, so there names should generally be verbs. The function Now() should actually be named Start(). Your function Start() should probably be named Continue(). The function SessionTime() calculates how long the timer has been running for, so probably should be named GetDuration().



          Conversely, the variables mtPause and mtRestart should be renamed to nouns as well. They are a bit confusing. Sure, you set mtPause in the Pause() function, but it doesn't describe what the value actually means. The same goes for mtRestart. I would instead write:



          clock::time_point StartTime;
          clock::time_point PauseTime;
          clock::duration PausedDuration;
          bool IsPaused;


          Now you can rewrite the function Now() to:



          void Start() 
          StartTime = clock::now();
          IsPaused = false;
          PausedDuration = ;



          Remove mtRestart



          You are using two variables to handle the timer being paused, mtPause and mtRestart. However, you only need one. In the Pause() function, you indeed just record when this function is called. However, when restarting the timer, instead of adding the duration of being paused to mtRestart, just add that duration to mtpNow instead:



          void Start() 
          if(mbIsPause)
          mtpNow += cppTimer::now() - mtPause;
          mbIsPause = false;




          This also simplifies SessionTime():



          std::vector<int64_t> SessionTime() 
          auto end = mbIsPause ? mtPause : cppTimer::now();
          auto tp = std::chrono::duration_cast<std::chrono::seconds>(end - mtpNow);
          ...



          Also, since mtPause is only ever 0 when you didn't pause, you can use that to signal whether the timer is paused instead of having bool mbIsPause.



          Another option is @user673679's suggestion of storing only the start time and the accumulated elapsed time so far. You would then use the start time being equal to as a signal that the timer has not been started.



          Just return a std::chrono::duration



          When you want the elapsed time, I would avoid having the Timer class be responsible for converting the duration to a vector of integers representing hours, minutes and seconds. It reduces the accuracy of your timer. Instead, I would just return a std::chrono::duration, and have the caller decide whether it wants to convert that to something. It also is much more efficient than having to construct a std::vector<int64_t>.



          Try to make it behave reasonable in all situations



          One issue with your code is that it only gives reasonable results for SessionTime() if you have called Now() at least once. You didn't initialize mtpNow, and even if it was value-initialized to zero, then SessionTime() will return the time that has passed since the epoch.



          If you want the Timer to behave like it was started at construction time, then initialize mtpNow to cppTimer::now(). If you want it to behave like it was paused, then ensure both mtpNow and mtPause are initialized to the same value (I suggest just using ), and that mbIsPause is true.



          Make it work like a real stopwatch



          As already suggested by others, it helps to think of a timer as a stopwatch. A real stopwatch starts in a stopped state, showing an elapsed time of zero. Then, you can start and stop the timer mechanism with buttons. Usually, there is a separate button to reset the stopwatch to its initial state. By making the class act like something a lot of people are already familiar with, the code is easier to understand for others.



          Reworked code



          Here is an example of what the code would look like with my suggestions applied, as well as @user673679's way of storing the elapsed time between previous start and stops of the clock:



          #include <chrono>

          class Timer
          using clock = std::chrono::steady_clock;
          clock::time_point StartTime = ;
          clock::duration ElapsedTime = ;

          public:
          bool IsRunning() const
          return StartTime != clock::time_point;


          void Start()
          if(!IsRunning())
          StartTime = clock::now();



          void Stop()
          if(IsRunning())
          ElapsedTime += clock::now() - StartTime;
          StartTime = ;



          void Reset()
          StartTime = ;
          ElapsedTime = ;


          clock::duration GetElapsed()
          auto result = ElapsedTime;
          if(IsRunning())
          result += clock::now() - StartTime;

          return result;

          ;
          ```





          share|improve this answer











          $endgroup$














          • $begingroup$
            That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
            $endgroup$
            – Peter Mortensen
            3 hours ago



















          2












          $begingroup$

          • It's fine to prefix member variables with an m, but it's probably best to avoid type prefixes (e.g. mtpNow). It makes code harder to read (you have to know what every abbreviation means), it's a pain to maintain (e.g. mtPause should probably be mtpPause to be consistent). Modern tools eliminate the need for this too (mousing over a variable in Visual Studio will tell me the exact type, not an approximation).


          • Functions defined inline in the class don't need to be declared inline.



          • The naming is very confusing:



            • Now() differs from the standard library (now() returns the current time, and is arguably still a terrible name). Functions names should be commands or questions. Perhaps Restart() or Reset() would be better.


            • Start() is also not ideal. One might expect the function to do what Now() does. I'd suggest calling it Unpause(), which makes the purpose clearer.


            • mtRestart is an odd name for the time spent paused.



          • We don't really need the Now() / Restart() function, since we can just assign a new timer to the old one to do the same thing (e.g. Timer timer; ...; timer = Timer(); // restarted!).


          • There's no reason to keep a vector in the class (we're copying it every time anyway, so we might as well just create a new vector each time).


          • We don't need a vector, since it always has 3 values, it would be neater to return a simple struct, which would allow us to give each value a name. Or...


          • The real solution is to just return an appropriate chrono:: type, and let the user worry about formatting / converting it.


          • I'd suggest naming the class Stopwatch, since that's more specific to the pausable timing functionality we need. We can actually implement this functionality based on a simpler, non-pausable Timer class.



          So overall I'd suggest something more like this (not tested properly):



          #include <chrono>

          template<class ClockT = std::chrono::high_resolution_clock>
          class Timer

          ClockT::time_point m_start;

          public:

          Timer():
          m_start(ClockT::now())




          ClockT::duration GetElapsedTime() const

          return ClockT::now() - m_start;

          ;

          template<class ClockT = std::chrono::high_resolution_clock>
          class Stopwatch

          bool m_paused;
          Timer<ClockT> m_timer;
          ClockT::duration m_timeAccumulated;

          public:

          explicit Stopwatch(bool paused = false):
          m_paused(paused),
          m_timer(),
          m_timeAccumulated(0)




          void Pause()

          m_timeAccumulated += m_timer.GetElapsedTime();
          m_paused = true;


          void Unpause()

          if (m_paused)

          m_timer = Timer<ClockT>();
          m_paused = false;



          ClockT::duration GetElapsedTime() const

          if (m_paused)
          return m_timeAccumulated;

          return m_timeAccumulated + m_timer.GetElapsedTime();

          ;

          #include <iostream>

          int main()

          using seconds_t = std::chrono::duration<float>;

          Stopwatch s;

          for (int i = 0; i != 50; ++i) std::cout << ".";
          std::cout << "n";

          std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

          s = Stopwatch(true);
          std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

          s.Unpause();

          for (int i = 0; i != 50; ++i) std::cout << ".";
          std::cout << "n";

          s.Pause();
          std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

          for (int i = 0; i != 50; ++i) std::cout << ".";
          std::cout << "n";

          std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;






          share|improve this answer









          $endgroup$

















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "196"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );






            Mohit is a new contributor. Be nice, and check out our Code of Conduct.









            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f225923%2fa-simple-stop-watch-which-i-want-to-extend%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            6












            $begingroup$

            Don't use member variables for temporary storage



            Your class Timer has a member variable mvSession, which is unnecessary. It is only used in SessionTime(), where it is filled in and returned. No other functions use it. Instead, just declare std::vector<int64_t> mvSession(3) inside SessionTime().



            By making it a member variable, you introduced two problems: first, your class now uses more memory than necessary. Second, the function SessionTime() is now no longer reentrant; if two threads would call SessionTime() simultaneously, they would both write to the same mvSession variable, potentially corrupting it.



            Use std::chrono::steady_clock for timers



            The problem with std::chrono::high_resolution_clock() is that it is not guaranteed what kind of clock it is. It can represent wall clock time, which can jump ahead or forwards because of summer and winter time, leap seconds, the computer suspending and resuming. This is not something you want for a timer where you are interested in a simple duration. For this, you want to use std::chrono::steady_clock, which is guaranteed to be a monotonically increasing clock. Also, your function SessionTime() returns the time in a resolution of seconds, so you don't need a high resolution clock anyway.



            Don't use Hungarian notation



            There might be some merits to Hungarian notation, but it really isn't necessary to use it for C++, since the compiler will do type checking for you. Moreover, it's easy to use the wrong prefix, and it's hard to come up with a reasonable prefix when you can have complex types.



            You are already making mistakes in your code. For example, mtpNow and mtPause are both of type cppTimer::time_point. So the prefix should have been the same. And mtRestart has a different type than mtPause, so their prefixes should have been different. I recommend that you just avoid using Hungarian notation altoghether.



            Be consistent with using



            You are declaring using seconds = std::chrono::seconds, and use seconds in a few places, but you also use std::chrono::seconds in a lot of places. Furthermore, you also use std::chrono::minutes and std::chrono::hours, but have not declared an alias for them. In this case, I suggest you don't declare using seconds at all.



            I would keep using cppTimer though, since it basically selects which clock to use. That makes it easier to change the clock later by just changing one line of code. I would write using clock = ... though, to be consistent with the C++ library itself.



            Don't cast to seconds too early



            Instead of seconds mtRestart, use cppTimer::duration mtRestart. This will keep the accuracy of the duration to the same as the clock itself. Only cast durations to seconds or other time intervals until the last moment possible. The same goes for the calculation of delay in SessionTime(), just write:



            auto delay = now - mtpNow;


            Use nouns for variable names, verbs for function names



            A variable holds (the value of) a thing, so its name should naturally be a noun. Functions do stuff, so there names should generally be verbs. The function Now() should actually be named Start(). Your function Start() should probably be named Continue(). The function SessionTime() calculates how long the timer has been running for, so probably should be named GetDuration().



            Conversely, the variables mtPause and mtRestart should be renamed to nouns as well. They are a bit confusing. Sure, you set mtPause in the Pause() function, but it doesn't describe what the value actually means. The same goes for mtRestart. I would instead write:



            clock::time_point StartTime;
            clock::time_point PauseTime;
            clock::duration PausedDuration;
            bool IsPaused;


            Now you can rewrite the function Now() to:



            void Start() 
            StartTime = clock::now();
            IsPaused = false;
            PausedDuration = ;



            Remove mtRestart



            You are using two variables to handle the timer being paused, mtPause and mtRestart. However, you only need one. In the Pause() function, you indeed just record when this function is called. However, when restarting the timer, instead of adding the duration of being paused to mtRestart, just add that duration to mtpNow instead:



            void Start() 
            if(mbIsPause)
            mtpNow += cppTimer::now() - mtPause;
            mbIsPause = false;




            This also simplifies SessionTime():



            std::vector<int64_t> SessionTime() 
            auto end = mbIsPause ? mtPause : cppTimer::now();
            auto tp = std::chrono::duration_cast<std::chrono::seconds>(end - mtpNow);
            ...



            Also, since mtPause is only ever 0 when you didn't pause, you can use that to signal whether the timer is paused instead of having bool mbIsPause.



            Another option is @user673679's suggestion of storing only the start time and the accumulated elapsed time so far. You would then use the start time being equal to as a signal that the timer has not been started.



            Just return a std::chrono::duration



            When you want the elapsed time, I would avoid having the Timer class be responsible for converting the duration to a vector of integers representing hours, minutes and seconds. It reduces the accuracy of your timer. Instead, I would just return a std::chrono::duration, and have the caller decide whether it wants to convert that to something. It also is much more efficient than having to construct a std::vector<int64_t>.



            Try to make it behave reasonable in all situations



            One issue with your code is that it only gives reasonable results for SessionTime() if you have called Now() at least once. You didn't initialize mtpNow, and even if it was value-initialized to zero, then SessionTime() will return the time that has passed since the epoch.



            If you want the Timer to behave like it was started at construction time, then initialize mtpNow to cppTimer::now(). If you want it to behave like it was paused, then ensure both mtpNow and mtPause are initialized to the same value (I suggest just using ), and that mbIsPause is true.



            Make it work like a real stopwatch



            As already suggested by others, it helps to think of a timer as a stopwatch. A real stopwatch starts in a stopped state, showing an elapsed time of zero. Then, you can start and stop the timer mechanism with buttons. Usually, there is a separate button to reset the stopwatch to its initial state. By making the class act like something a lot of people are already familiar with, the code is easier to understand for others.



            Reworked code



            Here is an example of what the code would look like with my suggestions applied, as well as @user673679's way of storing the elapsed time between previous start and stops of the clock:



            #include <chrono>

            class Timer
            using clock = std::chrono::steady_clock;
            clock::time_point StartTime = ;
            clock::duration ElapsedTime = ;

            public:
            bool IsRunning() const
            return StartTime != clock::time_point;


            void Start()
            if(!IsRunning())
            StartTime = clock::now();



            void Stop()
            if(IsRunning())
            ElapsedTime += clock::now() - StartTime;
            StartTime = ;



            void Reset()
            StartTime = ;
            ElapsedTime = ;


            clock::duration GetElapsed()
            auto result = ElapsedTime;
            if(IsRunning())
            result += clock::now() - StartTime;

            return result;

            ;
            ```





            share|improve this answer











            $endgroup$














            • $begingroup$
              That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
              $endgroup$
              – Peter Mortensen
              3 hours ago
















            6












            $begingroup$

            Don't use member variables for temporary storage



            Your class Timer has a member variable mvSession, which is unnecessary. It is only used in SessionTime(), where it is filled in and returned. No other functions use it. Instead, just declare std::vector<int64_t> mvSession(3) inside SessionTime().



            By making it a member variable, you introduced two problems: first, your class now uses more memory than necessary. Second, the function SessionTime() is now no longer reentrant; if two threads would call SessionTime() simultaneously, they would both write to the same mvSession variable, potentially corrupting it.



            Use std::chrono::steady_clock for timers



            The problem with std::chrono::high_resolution_clock() is that it is not guaranteed what kind of clock it is. It can represent wall clock time, which can jump ahead or forwards because of summer and winter time, leap seconds, the computer suspending and resuming. This is not something you want for a timer where you are interested in a simple duration. For this, you want to use std::chrono::steady_clock, which is guaranteed to be a monotonically increasing clock. Also, your function SessionTime() returns the time in a resolution of seconds, so you don't need a high resolution clock anyway.



            Don't use Hungarian notation



            There might be some merits to Hungarian notation, but it really isn't necessary to use it for C++, since the compiler will do type checking for you. Moreover, it's easy to use the wrong prefix, and it's hard to come up with a reasonable prefix when you can have complex types.



            You are already making mistakes in your code. For example, mtpNow and mtPause are both of type cppTimer::time_point. So the prefix should have been the same. And mtRestart has a different type than mtPause, so their prefixes should have been different. I recommend that you just avoid using Hungarian notation altoghether.



            Be consistent with using



            You are declaring using seconds = std::chrono::seconds, and use seconds in a few places, but you also use std::chrono::seconds in a lot of places. Furthermore, you also use std::chrono::minutes and std::chrono::hours, but have not declared an alias for them. In this case, I suggest you don't declare using seconds at all.



            I would keep using cppTimer though, since it basically selects which clock to use. That makes it easier to change the clock later by just changing one line of code. I would write using clock = ... though, to be consistent with the C++ library itself.



            Don't cast to seconds too early



            Instead of seconds mtRestart, use cppTimer::duration mtRestart. This will keep the accuracy of the duration to the same as the clock itself. Only cast durations to seconds or other time intervals until the last moment possible. The same goes for the calculation of delay in SessionTime(), just write:



            auto delay = now - mtpNow;


            Use nouns for variable names, verbs for function names



            A variable holds (the value of) a thing, so its name should naturally be a noun. Functions do stuff, so there names should generally be verbs. The function Now() should actually be named Start(). Your function Start() should probably be named Continue(). The function SessionTime() calculates how long the timer has been running for, so probably should be named GetDuration().



            Conversely, the variables mtPause and mtRestart should be renamed to nouns as well. They are a bit confusing. Sure, you set mtPause in the Pause() function, but it doesn't describe what the value actually means. The same goes for mtRestart. I would instead write:



            clock::time_point StartTime;
            clock::time_point PauseTime;
            clock::duration PausedDuration;
            bool IsPaused;


            Now you can rewrite the function Now() to:



            void Start() 
            StartTime = clock::now();
            IsPaused = false;
            PausedDuration = ;



            Remove mtRestart



            You are using two variables to handle the timer being paused, mtPause and mtRestart. However, you only need one. In the Pause() function, you indeed just record when this function is called. However, when restarting the timer, instead of adding the duration of being paused to mtRestart, just add that duration to mtpNow instead:



            void Start() 
            if(mbIsPause)
            mtpNow += cppTimer::now() - mtPause;
            mbIsPause = false;




            This also simplifies SessionTime():



            std::vector<int64_t> SessionTime() 
            auto end = mbIsPause ? mtPause : cppTimer::now();
            auto tp = std::chrono::duration_cast<std::chrono::seconds>(end - mtpNow);
            ...



            Also, since mtPause is only ever 0 when you didn't pause, you can use that to signal whether the timer is paused instead of having bool mbIsPause.



            Another option is @user673679's suggestion of storing only the start time and the accumulated elapsed time so far. You would then use the start time being equal to as a signal that the timer has not been started.



            Just return a std::chrono::duration



            When you want the elapsed time, I would avoid having the Timer class be responsible for converting the duration to a vector of integers representing hours, minutes and seconds. It reduces the accuracy of your timer. Instead, I would just return a std::chrono::duration, and have the caller decide whether it wants to convert that to something. It also is much more efficient than having to construct a std::vector<int64_t>.



            Try to make it behave reasonable in all situations



            One issue with your code is that it only gives reasonable results for SessionTime() if you have called Now() at least once. You didn't initialize mtpNow, and even if it was value-initialized to zero, then SessionTime() will return the time that has passed since the epoch.



            If you want the Timer to behave like it was started at construction time, then initialize mtpNow to cppTimer::now(). If you want it to behave like it was paused, then ensure both mtpNow and mtPause are initialized to the same value (I suggest just using ), and that mbIsPause is true.



            Make it work like a real stopwatch



            As already suggested by others, it helps to think of a timer as a stopwatch. A real stopwatch starts in a stopped state, showing an elapsed time of zero. Then, you can start and stop the timer mechanism with buttons. Usually, there is a separate button to reset the stopwatch to its initial state. By making the class act like something a lot of people are already familiar with, the code is easier to understand for others.



            Reworked code



            Here is an example of what the code would look like with my suggestions applied, as well as @user673679's way of storing the elapsed time between previous start and stops of the clock:



            #include <chrono>

            class Timer
            using clock = std::chrono::steady_clock;
            clock::time_point StartTime = ;
            clock::duration ElapsedTime = ;

            public:
            bool IsRunning() const
            return StartTime != clock::time_point;


            void Start()
            if(!IsRunning())
            StartTime = clock::now();



            void Stop()
            if(IsRunning())
            ElapsedTime += clock::now() - StartTime;
            StartTime = ;



            void Reset()
            StartTime = ;
            ElapsedTime = ;


            clock::duration GetElapsed()
            auto result = ElapsedTime;
            if(IsRunning())
            result += clock::now() - StartTime;

            return result;

            ;
            ```





            share|improve this answer











            $endgroup$














            • $begingroup$
              That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
              $endgroup$
              – Peter Mortensen
              3 hours ago














            6












            6








            6





            $begingroup$

            Don't use member variables for temporary storage



            Your class Timer has a member variable mvSession, which is unnecessary. It is only used in SessionTime(), where it is filled in and returned. No other functions use it. Instead, just declare std::vector<int64_t> mvSession(3) inside SessionTime().



            By making it a member variable, you introduced two problems: first, your class now uses more memory than necessary. Second, the function SessionTime() is now no longer reentrant; if two threads would call SessionTime() simultaneously, they would both write to the same mvSession variable, potentially corrupting it.



            Use std::chrono::steady_clock for timers



            The problem with std::chrono::high_resolution_clock() is that it is not guaranteed what kind of clock it is. It can represent wall clock time, which can jump ahead or forwards because of summer and winter time, leap seconds, the computer suspending and resuming. This is not something you want for a timer where you are interested in a simple duration. For this, you want to use std::chrono::steady_clock, which is guaranteed to be a monotonically increasing clock. Also, your function SessionTime() returns the time in a resolution of seconds, so you don't need a high resolution clock anyway.



            Don't use Hungarian notation



            There might be some merits to Hungarian notation, but it really isn't necessary to use it for C++, since the compiler will do type checking for you. Moreover, it's easy to use the wrong prefix, and it's hard to come up with a reasonable prefix when you can have complex types.



            You are already making mistakes in your code. For example, mtpNow and mtPause are both of type cppTimer::time_point. So the prefix should have been the same. And mtRestart has a different type than mtPause, so their prefixes should have been different. I recommend that you just avoid using Hungarian notation altoghether.



            Be consistent with using



            You are declaring using seconds = std::chrono::seconds, and use seconds in a few places, but you also use std::chrono::seconds in a lot of places. Furthermore, you also use std::chrono::minutes and std::chrono::hours, but have not declared an alias for them. In this case, I suggest you don't declare using seconds at all.



            I would keep using cppTimer though, since it basically selects which clock to use. That makes it easier to change the clock later by just changing one line of code. I would write using clock = ... though, to be consistent with the C++ library itself.



            Don't cast to seconds too early



            Instead of seconds mtRestart, use cppTimer::duration mtRestart. This will keep the accuracy of the duration to the same as the clock itself. Only cast durations to seconds or other time intervals until the last moment possible. The same goes for the calculation of delay in SessionTime(), just write:



            auto delay = now - mtpNow;


            Use nouns for variable names, verbs for function names



            A variable holds (the value of) a thing, so its name should naturally be a noun. Functions do stuff, so there names should generally be verbs. The function Now() should actually be named Start(). Your function Start() should probably be named Continue(). The function SessionTime() calculates how long the timer has been running for, so probably should be named GetDuration().



            Conversely, the variables mtPause and mtRestart should be renamed to nouns as well. They are a bit confusing. Sure, you set mtPause in the Pause() function, but it doesn't describe what the value actually means. The same goes for mtRestart. I would instead write:



            clock::time_point StartTime;
            clock::time_point PauseTime;
            clock::duration PausedDuration;
            bool IsPaused;


            Now you can rewrite the function Now() to:



            void Start() 
            StartTime = clock::now();
            IsPaused = false;
            PausedDuration = ;



            Remove mtRestart



            You are using two variables to handle the timer being paused, mtPause and mtRestart. However, you only need one. In the Pause() function, you indeed just record when this function is called. However, when restarting the timer, instead of adding the duration of being paused to mtRestart, just add that duration to mtpNow instead:



            void Start() 
            if(mbIsPause)
            mtpNow += cppTimer::now() - mtPause;
            mbIsPause = false;




            This also simplifies SessionTime():



            std::vector<int64_t> SessionTime() 
            auto end = mbIsPause ? mtPause : cppTimer::now();
            auto tp = std::chrono::duration_cast<std::chrono::seconds>(end - mtpNow);
            ...



            Also, since mtPause is only ever 0 when you didn't pause, you can use that to signal whether the timer is paused instead of having bool mbIsPause.



            Another option is @user673679's suggestion of storing only the start time and the accumulated elapsed time so far. You would then use the start time being equal to as a signal that the timer has not been started.



            Just return a std::chrono::duration



            When you want the elapsed time, I would avoid having the Timer class be responsible for converting the duration to a vector of integers representing hours, minutes and seconds. It reduces the accuracy of your timer. Instead, I would just return a std::chrono::duration, and have the caller decide whether it wants to convert that to something. It also is much more efficient than having to construct a std::vector<int64_t>.



            Try to make it behave reasonable in all situations



            One issue with your code is that it only gives reasonable results for SessionTime() if you have called Now() at least once. You didn't initialize mtpNow, and even if it was value-initialized to zero, then SessionTime() will return the time that has passed since the epoch.



            If you want the Timer to behave like it was started at construction time, then initialize mtpNow to cppTimer::now(). If you want it to behave like it was paused, then ensure both mtpNow and mtPause are initialized to the same value (I suggest just using ), and that mbIsPause is true.



            Make it work like a real stopwatch



            As already suggested by others, it helps to think of a timer as a stopwatch. A real stopwatch starts in a stopped state, showing an elapsed time of zero. Then, you can start and stop the timer mechanism with buttons. Usually, there is a separate button to reset the stopwatch to its initial state. By making the class act like something a lot of people are already familiar with, the code is easier to understand for others.



            Reworked code



            Here is an example of what the code would look like with my suggestions applied, as well as @user673679's way of storing the elapsed time between previous start and stops of the clock:



            #include <chrono>

            class Timer
            using clock = std::chrono::steady_clock;
            clock::time_point StartTime = ;
            clock::duration ElapsedTime = ;

            public:
            bool IsRunning() const
            return StartTime != clock::time_point;


            void Start()
            if(!IsRunning())
            StartTime = clock::now();



            void Stop()
            if(IsRunning())
            ElapsedTime += clock::now() - StartTime;
            StartTime = ;



            void Reset()
            StartTime = ;
            ElapsedTime = ;


            clock::duration GetElapsed()
            auto result = ElapsedTime;
            if(IsRunning())
            result += clock::now() - StartTime;

            return result;

            ;
            ```





            share|improve this answer











            $endgroup$



            Don't use member variables for temporary storage



            Your class Timer has a member variable mvSession, which is unnecessary. It is only used in SessionTime(), where it is filled in and returned. No other functions use it. Instead, just declare std::vector<int64_t> mvSession(3) inside SessionTime().



            By making it a member variable, you introduced two problems: first, your class now uses more memory than necessary. Second, the function SessionTime() is now no longer reentrant; if two threads would call SessionTime() simultaneously, they would both write to the same mvSession variable, potentially corrupting it.



            Use std::chrono::steady_clock for timers



            The problem with std::chrono::high_resolution_clock() is that it is not guaranteed what kind of clock it is. It can represent wall clock time, which can jump ahead or forwards because of summer and winter time, leap seconds, the computer suspending and resuming. This is not something you want for a timer where you are interested in a simple duration. For this, you want to use std::chrono::steady_clock, which is guaranteed to be a monotonically increasing clock. Also, your function SessionTime() returns the time in a resolution of seconds, so you don't need a high resolution clock anyway.



            Don't use Hungarian notation



            There might be some merits to Hungarian notation, but it really isn't necessary to use it for C++, since the compiler will do type checking for you. Moreover, it's easy to use the wrong prefix, and it's hard to come up with a reasonable prefix when you can have complex types.



            You are already making mistakes in your code. For example, mtpNow and mtPause are both of type cppTimer::time_point. So the prefix should have been the same. And mtRestart has a different type than mtPause, so their prefixes should have been different. I recommend that you just avoid using Hungarian notation altoghether.



            Be consistent with using



            You are declaring using seconds = std::chrono::seconds, and use seconds in a few places, but you also use std::chrono::seconds in a lot of places. Furthermore, you also use std::chrono::minutes and std::chrono::hours, but have not declared an alias for them. In this case, I suggest you don't declare using seconds at all.



            I would keep using cppTimer though, since it basically selects which clock to use. That makes it easier to change the clock later by just changing one line of code. I would write using clock = ... though, to be consistent with the C++ library itself.



            Don't cast to seconds too early



            Instead of seconds mtRestart, use cppTimer::duration mtRestart. This will keep the accuracy of the duration to the same as the clock itself. Only cast durations to seconds or other time intervals until the last moment possible. The same goes for the calculation of delay in SessionTime(), just write:



            auto delay = now - mtpNow;


            Use nouns for variable names, verbs for function names



            A variable holds (the value of) a thing, so its name should naturally be a noun. Functions do stuff, so there names should generally be verbs. The function Now() should actually be named Start(). Your function Start() should probably be named Continue(). The function SessionTime() calculates how long the timer has been running for, so probably should be named GetDuration().



            Conversely, the variables mtPause and mtRestart should be renamed to nouns as well. They are a bit confusing. Sure, you set mtPause in the Pause() function, but it doesn't describe what the value actually means. The same goes for mtRestart. I would instead write:



            clock::time_point StartTime;
            clock::time_point PauseTime;
            clock::duration PausedDuration;
            bool IsPaused;


            Now you can rewrite the function Now() to:



            void Start() 
            StartTime = clock::now();
            IsPaused = false;
            PausedDuration = ;



            Remove mtRestart



            You are using two variables to handle the timer being paused, mtPause and mtRestart. However, you only need one. In the Pause() function, you indeed just record when this function is called. However, when restarting the timer, instead of adding the duration of being paused to mtRestart, just add that duration to mtpNow instead:



            void Start() 
            if(mbIsPause)
            mtpNow += cppTimer::now() - mtPause;
            mbIsPause = false;




            This also simplifies SessionTime():



            std::vector<int64_t> SessionTime() 
            auto end = mbIsPause ? mtPause : cppTimer::now();
            auto tp = std::chrono::duration_cast<std::chrono::seconds>(end - mtpNow);
            ...



            Also, since mtPause is only ever 0 when you didn't pause, you can use that to signal whether the timer is paused instead of having bool mbIsPause.



            Another option is @user673679's suggestion of storing only the start time and the accumulated elapsed time so far. You would then use the start time being equal to as a signal that the timer has not been started.



            Just return a std::chrono::duration



            When you want the elapsed time, I would avoid having the Timer class be responsible for converting the duration to a vector of integers representing hours, minutes and seconds. It reduces the accuracy of your timer. Instead, I would just return a std::chrono::duration, and have the caller decide whether it wants to convert that to something. It also is much more efficient than having to construct a std::vector<int64_t>.



            Try to make it behave reasonable in all situations



            One issue with your code is that it only gives reasonable results for SessionTime() if you have called Now() at least once. You didn't initialize mtpNow, and even if it was value-initialized to zero, then SessionTime() will return the time that has passed since the epoch.



            If you want the Timer to behave like it was started at construction time, then initialize mtpNow to cppTimer::now(). If you want it to behave like it was paused, then ensure both mtpNow and mtPause are initialized to the same value (I suggest just using ), and that mbIsPause is true.



            Make it work like a real stopwatch



            As already suggested by others, it helps to think of a timer as a stopwatch. A real stopwatch starts in a stopped state, showing an elapsed time of zero. Then, you can start and stop the timer mechanism with buttons. Usually, there is a separate button to reset the stopwatch to its initial state. By making the class act like something a lot of people are already familiar with, the code is easier to understand for others.



            Reworked code



            Here is an example of what the code would look like with my suggestions applied, as well as @user673679's way of storing the elapsed time between previous start and stops of the clock:



            #include <chrono>

            class Timer
            using clock = std::chrono::steady_clock;
            clock::time_point StartTime = ;
            clock::duration ElapsedTime = ;

            public:
            bool IsRunning() const
            return StartTime != clock::time_point;


            void Start()
            if(!IsRunning())
            StartTime = clock::now();



            void Stop()
            if(IsRunning())
            ElapsedTime += clock::now() - StartTime;
            StartTime = ;



            void Reset()
            StartTime = ;
            ElapsedTime = ;


            clock::duration GetElapsed()
            auto result = ElapsedTime;
            if(IsRunning())
            result += clock::now() - StartTime;

            return result;

            ;
            ```






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 8 hours ago

























            answered 15 hours ago









            G. SliepenG. Sliepen

            1,5024 silver badges11 bronze badges




            1,5024 silver badges11 bronze badges














            • $begingroup$
              That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
              $endgroup$
              – Peter Mortensen
              3 hours ago

















            • $begingroup$
              That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
              $endgroup$
              – Peter Mortensen
              3 hours ago
















            $begingroup$
            That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
            $endgroup$
            – Peter Mortensen
            3 hours ago





            $begingroup$
            That is "system" Hungarian notation (the Microsoft Windows documentation team grossly misinterpreted the original Hungarian notation), not the original Hungarian notation (which is not about types). See e.g. Triangulation episode 277, 4 min 00 secs to 5 min 19 secs.
            $endgroup$
            – Peter Mortensen
            3 hours ago














            2












            $begingroup$

            • It's fine to prefix member variables with an m, but it's probably best to avoid type prefixes (e.g. mtpNow). It makes code harder to read (you have to know what every abbreviation means), it's a pain to maintain (e.g. mtPause should probably be mtpPause to be consistent). Modern tools eliminate the need for this too (mousing over a variable in Visual Studio will tell me the exact type, not an approximation).


            • Functions defined inline in the class don't need to be declared inline.



            • The naming is very confusing:



              • Now() differs from the standard library (now() returns the current time, and is arguably still a terrible name). Functions names should be commands or questions. Perhaps Restart() or Reset() would be better.


              • Start() is also not ideal. One might expect the function to do what Now() does. I'd suggest calling it Unpause(), which makes the purpose clearer.


              • mtRestart is an odd name for the time spent paused.



            • We don't really need the Now() / Restart() function, since we can just assign a new timer to the old one to do the same thing (e.g. Timer timer; ...; timer = Timer(); // restarted!).


            • There's no reason to keep a vector in the class (we're copying it every time anyway, so we might as well just create a new vector each time).


            • We don't need a vector, since it always has 3 values, it would be neater to return a simple struct, which would allow us to give each value a name. Or...


            • The real solution is to just return an appropriate chrono:: type, and let the user worry about formatting / converting it.


            • I'd suggest naming the class Stopwatch, since that's more specific to the pausable timing functionality we need. We can actually implement this functionality based on a simpler, non-pausable Timer class.



            So overall I'd suggest something more like this (not tested properly):



            #include <chrono>

            template<class ClockT = std::chrono::high_resolution_clock>
            class Timer

            ClockT::time_point m_start;

            public:

            Timer():
            m_start(ClockT::now())




            ClockT::duration GetElapsedTime() const

            return ClockT::now() - m_start;

            ;

            template<class ClockT = std::chrono::high_resolution_clock>
            class Stopwatch

            bool m_paused;
            Timer<ClockT> m_timer;
            ClockT::duration m_timeAccumulated;

            public:

            explicit Stopwatch(bool paused = false):
            m_paused(paused),
            m_timer(),
            m_timeAccumulated(0)




            void Pause()

            m_timeAccumulated += m_timer.GetElapsedTime();
            m_paused = true;


            void Unpause()

            if (m_paused)

            m_timer = Timer<ClockT>();
            m_paused = false;



            ClockT::duration GetElapsedTime() const

            if (m_paused)
            return m_timeAccumulated;

            return m_timeAccumulated + m_timer.GetElapsedTime();

            ;

            #include <iostream>

            int main()

            using seconds_t = std::chrono::duration<float>;

            Stopwatch s;

            for (int i = 0; i != 50; ++i) std::cout << ".";
            std::cout << "n";

            std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

            s = Stopwatch(true);
            std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

            s.Unpause();

            for (int i = 0; i != 50; ++i) std::cout << ".";
            std::cout << "n";

            s.Pause();
            std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

            for (int i = 0; i != 50; ++i) std::cout << ".";
            std::cout << "n";

            std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;






            share|improve this answer









            $endgroup$



















              2












              $begingroup$

              • It's fine to prefix member variables with an m, but it's probably best to avoid type prefixes (e.g. mtpNow). It makes code harder to read (you have to know what every abbreviation means), it's a pain to maintain (e.g. mtPause should probably be mtpPause to be consistent). Modern tools eliminate the need for this too (mousing over a variable in Visual Studio will tell me the exact type, not an approximation).


              • Functions defined inline in the class don't need to be declared inline.



              • The naming is very confusing:



                • Now() differs from the standard library (now() returns the current time, and is arguably still a terrible name). Functions names should be commands or questions. Perhaps Restart() or Reset() would be better.


                • Start() is also not ideal. One might expect the function to do what Now() does. I'd suggest calling it Unpause(), which makes the purpose clearer.


                • mtRestart is an odd name for the time spent paused.



              • We don't really need the Now() / Restart() function, since we can just assign a new timer to the old one to do the same thing (e.g. Timer timer; ...; timer = Timer(); // restarted!).


              • There's no reason to keep a vector in the class (we're copying it every time anyway, so we might as well just create a new vector each time).


              • We don't need a vector, since it always has 3 values, it would be neater to return a simple struct, which would allow us to give each value a name. Or...


              • The real solution is to just return an appropriate chrono:: type, and let the user worry about formatting / converting it.


              • I'd suggest naming the class Stopwatch, since that's more specific to the pausable timing functionality we need. We can actually implement this functionality based on a simpler, non-pausable Timer class.



              So overall I'd suggest something more like this (not tested properly):



              #include <chrono>

              template<class ClockT = std::chrono::high_resolution_clock>
              class Timer

              ClockT::time_point m_start;

              public:

              Timer():
              m_start(ClockT::now())




              ClockT::duration GetElapsedTime() const

              return ClockT::now() - m_start;

              ;

              template<class ClockT = std::chrono::high_resolution_clock>
              class Stopwatch

              bool m_paused;
              Timer<ClockT> m_timer;
              ClockT::duration m_timeAccumulated;

              public:

              explicit Stopwatch(bool paused = false):
              m_paused(paused),
              m_timer(),
              m_timeAccumulated(0)




              void Pause()

              m_timeAccumulated += m_timer.GetElapsedTime();
              m_paused = true;


              void Unpause()

              if (m_paused)

              m_timer = Timer<ClockT>();
              m_paused = false;



              ClockT::duration GetElapsedTime() const

              if (m_paused)
              return m_timeAccumulated;

              return m_timeAccumulated + m_timer.GetElapsedTime();

              ;

              #include <iostream>

              int main()

              using seconds_t = std::chrono::duration<float>;

              Stopwatch s;

              for (int i = 0; i != 50; ++i) std::cout << ".";
              std::cout << "n";

              std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

              s = Stopwatch(true);
              std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

              s.Unpause();

              for (int i = 0; i != 50; ++i) std::cout << ".";
              std::cout << "n";

              s.Pause();
              std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

              for (int i = 0; i != 50; ++i) std::cout << ".";
              std::cout << "n";

              std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;






              share|improve this answer









              $endgroup$

















                2












                2








                2





                $begingroup$

                • It's fine to prefix member variables with an m, but it's probably best to avoid type prefixes (e.g. mtpNow). It makes code harder to read (you have to know what every abbreviation means), it's a pain to maintain (e.g. mtPause should probably be mtpPause to be consistent). Modern tools eliminate the need for this too (mousing over a variable in Visual Studio will tell me the exact type, not an approximation).


                • Functions defined inline in the class don't need to be declared inline.



                • The naming is very confusing:



                  • Now() differs from the standard library (now() returns the current time, and is arguably still a terrible name). Functions names should be commands or questions. Perhaps Restart() or Reset() would be better.


                  • Start() is also not ideal. One might expect the function to do what Now() does. I'd suggest calling it Unpause(), which makes the purpose clearer.


                  • mtRestart is an odd name for the time spent paused.



                • We don't really need the Now() / Restart() function, since we can just assign a new timer to the old one to do the same thing (e.g. Timer timer; ...; timer = Timer(); // restarted!).


                • There's no reason to keep a vector in the class (we're copying it every time anyway, so we might as well just create a new vector each time).


                • We don't need a vector, since it always has 3 values, it would be neater to return a simple struct, which would allow us to give each value a name. Or...


                • The real solution is to just return an appropriate chrono:: type, and let the user worry about formatting / converting it.


                • I'd suggest naming the class Stopwatch, since that's more specific to the pausable timing functionality we need. We can actually implement this functionality based on a simpler, non-pausable Timer class.



                So overall I'd suggest something more like this (not tested properly):



                #include <chrono>

                template<class ClockT = std::chrono::high_resolution_clock>
                class Timer

                ClockT::time_point m_start;

                public:

                Timer():
                m_start(ClockT::now())




                ClockT::duration GetElapsedTime() const

                return ClockT::now() - m_start;

                ;

                template<class ClockT = std::chrono::high_resolution_clock>
                class Stopwatch

                bool m_paused;
                Timer<ClockT> m_timer;
                ClockT::duration m_timeAccumulated;

                public:

                explicit Stopwatch(bool paused = false):
                m_paused(paused),
                m_timer(),
                m_timeAccumulated(0)




                void Pause()

                m_timeAccumulated += m_timer.GetElapsedTime();
                m_paused = true;


                void Unpause()

                if (m_paused)

                m_timer = Timer<ClockT>();
                m_paused = false;



                ClockT::duration GetElapsedTime() const

                if (m_paused)
                return m_timeAccumulated;

                return m_timeAccumulated + m_timer.GetElapsedTime();

                ;

                #include <iostream>

                int main()

                using seconds_t = std::chrono::duration<float>;

                Stopwatch s;

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                s = Stopwatch(true);
                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                s.Unpause();

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                s.Pause();
                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;






                share|improve this answer









                $endgroup$



                • It's fine to prefix member variables with an m, but it's probably best to avoid type prefixes (e.g. mtpNow). It makes code harder to read (you have to know what every abbreviation means), it's a pain to maintain (e.g. mtPause should probably be mtpPause to be consistent). Modern tools eliminate the need for this too (mousing over a variable in Visual Studio will tell me the exact type, not an approximation).


                • Functions defined inline in the class don't need to be declared inline.



                • The naming is very confusing:



                  • Now() differs from the standard library (now() returns the current time, and is arguably still a terrible name). Functions names should be commands or questions. Perhaps Restart() or Reset() would be better.


                  • Start() is also not ideal. One might expect the function to do what Now() does. I'd suggest calling it Unpause(), which makes the purpose clearer.


                  • mtRestart is an odd name for the time spent paused.



                • We don't really need the Now() / Restart() function, since we can just assign a new timer to the old one to do the same thing (e.g. Timer timer; ...; timer = Timer(); // restarted!).


                • There's no reason to keep a vector in the class (we're copying it every time anyway, so we might as well just create a new vector each time).


                • We don't need a vector, since it always has 3 values, it would be neater to return a simple struct, which would allow us to give each value a name. Or...


                • The real solution is to just return an appropriate chrono:: type, and let the user worry about formatting / converting it.


                • I'd suggest naming the class Stopwatch, since that's more specific to the pausable timing functionality we need. We can actually implement this functionality based on a simpler, non-pausable Timer class.



                So overall I'd suggest something more like this (not tested properly):



                #include <chrono>

                template<class ClockT = std::chrono::high_resolution_clock>
                class Timer

                ClockT::time_point m_start;

                public:

                Timer():
                m_start(ClockT::now())




                ClockT::duration GetElapsedTime() const

                return ClockT::now() - m_start;

                ;

                template<class ClockT = std::chrono::high_resolution_clock>
                class Stopwatch

                bool m_paused;
                Timer<ClockT> m_timer;
                ClockT::duration m_timeAccumulated;

                public:

                explicit Stopwatch(bool paused = false):
                m_paused(paused),
                m_timer(),
                m_timeAccumulated(0)




                void Pause()

                m_timeAccumulated += m_timer.GetElapsedTime();
                m_paused = true;


                void Unpause()

                if (m_paused)

                m_timer = Timer<ClockT>();
                m_paused = false;



                ClockT::duration GetElapsedTime() const

                if (m_paused)
                return m_timeAccumulated;

                return m_timeAccumulated + m_timer.GetElapsedTime();

                ;

                #include <iostream>

                int main()

                using seconds_t = std::chrono::duration<float>;

                Stopwatch s;

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                s = Stopwatch(true);
                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                s.Unpause();

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                s.Pause();
                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;

                for (int i = 0; i != 50; ++i) std::cout << ".";
                std::cout << "n";

                std::cout << std::chrono::duration_cast<seconds_t>(s.GetElapsedTime()).count() << std::endl;







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 15 hours ago









                user673679user673679

                4,7601 gold badge14 silver badges34 bronze badges




                4,7601 gold badge14 silver badges34 bronze badges























                    Mohit is a new contributor. Be nice, and check out our Code of Conduct.









                    draft saved

                    draft discarded


















                    Mohit is a new contributor. Be nice, and check out our Code of Conduct.












                    Mohit is a new contributor. Be nice, and check out our Code of Conduct.











                    Mohit is a new contributor. Be nice, and check out our Code of Conduct.














                    Thanks for contributing an answer to Code Review Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    Use MathJax to format equations. MathJax reference.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f225923%2fa-simple-stop-watch-which-i-want-to-extend%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

                    Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

                    199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單