[LANG-315] StopWatch: suspend() acts as split(), if followed by stop()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0, 2.1, 2.2
• Fix Version/s: 2.3
• Assignee: Unassigned
• Reporter: Horst Gernhardt
• Created: 06/Feb/07 13:52
• Updated: 06/Feb/07 22:49
• Resolved: 06/Feb/07 22:49

Description

In my opinion, it is a bug that suspend() acts as split(), if followed by stop(); see below:

StopWatch sw = new StopWatch();

sw.start();
Thread.sleep(1000);
sw.suspend();
// Time 1 (ok)
System.out.println(sw.getTime());

Thread.sleep(2000);
// Time 1 (again, ok)
System.out.println(sw.getTime());

sw.resume();
Thread.sleep(3000);
sw.suspend();
// Time 2 (ok)
System.out.println(sw.getTime());

Thread.sleep(4000);
// Time 2 (again, ok)
System.out.println(sw.getTime());

Thread.sleep(5000);
sw.stop();
// Time 2 (should be, but is Time 3 => NOT ok)
System.out.println(sw.getTime());

suspend/resume is like a pause, where time counter doesn't continue. So a following stop()-call shouldn't increase the time counter, should it?