Topical Information

This lab will help you practice with classes.

Program Information

From time to time in programming, it comes in handy to be able to determine how long it takes/took to perform a certain action(s). (See, for instance, the sort timing lab.)

You are to write a class which will allow an easy interface to the computer's timing facilities. When you first create a Timer object, it should be set to a 'stop' state. When the programmer wants to use it to time something, they can call the start() method before the 'something' executes and then call the stop() method afterward the 'something' finishes. To determine how long the 'something' took, they'll call the elapsed() method. This elapsed time will be reported in (whole) seconds.

Unfortunately, this describes extremely simple operation and may not suit all programmers' needs. To allow more general usage of the class, we'll also allow the programmer to start the timer at the object's declaration. We'll also allow the programmer to get the elapsed time whether the timer is still running or not. Finally, we'll provide an output() method so the programmer can directly print the currently elapsed time without having to retrieve it separately.

In addition, allow the programmer to subtract() and add() two Timer objects to receive a Timer object that is the difference/total of the original two Timers' currently elapsed times. (The resulting object should not be running.)

Then we have to boobie-proof the class. Make sure that things work correctly if the programmer tries to get/print the elapsed time of a Timer object which has never been started. Make sure nothing goes wrong if the programmer tries to stop a Timer object that isn't currently running.

We won't need a reset() method since the programmer can simply call start() again to start over...

It makes no sense to me, but people keep wanting to call the functions localtime and asctime from the standard C library ctime here. Just don't! They do nothing useful here! (And asctime leaves a mess behind you would probably forget to clean up even if you knew how!)

Finally, place your Timer class in a library and write a test application that makes sure it is working properly. The easiest way would be to print the current system time, start the Timer, and ask the tester to wait for a while before hitting Enter. Then, when they do hit Enter, stop the Timer and print both the Timer's elapsed seconds and the system time. Then the tester can check the elapsed time for themselves. Place this interaction in a yes/no loop so the tester can repeat the testing easily by simply saying 'yes' or 'no' to your question of whether or not to continue. (Of course, IGWOS that your loop should allow the tester to enter either y/n or the full words yes/no. But don't worry about them typing 'yellow' or 'Naugahyde' or whatever.)

Thought Provoking Questions

1. How many data members do you have? What data types are they? Where is this data type declared? (Don't forget to #include any standard libraries you need!)
2. How many constructors do you have? What is the purpose of each (i.e. in what situation would 'the programmer' use each; or in what situation would each be used by the compiler on behalf of the programmer)?
3. Is it okay that the mutators for the run state of the Timer are not named in the standard way? (i.e. They don't start with set_.)
4. Is it okay that the accessor for the elapsed seconds of the Timer is not named in the standard way? (i.e. It doesn't start with get_.)
5. Does your output() method print anything besides the elapsed seconds (even an endl)? Why should it not?
6. Does your add() method change the value of the calling object? Should it? (Hint: Does the compiler change x when you have 'x + y' in your program? What about y?) Does/Should your add() method change the other Timer object? Does this extend to subtraction(), too?
7. Why is an input method not a good/reasonable idea for the Timer class?
8. Why don't you have a mutator for the elapsed time?
9. The proposed driver/test 'app' doesn't really test all of your class' functionality, does it? Indicate specifically which methods are never tested and make suggestions to remedy these deficiencies. (Note: some methods will be explicitly tested and others will be implicitly tested. Be careful!) (Note: you need not correct the deficiencies in your program unless you choose the option below.)

This assignment is (Level 3).

Option(s)

• Add (Level 2) to properly apply inline'ing and const-ness to all of your class methods. (This includes proper use of initializer lists on constructors!)

  More Thought Provoking Questions

  1. Should any of your methods be inline'd for speed? Which ones will you inline? How does one do this for a class method?
  2. If you end up inline'ing all of your methods, do you still need an implementation file for your library? Why/Why not?
  3. Do the accessors, output, or math operation methods alter the calling object in any way? How do you specify such a situation to the compiler so it can better handle/enforce your decision?
  4. What needs to be in your constructor initializer lists? Is there a certain order to the list? Does it go on the prototype or the definition?

• Add (Level 2) to provide the tester with a menu of different testing methods (that is, means of testing — not class methods that do testing). One should be the above 'hit Enter' method. Others should focus on printing the system time, performing some action multiple times, and printing the elapsed and system times for verification.

  Note: this version will have a 'Quit' option in the menu instead of the yes/no loop.

  Note 2: options are to be choose-able by number or significant letter(s) — as all our menus have been.

  Note 3: when the tester is choosing by significant letter, they might actually type the whole word that significant letter begins.

  Note 4: you can use this opportunity to correct the testing omissions you found in the thought-provoking question above.

  Note 5: you'll receive additional (Levels) for each good alternative testing method after the second. (So you need to provide at least 3 testing methods and after that you get more credit depending on how good the tests are.)

Total Level Possible

If you did all above options, this lab could be worth as much as (Level 7+).